Legal · Sub-processors
Sub-processors
Seven providers, and that's the whole list. Your account data and clip records live in the EU. Clip processing happens in Switzerland. Transcription and scoring send derived audio and text to two US providers, and card payments are handled by Stripe; we never see your card number. Nobody on this list is allowed to use your data for anything but running Clipsie.
This page is Annex II to our Data Processing Agreement and lists every sub-processor we engage to process personal data on behalf of our customers, as required by Art. 28(2) GDPR.
Each sub-processor is bound by data-protection obligations no less protective than those in our DPA, and we remain fully liable to you for what they do. Before a new one starts processing your data we give 30 days' notice by email and update this page. You can object on reasonable data-protection grounds within that window; see DPA section 06 for what happens then.
Current sub-processors
Supabase
Application database, authentication and object storage
- Data
- Account details, channel settings, clip records and metadata, streamer reference photos, encrypted OAuth tokens
- Location
- EU (AWS eu-central-1, Frankfurt, Germany)
- Transfer
- No transfer out of the EEA for stored data
Cloudflare
Website and dashboard hosting, CDN, media delivery (media.clipsie.app), privacy-first website analytics
- Data
- Rendered clips awaiting review, static assets, request logs and IP addresses, aggregate page-view counts (no cookies, no cross-site identifiers)
- Location
- Global edge network, operated from the US
- Transfer
- EU Standard Contractual Clauses with Swiss addendum; EU-U.S. Data Privacy Framework
Anthropic
Moment scoring and title generation (Claude)
- Data
- Transcript excerpts and short text derived from Twitch content
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum. Inputs are not used to train models.
Groq
Speech-to-text transcription
- Data
- Clip audio derived from Twitch content
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum
OpenRouter
AI request routing for live chat-moment pre-filtering, clip scoring and title generation
- Data
- Short excerpts of public Twitch chat (usernames and messages), channel activity statistics, clip keyframe images, streamer reference photos and transcript excerpts derived from Twitch content; prompts are not stored by default
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum
OpenAI
Live chat-moment pre-filtering, clip scoring and title generation (via OpenRouter)
- Data
- Short excerpts of public Twitch chat (usernames and messages), channel activity statistics, clip keyframe images, streamer reference photos and transcript excerpts derived from Twitch content
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum. API inputs are not used to train models.
Resend
Transactional email (account, billing and service notices, contact-form delivery)
- Data
- Email address and message content
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum
Stripe
Payment processing and subscription billing
- Data
- Billing name and email, billing address and country, any VAT ID supplied, subscription and invoice records, card brand and last four digits. Full card details go directly to Stripe and are never received or stored by Clipsie.
- Location
- United States (Stripe Payments Europe for EEA customers)
- Transfer
- EU Standard Contractual Clauses with Swiss addendum; EU-U.S. Data Privacy Framework
Clipsie processing server
The clip pipeline itself: detection, rendering, upload scheduling
- Data
- Source footage, audio, transcripts, streamer reference photos, short-lived face comparison vectors used to confirm a reference photo, render artefacts, operational logs
- Location
- Switzerland
- Transfer
- Switzerland holds an EU adequacy decision; no additional safeguard required
The platforms you connect
Twitch, YouTube and TikTok are not sub-processors. When Clipsie publishes to your YouTube channel it acts on your instruction, but Google then processes that video as an independent controller under its own terms with you. The same goes for Twitch and TikTok. We list them here because they clearly do receive data, just not as our sub-processors.
Getting notified of changes
Customers are notified by email at the address on their account. If you are not a customer but want to track changes to this page, write to [email protected] and we'll add you to the notice list.