How Atlas protects your pages and keys.
This page describes how each is protected and lists what we have not done yet.
Last updated November 12, 2026
Keyring to use a key.
The key stays there.
- A separate program, running as its own user on the server
- A separate database that the books’ database login cannot open
- An encryption key for each workspace
- A master key stored in a file outside both databases and their backups
Pages and keys are stored separately
Atlas stores two kinds of data and handles them differently. Your pages are documents. They are stored in a database, and every read and write is limited to your workspace.
Your keys (passwords, API keys, tokens) are not stored with your pages. They are stored in the Keyring, which is a separate program with its own database, running as its own user on the server. The part of Atlas that serves your pages can ask the Keyring to use a key. It can get a key's value only if you have turned viewing on for that key.
How keys are encrypted
Every key is encrypted before it is stored.
- Encryption is AES-256-GCM, with a separate encryption key for each workspace
- The workspace keys are encrypted by a master key. The master key is a file on the server, outside the database and outside its backups
- Each stored key is bound to its own workspace and its own entry, so it cannot be decrypted if it is copied to another entry or workspace
- A copy of the database alone, or of a backup alone, cannot be decrypted
Your AI uses a key without receiving it
When a connected AI needs to call an outside service, it asks Atlas to make the request and names the key. Atlas adds the key, sends the request, and returns the response.
- A key is sent only to the sites you listed for it. A request to any other site is refused and logged
- Keys are sent only over https and never to an address inside our own network. If the site answers with a redirect, Atlas returns the redirect and does not follow it
- Before the response goes to your AI, Atlas removes the key from it in every form it was sent in, along with anything else that looks like a password or key
- A saved key cannot be viewed by anyone, including you, unless you turn viewing on for that key
The Keyring requires its own code
Being signed in does not open the Keyring. To open it, add or change a key, or give a key to an AI, you enter a new six-digit code sent to your email. The Keyring then stays open for fifteen minutes in that browser, and you can lock it sooner. Each time it is opened or locked, and each wrong code, is recorded in the Keyring's log.
This protects your keys from someone who uses a browser where you are signed in. It is not a second password. The code goes to the same email address you sign in with, so anyone who controls that mailbox can still open the Keyring.
Passwords and keys are kept off pages
If you paste something that looks like a password, API key or token into a page, Atlas does not save the page. It shows a masked version of what it found and offers to move it to the Keyring and put the key's name on the page instead. The same check runs on text that a connected AI proposes or logs.
For uploaded files, saved web pages and pasted text, Atlas removes anything that looks like a password or key before it stores the text.
What a connected AI can and cannot do
Each AI you connect has its own address and its own permissions.
- You choose which books it can read, whether it can propose changes, and which keys it can use
- It cannot edit a page directly. A change it proposes is not part of the book until a person approves it. The one exception is a book's Log page, where an AI with write permission can add a dated line
- A connection's address is shown once. Atlas stores only a hash of it, which cannot be converted back into the address. Turning a connection off stops it immediately
- Each search, read, proposal, key use and refused request is logged with the connection's name
- Each workspace has limits on how many requests its AIs can make per minute and how many times its keys can be used per day
Atlas does not run an AI
Atlas has no model of its own and makes no calls to one. We do not send your pages to an AI provider, and they are not used to train a model. Your own AI reads only what you allowed its connection to read. That AI handles what it reads under your agreement with its provider.
Signing in and paying
You sign in with a six-digit code sent to your email address. Atlas stores no passwords for signing in. Payment is taken on Stripe's pages. Atlas never receives or stores a card number.
Workspaces are separate
Every page, key, proposal and log entry belongs to one workspace, and every request is limited to the workspace of the person or connection making it. Automated tests try to reach one workspace with another workspace's credentials, and they run before every change is released.
Backups, export and deletion
The databases are backed up every night. Backups are encrypted and stored off the server. The key that decrypts them is not stored on the server. The Keyring's master key is not in those backups.
You can export every book at any time as a folder of Markdown files, including after a trial ends. A workspace's owner can delete the workspace and all of its data from the People page. If you need help, write to support@atlasknows.io.
What we have not done
Atlas has not had an independent security audit and does not hold a SOC 2 report or any other certification. It runs on a single server that we operate. If your organisation needs audited controls today, Atlas does not meet that requirement yet.
Reporting a security issue
If you believe you have found a vulnerability, email support@atlasknows.io with the details and the steps to reproduce it. Please give us a reasonable amount of time to fix it before you make it public. We do not take legal action against people who report in good faith.
Try Atlas free for 14 days.
No card is needed. You sign in with your email address, and you can export your books at any time.