Skip to content

How ReviveDB protects customer backup data.

Recovery points can contain personal data. These controls limit how ReviveDB accesses, stores, verifies and deletes it.

Limited purpose
Customer data is used only for backup and recovery, never for advertising or analytics.
Temporary source access
A unique read-only login is created for each backup. Its password expires after one hour, and cleanup is requested after the run.
Controlled deletion
Recovery points expire automatically and failed deletions are retried.

Data access boundaries

Processed for backup and recovery

  • Read the database and Auth, including rows protected by Row Level Security.
  • Capture Storage files, Edge Function bundles and supported project configuration.
  • Restore into isolated Postgres and compare the result with the source inventory.

Not collected or permitted

  • The temporary database login cannot write to or change the source database.
  • The temporary database login cannot create roles or databases, replicate, act as superuser or elevate itself.
  • ReviveDB does not copy Edge Function or Vault secret values.

Security controls

Storage and data location

Recovery points use Cloudflare R2 with AES-256 encryption at rest and TLS in transit. The production storage endpoint is restricted to R2's EU jurisdiction, and signed download links expire after five minutes.

Credentials and account access

OAuth grants and fallback credentials use authenticated encryption with a separately supplied key. They are decrypted only by the backend operations that need them and are never returned through the API.

Account and operational access

Production sessions use secure, HttpOnly cookies and can be revoked. Security events are recorded, and logs redact credentials, authorisation headers, email addresses and connection strings.

Isolated restore verification

Every database backup is restored into isolated temporary Postgres and compared with the source inventory. Storage files and Edge Function bundles are hash-checked, scratch data is removed, and a mismatch fails the run.

Documents for your review

Security and privacy reviews

If you are assessing ReviveDB for personal data, we can answer questions about access, retention, deletion, subprocessors or your security questionnaire.