Privacy Policy (DRAFT)
This is a draft, not legal advice. A lawyer or Lord Lodhi will review before publication.
Last updated: 2026-11-20
1. Who we are
SynteCall is operated by [Company legal name], [address]. Contact: [contact email]
2. What data we collect
We collect the following categories of data:
Account data
- Name, email address, password hash (stored by Supabase Auth)
- Workspace name, timezone, business hours
Business profile
- Company name, website, industry (optional)
Contacts uploaded by customers
- Names, phone numbers, email addresses, custom fields
- Consent flags and opt-out status
Call data
- Audio recordings of calls
- Full transcripts of calls
- AI-generated summaries and structured data
- Call metadata: direction, duration, status, cost, timestamps
WhatsApp messages
- Message content (text, media captions)
- Sender and recipient phone numbers
- Delivery status and timestamps
Calendar data (Google Calendar)
- Free/busy information for the selected calendar
- Events created, changed or cancelled by the AI agent on behalf of the caller
- Calendar list (names and IDs) so the customer can pick one
Connected-account credentials (encrypted)
- Twilio Account SID and Auth Token
- Vapi private API key
- GoHighLevel Private Integration Token and Location ID
- Google OAuth refresh token (for Calendar)
- These are encrypted at rest with AES-256-GCM and never returned to the browser
Usage and billing
- Plan, subscription status, current period end
- Call counts and costs (for display only; customers pay providers directly)
Technical data
- IP address, browser user agent, request timestamps (standard web logs)
3. Why we collect it (purposes and legal bases)
| Purpose | Legal basis (GDPR) |
|---|---|
| Provide the service (create agents, make/receive calls, store recordings, transcripts, summaries) | Contract |
| Run the Lite CRM (contacts, calls, notes, tags) | Contract |
| Sync data to GoHighLevel if the customer connects it | Contract |
| Send WhatsApp messages the customer initiates | Contract |
| Check calendar free/busy and book appointments the agent makes | Contract |
| Generate scripts with the AI script writer | Legitimate interest |
| Security, fraud prevention, debugging | Legitimate interest |
| Billing and subscription management (Stripe later) | Contract |
| Comply with legal obligations (tax, law enforcement) | Legal obligation |
We do not use personal data for advertising, profiling beyond what is needed for the service, or selling to third parties.
4. Providers we share data with and why
| Provider | What they receive | Why |
|---|---|---|
| Supabase | All application data (Postgres, Auth, Storage) | Hosted database, auth, file storage |
| Vapi | Agent configuration, call audio streams, tool calls | Runs the voice AI and connects to Twilio |
| Twilio | Phone numbers, call control, WhatsApp messages | Carrier connectivity and WhatsApp |
| Google (Calendar API) | Free/busy queries, event create/update/delete, calendar list | Appointment booking feature |
| AI script writer provider (FreeLLMAPI / Groq / Cerebras) | Script generation prompts (no personal data) | Generate with AI feature |
| Stripe (later) | Subscription data, payment method token | Billing |
Each provider processes data only on our behalf under a data processing agreement or equivalent terms. We do not share customer data with any other third parties.
5. How long we keep data
- Account and workspace data: until the customer deletes the workspace
- Calls, recordings, transcripts, summaries: 2 years from the call date, then deleted
- Contacts: until the customer deletes them or the workspace
- WhatsApp messages: 2 years from receipt
- Calendar events created by the agent: kept in Google Calendar; we store only the appointment record (id, time, contact link) for 2 years
- Encrypted credentials: deleted immediately when the customer disconnects the integration
- Web logs: 30 days
Customers can request earlier deletion at any time (see Your rights below).
6. Security
- All connected-account credentials are encrypted at rest with AES-256-GCM using a per-workspace key derived from a master ENCRYPTION_KEY. The key never leaves the server.
- Access tokens (Google, Vapi, Twilio) are fetched on demand from the encrypted refresh token or credentials and are never stored.
- TLS in transit for all connections.
- Row-level security in Supabase ensures each workspace sees only its own data.
- No secrets appear in API responses, browser network tabs, or logs.
7. Your rights
You (the customer) may at any time:
- Access: request a copy of all personal data we hold about you and your contacts
- Delete: request deletion of your workspace and all associated data
- Export: receive a machine-readable export (JSON) of contacts, calls, recordings, transcripts, notes, tags, and WhatsApp messages
- Rectify: correct inaccurate data
- Restrict or object: ask us to stop processing specific data (may limit the service)
- Portability: receive data in a structured format to move to another service
To exercise these rights, email [contact email]. We respond within 30 days.
8. Google user data
This section applies only to data received through the Google Calendar API.
- We only use Google Calendar data to check free times and to create, change or cancel appointments that the AI agent books on behalf of the caller.
- We never sell Google user data.
- We never use Google user data for advertising, profiling, or training machine learning models.
- We comply with the Google API Services User Data Policy, including the Limited Use requirements.
- We request only the narrowest scopes needed: calendar list, free/busy, and event read/write on the single calendar the customer selects.
- The customer can disconnect Google Calendar at any time, which deletes our stored refresh token and revokes our access.
9. Children
SynteCall is not directed to children under 16. We do not knowingly collect personal data from children. If we learn we have collected such data, we will delete it promptly.
10. Changes to this policy
We may update this policy. Material changes will be announced by email and/or an in-app banner at least 30 days before they take effect. The Last updated date at the top reflects the latest version.
11. Contact
Questions about this policy or your data: [contact email]