How this deployment handles Google user data.
This service is a private, self-hosted deployment run by one operator for their own Google accounts. It has no other users, no shared backend, and no central operator. The authors of the underlying open-source project receive no data from it.
When the operator connects a Google account, this service asks Google for permission to: read, compose and organise mail in Gmail; see, create and edit files in Google Drive (including Docs and Sheets); and see calendars and create or edit their events. Google shows the exact permissions on its own consent screen before anything is granted.
Although those permissions are broad, this service itself never sends email, never deletes or trashes mail, files or events, and never changes who a file or calendar is shared with. Those operations are refused in the service's code before any request reaches Google.
Data is fetched from Gmail, Drive or Calendar only in direct response to a request the operator makes in their AI assistant -- for example, searching a mailbox, opening a document, or listing next week's events. Results are returned to that assistant so it can answer. Nothing is fetched on a schedule, in the background, or for any purpose the operator did not ask for.
This service stores the OAuth refresh token for each connected account, plus that account's alias and email address, in an encrypted file on the operator's own server. That is the only persistent storage. Email, file and calendar content is never written to disk or to any database by this service -- it passes through memory to answer one request and is then discarded.
Data is sent only to the AI assistant the operator connected, at the moment they ask for it. It is not sold, rented, or shared with anyone else. It is not used for advertising, for building profiles, or to train any generalized artificial intelligence or machine learning model. There is no analytics, telemetry, or crash reporting in this service of any kind.
This application's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Operational logs record request timing, HTTP status codes, tool names, and account aliases so the operator can debug their own deployment. They never contain OAuth tokens, credentials, message bodies, subject lines, file names or content, event details, or sender and recipient addresses.
Disconnecting an account from this service's admin page deletes its stored token. The operator can also revoke this application's access to any Google Account at any time from Google Account permissions, which immediately and permanently ends this service's access to that account. Deleting the service's data folder destroys all stored data.
Because each deployment is independent and private, any change to this policy takes effect for that deployment when its operator updates and redeploys the service.