How Google user data is handled

G9 AIOS Agent · Updated 7 October 2026

This page sets out the technical controls behind the Privacy Policy. It is written for a reader who wants the mechanism, not the summary.

Least privilege, enforced

The Agent requests the narrowest Google scopes its features require. It does not hold access "for later". Two capabilities are withheld at the tool layer, where a scope alone could not withhold them:

AreaGrantedWithheld
Drive / Docs / SheetsRead, create, organise the user's own files Anything outside the authorising user's own account
CalendarRead and create eventsCalendars the user does not own
GmailRead and draft Sending — disabled at the tool layer, not merely unrequested
YouTubeRead and manage playlists Deleting playlists, removing items — disabled
IdentityEmail address, display name Used only to bind an action to the right account

Where data lives

On the owner's own privately operated server, on the owner's own premises — not on a commercial multi-tenant platform. OAuth credentials are stored as files readable only by the account the Agent runs under.

In transit

All communication with Google APIs, and with every third-party AI model the Agent calls, uses HTTPS.

Third-party AI models

The Agent calls third-party AI models to produce its responses, including Google's own AI services (the Gemini API). Every such model is reached through a paid API tier configured to opt out of training-data collection. Provider handling of API data is governed by each provider's own API terms.

The Agent includes a PII sanitizer, enabled at all times during normal operation. It is switched off only during maintenance work; while it is off, access to Google user data is restricted or suspended, so that unsanitised content is not transmitted to any third-party model. That control is applied on a best-effort basis. Where the Agent produces a written deliverable for an outside party, sensitive identifiers are redacted before transmission.

Human access

No person reads Google user data in the course of normal operation. Data is inspected only on the user's own request, or where necessary to diagnose a fault or investigate abuse.

No secondary use

Google user data is not sold, not rented, not used for advertising or profiling, and not used to train AI models. It is transferred only to the AI model providers described above, and only to produce the output the user asked for.

Revocation and deletion

Access may be revoked at myaccount.google.com/permissions, effective immediately. The Agent's locally stored copies are deleted on request. Data held inside the user's own Google Account remains under that user's control through Google.

Contact

mrmosh@gmail.com