What this policy covers
This policy describes how MCP Personal (the “app”) handles data obtained from Google APIs.
The app is a personal, single-user tool. It is operated by one person for his own Google account. It is not a product, it is not distributed, it is not offered for sale, and it has no users other than its operator.
Scope limitation. This policy applies only to the app described here. It does not cover Reylix Inc.’s consulting engagements or client work, and it does not describe data handling for any other Reylix service. For how the reylix.io website itself treats visitors, see The reylix.io website below.
Who operates the app
- Operator and data controller: Justin Carter, Reylix Inc., Ontario, Canada
- Contact: [email protected]
- Google Cloud project:
claude-mcp-personal-507410 - OAuth client type: Desktop app, redirecting to
http://localhost:8000
What the app is
MCP Personal is an MCP (Model Context Protocol) server — a build of the open-source google_workspace_mcp project. It runs locally on the operator’s MacBook under macOS.
It is not a hosted service. There is no server, no backend, no database, and no cloud infrastructure operated by Reylix Inc. in connection with this app. Nothing runs unless the operator starts it on his own machine.
Its purpose is to let the operator’s AI assistant — Claude, made by Anthropic — read and act on the operator’s own Google account data, on his explicit instruction.
What data the app accesses
The app requests the Google OAuth scopes listed below. Several of these are classified by Google as sensitive or restricted scopes. They are requested so the assistant can work across the operator’s own Workspace data in a single session rather than being limited to read-only summaries.
| Service | Scopes requested | Why |
|---|---|---|
| Gmail | gmail.readonlygmail.modifygmail.sendgmail.composegmail.labelsgmail.settings.basic |
Read, search, draft, send and label the operator’s own mail; read basic mailbox settings. |
| Drive | drivedrive.readonlydrive.file |
Locate, read, create and organise the operator’s own files. |
| Calendar | calendarcalendar.eventscalendar.readonly |
Read the operator’s schedule and create or amend his own events. |
| Docs | documentsdocuments.readonly |
Read and edit the operator’s own documents. |
| Sheets | spreadsheetsspreadsheets.readonly |
Read and update the operator’s own spreadsheets. |
| Slides | presentationspresentations.readonly |
Read and edit the operator’s own presentations. |
| Forms | forms.bodyforms.body.readonlyforms.responses.readonly |
Read and edit the operator’s own forms and review their responses. |
| Tasks | taskstasks.readonly |
Read and maintain the operator’s own task lists. |
| Contacts | contactscontacts.readonly |
Resolve names to email addresses when addressing mail or invitations. |
| Identity | openiduserinfo.emailuserinfo.profile |
Confirm which Google account is connected, so tokens are filed against the right account. |
The app accesses only the operator’s own Google account. It does not access anyone else’s account, and no other person can authorise it.
How data flows
Credentials are stored locally
OAuth tokens are written to the operator’s machine at ~/.google_workspace_mcp/credentials/, one JSON file per connected Google account. Each file contains an access token, a refresh token, the granted scopes, an expiry timestamp, and the OAuth client identifier and secret.
These files are stored unencrypted. They are plain JSON on local disk, protected only by macOS file permissions restricting them to the operator’s user account, plus whatever full-disk encryption the operating system provides. They are never transmitted anywhere — not to Reylix Inc., not to Anthropic, not to any other party.
Google data is fetched on demand
The app retrieves Google user data only at the moment the operator issues an instruction that requires it. Nothing is bulk-synchronised, crawled, indexed, mirrored, or warehoused. There is no background job and no copy of the operator’s mailbox, Drive or calendar held anywhere by this app.
Retrieved content is sent to Anthropic
When the operator asks the assistant to do something with his Google data, the content retrieved from Google is transmitted to Anthropic, PBC as part of the AI request that acts on it. This is inherent to how the tool works: the assistant cannot summarise an email or edit a document without receiving its contents.
Anthropic is therefore a third-party processor of this data. Anthropic’s handling is governed by its own terms and privacy policy, available at anthropic.com/legal/privacy.
Data is transmitted to Anthropic solely to generate the response to the operator’s immediate request. Model-training and model-improvement settings are kept disabled on the Anthropic account used with this tool, so this content is not used to train or improve Anthropic’s models.
No other third party receives data from this app.
Google Limited Use disclosure
MCP Personal’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.
The use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
In practice, this means the app does not:
- Use Google user data for advertising of any kind, including retargeting, personalised or interest-based advertising.
- Sell or transfer Google user data to data brokers, information resellers, advertising platforms, or any other party, other than the transmission to Anthropic described above, which exists solely to deliver the user-facing feature the operator requested.
- Use, transfer or retain Google user data to create, train or improve any generalised artificial intelligence or machine learning model.
- Permit human review of Google user data. The operator is the sole user and reads only his own data. No employee, contractor or third party of Reylix Inc. reads data obtained through this app.
Retention and deletion
- Google content is held only in memory for the duration of the request that needed it. The app keeps no persistent copy.
- OAuth tokens persist on the operator’s local disk until deleted. Deleting the files in
~/.google_workspace_mcp/credentials/destroys the stored credentials permanently. - Anthropic’s retention of request content is governed by Anthropic’s own policies, not by this app.
Revoking access
Access granted to this app can be withdrawn at any time from the Google Account permissions page:
https://myaccount.google.com/permissions
Revoking there invalidates the stored refresh token immediately. Deleting the local credential files removes the app’s stored copy as well.
Security
Stated honestly, without overclaiming: the app runs on a single personal laptop and relies on the security of that machine and its user account. Tokens are stored unencrypted on disk, as described above. Traffic to Google and Anthropic uses HTTPS.
Reylix Inc. makes no certification claims in connection with this app. It has not been assessed against SOC 2, ISO 27001, or any similar framework, and no such claim should be inferred.
The reylix.io website
This policy is published on reylix.io, which is a static marketing site hosted on Cloudflare Pages. To be clear about the distinction:
- The website runs no analytics, no tracking scripts, no advertising pixels and no cookies of its own, and collects no form submissions.
- Cloudflare, as the hosting provider, processes standard server request data such as IP addresses in the ordinary course of serving and protecting the site.
- The website and the app are separate. Visiting reylix.io grants no access to any Google account, and the app collects nothing about website visitors.
Children
The app is a personal tool used by an adult. It is not directed at children and is not made available to them.
Changes to this policy
If the app’s data handling changes — for example if scopes are added or a different AI provider is used — this policy will be updated and the “last updated” date at the top revised accordingly.
Contact
Questions about this policy: [email protected]
Justin Carter
Reylix Inc.
Ontario, Canada
See also the Terms of Service.