How your data is handled.
You're uploading lead contact data — emails, phones, IP addresses. Here's exactly what happens to it, in plain language instead of a compliance checklist.
Per-account data isolation
Every table — leads, scores, uploads, your team, your lists — is scoped by a database-level policy tied to your account, enforced by Postgres itself on every query. Not application code that could be forgotten in one new route; a policy the database won't let any query bypass.
Encrypted in transit and at rest
Every connection to the app and the API runs over HTTPS. The underlying database and file storage are encrypted at rest by our infrastructure provider, the same default every serious cloud database runs on.
Raw files scoped to your account, not one login
The CSV or Excel file you upload is readable by any signed-in member of your account, not just the person who uploaded it — and it stays that way even after that teammate leaves. Deleting an upload, deleting your account, or an automatic retention purge all remove the original file too, not just the processed rows.
API keys, hashed and revocable
A read-only API key for pulling your data programmatically is shown to you exactly once, at creation. We store only its cryptographic hash — the same principle as a password — so the real key exists nowhere but wherever you saved it. Revoking one blocks it immediately, on its very next use.
Signed, verifiable webhooks
Every webhook we send your systems carries a signature computed from a secret only your account holds, plus a timestamp, so you can verify a request genuinely came from us and reject a stale or forged one.
We never see your card
Billing runs through Stripe. Your card details go straight to them — we store your subscription status and plan, never a full card number.
Also worth knowing
- Every account action a teammate can take — invites, role changes, billing, deletions — is written to an audit log any teammate can review, not just the owner.
- Sensitive actions (uploads, API key creation, evidence-pack exports) are rate-limited so a compromised session or a runaway script can't hammer your account.
- Signing in uses Supabase's own authentication, with a bot-resistant challenge on the login and signup forms.
- Error monitoring flags real problems quickly instead of a customer being the first to notice.