Supabase backups and GDPR
Supabase says its managed backups stay in the AWS region selected for the project, alongside the database, Auth and Storage. Choose a specific EU region if your commitment requires EU hosting. Your own exports and backups are separate copies with their own processing locations.
Pick a country, not "Europe"
Supabase's GDPR guide points out that its Europe option includes London and Zurich. Both have an adequacy decision, but neither is in the EU. If your commitment to customers says EU, choose a specific EU region such as Frankfurt, Paris, Ireland or Stockholm.
Supabase's October 2026 data-residency FAQ says core data and managed backups stay in the selected region. It also identifies processing that can occur elsewhere, including support access, telemetry and Storage CDN delivery. Keep those transfers separate from the location of your own exported copies.
Every copy is a processing location
| Where the copy lives | What to check |
|---|---|
| Supabase daily backups or PITR | In the selected project region; review the DPA and other data transfers |
| GitHub Actions artifacts | GitHub is a processor in the United States |
| Your own S3, R2 or B2 bucket | The bucket region and the provider’s DPA |
| A dump on a laptop | Encryption, and whether anyone knows it exists |
| A backup service | Its storage region, DPA and subprocessor list |
Each place belongs in your record of processing activities, and each provider on your subprocessor list if you process data for customers.
Erasure requests and backups
You do not have to rewrite every backup when someone asks to be deleted. The UK regulator's right to erasure guidance accepts backup data being put beyond use: you do not use it for anything else, and it is deleted when the backup expires on a fixed schedule. That means:
- Delete the person from the live project straight away.
- Keep a list of erased user ids and apply it again after any restore, so an old backup does not bring them back.
- Tell the person when the remaining copies expire.
- Keep retention as short as your recovery needs allow. How long to keep Supabase backups goes into choosing that period.
Where ReviveDB fits
ReviveDB stores recovery points in Cloudflare R2 under its EU jurisdiction and processes backups in Amsterdam. Our DPA and subprocessor list are public. Recovery points are deleted when they leave your plan's retention, and when you delete a project or your account.