Administration/Security
Sub-processors
Third-party services Clipido uses to run the product, what data they receive, and how to request the full list.
Use this article to understand which third-party services (sub-processors) Clipido uses to deliver the product, and what categories of data they may process on Clipido's behalf.
Clipido BV remains responsible for your data. Each sub-processor listed below processes data only to provide the service described. Clipido maintains Data Processing Agreements (DPAs) with these providers where required under GDPR.
A full register with certification details is available on request. Email "hello@clipido.com" if you need the current copy for a vendor review or DPIA.
Infrastructure and storage
These providers host or store Clipido production systems and customer content.
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "Google Cloud Platform" | Cloud Run services, Cloud Storage, Cloud SQL, logging, translation | Uploaded media, processing metadata, audit logs |
| "DigitalOcean" | Managed Kubernetes, PostgreSQL, Redis | Account data, file metadata, job queues, application logs |
| "Cloudflare" | R2 object storage and edge image transforms | Preview images, CDN request metadata |
Sign-in and identity
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "Google" | Sign in with Google | Email, name, profile picture, OAuth subject ID |
| "Microsoft" | Sign in with Microsoft | Email, name, OAuth subject ID |
| "Your organization's IdP" (SAML / SCIM) | Enterprise single sign-on and user provisioning, when configured | Identity attributes your IdP sends (email, name, groups) |
When you use enterprise SSO, your organization controls its identity provider. Clipido processes only the attributes needed to sign you in and map group access.
Email, real-time updates, and support
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "Resend" | Transactional email (login codes, invitations, notifications) | Recipient email address, message content |
| "Pusher" | Real-time upload and download progress in the browser | Channel names, file IDs, progress events |
| "Formspark" | In-app feedback forms (bug reports, feature requests) | Submitter email from your session, free-text feedback |
Media processing
These providers receive files or URLs only when Clipido sends work to them (for example video transcoding or document conversion).
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "Coconut" | Video transcoding | Source video URLs and job metadata |
| "CloudConvert" | Document and media format conversion | File URLs and conversion job metadata |
| "Replicate" | Optional AI embedding generation for some clubs | Image or text content submitted for inference |
Not every workspace uses every media processor. For example, "Replicate" is used only when a club's embedding configuration routes inference there.
Monitoring and reliability
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "Better Stack (Logtail)" | Application log aggregation | Request logs, error traces, IP addresses in log context |
| "Better Stack (Errors)" | Error tracking | Stack traces, request context |
Logs may include user IDs or IP addresses for debugging and security investigation. Application log retention follows Clipido's "90-day" operational target.
Database backups
| Provider | What they do for Clipido | Data they may process |
|---|---|---|
| "SimpleBackup" | External PostgreSQL backups to Clipido-owned storage | Full database contents, including account and metadata |
Backup data stays in infrastructure controlled by Clipido. See "Where your data is hosted and how it's backed up" for retention periods.
When Clipido adds or changes sub-processors
Clipido reviews its sub-processor list at least annually and before onboarding a new provider that processes personal data. Material changes are reflected in the register available on request.
If your organization needs advance notice of sub-processor changes for contractual reasons, contact "hello@clipido.com" to discuss your agreement.
What this list does not include
This article lists services that process customer data during normal product operation. It does not list internal development tools (for example source control or infrastructure-as-code platforms) that do not handle customer content in production.
Some optional integrations configured in Clipido's codebase but not active for all customers may appear in the full register before they are removed or formally onboarded. Request the current register if you need that level of detail.