Sub-processors
Last updated 9 October 2026
CaptionKit uses the providers below to deliver the service. Each one processes personal data only for the purpose listed, under a written agreement with data-protection terms. For how we use this data, see our Privacy Policy.
For churches in the EU, EEA, UK or Switzerland, we email the account owners of every church whose data we hold at least 14 days before adding a provider that isn't on this page, so you have time to object. If a provider fails or has a security problem, we may move its work to another provider on this page straight away. Customers can request a detailed schedule of each provider's role, locations and contact details. To receive notices wherever you are, at another address, or to request the schedule, email help@captionkit.com.
Speech and language AI
We use specialist providers for speech recognition, translation and text-to-speech. We route each language to the providers that work best for it, and that mix changes over time, so not every provider below is in use at any given moment.
- Providers: AssemblyAI, Deepgram, ElevenLabs, Google (Gemini API), Inworld, Meta, Microsoft Azure, OpenAI, Soniox, Speechmatics
- Data: Live broadcast audio and custom vocabulary; caption text, recent context and translation instructions
- Location: United States. Google may also process data in other countries where it operates, and Microsoft in Australia or the United Kingdom.
Infrastructure, payments and support
- Cloudflare
- Live processing servers, translated audio storage, network
- All service data in transit; transcripts during broadcasts; translated audio; attendee analytics
- United States (storage); global network
- Supabase
- Database, authentication and file storage
- Account details, transcripts, translations, attendee analytics
- United States
- Vercel
- Website and API hosting
- Account and API requests, attendee analytics
- United States; global network
- Upstash
- Live caption caches and session state
- Recent captions (30-minute expiry), attendee analytics during broadcasts
- United States
- Google Cloud
- Backup processing servers
- Live broadcast audio (in memory only), caption text
- United States
- Stripe
- Payments and invoicing
- Billing contact and payment details
- United States
- Google Workspace
- Customer correspondence
- United States
- Loops
- Product and account emails
- Account contact details
- United States
- Intercom
- Customer support chat
- Account contact details and support conversations
- United States
- PostHog
- Product analytics and error reports
- Dashboard usage by account users; caption page visits
- United States
- DataFast
- Website and caption page analytics
- Page visits, device type, approximate location
- United States
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Cloudflare | Live processing servers, translated audio storage, network | All service data in transit; transcripts during broadcasts; translated audio; attendee analytics | United States (storage); global network |
| Supabase | Database, authentication and file storage | Account details, transcripts, translations, attendee analytics | United States |
| Vercel | Website and API hosting | Account and API requests, attendee analytics | United States; global network |
| Upstash | Live caption caches and session state | Recent captions (30-minute expiry), attendee analytics during broadcasts | United States |
| Google Cloud | Backup processing servers | Live broadcast audio (in memory only), caption text | United States |
| Stripe | Payments and invoicing | Billing contact and payment details | United States |
| Google Workspace | Customer correspondence | United States | |
| Loops | Product and account emails | Account contact details | United States |
| Intercom | Customer support chat | Account contact details and support conversations | United States |
| PostHog | Product analytics and error reports | Dashboard usage by account users; caption page visits | United States |
| DataFast | Website and caption page analytics | Page visits, device type, approximate location | United States |