Your browser
Unlocks your private space and encrypts supported content for saving.
PRIVACY YOU CAN TRY
See encryption
in action.
Type a harmless sample and watch your browser turn it into protected data. Then try to change it and see the check fail. This is an interactive illustration of the protection used for supported saved work in Atlas.
This page runs the example in your browser. It does not connect to your Atlas account or inspect the live Atlas database.
TRY IT YOURSELF
Your words go in.
Ciphertext comes out.
Use the example below or write your own non-sensitive sentence. The sample and its temporary key stay in this tab; this page does not send or save them.
- Encrypt your sample.
- See the protected result.
- Reveal it, or alter one byte and watch the integrity check reject it.
Please do not enter passwords, private messages, or customer information.
ENCRYPTED RESULTAES-GCM · 256-bit key
The encrypted value below changes every time, even for the same words, because each run uses fresh randomness.
“Alter one byte” simulates someone changing the encrypted value. Reveal will then fail until you select “Restore original.”
HOW A SUPPORTED PRIVATE CHAT REQUEST MOVES
Separate machines.
Separate jobs.
Atlas separates encrypted storage from the machine allowed to process a selected private-chat request. Follow the arrows to see where saved content stays encrypted and where a request must briefly be readable. Other features may use different paths.
Protected storage
Keeps the encrypted saved copy and passes along only an authorized request.
Separate processor
Opens the selected request temporarily, uses the chosen AI service, and protects the result before it returns.
Back to you
The protected result returns. Your browser opens the saved reply after unlock.
Where AI processing differs: The separate processor and chosen cloud AI provider can read the content needed for an authorized request while it is processed. Encryption of saved work does not mean prompts are hidden from every operator or provider.
Live: private processing, remote admin access closed
The protected processor closes its SSH access while serving private requests.
Maintenance: processing stops before access opens
That processor drains and stops private work before authorized maintenance access opens. Other infrastructure has separate access controls; one switch does not govern every machine.
WHAT THIS DOES—AND DOESN’T—SHOW
A real technique.
An honest boundary.
Atlas uses this kind of protection
Supported private conversations, uploads, and generated images are encrypted before Atlas stores them. A database copy alone cannot open those saved records; your private unlock opens your saved copy in the browser.
A demonstration, not a database view
This exercise uses your browser’s encryption tools and never writes to Atlas. It shows how encryption and tamper detection work, but it cannot certify every live record or historical backup.
Less information at signup
Free preview signup asks for a display name, username, email, and password—no mailing address or card. If paid checkout is offered, a third-party payment processor handles card entry and receives the billing details needed for payment, not private conversations or files. Atlas keeps limited billing references and display details, not full card numbers or security codes.
Processing has a separate boundary
When you ask Atlas to use a cloud AI service, the content needed for that request is temporarily readable for processing. Some account and operational metadata remains readable, too. A privileged operator’s control of a live service is different from reading stored ciphertext.
Want to see the exact scope of the current preview?