Trust
Every call your AI agent answers touches your business data and your callers' data. Here's exactly how it's handled.
All traffic between your browser, our servers, and every category of provider below is encrypted in transit with TLS. Data at rest — business records, call transcripts, account details — is encrypted with AES-256 via our database provider.
Every table that holds business data has row-level security policies enforced by the database itself, not just application code — a business's row can only be read by that business's own authenticated session, regardless of which page or API route is asking. We don't just assume this works: we test it directly against the live database — generating a real session for one business and confirming it genuinely cannot read another business's records — rather than trusting the policy configuration alone.
To actually answer calls, book appointments, and process payments, we share data with the categories of providers below — never more than the feature requires. We may add more as we add features; when we do, we update this table and the Privacy Policy before a new provider starts processing your data.
| Category | Purpose | Data shared |
|---|---|---|
| AI voice & conversational processing | Powers your agent's voice, language understanding, and generated responses during a call; also used directly by us after a call for sentiment/name analysis, menu extraction, and demo generation | Call audio (streamed in real time), agent configuration, knowledge base content, conversation transcripts |
| Telephony & real-time call infrastructure | Phone number provisioning, call routing, SMS, and the infrastructure carrying call audio to our AI processing in real time | Caller phone numbers, call metadata, SMS message content, call audio in transit |
| Calendar integration (opt-in) | Checks availability and manages appointments on your calendar | OAuth tokens, calendar availability — never the content of your other existing events |
| Payment processing | Billing and subscription payments | Billing details, subscription plan — we never see or store raw card numbers |
| Database & authentication | Database and authentication | All structured application data |
| Email delivery | Transactional and notification email delivery | Recipient email address, email content |
| Application hosting | Hosts our web application and API | Server logs, IP addresses, and application data in transit |
Full detail on what’s collected and why lives in the Privacy Policy. A list naming our specific providers is available on request — email security@voicesse.io.
Your AI agent may record and transcribe calls. Every agent automatically opens each call with a spoken disclosure that it's an AI assistant and that the call may be recorded — this is built into the Service itself and can't be turned off or overridden by your agent's greeting or instructions. Depending on your state or country, you may still be legally required to obtain additional consent beyond this baseline notice — that responsibility is yours, not ours, and we say so plainly rather than burying it.
Full detail, including the public demo widget, lives in the Privacy Policy.
We don't hold SOC 2 or ISO 27001 certification today, and we'd rather tell you that directly than stay quiet about it. What we do have: encryption in transit and at rest, database-enforced tenant isolation that we test empirically rather than assume, signed webhook verification on every inbound integration, and HTTP security headers (CSP, HSTS, and related) on every page we serve. If a formal certification is a requirement for your business, reach out — we'd rather have that conversation than let a vague claim stand in for it.
If you believe you've found a security vulnerability in Voicesse, email security@voicesse.io directly rather than filing a public issue. We'll acknowledge all reports and won't pursue action against good-faith security research.