Subprocessors | Cutvey

Version 1.0
Effective date: September 8, 2026
Last updated: October 5, 2026

This page lists the third parties Cutvey LLC uses to run its products, and that may process personal data on our behalf. It is part of the Cutvey Privacy Policy and is incorporated into our Data Processing Addendum.

Every party on this list processes data for us under written terms (their data processing terms, our agreement, or both) that limit them to providing their service to us, and that require confidentiality and appropriate security. None of them is an advertising network or a data broker, and none may use the data for advertising. One of them, our email provider, holds correspondence you send us rather than data from a workspace. Two of them also act on their own account for part of what they do, and we say which and why below, rather than implying a control we do not have.

Current subprocessors

Provider	Purpose	Data it may process	Location	First listed
DigitalOcean, LLC	Application hosting and compute for the Service	All data held in the Service: account data, workspace content, logs	United States (New York)	August 21, 2026
netcup GmbH	Media processing for the Service: streaming versions, posters, thumbnails and previews, including watermarked previews, of the videos and photos you upload. The originals and every result are stored with Cloudflare, below, and nothing is played or served from netcup's server	Copies of uploaded videos and photos, one file at a time, which may show or identify people and may carry names in file names and watermark text. Each copy is held only while it is being processed, then deleted. No account data, no database access and no storage credentials	United States (Manassas, Virginia)	September 28, 2026
Cloudflare, Inc.	File storage (R2), database backups, CDN and DNS, bot protection, routing of email sent to your workspace's Cutvey address, and hosting for the marketing and product websites. Cloudflare's network also stands in front of the Service: it receives the traffic to the web application and to studios' custom domains, protects it against attacks and abuse, and passes it to our servers, and it issues and renews the TLS certificate a visitor's browser sees for the application and for a custom domain	Uploaded files and media, database backups, IP address and request metadata, form submissions passing bot checks, and, for inbound email, the sender, subject and body of a message sent to your workspace's Cutvey address, which the routing provider sees before we do. For traffic to the web application and to custom domains, Cloudflare also processes the content of each request and response while it passes through its network, which is whatever is being sent or viewed in the Service at that moment, together with the IP address and connection details of the person's device. The connection is decrypted on Cloudflare's network so that it can be inspected and protected, and encrypted again on the way to our servers. Cloudflare processes that content in transit, to deliver and protect it; it may hold a temporary cached copy of static application files and of files a workspace has made public, and it keeps security and traffic records about requests	Stored data (object storage and backups) is held in the United States, encrypted at rest by Cloudflare with keys Cloudflare manages. CDN and DNS traffic, and traffic to the web application and to custom domains, is handled on a global edge, so a request may be received and processed at a location near you, which may be outside the United States, before it is passed to our servers in the United States, under Cloudflare's own data processing addendum and transfer clauses	August 21, 2026. Role extended October 5, 2026, to the network in front of the Service
Stripe, Inc.	Subscription billing for Cutvey plans and App licenses, and Stripe Connect so a studio's clients pay the studio directly	Name, email, billing address, payment method (held by Stripe, never by us), subscription and transaction records	United States, with regional processing by Stripe	August 21, 2026
Resend, Inc.	Transactional and product email delivery	Recipient email address, sender and message content, delivery, bounce, open and click events	United States	August 21, 2026
ActiveCampaign, LLC (Postmark)	Fallback transactional email delivery, used only when the primary provider is unavailable	Same as above	United States	August 21, 2026
Google LLC (Google Workspace)	Business email and calendar for [email protected], which is how we receive and answer support, privacy, legal and abuse correspondence	The content of email you send us and our replies, your email address, and any attachment you send	United States, with Google's global infrastructure	August 21, 2026
Anthropic, PBC	AI assistant features in the Service	The text or workspace data you point an AI feature at, and the generated output. Under Anthropic's commercial API terms, inputs and outputs are not used to train models	United States	August 21, 2026
OpenAI, L.L.C.	Standby AI provider for AI assistant features in the Service, used only when our primary AI provider is unavailable	The text or workspace data you point an AI feature at, and the generated output. Under OpenAI's commercial API terms, inputs and outputs are not used to train models	United States	September 8, 2026
Apple Inc.	Push notification delivery (APNs) for the native apps and the companion app	Device push tokens	United States and Apple's global infrastructure	August 21, 2026
Open-Meteo GmbH	Weather forecasts shown on call sheets	Latitude and longitude of a shoot location only. The request is made by our servers, not by your browser, so no user identifier, account data or your IP address is sent	Germany	August 21, 2026
Sentry (Functional Software, Inc.)	Crash reporting for the native apps, and server error reporting for the Service	Technical diagnostics: app, operating system and release version, device or server context, the operation that failed, memory figures and the stack trace. Reports are designed and filtered so that they do not carry customer content, and we remove account names, volume names and access tokens on the paths we control before a report is sent. Where personal data nevertheless appears in the text of an error, we treat that report as customer data	United States	August 21, 2026
GitHub, Inc. (Microsoft)	Source code hosting and continuous integration	Source code and build logs. No customer data and no production personal data	United States	August 21, 2026

We name two AI providers because one is a standby for the other, in the same way our email list names a fallback. Only one of them handles any given request, and which one it is does not change what may be sent or how it may be used.

Where we change the provider that routes inbound email to us, that is a change to this list under the process on this page.

Where a provider above that is established outside the EEA, the UK and Switzerland receives personal data protected by the law of any of them, we have Standard Contractual Clauses in place with it, with the UK Addendum where relevant.

netcup GmbH is established in Germany and is directly subject to the GDPR. It processes for us on a server in the United States under its data processing agreement under Article 28 of the GDPR, which we concluded with it on September 28, 2026. Its group companies in Germany and Austria, which it names as its own subprocessors, may access that server for support and infrastructure work. They are Anexia Holding GmbH and Anexia Cloud Solutions GmbH, both of Klagenfurt, Austria, and Anexia Cloud Solutions GmbH of Karlsruhe, Germany.

Contact details. Each provider publishes a privacy contact in its own privacy policy. If you need the current contact details for any provider on this list, for a data subject request, for Annex III of the Standard Contractual Clauses, or for your own records, email [email protected] and we will send them to you. We keep them rather than reprint them here, so that this page cannot go stale about somebody else's address.

Independent controllers

Two of the companies above also act on their own account, not only on ours, and it would be misleading to present them purely as our subprocessors.

Stripe is our processor for the billing data we send it. It is also an independent controller for its own fraud prevention, financial-crime and regulatory obligations. What it does in that capacity is governed by Stripe's own privacy policy, not by ours.
Apple is our processor for the push tokens we send it. It is an independent controller for App Store purchases, receipts and your Apple Account, and for your own private iCloud database, which we cannot read. What Apple does in those capacities is governed by Apple's privacy policy.

Corporate group

Cutvey LLC currently has no affiliates or group companies that process personal data. If that changes, they will be listed here.

Not subprocessors

For clarity, these process data, but not on our behalf:

Apple's own crash sharing. Your Apple device may send crash information to us through Apple's own developer channel, if you turned that on in your device settings. That is Apple's mechanism under Apple's terms, and you control it there rather than in our apps. Crash reports our apps send themselves go to an endpoint we operate, and we forward them from our own servers to the crash-reporting provider in the table above, on the consent basis described in section 8 of the Privacy Policy.
Our own crash and error endpoint. Error reports from the Service, and crash and diagnostic reports from our apps, go to an endpoint we run ourselves on app.cutvey.com. That is us, not a third party, so it is not on the list above.
Apple, for App Store distribution and in-app purchases. When you buy or download an App, Apple acts for itself under its own terms, not on our behalf. The App confirms the purchase with Apple on your device. Nothing about that purchase is sent to us, and we do not receive your payment details.
A studio's own Stripe account. When a studio's client pays an invoice, the money and the payment data go to the studio's own Stripe account, under the studio's own relationship with Stripe. Cutvey never holds those funds.
A destination you configure yourself in an App, such as your own storage bucket, a network drive, or a webhook. Your files go where you send them, under your own arrangements.
An AI assistant you connect yourself. If your plan includes it, you can connect your own ChatGPT or Claude to your workspace. That provider answers to you, under your account and your agreement with it. We do not choose it, do not pay it and get nothing back from it, so it is not on the list above. Section 17A of the Terms of Service says what it can and cannot do, and Section 5.8 of the Data Processing Addendum explains the roles.
Your Apple Account and iCloud, when you sync an app's data to your own private iCloud database. That relationship is between you and Apple.

Changes to this list

We keep this list current, and we do not add a subprocessor quietly.

We describe each provider by the job it does. Replacing a provider with another that does the same job, in the same country, under the same kind of terms, follows the notice process below like any other change.

Subscribe to notifications. Any customer can subscribe to subprocessor change notices by emailing [email protected] with "Subprocessor notifications" in the subject line. Workspace owners and billing contacts are subscribed by default.
Advance notice. Before we add a new subprocessor, or replace an existing one, we notify subscribers at least 30 days in advance by email, and we update the "Last updated" date on this page.
Where we must move faster. Sometimes we have to act sooner: to keep the service running, to fix a security or reliability problem, or because a provider gives us less than 30 days' notice of its own change. Then we notify subscribers as soon as we reasonably can instead. The right to object below then runs from the date of that notice.
Right to object. For processing where Cutvey acts as a processor on a business customer's behalf, that customer may object in writing to a new subprocessor within 30 days of the notice, on reasonable grounds relating to data protection. We will work with the customer in good faith to find an alternative or a mitigation. If we cannot, the customer may terminate the affected subscription by written notice given within that 30-day window. Termination takes effect at the end of the customer's current paid period, and no refund or proration is given, consistent with our Terms of Service. Until then, where technically possible, we will keep that customer's data off the new subprocessor. Where that is not possible, the customer may instead end the subscription immediately, again without refund. The full terms of this right are in our Data Processing Addendum.
Removals do not require notice, though we will note them here.
When this page changes, the version it replaces will be kept at https://cutvey.com/legal/archive, with the date each version took effect, so you can show which list was in force when you accepted.
How we number and notify. Section 20 of our Privacy Policy sets out how we number every document in this suite, what counts as a change to a row rather than a change to the words themselves, and when we tell you. This page follows that rule.

Questions: [email protected].