Subprocessors
This is an archived version. Version 1.7 of the Subprocessors took effect on November 1, 2026 and was replaced by Version 2.0 on November 1, 2026. This is the text of Version 1.7 that was in force until then. Read the current version, or see every earlier version.
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 in the table of current subprocessors below 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. The weather service our servers ask for a forecast, and the stock photo service our servers search, are different: we use each under its published terms, but neither publishes a data processing agreement, so neither is in that table, and each has a section of its own below that says exactly what it is sent. No party in the table, and not the weather service, is an advertising network or a data broker, and none of them may use the data for advertising. The stock photo service is not bound that way: it decides for itself what it does with the words of a search, under its own terms, which is why we send it nothing else. One of the parties in the table, 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, and, when a member of a studio's team asks for one, the transcript of a cut's speech, made by speech recognition software that runs on that server. 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, and, for a transcript, the cut's sound and the words spoken in it, which come back to us as 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. Role extended October 28, 2026, to transcripts |
| 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. For a workspace that links a bank or card account to its Books, Stripe Financial Connections, which connects to the bank and passes us that account's transactions, of which we keep the posted ones | Name, email, billing address, payment method (held by Stripe, never by us), subscription and transaction records. For a linked bank or card account: its transactions (date, amount and the bank's description of each), of which we keep the posted ones, and the bank's name, the account's name and its last four digits, which we display and do not store. For a workspace with no billing record yet, the workspace's name and the email address of the member who links the first account, to make one. On Stripe's request, the email address of the member who linked an account and the record of that connection. The bank login is given to the bank or to Stripe, never to us | United States, with regional processing by Stripe | August 21, 2026. Role extended October 21, 2026, to bank connections in Books |
| 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 contact@cutvey.com, 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 |
| Twilio Inc. | Text messages for the Service: the shoot and call sheet reminders a crew member asks for on their own call sheet, sent from Cutvey's own number, and the replies to them (YES, STOP, START and HELP). Used only by text reminders for crew, an optional feature a studio turns on, where it is named | The crew member's mobile number, the words of each text (the studio's name, the date, the call time and a link to the call sheet), the words of each reply, and delivery status. Never money, a client's or a project's name, a location or a note. Numbers in the United States and Canada only | United States | October 28, 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 |
| KEPTAGO LTD (Geoapify) | Place search and routing for the Service: finds the coordinates of a place you type, so that a call sheet can show a forecast and the nearest hospital, finds that hospital, and works out the driving distance of a trip in Books mileage; and, while a member of a workspace types into an address field, suggests matching addresses and offers a correction of a misspelled one | The address of a shoot location as typed, or its name if it has no address, or the workspace's own business address if the day has no location, and up to two shorter forms of the same text (with any suite, unit, apartment or floor number taken out, and without its first part or its first two parts); for Books mileage, the two places typed for a trip, or the saved address of a place saved under that name. With any of this text, the country codes that fit the workspace, worked out from its time zone or currency. For the nearest hospital, the latitude and longitude found for the place. For a driving distance, two pairs of latitude and longitude. For address suggestions, as a member of a workspace types into an address field: the text in that field so far, however partial, once it holds at least four characters; the same text once more, for a correction, if it reads as a street address and they typed it rather than picked a suggestion; those country codes; and the position of the workspace's own business address, which we find by sending that address with the country codes, about once a day, about once an hour while it cannot be found, and when it changes. The fields are the address and the parking of a shoot location, the hospital address on a call sheet, a client's address, the location of a calendar event or a mini-session, the workspace's own business address, the two places of a mileage trip and the address of a saved place. A client or a visitor cannot start this, no page they use sends it, and a crew seat in a studio's workspace is refused. Every request is made by our servers, never by your browser, so it carries no IP address, cookie or device detail of yours, and nothing we add that names you or your studio: no name, no email address, no account and no workspace identifier. What we add about your studio is the country codes and the position of its own business address. The place text and the text of an address field are sent as they were typed, even when partial, so the name of a venue, or of a person if one was typed there, goes with them, a shoot at a private home sends that home's address, and a client's address, often a home, goes too | European Union. We use Geoapify's European Union endpoint, which it commits to process only within the European Union. The company is established in Cyprus | October 9, 2026. Role extended November 1, 2026, to address suggestions |
| 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.
KEPTAGO LTD, which operates Geoapify, is established in Cyprus and is directly subject to the GDPR. It processes for us in the European Union under its data processing agreement under Article 28 of the GDPR. For the endpoint we use it names two subprocessors of its own: BunnyCDN in Slovenia, and Hetzner in Germany and Finland.
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 contact@cutvey.com 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.
Weather service
The weather forecast, sunrise and sunset shown on a call sheet and a shoot day come from Open-Meteo, a weather service operated by OpenMeteo GmbH of Bürglen, Switzerland. We pay for its commercial plan and use it under the terms it publishes for that plan. It is not in the table above because it differs from it in one important way: it publishes no data processing agreement, and we have not signed one with it. The statements on this page and in our Privacy Policy about data processing terms, and about Standard Contractual Clauses, do not apply to it.
What limits it is what we send. Every request is made by our servers, never by your browser, so it receives no IP address, cookie or device detail of yours, and no request carries anything that identifies you or your studio: no name, no email address, no account, no workspace identifier, and no address or place name. A request carries the key of our own account with it, which says that the request comes from Cutvey.
| Service | Operated by | What it does for us | What our servers send it | When |
|---|---|---|---|---|
| Open-Meteo forecast (customer-api.open-meteo.com) | OpenMeteo GmbH, Switzerland | The weather forecast, sunrise and sunset shown on a call sheet and a shoot day | The latitude and longitude found for the place, and the date of the shoot | When a forecast for that day is first needed, and again when it is refreshed |
Its published terms say that it keeps a log of the requests made to it, including the address of the server that asked, which is ours, and the request itself, for 90 days. Where a call sheet shows its forecast, the call sheet credits it.
Open-Meteo was listed in the table of current subprocessors until October 9, 2026. It is described here instead because we have no data processing agreement with it, and because that entry gave the wrong company and country.
Stock photo service
Stock photo search on a moodboard comes from Pexels or Pixabay, two free stock photo libraries operated by Canva Germany GmbH, Pappelallee 78/79, 10437 Berlin, Germany. We use their APIs under the terms and API guidelines each publishes. Like the weather service, its operator publishes no data processing agreement, and we have not signed one with it. Neither is our subprocessor: its operator's published terms let it use the words of a search, with its affiliates and partners, to develop and improve its own services, including by machine learning, and it decides that for itself. The statements on this page and in our Privacy Policy about data processing terms, about advertising, and about Standard Contractual Clauses do not apply to it.
What limits it is what we send. Every request is made by our servers, never by a browser: the search, the small previews a member of a workspace looks through and the photo they choose all pass through our servers, so the library receives no IP address, cookie or device detail of anyone in the workspace or of anyone the board is shared with. A request carries the key of our own account, which says that the request comes from Cutvey, and nothing that identifies a studio, a member of its team or a client.
| Service | Operated by | What it does for us | What our servers send it | When |
|---|---|---|---|---|
| Pexels API (api.pexels.com, and images.pexels.com for the photos) | Canva Germany GmbH, Germany | Stock photo search on a moodboard | The words a member of a workspace searches for, as typed, and the page of results asked for; for a preview or a chosen photo, the address of that photo | When someone searches, looks through results or chooses a photo |
| Pixabay API (pixabay.com, for the search and the photos) | Canva Germany GmbH, Germany | Stock photo search on a moodboard | The words a member of a workspace searches for, as typed, and the page of results asked for; for a preview or a chosen photo, the address of that photo | When someone searches, looks through results or chooses a photo |
The words are sent as they were typed, so a name typed into a search goes with them. Their published terms set no period for keeping requests, and Pexels and Pixabay each say they may also process data outside the European Union. Previews pass through our servers and are kept in memory for at most ten minutes. The results of a search are kept in memory for at most ten minutes for Pexels and at most 24 hours for Pixabay, whose API terms require it, then removed. A photo someone chooses is copied into the workspace's own storage, and from then on it is served by us like any other upload, so showing it to anyone sends the library nothing. The search panel credits the library it searches, and each chosen photo carries its creator's name and a link to it on that library.
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, and for passing us the transactions of a bank or card account a workspace links to its Books, of which we keep the posted ones. It is also an independent controller for its own fraud prevention, financial-crime and regulatory obligations, and for the connection to the bank itself: the person who links an account agrees to Stripe's own terms in Stripe's window, signs in to the bank there or on the bank's own site, and may choose to save the connection to Link, Stripe's own service. Stripe can collect more from the bank than it passes to us, and may ask us for the email address of the person who linked an account and the record of that connection, for its own notices and its own obligations to banks. What Stripe 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. We read back from that account what it reports about those payments (their status, refunds, disputes and fees) and its payouts, so the studio's invoices and books are right.
- 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.
- An account you hold elsewhere and connect yourself, such as a Google or Microsoft account for sending email or for your calendar, your QuickBooks or Xero company, your Slack workspace, or your Zapier account. The account, and what that company does with your data, are yours, under your agreement with it. We accept each of these companies' developer terms so the connection can work, but that does not make them our subprocessors. Their own terms may also let them use what passes through their service to run, secure and improve it, or as their own privacy policies allow. Google also appears in the table above, for our own mailbox; that is a different service. Section 11 of the Privacy Policy says what we send and read, 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 contact@cutvey.com 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 14 days in advance by email and in the product, and we update the "Last updated" date on this page. A notice may be a short summary with a link to 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 14 days' notice of its own change. Then we notify subscribers at the same time. The right to object below then runs from the date of that notice.
- Optional features. A subprocessor that only an optional feature uses, named where the feature is turned on, is authorized by the workspace that turns it on, from that moment and for that workspace only. We list it here no later than the day the feature is first offered.
- 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 14 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 14-day window, and we refund the part of what it has already paid that covers the period after the subscription ends, as our Terms of Service provide. 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, with the same 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: contact@cutvey.com.