We keep what we cannot read.
This page says exactly how: what is encrypted and where, who holds the keys, what we can still see about you, and what this design cannot protect you from.
Encryption starts on your device
Every file is encrypted on your device, before it leaves for us. We use AES-256-GCM, and every file has a key of its own. That key is then protected with your public key (RSA-OAEP, 2048 bits).
Only encrypted content reaches our servers. We cannot read it, search it or hand it to anyone in readable form – not at your request, and not at anyone else's. The service does not allow files to be stored unencrypted.
You hold the keys
Your private key is created on your device and is never given to us in readable form. You keep it as a file, apart from the device and from your password.
In the browser, a loaded key locks itself after eight minutes of inactivity. In the desktop app it is kept encrypted, protected by the operating system's key storage, and is unlocked with your confirmation.
We do not store your password; we keep only a one-way hash of it (Argon2).
The consequence is serious and we do not hide it: if you lose the file with your private key and have not turned on key recovery, access to your content is lost for good. We cannot restore it either.
What we see and what we don't
Encryption protects the content of files. Running the service also takes data that is not encrypted, and it is only fair to list it.
We see
- your e-mail address, first name and surname
- the names and sizes of files, the names and descriptions of folders, shared spaces and packages
- the details of recipients that you enter
- delivery conditions and statuses, the time of your last activity and records of actions
- subscription and invoice data
We don't see
- the content of files
- your private key
- your password
- the full number of your payment card
Delivery keys are split across four places
For scheduled delivery and digital legacy, the keys that open a package do not sit with us in one piece. They are cryptographically split into four parts (Shamir's scheme), and each part is kept in a separate vault, under that vault's own key. At least three of the four parts are needed to unlock.
Unlocking happens only once the delivery condition you set has occurred, in a supervised procedure we call a ceremony, with the approval of a quorum of trustees. The trustees see neither the content, nor your name, nor your e-mail address.
The vaults are not directly reachable from the public internet. Their public keys are built into our apps as a signed list, so nobody can slip the app a false key.
The exception is immediate delivery: the key is then in the link the recipient gets by e-mail. It passes through our server only so the message can be sent, and we do not store it, but the security of such a delivery also depends on the security of the recipient's mailbox.
Key recovery – only if you turn it on
Key recovery is voluntary and stays off until you turn it on yourself. Your private key is then encrypted on your device and split into four parts, one for each vault; three are needed for recovery.
Only you can start a recovery. A 48-hour waiting period follows, of which we notify you by e-mail at once and during which you can cancel it. Recovery is never approved automatically, and the key is unlocked only for the device you requested it from.
You can turn recovery off at any time; the stored parts of the key then become unusable.
In a company, the organisation holds a key too
For business users, every file of a member of the organisation is also encrypted with the organisation's master key. The owner and the administrators of the organisation can therefore access their members' files, and every such access is logged. This is deliberate: a company must not lose its documents when an employee leaves. We still cannot read those files.
Servers and network
All data is stored within the EU, with the exceptions listed in the Privacy Policy.
- Encrypted content is stored redundantly, on several disks, so the failure of one disk does not mean data is lost.
- All traffic between your device and the service is encrypted (TLS).
- Internal systems are connected by a separate private network, and the key-management systems are not directly reachable from the public internet.
- Only authorised persons have access to the servers, by means of cryptographic keys.
- The number of requests to the service is limited, to protect against overload and password guessing.
- The test environment is separate from production.
The service is no substitute for your own backups: keep content of particular importance in another place as well.
What this protects you from, and what it doesn't
It protects you from
- a break-in into our servers: an attacker would get encrypted content, not files
- curiosity or a mistake on our side: we cannot open the content either
- third parties demanding readable content: we can hand over only the encrypted form
- a break-in into one vault: one part of a key is worth nothing on its own
It does not protect you from
- an infected or unlocked device: whoever controls your device while the key is loaded sees what you see
- losing your private key without recovery turned on
- a password and a key kept in the same place
- a break-in into the recipient's mailbox, for immediate delivery
- what is not encrypted: we see file names and the other data listed above
Reporting a security vulnerability
If you have found a vulnerability, write to us at security@thesafebox.eu. Reports made in good faith are handled as described in Article 10 of the Terms of Service.