Data residency and backups
Where your data lives, what we do and do not claim, and what you can verify.
What is true today, stated plainly:
- Primary data is in the United States. The database and file storage are hosted with Supabase on AWS in
us-east-1. The region is a project setting we confirm in the provider's dashboard; the repository cannot prove it. - EU or APAC data residency is not available. There is no customer-selectable region, and no multi-region storage.
- The edge is global. Cloudflare serves the application worldwide; it holds a five-minute cache of knowledge-base retrieval results keyed by workspace and a one-way hash of the query, and request logs for up to 30 days.
- Voice call state is held briefly in a Cloudflare Durable Object, which is not pinned to a country, and is deleted when the call ends.
- Backups: automated daily database backups, retained per our provider plan and never longer than 30 days. We do not represent point-in-time recovery as enabled. The recovery point is up to 24 hours. Uploaded files are not in the database backups. No recovery-time objective is stated and no restore drill has been recorded.
- Sub-processors that may process content (model providers, email, telephony) are listed at
/subprocessors; the contract terms are in the Data Processing Agreement at/dpa.
If your procurement requires a residency guarantee we do not offer, this is the answer; we will not claim one.
To take your data or have it deleted, see /dashboard/settings/data and What you get when you leave.
In the product: /dashboard/settings/data (sign-in required).