Security and privacy

Atoi keeps your keys and sessions out of threads, documents, logs, and model context, and stops before anything outward-facing or destructive. This page describes how the product behaves. The Privacy Policy and Terms linked in the footer are the legal commitments.

#Keys and sessions

Provider keys and browser sessions are stored encrypted and decrypted only on the server when a request needs them. They never enter a thread, a document, a log, or a model's context. Atoi never types passwords, payment details, passkeys, or two-factor codes for you.

#Permissions

Connections and computers have explicit scope. Atoi acts on its own for read-only and reversible work and asks before anything outward-facing, destructive, credential-related, or permission-changing. See Asks and approvals.

#Sharing

Inviting a person and publishing a page are different actions with different audiences. Read a thread before you invite and before you publish, because Publish creates the public copy when you open it, and revoke exactly the access you want to end. See Sharing and invites.

#Execution data

Tasks produce logs, diffs, screenshots, and recordings. Treat them like the data they contain: a screenshot can hold a path, a name, or an account state that should not be published.

#Your account data

Open Settings → Data to see and remove uploads and shared links. Clear all data sits under its Danger heading and asks before it acts. Deleting a record, its file, and a published page are separate actions, and each confirmation says what it removes.

#Report a security concern

Do not include live secrets. Describe the surface, the smallest reproduction, the boundary you crossed, the boundary you expected, and whether it still happens. Use the security contact linked from the legal pages.

Read Asks and approvals for the gates that stop consequential work before it runs.