← Octuo legal index

Octuo How Octuo uses Google user data

Last updated: 2026-11-19

How Octuo uses Google user data

Connecting a Google service is optional. This page applies whenever Google user data is accessed through Google APIs on your behalf, by Octuo or through a service provider listed on our Sub-processors page. This page describes available connections, what Octuo does with the information and how to remove access or data. The Privacy Policy governs all Google user data and takes priority over this explanation. Connections are available only where Octuo offers them; a permission is not a promise that every action it permits is implemented.

1. Permissions and actual access

Signing in with Google identifies you; it does not connect your mail or calendar. The production app requests exactly three Google permissions today: gmail.modify, openid and email. The authorization screens for your connection show the permissions requested. Octuo accesses only what the permissions you grant allow, for the connected service and your requested tasks.

Permission What it allows and what Octuo currently uses
openid, email Identify the Google account associated with a connection.
https://www.googleapis.com/auth/gmail.modify Read and modify mail, compose and send it. Depending on the connection and requested task, retrieved information can include message content and message/thread metadata: sender, recipients, subject, dates, message identifiers, labels, authentication/unsubscribe headers and short snippets. It can create/update drafts, send drafts or replies, organize mail and move it to Spam or Trash; it does not permanently delete mail.

2. Actions you request

Octuo calls the connected service for requests you make directly or through tasks you schedule. Sending mail or a reply is presented for approval first. Drafting, labeling, archiving, marking, moving mail to Spam or Trash and unsubscribing can run on your request without another approval. Editing a draft replaces its previous content. Content and attachments you provide for an outgoing message are sent through your account to the recipients you approve.

Unsubscribing can send an unsubscribe email from your account or make a sender's one-click unsubscribe request when supported and permitted by the sender checks. The sender then learns that your address unsubscribed. In cases Octuo cannot handle automatically, you must use the sender's unsubscribe link yourself.

3. Processing, recipients and storage

Octuo uses Google data only to provide or improve the visible, user-facing assistance you asked for and to operate and secure it. Hosting providers store it. AI providers process retrieved information and relevant context to answer you, summarize, retry or help with a task. More than your selected model may be involved. With your AI-sharing permission, background reviews of recent conversations and memories can also process information already saved from a connection to organize it or suggest next steps.

Octuo can save facts from retrieved information to memory when asked or on its own judgment. Messages, replies and saved facts are also sent for AI processing into searchable representations; raw tool results are not themselves indexed as conversation messages, but replies can restate them. Later conversations, memory processing and background reviews can use this saved information again. See Sub-processors for current recipients and transfer safeguards.

Other recipients include people you communicate with and services or tools used for your requested task, subject to your permissions and Limited Use. Google data is not used for advertising or advertising measurement, sold to data brokers, used for creditworthiness or lending, or used or transferred to develop, improve or train generalized AI/ML models. Providers are not permitted to use it for those purposes.

Connected-account credentials are stored encrypted on our servers and used only to act on your request. Operational records can contain retrieved data, request context or error-text fragments. Normal operation does not require staff to read your Google data; the four human-access exceptions are in section 6.

4. Disconnect and revoke access

Disconnect the Google connection in Octuo's connection settings, or open Google Account connections, select the relevant authorization for Octuo or the service provider and remove its access.

Disconnecting in Octuo stops new access through that connection and removes its active credentials. Where a connection supports revocation, Octuo requests it; an encrypted credential copy can remain while revocation is retried. Related connections may also be disconnected. You can separately remove the relevant authorization in your Google account or the service provider’s settings. Removing access at Google prevents continued access with that authorization.

Disconnecting does not erase saved conversations, memories, summaries or background records. Withdrawing AI-sharing permission stops processing that requires it; it does not erase existing copies or undo actions already completed.

5. Delete saved data and understand retention

  • Conversations: use the conversation deletion control. Associated search/context records and linked internal request copies are removed with it. If the deletion dialog offers to delete memories recorded as coming from that conversation, select that option too. Other memories and profile information can remain until account erasure. You cannot currently erase a single memory separately. Asking Octuo to forget withdraws a memory from new-conversation recall and searches, but does not erase its text; direct lookups, existing context, source conversations and summaries can still expose the information.
  • Archives and background records: clearing a view or archiving is not deletion. Background-review records can restate connected data and remain until account erasure; you cannot separately list or delete them.
  • Account: request deletion in the app or email privacy@tutuo.ai from your account address. Once recorded, the account closes immediately and account content, connections, tokens and memories are erased from live systems within 30 days, subject to legally required preservation and to the operational copies and backups described below. When you ask us to delete your account, we disconnect your Google connection, delete our copy of its tokens and ask Google to revoke Octuo's access; you can also remove Octuo's access yourself in your Google Account at any time. Billing and other required records are retained as the Privacy Policy describes.

Operational copies follow their own schedules: internal tool/model event records are normally removed after about 90 days; diagnostic request copies normally after about 14 days, which engineers can extend during an investigation; server logs are normally removed within about 90 days. Server logs can contain fragments of content; their entries are not edited when you delete a conversation or your account, and they expire on that schedule. Conversation-linked copies can be removed sooner with the conversation; unlinked logs need not be. Background-review records remain until account erasure. For a pending action, its preview and encrypted copy are removed when it is approved, declined or expires; an outcome record without the message normally remains about 30 days afterward.

Backups rotate separately, normally expiring about 35 days after creation; individual records are not removed from an existing backup. Periodic deletion jobs and provider processing can cause delays beyond nominal retention periods. Deleting in Octuo does not itself delete copies already held by communication recipients or send deletion requests to every AI provider. Contact privacy@tutuo.ai to exercise your rights; the Privacy Policy explains them and these limits.

6. Limited Use and human access

Octuo'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. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

Transfers are allowed only with your consent to provide or improve visible, user-facing features; for necessary security purposes; to comply with law; or in a merger, acquisition or sale of assets with your explicit prior consent. Other transfers are prohibited. These rules cover derived data and our employees, agents, contractors and successors.

Humans may read Google data only:

  • With your documented affirmative agreement to view specific data.
  • When necessary for security, such as investigating abuse.
  • When necessary to comply with law.
  • When the data, including derivations, is aggregated and anonymized for internal operations as permitted by law.

New data types or uses not previously disclosed require updated disclosures and privacy policy, notice and the consent Google requires before access or use begins.

7. Contact

Data questions and rights: privacy@tutuo.ai. Help using Octuo: support@tutuo.ai. This living page is updated in place as connection details change.