Third parties processing your customer data.
Every vendor with access to data flowing through celliq, the data they touch, where it goes, and the legal basis for transfer. Updated in real time from celliq's internal register.
ElevenLabs scope upgrading from TTS-only to full voice runtime (see decision). Effective 2026-06-01. No change to data classes processed.
These vendors process customer data on every call, regardless of which integrations are connected.
- Phone numbers (E.164)
- Call audio (recorded segments)
- Call metadata (duration, disposition)
- Call audio (live + transcribed)
- Agent script + dynamic context
- Voice profile metadata
- Call transcript snippets
- Pre-call brief + plan context
- All structured customer data — agents, calls, outcomes, contacts, accounts
- Call recordings + transcripts (Cloud Storage)
- Compute logs + traces
- Pseudonymised analytics events (BigQuery)
- User identities (email, name, login timestamps)
- Hashed user_id + tenant_id (no raw PII)
- UI interaction event names + non-PII properties
These vendors only receive data if you've connected the corresponding integration in Settings → Integrations. Disconnect any time to stop processing.
- Prospect names + contact info
- Account data
- Call summaries + structured outcomes
- AE availability
- Meeting attendees + content
- Call summaries
- Recording links (signed URLs, 24h TTL)
Recent changes
Notification policy
Material changes to this register trigger a 30-day in-app banner notice to your workspace admins (our compliance policy). Material changes include: adding a sub-processor, removing one, or upgrading the scope of an existing one. Email notifications ship at GA when invite-flow infrastructure lands.
Audit-source: data/sub-processors.yaml in the celliq repo · CODEOWNERS-gated · changes require James + (post-counsel) external counsel approval.