Data Processing Addendum

1. Roles

Where a customer submits personal data (for example, client or patient identifiers) into the service, the customer is the data controller and Amnesia AI is the data processor, processing that data only on the customer's documented instructions, as set out here and in the Terms of Service.

2. Nature and purpose of processing

Personal data entered into the desktop app is encrypted on the customer's device to a key held by the confidential-computing enclave that runs the model. The encrypted request passes through our gateway, which relays it without holding a key that decrypts it, and is decrypted only inside that enclave. Our processing is therefore limited to: relaying encrypted requests, receiving the unencrypted portions of a turn described in section 3, metering (model, token counts, timestamp), and account and billing administration.

3. Categories of data

Depending on how the customer uses the service, this may include names, tax identifiers, financial account numbers, client or patient identifiers, and similar values entered into the app. Values contained in message content reach us only as ciphertext.

The following are not encrypted and do reach our gateway in readable form, because the protocol requires it: tool definitions; the names, arguments and results of tool calls in both directions, which may include file paths, URLs, shell commands and search queries; images and screenshots sent to the model; the identity of the model, the size of the request and reply, and the timing of the turn; and audio submitted for dictation. Where a customer's agent places personal data into any of those, we receive it in readable form.

4. Security measures

Full detail is on our security architecture page. In summary:

• End-to-end encryption from the customer's device to the enclave (X25519 key agreement, HKDF-SHA256, XChaCha20-Poly1305). Our gateway holds no key that decrypts message content.
• Inference inside an Intel TDX confidential-computing enclave with encrypted memory, where TLS terminates inside the enclave rather than at our gateway.
• Hardware attestation of the enclave verified before each reply is returned: Intel DCAP quote and certificate chain, TCB and revocation status against Intel collateral, GPU attestation via NVIDIA NRAS, TLS binding, and a signature over the response. The report is exportable by the customer.
• Local data encrypted with SQLCipher and XChaCha20-Poly1305, keyed by Argon2id derivation from a customer-held passphrase we never receive.
• Agent actions that reach outside the device (web search, shell commands, file writes) require explicit per-call approval by the user.

5. Subprocessors

We use the following subprocessors to operate the service:

• Stripe: payment processing.
• Supabase: authentication and account data storage.
• Resend: transactional email.
• Sentry: error monitoring.
• Vercel, Fly.io: application and gateway hosting.
• NEAR AI Cloud: operates the confidential-computing enclaves that run the models. Message content reaches it encrypted and is decrypted only inside the enclave; the unencrypted portions listed in section 3 reach it readable.
• Brave Search: receives search queries in the clear, when the user approves a web search.

We will notify customers of new subprocessors with material access to personal data with reasonable notice, at legal@amnesia.ai.

6. International transfers

Where personal data is transferred outside the customer's region, we rely on appropriate safeguards, including Standard Contractual Clauses, with our subprocessors.

7. Assistance with data subject rights

We will assist customers, to the extent our architecture allows, in responding to data subject access, correction, or deletion requests concerning account and billing data we hold. For data that only ever existed on the customer's own device, the customer controls it directly, including through free encrypted export.

8. Breach notification

We will notify affected customers without undue delay after becoming aware of a security incident affecting their personal data, with the information available to us at the time.

9. Audit rights

On reasonable request, and no more than once per year absent a security incident, we will make available information reasonably necessary to demonstrate compliance with this addendum.

10. Term and deletion

This addendum applies for as long as we process personal data on the customer's behalf. On termination, we will delete or return the account and billing data we hold within a reasonable period, except where retention is required by law.

Contact

To execute a signed, entity-specific DPA, or with questions about this page: legal@amnesia.ai.