axsDocs
Account

Security

Where your data lives and who can read it.

axs brain

  • Encrypted per team: memory text, history and kept hook data are encrypted with a key per team. Search fields (titles, words, embeddings) are not.
  • Separated per team in the database with row level security.
  • Where: our own servers at OVH in France, encrypted backups at Hetzner in the EU.
  • No AI provider: search and embeddings run on our servers.
  • Hook data (prompts as single words, commands, paths) is kept 7 days for rule trial runs.

Give write access to shared spaces only to people you trust: a memory written by someone else goes into your agent's context.

axs cred

Credentials are encrypted and signed in your browser and decrypted only on your confirmed devices. The server stores only public keys, sealed data and signatures. See axs cred.

Login

No passwords: e-mail code, passkey, Google or GitHub. Device tokens are stored as a hash.

The full details are on the security page.

On this page