Security & privacy
Security
A backup service stores supported workspace data and files, so access and storage controls matter. This page describes what BackupLatte does to protect that copy.
Access to Linear
- You connect through Linear's OAuth. BackupLatte never sees your Linear password.
- It asks for
readaccess to make backups andwriteaccess only to perform restores you start. Linear'sadminaccess is requested only when you turn on extended coverage. - Linear access tokens are stored encrypted with AES-256-GCM and renewed automatically. Disconnecting a workspace deletes them.
- You can revoke BackupLatte's access at any time in Linear's settings.
Your backups
- Snapshots and copied files are stored in a private Cloudflare R2 bucket under its EU jurisdiction. Nothing in it is public.
- Downloads use private links that expire after 15 minutes.
- You can protect stored snapshots and files with your own key on every plan. ZIP exports of encrypted snapshots use a separate password. See Encrypt backups with your own key.
- Other BackupLatte accounts cannot see, download or restore your backups.
- Credentials, webhook URLs and secrets of integrations and webhooks are never collected, and neither are Linear's security settings or users' personal items. See What a backup contains.
Your account
- Passwords, when used, are stored only as bcrypt hashes. Google sign-in is offered only when enabled for the environment.
- Sessions use short-lived tokens (15 minutes) renewed through an HTTP-only cookie that lasts up to 7 days, renewed during use. Log out clears the browser's session and revokes refresh access. Already issued access tokens can remain valid until their 15-minute expiry.
- Sign-in attempts are rate-limited per IP address and per email.
Infrastructure
- The application, database and background jobs run on servers in Germany (Hetzner, Falkenstein).
- The website and the app are served by Cloudflare, which also sits in front of the application.
- Payments are handled entirely by Paddle, our Merchant of Record. BackupLatte never sees your card details.
The full list of providers and what they process is in the subprocessors list; how personal data is handled is described in the Privacy Policy and the Data Processing Addendum.
Report a security issue
Write to support@backuplatte.com with the details. Please do not test against other customers' data or run load tests against the service.
ClickUp
ClickUp OAuth authorizes selected workspaces rather than offering Linear-style read/write/admin scopes. The access token is encrypted with AES-256-GCM. Access remains limited by the connected user's permissions. File copying restricts source hosts and redirects. A Doc restore requests private visibility and reports a refusal instead of silently making content public. Restore decisions are scoped to account, operation, plan and intent versions; their saved UUID/payload is reused after an uncertain response. Connect ClickUp explains access.
Something missing or unclear? Write to [email protected].