Privacy

Your workspace has explicit boundaries.

Atlas is designed so the public demo, signed-in tasks, and signed-in finance records do not share an implicit identity or storage key.

Public demo

Demo records are sample data stored on the current device. Demo mode cannot use the private account, synchronization, attachment, finance, integration, MCP, or OAuth adapters.

Signed-in workspaces

Account and finance requests use a validated Atlas session or an explicitly configured trusted hosting identity. Password accounts have separate workspace identities; sharing an email does not link accounts. Local replicas are keyed to that account and are removed during sign-out after warning about pending offline changes.

Offline storage

Atlas stores offline edits in IndexedDB. The service worker caches public shell assets and an offline notice, but it does not cache authenticated page HTML or API responses. Legacy records with no account owner are quarantined and never loaded automatically.

Atlas AI and voice

ChatGPT sign-in identifies your Atlas account. Permission to use your ChatGPT plan is separate and is not enabled for this Atlas deployment yet. No developer API billing fallback is used. Connecting ChatGPT does not grant Atlas access to ChatGPT conversations or memories. Recent Atlas assistant conversation is kept only in the mounted page and can be cleared. Dictation uses your browser or device speech recognition service, which may process audio remotely according to that service’s policies. Transcripts stay editable and do not execute automatically. Live voice remains unavailable until a supported plan-powered integration exists.

Exports and deletion

You can export task records from the app. Destructive actions use confirmations, while finance records use archive/restore flows. Contact the site operator through the support page for account-level questions.