Know what you share. Know what you authorize.

Local working data

The desktop stores working information such as saved discussions, task history, profiles, and files in local application and browser storage. Local history is not a promise of encrypted storage, unlimited retention, or automatic backup.

Provider tools may also maintain their own history or files. Those stores follow the provider tool’s behavior.

AI provider requests

Selected role instructions, supplied content, and relevant conversation context can be included in AI requests. The provider processes that information outside the desktop according to its service, configuration, and agreements.

Do not assume all providers have the same training, retention, or human-review rules. Check the settings and terms of the service you choose.

Cloud preview records

Cloud preview workflows send account, installation, configuration, conversation, and run information to configured platform services. The server stores accepted content and can read it; this is not end-to-end encrypted messaging.

The isolated cloud drafting path requires a separate per-turn review and disables tools. This behavior does not describe every local workflow. Hosted customer release, retention, export, and account-deletion procedures remain pending.

Files, browser & tools

Local tool workflows depend on profile and provider permissions. Supplied attachments and screenshots may become part of a request. Review their contents before sharing them.

Opt-in browser control uses a separate agent-owned browser window. A permitted browser session can continue between turns until the agent stops. Screenshot and browser implementation evidence does not establish universal support or isolation across every provider.

Connection permissions

Business-service access needs separate authorization. Google sign-in identifies an account; Gmail authorization permits specific mailbox access. Neither an AI role nor a “team” name grants access.

The documented Gmail native preview is read-only and owner initiated. It does not send mail to AI providers, and agent access is unavailable. See Connections for exact preview limitations.

Disconnecting and deleting are different

Disconnecting stops a configured connection’s local use. Revoking provider authorization withdraws permission at the provider. Neither automatically deletes previously saved, exported, or transmitted content.

Uninstalling the desktop does not establish deletion of local data, cloud records, provider records, or backups. Account deletion and retention processes must be approved before a public cloud rollout.

See the Privacy Policy for the document’s current status.