How your data travels
Follow one email or file from Microsoft 365 into your backup storage and back again. Step through the diagram, or press Play tour. Select any box to jump to the step where it does its work.
STEP 1 OF 7
Unlock the data key
Each organisation has one random data key, and it is never stored in readable form. The bucket holds only a locked copy. At the start of a run, Atlas turns your passphrase into an unlock key and opens the data key with it. The open key exists only in memory while Atlas runs.
scrypt (N=65536, r=8, p=1, 32-byte random salt) derives a 256-bit KEK. The KEK unwraps _meta/dek.enc with AES-256-GCM. Lose the passphrase and the backups cannot be opened by anyone.
The three ideas behind it
Only you can open the backups. Everything is sealed with a data key, and that key is locked with your passphrase. The storage provider and anyone who copies the bucket see only sealed data. A lost passphrase cannot be recovered.
Unchanged content is not uploaded again. Atlas recognises content it already holds for the same mailbox, drive, site, or team, so repeat backups upload only what is new.
Every restore is checked. The snapshot records what each item looked like at backup time. An item that does not match is reported, not restored.
Learn more
| Topic | Page |
|---|---|
| The terms used across these docs | Concepts |
| Keys, encryption, and what an attacker could see | Security model |
| Protecting backups from deletion | Immutability and Object Lock |
| What sits where in the bucket | Storage layout |
| How Atlas finds what changed | Delta sync |

