PII redaction before AI & logs
SSN, DOB, phone, and bank routing/account are scrubbed before anything reaches a model or a log.
Enterprise-grade security
Secure by design.
Secure by design.
Engineered, not bolted on.
Sales calls collect sensitive data — SSN, DOB, bank details. So security here is the architecture, the engineering discipline, and the way it ships — enterprise-grade by design, development, and operation. Not a checkbox bolted on at the end.
Zerosecrets reach the client
Pre-AIPII redaction
Per-tenantdata isolation
Signedwebhooks, replay-proof
Data protection
Never travels
Never travels
unguarded.
Protection is enforced at the layer where it matters, before anything reaches a model, a log, or a screen.
Encryption in transit & at rest
Every connection is TLS-encrypted in transit, and stored data is encrypted at rest by default.
Zero-retention AI
The model runs server-side with zero data retention — redacted transcripts are never logged or used to train models.
No secret ever reaches the client
Provider keys and signing secrets live server-side only — the browser never holds anything sensitive.
Access & tenancy
Sealed off from
Sealed off from
every other team.
Isolation is enforced in the database and reinforced by least-privilege access and full audit trails. Defense in depth, by default.
Org-scoped auth + MFA
Every session is bound to an organization, and multi-factor authentication protects every login.
Row-level security isolation
Postgres row-level security enforces per-tenant boundaries in the database — not just app checks.
Least-privilege access
Services and roles get only the access they need — nothing reaches data it has no reason to touch.
Audit logging of sensitive actions
Access to and changes against sensitive data are recorded for review, attribution, and accountability.
Built to OWASP
Hardened at
Hardened at
every boundary.
Application security is a discipline applied to every request, input, and dependency — mapped against the OWASP Top 10 and enforced in the build itself.
01
Input validation everywhere
All external data — requests, payloads, webhooks — is schema-validated before it's ever processed.
02
Rate limiting + body caps
Per-tenant rate limits and strict payload-size limits blunt abuse and resource-exhaustion attacks.
03
Strict headers + CSP
A locked-down Content-Security-Policy and hardened response headers shrink the browser attack surface.
04
HMAC-verified webhooks
Every inbound event is signature-checked with a per-tenant secret and replay-protected.
05
Structured errors, no leaks
Errors return safe, structured responses — internals, stack traces, and secrets never reach a client.
06
Dependency & secret scanning
Every build scans dependencies for known vulnerabilities and blocks committed secrets before they ship.
Secure development lifecycle
A step in shipping,
A step in shipping,
not an afterthought.
Write — security in the loop
Changes are written against established patterns — validated inputs, scoped access, no secrets in code.
Review — on every change
Nothing merges without human review — security-sensitive paths get extra scrutiny before they land.
Scan — dependency + secret
CI scans every build for vulnerable dependencies and committed secrets, blocking risky changes automatically.
Gate — pre-launch security gate
A security gate and penetration test must pass before any real customer data ever flows through the system.
Ship — ongoing monitoring
In production, the system is monitored continuously so anomalies surface fast and get addressed quickly.
Security FAQWhat security
What security
teams ask first.
No. Standby runs models server-side with zero data retention — redacted transcripts are never logged for training and are never used to train any model, ours or a provider's. Your calls stay your calls.
Isolation is enforced in the database with Postgres row-level security under org-scoped authentication, so a tenant can only ever see its own rows. It's defense in depth — the boundary holds even if application logic is wrong — and it's reinforced by least-privilege access and audit logging.
Org-scoped authentication with MFA is standard, and SSO is available for enterprise plans so your team can sign in through your existing identity provider. Talk to us about your provider and we'll walk through the setup.
Yes. We're happy to complete security questionnaires, share our compliance posture, and walk your team through the architecture, controls, and development lifecycle. Reach out and we'll route you to the right materials and people.
Sensitive PII — SSN, DOB, phone numbers, and bank routing/account details — is redacted before anything reaches a model or a log. Data is encrypted in transit and at rest, and no provider key or signing secret ever reaches the client.
Retention is configurable per tenant, including long-term encrypted retention for regulated lines that require it. Call handling is consent-aware, with per-state disclosure logic for two-party-consent states and California's AB 2905 AI-disclosure rule.
Bring your security team
Put it in front of
Put it in front of
your security team.
Walk the architecture, controls, and lifecycle with us — questionnaire welcome. Built for the most sensitive data on a sales call.
No credit card · assist-only · we never auto-dial