Security and data
Where your data lives, how keys and webhooks are protected, how long records are kept, and who processes data for DialerSeat.
This page answers the questions a security review asks. For a questionnaire, a data processing agreement or anything not covered here, email sales@dialerseat.com.
Where it runs
- The API, console and miniplayer run on Vercel and are served over HTTPS only.
- Data is stored in PostgreSQL on Supabase, in the AWS us-east-2 region (Ohio, United States).
- Developer-platform tables have row-level security switched on: they are reached only through DialerSeat's own server code, never directly from a browser.
API keys
- Secret keys are stored only as SHA-256 hashes. The full key is shown once, when it is created; after that nobody, including DialerSeat, can read it back.
- Every key ends in a checksum, so a mistyped or truncated key is refused before any lookup.
- Live secret keys are refused from web pages: a request carrying a browser Origin header gets 403 and nothing runs.
- IP limits: a secret key can be limited to your servers' addresses or CIDR ranges (IPv4 or IPv6). Requests from anywhere else get 403 even with the right key.
- Publishable keys only work from the website origins you allow, and can only open the miniplayer.
- Revoking a key is immediate. Revoked keys are kept, marked revoked, so a leak can be traced.
- Each key may make 25 requests a second, with bursts to 50.
Miniplayer sign-in
- Your users sign in to the miniplayer with a session your server creates. Session tokens last 15 minutes and are stored hashed.
- What a user can dial follows your own teams, roles and campaign access, sent from your server.
- There is no live listening, whisper or barge on calls.
Webhooks
- Every delivery is signed with HMAC-SHA256 over the timestamp and the body, in the
DialerSeat-Signatureheader, with a secret only you and DialerSeat hold. Check it before trusting a delivery. - Failed deliveries are retried for 72 hours, then marked failed.
- Webhook addresses on private networks (10.x, 192.168.x, 172.16-31.x, link-local) are refused.
Sandbox and live
Sandbox and live data are kept apart. A sandbox key sees only sandbox records and never places a call; a live key sees only live records. Switching a project between them moves nothing.
How long data is kept
- API request log (shown in the console): 30 days.
- Webhook delivery attempts: 30 days.
- Miniplayer sign-in tokens: 7 days, hashed.
- Calls, seats, campaigns, dispositions, do-not-call lists and the billing ledger: kept while your project exists, because they are what you and your users are billed on and what compliance questions are answered from.
Payments
Cards are taken by Stripe in a secure form inside the console. Card numbers go to Stripe and never reach DialerSeat's servers; DialerSeat keeps only the brand and last four digits.
Who processes data for DialerSeat
- Vercel: hosting of the API, console and miniplayer.
- Supabase: the database.
- Clerk: sign-in to the console.
- Stripe: card payments.
- Telnyx: the telephone network for live calls.
Reporting a vulnerability
Email sales@dialerseat.com with what you found and how to reproduce it. Please do not test against other projects or place live calls to do it.
Related:Billing and signups, Errors and limits, OpenAPI and AI assistants (MCP) and Build your integration with AI.