Privacy Policy

Last updated: January 2026

1. Data We Collect

VoiceAI collects the following categories of data:

Account Data: Name, email, company name, billing information (processed by Stripe). We do not store credit card numbers.

Voice Data: Call audio recordings, real-time voice streams (processed by AssemblyAI for transcription and voice agent responses), and call metadata (phone numbers, duration, timestamps).

AI Processing Data: Transcripts, LLM prompts and responses, sentiment analysis, call summaries, and analytics. This data is processed by the customer's configured LLM provider (OpenAI, Anthropic, Google, etc.).

Usage Data: API calls, feature usage, agent configurations, CRM data (contacts, leads, appointments) entered by the customer.

2. How Voice Data Is Processed

When a call occurs, voice data flows through the following pipeline:

  1. Twilio handles the PSTN connection (phone number routing, call setup)
  2. VoiceAI Bridge streams audio between Twilio and AssemblyAI in real-time
  3. AssemblyAI performs speech-to-text and generates AI voice agent responses
  4. LLM Provider (customer-configured) processes the transcript to generate responses
  5. Supabase stores transcripts, call logs, and analytics in the customer's tenant

Call audio recordings are stored in Supabase Storage and are accessible only to the customer's tenant. Customers can delete recordings at any time. VoiceAI does not access, listen to, or use customer call recordings for any purpose.

3. Data Retention

Data retention is controlled by the customer:

  • Call recordings: Retained until customer deletes them. No automatic deletion unless configured.
  • Transcripts & analytics: Retained for the life of the account.
  • LLM logs: Request/response data retained for 90 days for debugging, then auto-deleted.
  • Account data: Retained until account termination. Deleted within 30 days of termination.
  • No-retention mode: Available on Scale plan — transcripts processed then immediately deleted, no recordings stored.

4. Subprocessors

We use the following subprocessors to deliver the service. Each is bound by data processing agreements:

SubprocessorPurposeData AccessedRegion
TwilioTelephonyPhone numbers, call metadata, audio streamUS/EU
AssemblyAISpeech processingAudio stream, transcriptsUS
SupabaseDatabase & authAll stored dataUS/EU
StripeBillingEmail, billing address, card tokenGlobal
LLM ProvidersAI generationTranscript text, promptsVaries
ResendEmail deliveryEmail address, message contentUS

5. Data Security

  • All data encrypted in transit (TLS 1.2+) and at rest (AES-256)
  • Per-tenant data isolation via Row Level Security (RLS) policies
  • API keys stored as SHA-256 hashes (never stored in plaintext)
  • Webhook signatures use HMAC-SHA256
  • SSO/SAML 2.0 available for enterprise customers
  • Audit trail for all administrative actions
  • Customer-managed encryption keys available on Scale plan

6. Your Rights (GDPR/CCPA)

Customers have the right to:

  • Access their data (export via API or dashboard)
  • Delete their data (account deletion removes all tenant data)
  • Export all data (CSV/JSON export available in dashboard)
  • Object to processing (disable specific features)
  • Data portability (API provides full data access)

For data subject requests, contact: privacy@voiceai.example

7. AI-Specific Disclosures

  • AI voice agents are clearly identified as automated in call recordings and transcripts
  • Customer call recordings and transcripts are not used to train AI models
  • LLM providers may retain transcript data per their own policies — customers should review their LLM provider's data retention terms
  • Voice cloning requires explicit consent documentation from the voice owner
  • AI-generated call summaries are labeled as AI-generated in the dashboard

8. Contact

Privacy questions: privacy@voiceai.example

See also: Data Processing Addendum