Privacy Policy
Most privacy policies explain what a company does with the data it collects. This one mostly explains why we do not have any.
Last updated 4 September 2026
The short version. The AIOS is software that runs on your own computer. When you connect Google Workspace, your calendar, mail and files travel from Google directly to your machine. They do not pass through any server we run, because we do not run one. We cannot read your data, and no change to this policy could give us that ability without changing the software itself — which is open source, so you would be able to see it.
One caveat belongs up here rather than buried: the AIOS ships an optional script that can call a model from another vendor. It stays inert until you create an API key file yourself, and it still sends us nothing — but once enabled it does send your content to that vendor. Details below.
Why we cannot see your data, mechanically
This is worth explaining precisely rather than asking you to take it on trust, because the mechanism is the actual guarantee.
The AIOS connects to Google using an installed-application OAuth client whose only redirect address is http://localhost — an address that means this computer. When you approve access, Google sends the authorization code to a small server running on your own machine, which exchanges it for a token and writes that token to your own disk, at ~/.google_workspace_mcp/credentials/.
There is no step in that sequence where your content reaches us. Our Google Cloud project supplies the app’s identity — the name and logo you see on the consent screen — and nothing else. It is a nameplate, not a pipe.
What we can see, stated honestly
Because the OAuth client belongs to our Google Cloud project, Google shows us aggregate API metrics for that project: how many requests were made to each Google API and how many failed. That is a count, not content. We cannot see who made them, from which account, or what they contained. We mention it because a policy claiming absolutely no visibility would be slightly untrue, and a policy you catch being slightly untrue is worth nothing.
Where your information actually lives
- Your vault — notes, context, daily plans — is a folder on your computer, and a private repository you own. We have no access to it and are not a party to it.
- Your Google tokens sit on your disk in your home directory. Deleting that folder revokes the AIOS’s access on that machine immediately.
- Your conversations with Claude are between you and Anthropic, under their terms. The AIOS is a set of instructions and tools that runs inside Claude Code; it is not an intermediary and does not receive a copy.
The one component that can send data off your machine
Everything above describes the AIOS as you install it. There is exactly one part that can behave differently, and we would rather name it here than have you find it.
The AIOS ships a script that calls a model from a different vendor — OpenRouter, or Google’s Gemini API. It exists for two narrow jobs: a cheaper lane for bulk text work, and an independent second opinion. The second job is the interesting one. A model cannot dock points for a habit it shares, so asking Claude to grade Claude’s own writing quietly misses whatever the two have in common. Crossing to another vendor is the fix.
It is switched off until you switch it on. The script looks for an API key in a file you create yourself. With no key present it makes no network call at all — it stops and prints the path you would need to create. An operator who never wants this has a dormant script on disk and nothing else. There is no default, no prompt, and no quiet fallback.
If you do turn it on, be clear about the trade you are making: whatever you pass that script travels to that vendor and is governed by their policy, not ours. It still never reaches us — we have no server in that path any more than in the Google one. But “not us” is a smaller promise than “nowhere,” and the difference matters.
Our guidance, which also ships in the documentation: pass it drafts and prose. Keep client material, anything under an NDA, financial records and personal context on your own machine. Before reaching for it at all, check whether a smaller Claude model or a plain deterministic script does the job — most of the time one of them does, and then nothing leaves at all.
The full boundary, including why we refuse to support proxies that reroute Claude Code itself, is in MODEL-ROUTING.md in the open-source repository.
What we collect
From the software: nothing. The AIOS contains no analytics, no telemetry, no phone-home, no crash reporting and no usage tracking. It does not send us a message when you install it, run it, or stop using it. We learn that someone is using it when they tell us.
From this website: standard web-server request logs held by our hosting provider, and nothing we have added on top.
If you contact us by email or open an issue on GitHub, we obviously have what you sent us. GitHub issues are public by design — please do not paste credentials or private content into one.
Google user data, specifically
The AIOS’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Google data is requested so the software can do the thing you asked it to do — read your real calendar when you ask for a plan for the day, draft into your own documents, find a file you referred to. It is used on your machine, in the session where you asked for it. It is not transmitted to us, not sold, not shared, not used for advertising, and not used to train any model by us.
Removing access
Any of these ends it, and none of them require us:
- Revoke access at myaccount.google.com/permissions — this is Google’s own control and it is the authoritative one.
- Delete
~/.google_workspace_mcp/credentials/on your machine. - Remove the connector entirely:
claude mcp remove google-workspace.
Because we hold nothing, there is no deletion request to send us and no waiting period. If you would like confirmation of that in writing anyway, ask and we will send it.
Children
The AIOS is a developer and professional tool. It is not directed at children under 13 and we do not knowingly collect information from them — a claim made easy by the fact that we do not knowingly collect information from anyone.
Changes to this policy
If this policy changes, the date at the top changes with it, and the change is visible in the public git history of this website. A policy that can be edited silently is not much of a commitment; ours cannot be.
Contact
Questions, or anything here that reads as untrue: hello@the-aios.com, or open an issue at github.com/The-AIOS/aios.