Privacy Policy
How Personal Workspace Connector accesses, uses, stores and shares Google user data.
Effective 15 September 2026 · Last updated 15 September 2026
1. Who this policy covers
This policy applies to Personal Workspace Connector (“the application”), a self-hosted application operated by a single private individual (“the operator”) on their own computer, together with the Google Cloud project and OAuth client that support it.
The application is a personal-use tool. It has no user accounts, no sign-up, no customers and no public distribution. The only Google accounts it connects to are accounts the operator personally controls or has been directly authorised to access. Every reference below to “you” or “the user” means the person who signs in at Google's consent screen and grants the application access to their own account.
In short. The application runs on one person's computer and calls Google's APIs directly. There is no server, no database and no company behind it. Google user data is not collected, not stored remotely, not sold, not used for advertising, not used to train any model, and not shared with anyone — with one exception, disclosed in full in section 6: the content you explicitly ask your local AI assistant to work with is transmitted to that assistant's provider, because that is how the assistant processes your request.
2. What Google user data the application accesses
The application accesses Google user data only through Google's official APIs, and only within the OAuth scopes you approve on Google's consent screen when you connect an account. It requests no other data.
Depending on which capabilities the operator has enabled in their installation, the application may request the following scopes. The authoritative list for your account is always the one Google shows you on the consent screen at the moment you grant access, and the list you can inspect at any time under your Google Account's connections settings.
| Google service | Scopes that may be requested | What it is used for |
|---|---|---|
| Account identity | openid, userinfo.email, userinfo.profile |
To confirm which account a given local server is connected to, so that mailboxes are not mixed up. |
| Gmail | gmail.readonly, gmail.send, gmail.compose, gmail.modify, gmail.labels, gmail.settings.basic |
To read and search messages, create drafts, send messages, and apply or remove labels, when the operator asks for it. |
| Google Calendar | calendar, calendar.readonly, calendar.events |
To list calendars, read events, and create or modify events, when the operator asks for it. |
| Google Drive | drive, drive.readonly, drive.file |
To find, read and create files, when the operator asks for it. |
| Docs, Sheets, Slides, Forms, Tasks, Chat, Contacts | documents, spreadsheets, presentations, forms.body, tasks, chat.messages, contacts and their .readonly variants |
To read and edit the corresponding items, only if the operator has enabled those tools in the installation. |
Several of these are classified by Google as sensitive or restricted scopes, in particular the Gmail scopes. They are requested because the application's purpose is to let its operator work with their own mailbox — reading it is not sufficient if the operator also wants to draft replies or file messages. An operator who only needs to read and search can run the application in read-only mode, which limits the request accordingly.
3. What the data is used for
Google user data is used for exactly one purpose: to carry out, in real time, the specific instruction the operator has just given. If the operator asks to see the last messages in a mailbox, the application calls the Gmail API and returns those messages. If nothing is asked, nothing is fetched.
Google user data is not used to:
- serve, target, personalise or measure advertising of any kind;
- build profiles, audiences, scores or any derived dataset;
- train, fine-tune or evaluate any machine-learning model operated by the developer;
- produce analytics, telemetry, usage statistics or crash reports;
- generate revenue, directly or indirectly. The application is not monetised in any way.
4. Limited Use commitment
Personal Workspace Connector's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Concretely, and in the terms of that policy:
- data obtained through Google APIs is used only to provide or improve the user-facing features described on the home page, and is not transferred or sold for any other purpose;
- data is not transferred to third parties except as strictly necessary to provide those features to the user, to comply with applicable law, or as part of the user's own explicit request;
- data is not used, and will not be used, for serving advertisements, including retargeting or personalised advertising;
- no human reads the data, other than the operator themselves reading their own data through the application. The developer and the operator are the same individual, and there is no support team, contractor or reviewer with access.
Google user data is also not used to develop, improve or train generalised or non-personalised artificial-intelligence or machine-learning models by the operator.
5. How and where data is stored
The application has no backend infrastructure. There is no server, database, object store, queue or log aggregator operated by the developer, and no cloud account where Google user data is deposited.
- Message and file content is not stored. It is fetched from Google's API when requested, passed to the requesting assistant, and discarded. The application keeps no copy, index, cache or archive of it.
- OAuth tokens are stored locally. The access token and refresh token issued by Google are written to a directory on the operator's own computer, one directory per connected account. They never leave that machine except to be presented back to Google when refreshing access.
- Credentials are local. The OAuth client ID and client secret live in the local configuration file on the operator's computer.
- The computer running the application is protected by full-disk encryption and the operating system's standard account protections.
This website itself is a set of static pages hosted on GitHub Pages. It sets no cookies, runs no scripts, embeds no third-party fonts or trackers, and performs no analytics. GitHub, as the host, may process standard server request data such as IP addresses in accordance with the GitHub Privacy Statement. No Google user data is ever sent to this website.
6. Who the data is disclosed to
Google user data is not sold, rented, licensed, published or shared with any third party for their own purposes. There are exactly two parties that receive it, and both do so because they are necessary to perform the operator's request:
- Google, which is the source of the data and receives the API calls that retrieve or modify it.
- The AI assistant application the operator is using locally, and its provider. This is the disclosure that matters most, and it is inherent to what the tool does: when the operator asks their assistant to read, summarise or reply to a message, the content of that message becomes part of the conversation with the assistant, and is therefore transmitted to and processed by the assistant's provider under that provider's own privacy terms. The application does not control, and cannot limit, what the provider does with the content of the conversation. Data reaches the assistant only in response to an explicit instruction from the operator; nothing is streamed or synchronised in the background.
Data may additionally be disclosed where required by a valid legal obligation. Given the personal, single-operator nature of the application, no such disclosure has been made or is anticipated.
7. Retention and deletion
Because content is never stored, there is no retention period to apply to it: it exists only for the duration of the request that fetched it.
OAuth tokens are retained until they expire, are revoked, or are deleted. To erase them, the operator deletes the local credentials directory for the account concerned; access ends immediately. Revoking access at Google (section 8) invalidates the tokens regardless of whether the local copy is removed.
8. Your control over access
Access is granted by you, at Google's consent screen, and can be withdrawn by you at any time and without involving the operator:
- go to myaccount.google.com/connections;
- select Personal Workspace Connector;
- choose to remove its access.
From that moment the application can no longer reach the account, and any token held locally stops working. Because no content was retained, nothing remains to be deleted on the application's side.
9. Security
The application runs locally and communicates with Google over TLS. The OAuth flow uses PKCE and single-use authorisation codes. Tokens and the client secret are treated as credentials: they are not committed to version control, not shared, and rotated if exposure is suspected.
Two limitations are stated plainly rather than glossed over. First, anyone with access to the operator's unlocked computer could reach the locally stored tokens; the security of the data therefore rests on the security of that machine. Second, content retrieved from a mailbox may itself contain text crafted to influence an AI assistant that reads it. The operator is aware of this class of risk and configures the application's write permissions accordingly.
10. Legal basis and jurisdiction
The application processes data belonging to its own operator, in the course of a purely personal activity. Where the General Data Protection Regulation (EU) 2016/679 is nonetheless considered applicable, the legal basis for processing is the consent of the data subject, given through Google's consent screen and revocable at any time as described in section 8.
11. Children
The application is not directed at children, is not made available to anyone other than its operator, and does not knowingly process the data of anyone under the age of 16.
12. Changes to this policy
If the application's data handling changes — for instance if additional Google APIs are enabled — this policy is updated before the change takes effect, and the “last updated” date above is revised. The full revision history of this page is public in the repository's commit history.
13. Contact
Questions about this policy, or about how the application handles data, can be raised publicly at github.com/fed3c3sa/fed3c3sa.github.io/issues. This is the contact channel for an application whose entire user base is one person; requests are answered there.