How ReviveDB protects your backups
Temporary database logins, encrypted credentials and recovery points stored in the EU. Secret values are never copied.
Summary
No shared database password
Connect through your Supabase account. Most projects do not need your database password.
Short-lived logins
Each backup gets its own short-lived login, then it is removed.
Read-only access
The backup login reads what it needs. It cannot change your data.
Stored in the EU
Cloudflare R2, EU jurisdiction, AES-256 at rest. Processing in Amsterdam.
Backups are checked
Every database backup is restored into isolated PostgreSQL and compared before it becomes available.
Deletion removes the copies
Delete a project and its recovery points go with it. If storage is unavailable, deletion is retried for up to 30 days.
What the backup login can do
The temporary database login reads your data. Supabase OAuth grants separate management permissions for setup and recovery.
What it reads
- Your database and Auth data, including rows that RLS protects.
- Storage files, bucket settings and Edge Function code are captured through separate Supabase APIs.
What it cannot do
- Write to your database, create roles, replicate, or give itself more rights.
- Keep working after the backup.
- Send the backup login to a server that is not Supabase.
Access and permissions
Security documents
Security questions?
Ask us about access, retention, deletion, subprocessors or security reviews.