Security, regions and retention

ReviveDB stores the credentials required to read and restore a Supabase project. Credentials are encrypted at rest and are not exposed through customer-facing APIs.

Credentials

• Supabase OAuth tokens, fallback database credentials and service-role keys are encrypted at rest.
• Decrypted credentials are only read by the backup or recovery pipeline that needs them.
• Saved credentials are never returned through GraphQL responses or download links.
• Disconnecting a source removes saved source credentials and stops future backups; existing recovery points remain until deleted or expired.

Recovery-point storage

• Managed storage is separate from Supabase, so a provider or account incident does not remove both copies at once.
• Stored objects use server-side encryption and explicit region-specific destinations.
• Every Storage object is read back and checked by byte size and SHA-256 after upload.

Regions

You choose a configured data region for new recovery points. The selected destination is recorded with the backup. ReviveDB does not silently move a backup to another region when the selected destination is unavailable.

Open image

Retention and usage

Retention is a configurable maximum, not a promise that a recovery point exists for every day in the period. The number retained also depends on successful runs and the account-wide retained-data allowance.

• Expired snapshots are removed automatically according to the project policy.
• Content-addressed Storage blobs are removed only after their final retained snapshot reference expires.
• Optional retained capacity is never enabled automatically.

Privacy and operational controls

Read the public Security page, Privacy notice, DPA and subprocessor list for the current contractual and processing details.