Last updated 16 October 2026.
1. Who is responsible
[Company legal name], [Registered address], is the controller for personal data about account holders and visitors. For the data inside your databases and backups, you are the controller and we process it on your behalf, only to provide the service. Data protection questions: [email protected].
2. What we collect
Your account
- Name, email address, and a hash of your password.
- What you tell us when you sign up: your role, how you heard about us, and your timezone.
- Passkeys and two-factor settings, if you add them.
- Sign-in sessions, with the IP address and browser they came from, so you can see and end them.
Your workspace
- Workspace name, members and their roles.
- Database connection details and bucket keys, stored encrypted with AES-256-GCM.
- Backup records: file names, sizes, times, table names and row counts, restore test results, and uptime checks.
- An audit log of actions in the workspace: who acted, when, and from which IP address and browser.
- Notification channels you add, such as an email or a webhook.
Your backups
The backups themselves are copies of your databases, encrypted with age before they are stored. backupd’s key for your workspace can decrypt them; we use it only to run restore tests and restores, and for support you ask for. When backupd support signs in as a member to help, the workspace’s audit log says so. Restore tests run on our sandbox servers in the EU, and the temporary copy is deleted straight after.
3. Why we use it
- To run the service you signed up for (contract).
- To bill you, and meet tax and accounting rules (legal obligation).
- To keep backupd secure and fix problems, using server logs and the audit log (legitimate interest).
- To send you service emails: alerts, receipts and security notices. We don’t send marketing email without your consent.
- To understand how the website and the app are used, and to find errors, through product analytics and session replays, only if you accept them (consent). You can withdraw consent at any time.
We don’t sell personal data, and we don’t use your data to train models.
4. Who helps us
These providers process data for us under data processing terms that hold them to the same care:
- Oracle Cloud Infrastructure: Hosting: the website, app, API, its database, the backup workers and restore-test sandboxes. Frankfurt, Germany (EU). All service data.
- Backblaze B2: Storage for encrypted backups (backupd Storage). The region your workspace picks: EU Central (Amsterdam), US East or US West. Encrypted backups only.
- Cloudflare: DNS, TLS and network protection in front of every backupd site. Global network. Requests and IP addresses.
- Polar: Payments, invoices and sales tax, as merchant of record (an independent controller). See Polar's privacy policy. Billing details.
- Resend: Email delivery: alerts, invitations and security notices. United States. Email addresses and message content.
- PostHog: Product analytics, session replays and error tracking, only after you accept analytics. United States. Usage events and masked session replays.
- Zoho Mail: Our support, sales and privacy mailboxes. United States. Emails you send us.
- Have I Been Pwned: Checks new passwords against known breaches. Global. The first 5 characters of a password hash, never the password.
If you add your own bucket or a notification channel, data goes there on your instruction, under that provider’s terms. We tell customers before we add a provider that processes their data.
5. Where your data is
backupd runs in the EU: the app, its database, the backup workers and the restore-test sandboxes are in Frankfurt, Germany. Backups are stored in the region your workspace picks; choose EU Central to keep them in the EU. Some providers above are in the United States; transfers to them rely on the EU–US Data Privacy Framework or the European Commission’s Standard Contractual Clauses in their data processing terms.
6. How long we keep it
- Backups: as long as your retention setting. Deleted backups can be recovered for 7 days, then they are removed.
- Deleted workspaces: 7 days, in case it was a mistake, then the workspace and all its backups are removed.
- Uptime check and notification history: 90 days.
- Audit log: 1 year.
- Sign-in sessions: until they expire or you sign out.
- Server logs: rotated by size, kept for a short time.
- Your account: until you delete it. Your name and email are then also removed from the audit logs of workspaces you were in. Invoices are kept as long as tax law requires.
7. Cookies and similar storage
- A session cookie keeps you signed in and secure. It is needed for the app to work.
- Your analytics choice is kept in your browser’s storage, so we don’t ask again.
- Only if you accept analytics: PostHog stores a random id in a cookie and browser storage to count visits and record how pages are used. Replays mask every form field, and in the app every piece of text.
There are no advertising or cross-site tracking cookies. Change your choice any time with “Cookie settings” at the bottom of the site.
8. Your rights
- See and correct your profile in Settings → Profile, and delete your account there. Your workspaces must have another owner, or be deleted, first.
- Download your backups at any time. For a copy of your account data, write to us.
- Object to or limit how we use your data, or withdraw consent for analytics.
Write to [email protected] for anything not in the app; we answer within one month. You can also complain to your data protection authority. More on how backupd handles personal data: GDPR at backupd.
9. Security and breaches
How we protect data is described on our security page. If a breach affects your data, we tell the workspace’s owners without undue delay, and the supervisory authority within 72 hours where the law requires it.
10. Changes
If we change this policy in a way that matters, we will tell you by email or in the app before it takes effect.