Legal
Subprocessors
This page lists the companies Cutvey LLC uses to run its products that may process personal data on our behalf. Our Data Processing Addendum incorporates it, and we update it in place.
Core means part of running the Service. Optional means used only where a workspace turns the feature on.
| Provider | What it does | Data it may process | Location | Core or optional |
|---|---|---|---|---|
| DigitalOcean, LLC | Application hosting, compute, the production database and its backups | All data held in the Service: account data, workspace content, logs | United States (New York) | Core |
| netcup GmbH | Media and file processing for the Service: streaming versions, posters, thumbnails and previews, including watermarked previews, of what you upload; virus scanning of uploaded files; 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 | Copies of uploaded files of any kind, one at a time, for as long as a job runs. These may show or identify people and may carry names in file names and watermark text. For a transcript, the cut's sound and the words spoken in it | United States (Manassas, Virginia). netcup is established in Germany, and its group companies in Germany and Austria may access the server for support and infrastructure work | Core |
| Cloudflare, Inc. | File storage, CDN and DNS, bot protection, routing of email sent to your workspace's Cutvey address, and hosting for the marketing and product websites. Its 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, passes it to our servers, and issues the TLS certificates a visitor's browser sees | Uploaded files and media, IP address and request metadata, form submissions passing bot checks, and the sender, subject and body of email sent to your workspace's Cutvey address. For traffic to the web application and to custom domains, the content of each request and response in transit, which is decrypted on Cloudflare's network so that it can be protected, and encrypted again on the way to our servers, and any temporary cached copy of static files and of files a workspace has made public, with its security and traffic records | Stored files in the United States, encrypted at rest by Cloudflare with keys Cloudflare manages. Traffic on a global edge, so a request may be processed near you, which may be outside the United States | Core |
| Stripe, Inc. | Subscription billing for Cutvey plans and App licenses. 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 | Core for billing. Optional for bank connections |
| Resend, Inc. | Transactional and product email delivery | Recipient email address, sender and message content, delivery, bounce, open and click events | United States | Core |
| ActiveCampaign, LLC (Postmark) | Fallback delivery of sign-in codes and other account-critical email, when the primary provider is unavailable | Recipient email address and message content | United States | Core |
| Google LLC (Google Workspace) | Business email and calendar for contact@cutvey.com, which is how we receive and answer 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 | Core |
| Anthropic, PBC | AI features in the Service | The content a person points an AI feature at, and the generated output. Where a workspace turns on picture tagging, a small copy of each picture selected | United States | Core, used when a person uses an AI feature. Optional for moodboard picture tagging |
| OpenAI, L.L.C. | Standby AI provider, when our primary AI provider is unavailable | Same as Anthropic | United States | Core, used when a person uses an AI feature. Optional for moodboard picture tagging |
| 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) | 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 | Optional |
| Apple Inc. | Push notification delivery (APNs) for the native apps | Device push tokens | United States and Apple's global infrastructure | Core where a native app is used |
| KEPTAGO LTD (Geoapify) | Place search and routing: 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. While a member of a workspace types into an address field, suggests matching addresses and offers a correction of a misspelled one | The text of a place or address, up to two shorter forms of it, and, for suggestions, the text in the field so far and that text once more for a correction; the country codes that fit the workspace; latitude and longitude for a place or a route; and the position of the workspace's own business address. The place text and the text of an address field are sent as they were typed, even when partial, so a private home's address, a client's address, or a person's name if one was typed, goes with them. Requests are made by our servers, not your browser, so they carry no IP address, cookie or device detail of yours, and we add no name, email address, account or workspace identifier | European Union, through Geoapify's European Union endpoint, which it commits to process only within the European Union. The company is established in Cyprus, and its own subprocessors for that endpoint are in the European Union | Core |
| 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 to limit customer content. A report that does carry personal data is treated as customer data | United States | Core |
Services we use that are not subprocessors
These operators are not our subprocessors. Each request is made by our servers, not your browser, so it carries no IP address, cookie or device detail of yours.
| Service | Operator | What it does for us | What our servers send it | Its footing |
|---|---|---|---|---|
| Open-Meteo forecast (api.open-meteo.com) | OpenMeteo GmbH of Bürglen, 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 | Its published terms say it logs requests, including the address of the server that asked, which is ours |
| Pexels API (api.pexels.com, images.pexels.com) | Canva Germany GmbH, Germany | Stock photo search on a moodboard | The words a member of a workspace searches for, as typed, and the address of each photo our servers fetch | An independent controller. Its published terms let it use the words of a search to develop and improve its own services, including by machine learning. It may process outside the European Union. A name typed into a search goes with the words |
| Pixabay API (pixabay.com) | Canva Germany GmbH, Germany | Stock photo search on a moodboard | The words a member of a workspace searches for, as typed, and the address of each photo our servers fetch | Same as Pexels |
Independent controllers
Two of the companies above also act on their own account.
- 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 distribution and purchases, your Apple Account and your own iCloud. What Apple does in those capacities is governed by Apple's privacy policy.
Yours, not ours
These process data, but not on our behalf.
- 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. We read back what that account reports about those payments and its payouts, so the studio's invoices and books are right.
- A destination you configure yourself, such as your own storage bucket, a network drive or a webhook.
- An AI assistant you connect yourself. That provider answers to you, under your account and your agreement with it. Section 5.8 of the Data Processing Addendum explains the roles.
- An account you hold elsewhere and connect yourself, such as an email, calendar, accounting, messaging or automation 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. Section 5.8 of the Data Processing Addendum explains the roles.
- A website, player or map a person links to or opens. That provider's own service, under its own terms.
Getting notice of changes
- Who gets notices. We email subprocessor notices to workspace owners, who are enrolled automatically. Anyone else at a customer can ask for them at contact@cutvey.com. If you stop them, you will not hear of a change from us.
- Notice. We update this page and send that email at least 14 days before a new or replacement subprocessor begins processing customer personal data. A notice may be a short summary with a link here. Where we must move faster, as Section 5.6 of the Data Processing Addendum describes, we give notice at the same time.
- Objecting. A business customer for whom we act as a processor may object within 14 days of the notice, by emailing contact@cutvey.com, as Section 5.5 of the Data Processing Addendum provides.
- Optional features. A provider only an optional feature uses is authorized by the workspace that turns the feature on, from that moment and for that workspace. We list it here no later than the day the feature is first offered.
- Removals need no notice.
Questions, or a provider's current privacy contact: contact@cutvey.com.