Google connections privacy
Effective 5 October 2026 · Developer: Edi Hasaj
Oktapod is a personal agent that runs on a computer you control. Connecting a Google app lets your agent help with that app. It does not give the developer automatic access to your Google account.
What your agent accesses
You choose which apps to connect and review Google's consent screen. Depending on the connection and permissions you grant, your agent can access Gmail messages and drafts, calendar events and availability, contacts, or Drive files, Google Docs, and Sheets. Basic Google profile information identifies the connected account. Your agent receives access tokens; it does not receive your Google password.
The granted permissions can permit both reads and changes. Oktapod's separate approval policy controls actions such as sending mail or editing an event. Review approvals and any standing authority you grant to your agent. Signing in does not itself send a message or create an event.
Use and sharing
Your agent uses selected Google data to carry out your requests and schedules, such as finding mail, preparing a reply, showing today's calendar, or working with a document. To answer a request, it sends the selected content and relevant context to the AI model you configured. It does not upload your whole mailbox, calendar, or Drive.
You choose where that model runs. With a local model, such as Ollama, LM Studio, llama.cpp, vLLM, or SGLang, your Google data never leaves hardware you control. With a hosted provider, the provider processes the content under its own terms.
Oktapod enforces this. It reads Google data only when every AI model your runtime uses is a local model,
an API account whose terms exclude training (OpenAI, Azure OpenAI, or an Anthropic API key), or an
account you have confirmed has model training turned off. If a ChatGPT or Claude subscription or another
hosted model is connected without that confirmation, Oktapod refuses to read Google data and tells you
why. Run oktapod models data-use to see which models qualify.
Mail and calendar items your agent keeps as background observations are stored on your runtime as restricted data. No model analyses them by default. That needs your explicit approval, for one specific model, and you can withdraw it at any time.
Limited Use
Oktapod's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used only to provide the features you use in Oktapod. The developer does not sell it, use it for advertising, or use it to train or improve a general AI model, and no person at Oktapod reads it unless you send it in a support request or the law requires it.
Storage and protection
Account credentials and the agent's conversations, memory, activity records, and files stay in the runtime's data folder. Credentials use files restricted to the runtime's operating-system account. The operator controls machine security, disk encryption, backups, access, and connected model providers.
With your own Google OAuth client, your runtime exchanges and refreshes tokens directly with Google. Hosted sign-in uses Oktapod's sign-in service to handle the exchange and refresh. Its token broker encrypts the handoff for your installation. A callback relay routes the authorization response to the runtime; it does not read Gmail messages, calendar events, contacts, or documents.
Retention and deletion
Your runtime retains conversation and action records for their configured retention periods. Memory has retention classes; items you deliberately save can remain until you delete them. Scheduled tasks and approved observation features can retain selected source content and derived summaries. Those features have their own controls; connecting an account does not authorize every observation or model disclosure.
Disconnect the app in your agent's Connections settings and revoke Oktapod in your Google account connections to stop further access. Revocation does not remove earlier conversations, memory, imported files, or backups. Delete those copies on your runtime and remove backups you no longer need. Deleting an agent copy does not delete the original message, event, or document in Google, or recall data already sent to a configured provider.
Developer-held data and support
The developer does not automatically receive your conversations or Google content. Optional diagnostics and information you deliberately include in a support request are separate. See the mobile privacy pages for the phone controls. Runtime monitoring remains disabled unless its operator explicitly enables it and configures a destination.
For questions or deletion of information you sent to the developer, contact support@oktapod.ai. For data on a runtime operated by someone else, contact that operator. Google's Workspace user data policy describes the additional rules for Gmail, Calendar, Contacts, and Drive data.