Security & privacy
Encrypt backups with your own key
You can protect stored snapshots and copied files with your own key. ZIP exports of those snapshots use a separate password. The option is included in every plan and applies to the whole account: every workspace of every connected platform.
How it works
- You add an RSA public key to your account. The matching private key stays with you: BackupLatte never receives it.
- Every backup is sealed with its own random key (AES-256-GCM), and that key is wrapped for your public key (RSA-OAEP, SHA-256). Normally, opening a stored backup requires a matching private key. The server can also read it while it holds temporary data keys for a backup in progress, a retry or an operation you unlock.
- When you restore or export an encrypted snapshot, the app asks for your private key. It is read in your browser, which opens the keys of that one snapshot and hands them over for that one operation. Restore and decryption unlocks expire 72 hours after creation. Export unlocks expire after 24 hours. A failed restore can use the same unlock to resume before it expires.
Set it up
- Open Encryption in the app.
- Add a key:
- Create one here: your browser creates an RSA-4096 key pair and downloads the private key as
backuplatte-private-key.pem. Keep the file in a password manager or another safe place. You then choose that file once, to confirm it was saved. - Use my own key: paste a public key of 3072 bits or more. To make one with OpenSSL, run
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:4096 -aes256 -out private-key.pemand thenopenssl pkey -in private-key.pem -pubout -out public-key.pem. A key pair you already use with another backup service works too. You then choose the private key once, to prove it belongs to the public key.
- Create one here: your browser creates an RSA-4096 key pair and downloads the private key as
- Switch encryption on. New backups are sealed from then on, and the snapshots and files already stored are sealed in the background. The screen shows progress as readable snapshots and files are rewritten. Previous copies stay in storage until background cleanup removes them. Objects left by old failed backups are removed by normal retention.
Add a second key and keep it offline as a spare. Every backup is sealed for all active keys, so any one of them opens it. An account holds up to three keys.
If you lose the key
If every private key of the account is lost, the encrypted backups are lost for good. We cannot recover them: we never had the key. A spare key is the only protection.
Restore and export
- Restore asks for the private key before it starts. A restore that failed can be resumed without the key for 72 hours; after that it asks again.
- Download as ZIP asks for the private key and shows a ZIP password. Save it: it is shown once. The server uses it to build the ZIP and removes the active unlock after a successful build. The download,
backuplatte-…-encrypted.zip, is protected with AES-256 and holds one file,backuplatte-snapshot.zip, so not even the file names show without the password. Open the download with 7-Zip (Windows; from the official site, 7-zip.org), Keka (macOS) or7z xon Linux (packagep7zip-full; the standardunzipcannot open it) and the password, then openbackuplatte-snapshot.zipas any ZIP. The archive tools built into Windows and macOS list the file but cannot open it. If the password is lost, prepare a new ZIP. - The snapshot manifest is decrypted in your browser when you download it.
Changing keys and switching off
- A new key seals new backups straight away. To let it open older snapshots too, use Re-wrap for this key and choose a private key that already opens them: only the small per-backup keys are wrapped again, in your browser.
- Retire a key to stop sealing new backups with it. It still opens what it sealed.
- Remove is refused while any stored backup can be opened with that key only.
- Switching encryption off applies to new backups. Snapshots already encrypted stay encrypted and still need the key until they expire, or until you choose Decrypt stored backups and unlock them once.
What to expect
- In Linear, change history is normally carried over from the previous snapshot. A sealed snapshot cannot be read back, so with encryption on that history is collected in full every day. Backups of large workspaces take longer.
- Encrypted snapshots cannot be read by tools that work on snapshot content, including content tools of connected AI clients.
What encryption does not cover
To make a backup, BackupLatte reads the data from the connected platform, and it holds an access token to the live workspace. It also reads a snapshot again while a restore or export that you unlocked is running. Encryption protects the stored copy; it is not a guarantee that we can never see the data. Temporary data keys and ZIP passwords are encrypted under a separate server key. Database backups can contain encrypted copies of that material for the database backup retention period.
These stay unencrypted: your account email; workspace names and settings; the dates, sizes and record counts of snapshots; checksums, types and sizes of files; error messages from the connected platform; and the record of what a restore created. For a ClickUp restore that record includes the names of the statuses, tags, lists, folders and Spaces it touched and the email addresses used to match people.
Something missing or unclear? Write to [email protected].