Security
What is actually enforced, and what is a promise Axiom cannot make yet.
Axiom is pre-release. There is no production operator identity, published contact address, or approved retention schedule yet. This page describes exactly how the software behaves today; it is not yet a complete legal notice, and it will be replaced by one before anyone is asked to rely on it.
Getting in
An account is required, and no part of the product that touches a note renders before you are signed in. There is no anonymous mode and no device-only mode.
Axiom uses Firebase Authentication. Every backend service independently verifies each token's signature, key identifier, issuer, audience, time claims, and subject. No private signing key ships in the browser.
Secrets
The credential that compiles captures and the key used for speech-to-text are held as deployment secrets, read only in request memory, and never returned to a browser in any response, error, or log. No route accepts or echoes a credential.
An Upload token you provide is encrypted at rest and cannot be read back — replacing or disconnecting deletes it.
Boundaries
No Axiom client ever contacts the Upload service directly; only the Upload Bridge does. Capture media never reaches a database, an object store, a queue, a cache, or a log. Every request is scoped to the verified account, so there is no shared session or cross-request state to leak through.
Capture content is treated as untrusted data rather than instructions: the compilation request carries no tools and no external context, and everything the model returns is validated before it is stored.
What Axiom cannot promise
Axiom is not end-to-end encrypted, so a compromise of Axiom's hosting account is a compromise of note content. One operator-held credential compiles every capture, so its compromise affects everyone's captures rather than one person's.
Axiom cannot cryptographically prevent a model or speech provider from retaining what it receives. Voice capture has a wider disclosure surface than photo capture for that reason.
Reporting a problem
There is no published security contact yet, because there is no production operator identity yet. A disclosure address will be published here before general availability.