[ PLATFORM // TRUST & COMPLIANCE ]

Security is an architecture. Not an add-on.

We handle medical intakes, dispatch, and after-hours calls where getting it wrong has consequences. This page describes the controls that are actually implemented — and our legal documents name every provider that touches your data and every message the platform sends.

Current and historical availabilityView Status Page →

[ COMPLIANCE // AUDITED ]

Audited and attested.

[ HEALTHCARE // NEMT ]

HIPAA-aligned handling & BAA.

Protected Health Information is encrypted at rest with application-layer encryption and in transit with TLS, and medical terminology is scrubbed from logs and error reports before durable storage. A Business Associate Agreement is executed before any PHI is processed.

Request a BAA →

[ ENTERPRISE // INFRASTRUCTURE ]

Tenant isolation, enforced in the database.

Every query is scoped to a workspace, with a PostgreSQL row-level-security backstop bound per transaction. A missing scope fails closed at the database rather than leaking across tenants. Read the controls in full in our Security Overview.

Security Overview →

[ TELEPHONY // MESSAGING ]

TCPA & carrier compliance.

Outbound calling and messaging are bound by TCPA calling windows enforced in code, per-tenant campaign registration gates every message, and STOP is honored immediately across programs. Every program we run is enumerated in our Communications Policy.

Communications Policy →

[ ARCHITECTURE // DATA SOVEREIGNTY ]

Your data is yours. We do not share it.

Tenant isolation, enforced twice

Every query is scoped to your workspace, and PostgreSQL row-level security is bound per transaction underneath it. A query that fails to scope returns nothing rather than another tenant's rows.

We don't train on your data

We do not use your call transcripts, routing logic, or knowledge base to train models. The speech and language providers that process your calls do so under agreements that do not permit training on your data, and every one of them is named in our Sub-processors document.

Domain Split Architecture

We separate our standard web application (app.syntaxvoice.com) from our live communications layer (voice.syntaxvoice.com). If our billing dashboard undergoes scheduled maintenance, your live voice routing is entirely unaffected.

[ PROCUREMENT // AUDIT ACCESS ]

Enterprise procurement gateway.

Security FAQ.

Do you sell data?: No. We do not sell, broker, or trade call data, transcripts, or telemetry. Mobile numbers, opt-in data, and messaging consent are never shared with third parties or affiliates for marketing or promotional purposes.
Where is data stored?: Application and voice databases run on AWS RDS in the United States, with recordings and transcripts in S3. Our dashboard is hosted on Vercel. The full list of providers that process data on our behalf is published in our Sub-processors document.
Who else receives call data?: Speech recognition, language model, and speech synthesis providers process call audio and transcripts to deliver the service, and telephony carriers route the calls themselves. Each is named, with the data categories it receives, in our Sub-processors document rather than summarized as an 'e.g.' list.
How is one tenant isolated from another?: Every query is scoped to a workspace, and PostgreSQL row-level security is bound per transaction as a backstop, so a query that fails to scope fails closed at the database rather than returning another tenant's rows.

Request security documentation.

Procurement and IT teams can request our security documentation and completed questionnaires under NDA. Our controls are described in full in the Security Overview. Items marked not yet available are on the roadmap — ask and we'll tell you where they stand rather than leave you guessing.