Legal · Sub-processors
Sub-processors
10 entries, and that's the whole list. Your account data and clip records live in the EU. Clip processing happens in Switzerland. Transcription, scoring, titles and editing send derived audio, text and still images to AI providers in the US, 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. Changes are announced on our update log.
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 announce it on our update log and update this page, at least 14 days ahead (from 22 November 2026; until then 30 days, by email). A provider we must add at once to keep the service secure or available may start immediately and is announced as soon as possible. You can object on reasonable data-protection grounds within 14 days of an announcement; 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, and backup speech-to-text transcription (Workers AI) when the primary transcription provider is unavailable
- Data
- Rendered clips awaiting review, static assets, request logs and IP addresses, aggregate page-view counts (no cookies, no cross-site identifiers); for backup transcription, clip and stream audio derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo)
- Location
- Global edge network, operated from the US
- Transfer
- EU Standard Contractual Clauses with Swiss addendum; EU-U.S. Data Privacy Framework
Anthropic
AI clip editing (choosing cut points and framing), and backup moment scoring, title generation and video-frame checks when the primary model is unavailable (Claude)
- Data
- Transcript excerpts, short excerpts of public chat (usernames and messages), clip keyframe images and video frames, and streamer reference photos (only for accounts with face matching turned on), all derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo)
- 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 and stream audio derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo)
- 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 chat (usernames and messages), channel activity statistics, clip keyframe images, streamer reference photos (only for accounts with face matching turned on) and transcript excerpts derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo); 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 chat (usernames and messages), channel activity statistics, clip keyframe images, streamer reference photos (only for accounts with face matching turned on) and transcript excerpts derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo)
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum. API inputs are not used to train models.
Listening to clip and stream audio (Gemini, via OpenRouter): who says what in a clip, for its title, and which stretches of a VOD are worth clipping
- Data
- Clip and stream audio, transcript excerpts, the channel name and the names of people who often appear on it, and, where switched on, a few video frames, all derived from the streams and recordings Clipsie processes (from Twitch, YouTube, Kick or Vimeo)
- Location
- United States
- Transfer
- EU Standard Contractual Clauses with Swiss addendum; EU-U.S. Data Privacy Framework
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, Kick, Vimeo 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, and for YouTube, Kick or Vimeo when we fetch a recording you linked from their public page. We list them here because they clearly do receive data, just not as our sub-processors.
Getting notified of changes
Every change to this list is announced on our update log (clipsie.app/updates), which customers also see in the dashboard under Support → Updates, with a marker until they have opened it. We do not send these notices by email. Questions: [email protected].