Last updated: August 6, 2026
1. What this page covers
When your organization uses Clipido, it decides what is stored in the platform and why. Your organization is the controller of that data and Clipido is its processor. To run the service we rely on a limited number of outside providers, and where such a provider may process personal data on our instructions it is a subprocessor. This page lists every one of them.
Each subprocessor works under a written processing agreement that passes on the same obligations we carry towards our customers. It receives only the data it needs for the part of the service it delivers, may use that data for nothing else, and may not bring in a provider of its own without the same guarantees.
The last group covers providers we use to build and run the platform rather than to process what is in it. In normal operation they hold no customer media and no account data, and they are listed so that the overview is complete.
2. Where the data is stored
The platform runs in Europe. The application, its database and its job queues run in Amsterdam, and uploaded media and the previews generated from them are stored in Google Cloud's Belgian region and in Cloudflare's European region. The daily backup of the database is the exception: it is encrypted and written to storage we own in the United States.
Several providers below are established outside the EEA. Where a provider offers a European contracting entity, we contract with that entity. For the rest, the transfer rests on the standard contractual clauses adopted by the European Commission, supplemented by the EU-US Data Privacy Framework where the provider is certified under it. Data is encrypted in transit and at rest in every case.
In the tables below, the country printed under a provider's name is where its legal entity is established. The last column is where the data it handles is actually stored, which is not always the same place.
3. Infrastructure and hosting
These providers carry the platform itself: the servers it runs on, the databases behind it and the files you upload.
| Provider | Purpose | Data | Data location |
|---|---|---|---|
| Google Cloud PlatformUnited States | PurposeObject storage, container hosting, databases, message queues, logging and machine translation. | DataUploaded media and their metadata, processing and audit logs, text submitted for translation. | Data locationBelgium |
| DigitalOceanUnited States | PurposeManaged Kubernetes, PostgreSQL and Redis, and load balancing. | DataAccount data, sign-in state, activity and notification records, job queues and platform logs. | Data locationAmsterdam |
| CloudflareUnited States | PurposeObject storage for generated previews, image resizing at the edge, and content delivery. | DataPreview images and the metadata of the requests for them. | Data locationEurope |
| SimpleBackups (Union Lab SRL)Belgium | PurposeA daily encrypted backup of the database, written to storage that we own. | DataThe full contents of the application database, encrypted. | Data locationUnited States |
| DopplerUnited States | PurposeCentral management of the secrets the platform needs in order to run. | DataCredentials, API keys and signing keys. No customer content. | Data location— |
4. Signing in
You can sign in to Clipido with an email link or with an account you already have. The providers below are only involved when you choose the latter.
| Provider | Purpose | Data | Data location |
|---|---|---|---|
| GoogleUnited States | PurposeSigning in with a Google account, and the Workspace accounts our own team works from. | DataEmail address, name, profile picture and the account identifier. | Data location— |
| MicrosoftUnited States | PurposeSigning in with a Microsoft or Entra ID account. | DataEmail address, name and the account identifier. | Data location— |
5. Your own identity provider
Organizations on an enterprise agreement can connect their own identity provider over SAML or SCIM, so that people sign in with the account they already have at work and are provisioned automatically. That provider is chosen and contracted by your organization, and processes the sign-in data under your agreement with it rather than ours. It is therefore not a subprocessor of Clipido and is not listed here.
6. Converting uploaded files
Uploads run through a pipeline that converts and transcodes them into the formats the platform serves. The providers below each take one step of that pipeline, and only for the files that need it.
| Provider | Purpose | Data | Data location |
|---|---|---|---|
| CoconutFrance | PurposeTranscoding uploaded video into the formats the platform serves. | DataA temporary link to the source video and the settings of the job. | Data locationEuropean Union |
| CloudConvert (Lunaweb GmbH)Germany | PurposeConverting documents and less common media formats. | DataA temporary link to the source file and the settings of the job. | Data locationEuropean Union |
7. Notifications, monitoring and support
These providers deliver our messages to you, keep the platform observable for our engineers, and carry what you send us through the product.
| Provider | Purpose | Data | Data location |
|---|---|---|---|
| ResendUnited States | PurposeDelivering transactional email: sign-in links, invitations and notifications. | DataRecipient name and email address, and the content of the message. | Data location— |
| Pusher (Pusher Limited)United Kingdom | PurposePushing live updates to the interface, such as the progress of an upload. | DataChannel names tied to a user, and the progress events themselves. | Data location— |
| Better StackUnited States | PurposeCollecting application logs and errors and alerting us when something breaks. | DataApplication logs and error reports, which include IP addresses, request context and stack traces. | Data locationEU region |
| Formspark (Trampoline Software SRL)Belgium | PurposeReceiving the feedback and contact forms in the product and on this website. | DataWhatever you submit, including your email address and your message. | Data location— |
8. Building and running the platform
The last group belongs to how we develop and operate Clipido. In normal operation these providers hold no customer media and no account data; they are here for completeness rather than because they process your content.
| Provider | Purpose | Data | Data location |
|---|---|---|---|
| GitHubUnited States | PurposeSource control, automated builds, and the registry our container images are published to. | DataOur own source code and build artifacts. No customer content. | Data location— |
| HashiCorp (Terraform Cloud)United States | PurposeDescribing and applying the infrastructure the platform runs on. | DataNames and settings of infrastructure resources. No customer content. | Data location— |
9. Changes to this list
We update this page before a new subprocessor starts processing customer data, and note the date of the change at the top and the bottom of the page.
Customers can ask to be notified of changes by email at hello@clipido.com. If you object to a new subprocessor on reasonable data protection grounds, tell us and we will look for a workable alternative together.
10. Questions
For questions about this list, to request a copy of a processing agreement, or to exercise your rights, contact us at hello@clipido.com or by post at Clipido BV, Haagdoornlaan 23, 3511 Hasselt, Belgium. How we handle personal data more generally is described in our Privacy Policy.
This subprocessor list was last updated on August 6, 2026.
