Where is my SalesCrew data stored?
In a Supabase project that belongs to your instance alone, in the region you choose at setup, backed up every day.
The short answer
- SalesCrew stores each client's data in that client's own Supabase project: its own Postgres database, file storage and edge functions.
- You choose the region of your SalesCrew project at provisioning, so data residency follows your choice.
- SalesCrew keeps API keys and mailbox credentials in Supabase Vault inside your project and never displays them after entry.
- SalesCrew backs up every instance daily, and point-in-time recovery is an add-on at $120 a month.
One client, one database
SalesCrew is a single-tenant CRM. When your instance is created, it gets its own Supabase project: a Postgres database for your records, storage for your files, and edge functions that run your inbox sync, cadences and MCP server. Nothing about your pipeline sits in a table shared with another company.
That's what makes the rest of the answers simple. Your region is the project's region. Your backup is your database's backup. And when you export your data, you're taking a dump of a database that only ever held your records.
Where each kind of SalesCrew data lives
| Data | Where it's stored | Who can reach it |
|---|---|---|
| Contacts, companies, deals, notes, tasks | Postgres in your Supabase project | Your users and tokens, by their access scopes |
| Email threads and attachments | Postgres and storage in your project | Users scoped to that mailbox's channel |
| API keys, mailbox passwords | Supabase Vault in your project | Integrations at run time; never shown again |
| Audit log of every action | Postgres in your project | Read in the app; each row names the user, token or agent |
| Daily backups | Your project's own backup | Point-in-time recovery with the add-on |
SalesCrew architecture, September 2026.
Who can see what inside your instance
Row-level security runs on every table. On top of it, SalesCrew applies three access scopes to each user: channel, Upwork profile and area. Your MCP tokens carry the same scopes, so an AI client connected by a teammate sees exactly what that teammate sees, and no more.
Every action is written to the audit log with the actor behind it: a person, a token or an agent. You can read who changed a deal stage, which token pulled a contact list, and what an agent drafted. The security page walks through each control.
Ask where the backup lives, too
Questions
- Can I choose which region my SalesCrew data lives in?
- Yes. You pick the region when your SalesCrew instance is provisioned, and your Supabase project is created there. Records, files and the functions that process them all run in that one project. Data residency follows the region you chose.
- Does another SalesCrew customer share my database?
- No. SalesCrew is single-tenant: one Supabase project per client instance, with its own Postgres, storage and edge functions. Your records live only in your project. Another customer's instance has its own database, and neither can query the other.
- Where do my SalesCrew API keys and mailbox passwords go?
- Into Supabase Vault inside your own project. SalesCrew never shows a stored credential again after you enter it. Integrations read the key from the vault at run time, and you can replace or remove it in Settings at any point.
- Which companies process my data for SalesCrew?
- Three: Supabase hosts your database, Vercel serves the SalesCrew app, and Anthropic runs the AI features. With bring-your-own-key, AI calls use your own Anthropic key, stored in your vault, for $99 a month.