Subprocessors
Who touches your data, and what for.
A subprocessor is a company we use to run GambitClip that handles customer data on our behalf, under a contract that binds it to the same rules we follow. The ones marked footage can see your video, audio or the clips made from it; the rest see account, billing or technical data only. Every AI provider on this list is used on terms under which your content is not used to train its models.
When we add or replace a subprocessor we update this page and its date first. Customers under our DPA may object within ten business days of a change, as that agreement describes.
| Company | What it does for us | Data it handles | Location |
|---|---|---|---|
| Cloudflarefootage | Hosts the site and the app, stores your footage and clips, holds the waiting list | Footage, transcript and cut list (7 days), clips and their caption files (30 days), waiting-list emails | Global (EU and US), cloudflare.com |
| Fly.io | Runs the GambitClip service and its database | Account, settings, usage and job records | EU, fly.io |
| Modalfootage | Processes and renders video | Footage, audio, frames, clips, while a run is in progress | US, modal.com |
| Speechmaticsfootage | Speech to text | The audio track of your footage | UK and EU, speechmatics.com |
| Google (Gemini API)footage | Visual analysis of frames and short audio segments | Frames and audio segments from your footage | US and EU, ai.google.dev |
| Anthropicfootage | Analysis models used to find moments | Transcript, analysis notes, frames | US, anthropic.com |
| OpenRouterfootage | Routes our editorial model calls to their provider | Transcript, analysis notes, frames, in transit | US, openrouter.ai |
| OpenAIfootage | Editorial models that choose and cut clips | Transcript, analysis notes, frames | US, openai.com |
| Inngest | Schedules processing steps | Job identifiers and event names only | US, inngest.com |
| Clerk | Sign-in and account security | Email, name, sign-in events, IP address | US, clerk.com |
| Stripe | Payments, invoices and tax | Email, billing address, payment details (held by Stripe, never by us) | EU and US, stripe.com |
| Sentry | Error monitoring | Account identifier and technical error data, never footage | EU, sentry.io |
| Resend | Sends our emails to you | Email address and message content | US, resend.com |
| Google (YouTube API)footage | Publishing, only if you connect your channel | The clips you choose to upload | US, developers.google.com |
| TikTokfootage | Publishing, only if you connect your account | The clips you choose to post; account name and picture | US and Singapore, developers.tiktok.com |
| Meta (Instagram API)footage | Publishing, only if you connect your account | The clips you choose to post; account name and picture | US and EU, developers.facebook.com |
| Xfootage | Publishing, only if you connect your account | The clips you choose to post; account name | US, developer.x.com |
Where your data lives
Our own service and database run in the European Union. Footage and clips are stored with Cloudflare, which serves them from locations close to you. Video processing and the AI providers run in the United States. For customers in the EU, the EEA, the UK and Switzerland, transfers to the United States rest on the EU-U.S. Data Privacy Framework where the provider is certified and on Standard Contractual Clauses otherwise. Customers elsewhere, including the United States, should expect their data to be processed in both regions.