Security & privacy · Encryption with your own key

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

Set it up

  1. Open Encryption in the app.
  2. 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.pem and then openssl 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.
  3. 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

Changing keys and switching off

What to expect

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].