Enterprise
The infosec questionnaire is below, answered. The deployment model is single-tenant per customer for the first ten customers. The audit log is tamper-evident. Bring the questionnaire your team uses; we already answered the rest.
Security posture
SOC 2 Type 1 in progress
Audit underway with a Big Four firm. Target Q3 2026. Type 2 follows, Q1 2027. Customer questionnaires accepted today; we ship a complete answer pack within five business days.
Single-tenant per customer
The first ten customers each get their own database, their own bucket prefix, their own ElevenLabs workspace. No shared scoring queue. No cross-tenant data path.
Row-level security on every table
Postgres RLS bound to tenant id. Eighteen policies across the schema. A query that forgets the tenant filter returns zero rows by design, not by hope.
Broken-glass production access
Production transcripts are unreadable by Sales Lab staff by default. Access is time-bound, MFA-required, and recorded in a tamper-evident audit log the customer admin can review.
Per-rep TOTP MFA, optionally enforced
Every user can enable TOTP. Admins can require it company-wide with one toggle. Magic-link sign-in continues to work for the rep who has not set up TOTP yet, until the admin flip.
Data residency, US by default
Database in us-east-1 (Supabase), voice in US-East (ElevenLabs), scoring in US (Anthropic), email in US (Resend). EU and CA residency for the customer who needs it; ask.
Deployment
The deployment model is shaped for the first ten customers. Each gets a single-tenant deployment, a senior solutions engineer, and a live tenant the next day.
Kickoff call
Forty minutes. Pitch, pricing, top thirty objections, top three deal stages, the call type that costs you the most when it goes badly.
Tenant provisioned
Your subdomain, your database, your bucket prefix, your voice workspace. SSO endpoint registered. Audit log live.
Scenarios built
Three scenarios shaped around your most-expensive call type. Reviewed by the founder. Approved by your admin before reps see them.
Reps run calls
Magic-link invites go out. The first rep takes their first call. The first scorecard returns inside ten seconds of hangup.
Procurement Q&A
Each answer is the answer we already gave your peer. Copy it into your questionnaire as-is. Send the questionnaire to ben@tamras.co for anything we did not pre-answer here.
Customer records and transcripts in Supabase Postgres (us-east-1). Audio blobs in private S3-compatible storage with signed-URL access only. Voice synthesis on ElevenLabs (US-East). Scoring on Anthropic Claude (US). Outbound email via Resend (US). All in transit on TLS 1.3. All at rest on AES-256.
Nobody by default. Production access is broken-glass, MFA-required, time-bound, and logged in a tamper-evident audit trail your admin can review. Customer admins read every transcript via RLS-bound queries.
A complete tenant export as a JSON archive runs from /admin/data and returns under thirty seconds. A signed delete request runs on a seven-day cooling-off period, then removes every derived state including subprocessor data.
Supabase (database, auth, storage), ElevenLabs (voice synthesis), Anthropic (LLM scoring), Resend (transactional email), Upstash (Redis rate limiting), Stripe (billing), Vercel (hosting). The list is in the DPA and changes only with thirty days written notice.
The admin controls retention from seven days to ten years. The default is three hundred and sixty-five days. Audio is deletable independent of transcripts. Scorecards are retained as long as the parent session, then purged together.
No. Customer transcripts and scorecards are never used to train a foundation model, ours or a vendor's. Anthropic and ElevenLabs zero-data-retention modes are enabled on the production keys.
PII never leaves the customer's tenant boundary. We do not email third parties on the customer's behalf. We do not share data across tenants. The audit log records every read by name, role, and timestamp.
A senior solutions engineer takes a kickoff call, ingests the customer's pitch and top objections, builds the first three scenarios, and hands the admin a live tenant inside twenty-four hours. The customer's reps run their first calls the next day.
Salesforce, HubSpot, Slack, Resend, Stripe. Each one is shipped with a default schema and an opinionated config. Anything else is a roadmap conversation, not a checkbox.
PagerDuty rotation, sub-fifteen-minute acknowledgement, customer notification on confirmed Sev 1 or Sev 2 within one hour. Post-mortem published to the customer's admin within five business days of resolution.
For your CISO
The team comes out of Gong, Mindtickle, Second Nature, and Hyperbound — your procurement reviewer has likely seen our work before, under a different banner.
Or the public version at /legal/security.
Ready for the conversation
Five minutes. One scenario. One honest scorecard. The rest of your stack reports on what already happened.