Sub-processors
Last updated 28 October 2026 · Version 1.0
These are the companies that process personal data on behalf of ClipnClip customers, under our Data Processing Agreement. We give at least 30 days' notice before adding one.
Draft
Draft for lawyer review. This text is a placeholder and is not legal advice.
On this page
1.Current sub-processors
| Name | Purpose | Location | Data |
|---|---|---|---|
| Hosting provider [TBD] | Application servers, database, backups and ClipnClip Cloud video storage. | EU | All service data in ClipnClip Cloud; metadata, transcripts and comments in own-bucket mode. |
| Stripe, Inc. / Stripe Payments Europe | Subscription and desktop licence payments, invoices. | US / EU | Billing name, email, payment method (held by Stripe), invoice amounts. |
| Email provider [TBD] | Sign-in codes, invitations, comment notifications, export links, licence keys. | [TBD] | Recipient name and email, message content. |
| AI provider [TBD] (only when ClipnClip-included AI is on) | Transcripts, titles, summaries and chapters. | [TBD] | Audio of the clip and its transcript, for the duration of the request. Not used for training. |
The AI provider receives data only for workspaces that use ClipnClip-included AI. Workspaces with AI off, or using their own AI key, send nothing to it; with your own key, that provider is your processor.
2.Your own bucket
Your own bucket provider is your sub-processor, not ours. In own-bucket mode you choose and contract with the storage provider (AWS S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO or another S3-compatible service); your videos are stored there and are never stored on ClipnClip servers.
3.Desktop app
The desktop app keeps videos and your profile on your computer. Only the licence purchase goes through Stripe and the licence email through our email provider.
4.Changes to this list
We post changes here at least 30 days before they take effect and email workspace owners. To object to a new sub-processor, write to privacy@[domain] within that period.