Privacy & security

ACRE keeps what it needs, shows it only to the people you choose, uses first-party analytics with no trackers, and lets you export or delete everything yourself. ACRE never holds your AI tokens. For the full legal notice, see the Privacy policy.

What ACRE stores

Your account details. Sign-in sessions and keys are stored only as hashes.
Your profile and your place in the world.
Messages you send.
Your brain and memory.
Synced sessions, which are Only me by default and redacted twice.
Meeting notes, only with each speaker’s consent.
Your billing status. Card details stay with the payment provider.
Usage counts.

Tokens ACRE has to use on your behalf, such as a connected calendar or GitHub access, are encrypted at rest.

Who can see what

Everything has a visibility level, from narrowest to widest: Only me, Specific people, Friends, Team, Team + guests, Venture, Harbor and Public. One check decides access everywhere.

If you can’t see something, it doesn’t appear at all: not in counts, titles or search. A private island or organization looks exactly like one that doesn’t exist.

Islands have their own visit levels.

Redaction

Every synced chat is scrubbed of secrets twice: on your machine before upload, and again on the server. The rules catch, among others:

private keys (PEM blocks)
.env-style lines whose names mention a secret, token, password, credential, API key, auth, DSN, database URL or webhook
Authorization and API-key headers, and Bearer and Basic values
provider API keys and tokens in their known formats (AI providers, payment providers, code hosts, chat apps, cloud providers, package registries and others)
ACRE’s own session and client tokens
JSON Web Tokens
passwords inside URLs (user:pass@host)
secret-named fields in JSON

Redaction is a safety net, not a guarantee. Keep secrets out of chats you sync where you can, and use Don’t sync for chats that hold sensitive work.

Encryption at rest

Synced chats are not kept in ACRE’s main database. Each chat is its own file, compressed and then encrypted with AES-256-GCM. Each file is bound to its owner and chat, so it can’t be swapped or replayed elsewhere.

Per-person keys. Everyone has their own random 256-bit data key.
Envelope encryption. Your data key is itself stored only encrypted (AES-256-GCM), under a key derived with HKDF-SHA256 from a server secret.
Deletion removes the key. Deleting your account removes your folder, key included.

Only small metadata stays in the main store: titles, which harness, routing and sharing, sizes, hashes and times.

Your agents and your keys

Agents run on your own subscription, through the official CLI on your computer. ACRE never imports your provider’s credential files.
The desktop app removes API-key variables from everything it starts, so runs always use your subscription login.
MCP clients and the CLI get their own credentials through a browser approval. You never paste your browser session anywhere.

Cookies and analytics

ACRE uses one first-party cookie to keep you signed in, with no ads and no trackers. Analytics are first-party only: a keyed hash per person, per day and feature.

Export and delete

Export: Settings → General → Your data → Export my data downloads one JSON file with your data, including your synced chat transcripts. Secrets (hashes, tokens, vault contents, credentials) are left out.
Delete: type your name to confirm. You’re signed out everywhere at once, and your data is purged within 7 days at most. Cancel Pro first. Messages other people received stay theirs, shown as from “Deleted user”. Shared islands carry on for everyone else.

Reporting a problem

For abuse or takedown requests, email hello@useacre.dev.