Privacy & GDPR

We process your email address, encrypted OAuth or project credentials, backup metadata, database backups, Storage file bytes, Edge Function bundles and recovery manifests needed to provide the service. We do not sell personal data or use backup contents for advertising.

For account, security and service administration data, ReviveDB acts as controller. For personal data contained in a customer recovery point, ReviveDB normally acts as processor under the customer's instructions and our Data Processing Agreement.

We process this data to authenticate you, run and verify backups, provide restores, secure the service and meet our legal obligations. Where GDPR applies, processing is based on performing our agreement, legitimate security interests or your consent.

• Account creation, authentication, backups, restores and service email: steps before and performance of our contract.
• Fraud prevention, access security, operational logs and proportionate service feedback: our legitimate interest in operating and securing ReviveDB.
• Invoices, tax records and legally required disclosures: compliance with legal obligations.
• Optional processing presented with a consent control: consent, which can be withdrawn as easily as it was given.

Limited server-side product lifecycle analytics use our legitimate interest in measuring activation, reliability and paid conversion. The balancing assessment is documented and you can object from the privacy settings.

We use a strictly necessary session cookie to keep signed-in accounts secure. Vercel Web Analytics measures aggregate use without setting cookies; query strings are removed before an event is sent and login pageviews are excluded. PostHog receives a limited set of product lifecycle events from our server, such as account creation, connecting a project, backup results and starting checkout. Events use a keyed pseudonym instead of your account ID and do not contain your email address, IP address, project name, URL, credentials, database contents or dashboard content. This processing uses our legitimate interest in understanding whether ReviveDB works and where customers stop during setup. It does not use browser cookies, autocapture, pageviews or session recording. On signed-in dashboard pages, PostHog's browser library loads only when you deliberately open our feedback survey. The survey stores anonymous display state in local browser storage but sets no cookie. The PostHog project is configured with 30-day retention for product events, survey events and submitted feedback. You can object from the privacy settings.

Managed backups are protected with provider-side AES-256 encryption at rest and are currently stored in Europe. Project credentials are encrypted separately with libsodium secretbox and decrypted only when the backup or recovery pipeline needs them.

Account information is retained while your account is active and as legally required. Backup retention follows your plan. You may request access, correction, deletion, restriction, portability or object to processing, subject to applicable law. Signed-in users can export their data, permanently delete their account and managed backups, or submit a formal privacy request from the dashboard. Deleting your account also cancels any active subscription immediately. Billing records held by our payment processor, including invoices and the name and address on them, are kept after deletion for as long as tax and accounting law requires. Formal requests are recorded with their response deadline.

Account and project data are kept while the account exists. Failed backup metadata and application logs have a 30-day target; PostHog product and survey events are configured for 30 days; audit events for up to 365 days while the account exists; notification markers for 90 days; and closed privacy-request metadata for up to three years while the account exists. Backup retention follows the selected plan. Dutch invoice and tax records may be retained for seven years. Provider backups and deletion queues may take the documented operational period to expire, and deletion failures are retried.

You can request access, correction, deletion, restriction, portability or object to processing where the relevant legal conditions apply. You can withdraw consent without affecting earlier lawful processing. ReviveDB does not make decisions based solely on automated processing that produce legal or similarly significant effects. Providing an email address and authorised database access is necessary to create an account and deliver backups; without them we cannot provide those parts of the service.

We use carefully selected infrastructure, storage and email providers to operate the service. They process data only for the services they provide to us. We use appropriate safeguards when personal data must be transferred outside the EEA. Our current providers and purposes are published on the subprocessors page.

We receive account and project information directly from you. If you choose Google or Supabase OAuth, we also receive the verified account identifiers, email address, scopes and project information those providers make available. Backup contents come from the databases and storage locations the customer instructs us to access.

Privacy requests can be submitted through our contact page. You may also complain to the data-protection authority where you live or work.