Skip to main content

​
Local clipboard data

Original clipboard content, managed files, OCR, search indexes, provider settings, credentials, grants, and derived data are stored on the device. Settings sync does not include clipboard history. Optional models and extensions receive content needed for their tasks; external processing depends on configuration and granted capabilities.

​
Chats, models, and assistants

Recall chats and source snapshots are saved locally, separately from clipboard retention, and are excluded from settings sync. Deleting a chat removes its owned attachments without deleting captured clips. Provider credentials use protected device-local storage. Hosted providers receive content needed for enabled tasks; hosted background indexing requires explicit permission. Local MCP is off by default and requires a separate token for each assistant. Read-only grants allow retrieval; read/write grants also allow supported changes. Revoking or deleting access disconnects that assistant; deleting access does not delete clips or activity records.

​
Decision rules and failed checks

Built-in secret detection remains active. Optional decision rules can classify new text before storage, mark it private or secret, or skip saving. Secret and private clips are excluded from Recall, Meaning Search, MCP access, and automatic extensions. The privacy provider receives the text it evaluates; on-device inference is recommended. Rules do not scan existing history or image pixels and do not clear the system clipboard. If a configured check fails, the full clip is saved with a Not checked notice. Failure alone does not restrict the clip from AI or extension processing. Organization rules are skipped when privacy evaluation fails; existing restrictions and successfully detected secrets still apply. Read failure behavior before choosing your settings. No model guarantees detection of every secret. For assistant setup and access controls, see MCP. A local connection does not prevent the external assistant from sending retrieved text to its own provider.

​
Optional accounts

Supabase handles authentication, email, sessions, and supported settings-sync records. Google and GitHub process sign-in when selected. Pro billing and Vault are not advertised as available features. Settings sync is not end-to-end encrypted.

​
Deletion controls

Use Account settings to close your account. Resolve existing subscriptions and owned organizations first if applicable. Closure revokes hosted access and removes or disables hosted data according to integrity and security requirements. It does not promise immediate deletion from all retained records or backups. Account closure does not remove desktop history. Manage local data separately on each device. For the governing disclosure and contact details, read the Privacy Policy. This page is an operational guide. See settings sync and local AI boundaries.