Encrypt Linear and ClickUp backups with your own key

BackupLatte lets you encrypt stored Linear and ClickUp backups with your own RSA key pair on every plan. You add the public key to your account and keep the private key. BackupLatte never receives the private key.
A backup is a second copy of the specs, customer names and plans your team writes down. The new option adds encryption tied to your key to the stored copy, including supported files copied from your workspaces.
How does backup encryption work?
- You add an RSA public key to your account. The matching private key stays with you.
- Every backup is sealed with its own random key (AES-256-GCM). That key is wrapped for your public key using RSA-OAEP with SHA-256. Opening a stored backup normally requires a matching private key.
- Encryption applies to the whole account: every workspace on every connected platform, and the files copied from them.
How do you turn on backup encryption?
- Open Encryption in the app.
- Add a key. Choose Create one here, and your browser makes an RSA-4096 key pair and downloads the private key as
backuplatte-private-key.pem. Or choose Use my own key and paste a public key of 3072 bits or more. A pair you already use with another backup service works too. - Choose the private key file in your browser to confirm you saved it and that it matches.
- Switch encryption on. New backups are sealed from then on, and the snapshots and files already stored are encrypted in the background. Previous copies remain in storage until cleanup removes them.
What happens if you lose your private key?
If every private key of the account is lost, the encrypted backups are lost for good. We can't recover them, because we never had the key.
Add a second key and keep it offline. New backups are encrypted for all active keys. An account holds up to three. To give a new key access to older backups, use Re-wrap for this key while you still have a private key that opens them.
Restore and export still happen in the app
Restore asks for your private key before it starts. The key is read in your browser, which opens the keys of that one snapshot and hands them over for that one operation. If the restore fails, you can resume it without re-entering the key until the unlock expires, 72 hours after it was created.
Download as ZIP asks for the private key and shows a password once. The download is protected with AES-256 and contains a single inner ZIP, which keeps individual backup file names hidden until you unlock the download. Open it with 7-Zip on Windows, Keka on macOS or 7z x on Linux. The archive tools built into Windows and macOS can't open it.
What changes when encryption is on
- Linear backups of large workspaces take longer. Change history is normally carried over from the previous snapshot. A sealed snapshot can't be read back, so that history is collected in full every day.
- Tools that work on snapshot content can't read encrypted snapshots. That includes the content tools of connected AI clients.
What encryption doesn't cover
Encryption protects the stored copy. It is not a guarantee that we can never see your data.
- To make a backup, BackupLatte reads the data from Linear or ClickUp, and it holds an access token to the live workspace.
- BackupLatte can read data while it holds temporary data keys during a backup, a retry, or a restore or export you unlock. Restore unlocks expire after 72 hours and export unlocks after 24 hours.
- Some things stay unencrypted, including your account email, workspace names and settings, the dates, sizes and record counts of snapshots, and the record of what a restore created.
The encryption guide has the full list, and explains how to change keys or switch encryption off.
If you haven't set up backups yet, start with our guides for Linear and ClickUp.