Privacy notice draft for legal review.

This page organizes the topics a future privacy notice should address. It does not identify a legal entity, jurisdiction, retention period, or legal basis because those facts have not been approved for publication.

• Treat this text as a drafting checklist.
• Do not rely on it as a final privacy notice.
• Keep it out of search indexing until legal review is complete.

When a workspace owner or admin connects Google Sheets, Operade requests the Google `drive.file` scope and accesses only files the workspace explicitly selects or grants to the app. Operade uses the selected spreadsheet, tab, fixed range, headers, and column mapping to search rows or add one row. A read may send bounded selected cell results to the configured AI model. Those results may appear in agent responses and conversation history visible to authorized workspace members. Spreadsheet cells are treated as untrusted input, and the model is instructed not to follow instructions found in cells.

• OAuth access and refresh tokens are encrypted at rest and scoped to the workspace connection.
• Tokens, Google Sheets Tool configuration, internal provider and resource identifiers, and raw Activity payload remain protected; authorized members may see bounded results in responses and history plus a safe Activity summary.
• V1 supports My Drive files and does not support Shared Drive files.

Operade uses Google data to perform the Tool action configured by the workspace, show safe operational status, and retain conversation records needed for review. Requests necessarily pass through Google as the connected service provider, and selected read results may pass through the configured AI model provider. Operade does not describe either relationship here as a sale of data. Final retention periods, deletion commitments, subprocessors, cross-border disclosures, and legal bases remain subject to verified operating facts and legal review.

• Token material is stored separately from customer-visible Tool configuration.
• Conversation history can contain bounded spreadsheet results returned to an Agent.
• Support reports must omit account, file, range, query, cell, token, and provider-response values.

A workspace owner or admin can revoke a Google connection from Settings. Revocation destroys Operade's stored access and refresh tokens and stops future Google Sheets actions through that connection. Revoke does not delete existing Tools, immutable Agent versions, Google data already stored in conversation history, or records that another approved retention process still covers. Final wording must explain user request paths, the responsible contact, verified deletion behavior, and any lawful limits.

• Reconnect uses the same Google account in V1.
• Selecting a different Google identity as a replacement is not supported in V1.
• Deleting or retaining prior records requires the approved product and legal process, not an OAuth reconnect.

Before indexing or treating this page as a notice, legal review must confirm the legal entity, jurisdiction, Google API policy wording, service-provider disclosures, applicable purposes, retention practices, user rights, contact details, and final text. Until Vincent separately approves legal review and publication, this remains a non-indexable draft and is not a published legal notice.