Connected services (Google)

IsonAI can connect to your Google account — Google Calendar, Gmail, and Google Drive — so chat can answer with your personal context: today's schedule, a summary of recent email, or finding a file in Drive. The connection is entirely optional and requires your explicit consent.

Connecting and disconnecting

• Connecting: open Settings in chat → the connected-services section → connect Google. The official Google sign-in window opens; you review the requested permissions and approve them on Google's side.
• Disconnecting: from the same place, disconnect at any time. On disconnect, IsonAI revokes the token with Google and deletes the stored credentials from IsonAI's systems. You can also revoke access from Google's side at myaccount.google.com/permissions.
• Deleting your IsonAI account also deletes connected-service authorizations.

Currently active capabilities

Chat uses the Google connection for read capabilities:

In Naya, these write actions are available after an exact preview and explicit approval for each action:

Regular chat does not execute write actions and directs such requests to Naya. Payments, signatures, official submissions, Drive permission sharing, attachments, and unlisted actions are not executed.

Data flow — what is sent where

• When your question needs Google context, IsonAI calls Google's APIs on your behalf and receives the relevant slices of data (event lists, email snippets, file lists).
• That data is used at that moment to compose the answer — IsonAI does not copy your Calendar/Gmail/Drive contents into separate storage.
• However: connector information that appears inside an answer is saved as part of the conversation, like any other message content, and is subject to the same privacy policy.
• Toward Google, standard API requests with your token are sent — including search terms derived from your request (for example the file name in "find proposal.docx in my drive"). Beyond that, the contents of your conversations are not sent to Google.
• For a Naya action, only fields shown in the preview (such as recipient, subject, body, or event time) are sent to Google's API after approval. A compact result is saved with the mission for audit; the Google token is never put in the mission.

Token storage

After you approve, Google issues access tokens that are stored on IsonAI's servers (EPITHRE. infrastructure in Indonesia) so the connection does not have to be repeated every time. Tokens are deleted when you disconnect or delete your account, and are revoked with Google on disconnect.

Consent boundaries

• Connection only happens through the official Google sign-in flow that you approve yourself.
• IsonAI does not read connected services "quietly" for background personalization — data is fetched when your question needs it.
• Naya writes cannot run without per-action approval, which expires after 24 hours. A target from web or document content cannot silently become an action recipient or object ID.
• Double clicks are blocked. If a Gmail send has an uncertain outcome after a connection loss, Naya asks you to check Sent and does not automatically retry.

MCP connectors

Pro and admin accounts can opt into reviewed MCP connectors from Settings → Connections. The initial release provides Ison Search Indonesia, an internal read-only connector for Indonesian sources. Arbitrary server URLs, write connectors, stdio, and connectors outside the catalog are rejected. Schemas reach the model only on relevant turns, results are capped and treated as untrusted data, and a connector can be disconnected at any time.

Limits

• Connecting and disconnecting is done via the web — the iOS app does not yet have its own connection page. Once connected, Google-context answers apply from any device, including the iOS app.
• Answer quality depends on what can be read from your Google account (e.g. your own labels and folders).

Related

• Tools & agentic behavior
• Memory & personalization
• Privacy & data

Last verified: 2026-08-22