Data Processing Addendum
This is an archived version. Version 2.2 of the Data Processing Addendum took effect on October 20, 2026 and was replaced by Version 2.3 on October 21, 2026. This is the text of Version 2.2 that was in force until then. Read the current version, or see every earlier version.
How this document works
This Data Processing Addendum (this "DPA") is part of the Cutvey Terms of Service. It is incorporated into the Terms by reference.
You do not need to sign it, and you may. It applies automatically to every customer of the Cutvey subscription service ("the Service") whose use of the Service involves personal data that Cutvey handles on the customer's behalf. If you use the Service, this DPA and the Standard Contractual Clauses it incorporates are in force between you and Cutvey from the date you accepted the Terms of Service, and no signature is required, because Article 28(9) of the GDPR allows a processing contract to be in electronic form. If your organization's process requires an executed copy, complete the Signature Page in Annex IV, sign it, and email it to contact@cutvey.com. Cutvey will countersign and return it within five business days. The executed copy has the same terms as this document and takes effect from the date you first accepted the Terms of Service. Cutvey signs this document as published and does not negotiate customer-specific terms.
If this DPA conflicts with the Terms of Service, this DPA wins on the subject of personal data protection. If this DPA conflicts with the Standard Contractual Clauses in Section 11, the Standard Contractual Clauses win.
One list sits outside this DPA and is incorporated by reference, so it can be kept current without a new version of this document: the subprocessor list at https://cutvey.com/legal/subprocessors.
The security measures are in Annex II of this DPA. Annex II is the contractual statement of them. If Cutvey ever publishes a separate security page describing the same measures, that page is a description and not a replacement, and where the two differ the more protective description applies. A change that materially reduces the level of security described is a material change under Section 15 and is notified accordingly.
1. Definitions
Words defined in the Terms of Service keep their meaning here.
- "Data Protection Law" means every privacy and data protection law that applies to processing under this DPA, including the EU General Data Protection Regulation 2016/679 ("GDPR"), the GDPR as it forms part of UK law together with the UK Data Protection Act 2018 ("UK GDPR"), the Swiss Federal Act on Data Protection ("FADP"), the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA"), and other US state privacy laws.
- "Controller", "Processor", "Data Subject", "Personal Data", "Processing", "Personal Data Breach", and "Supervisory Authority" have the meanings given in the GDPR. Where the CCPA applies, "Business", "Service Provider", "Consumer", "Sell", "Share", and "Personal Information" have the meanings given in the CCPA.
- "Customer Personal Data" means Personal Data contained in the data a customer or its users put into the Service, or that the Service generates from it, and that Cutvey processes on the customer's behalf.
- "Standard Contractual Clauses" or "SCCs" means the clauses annexed to European Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
- "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, version B1.0, in force 21 March 2022.
- "Subprocessor" means a third party engaged by Cutvey to process Customer Personal Data.
2. Roles of the parties
2.1 Cutvey as processor. For Customer Personal Data, the customer is the Controller and Cutvey is the Processor. This is the data the customer's studio puts into its workspace: its clients, leads, crew, talent, contacts, project content, files, messages, and documents, and the personal data of the people the customer invites into a client portal or asks to sign a document.
Where the customer is itself a processor acting on behalf of another controller, the customer is a Processor and Cutvey is a Subprocessor, and this DPA applies with that reading. The customer confirms it has that controller's authorization to engage Cutvey, and remains responsible as between the parties for the instructions it gives.
2.2 Cutvey as controller. Cutvey is an independent Controller for a defined set of data it needs to run its own business: account holder and billing contact details, the account owner's authentication and security records, subscription and payment records, support correspondence, website visitor data, and Cutvey's own platform-level security and infrastructure logs, meaning logs generated outside any workspace for the purpose of operating and defending the platform as a whole. The in-workspace audit log of user actions, which the customer can see and export, is Customer Personal Data and Cutvey processes it as Processor. Cutvey's Privacy Policy, not this DPA, governs the processing for which Cutvey is Controller.
2.3 Customer obligations. The customer confirms that:
it has a lawful basis for the Personal Data it puts into the Service, and has given the notices and obtained the consents that Data Protection Law requires from the people the data is about;
its instructions to Cutvey comply with Data Protection Law;
the Service is not designed for, and the customer will not use it as a system of record for, special category data under GDPR Article 9, criminal offense data under Article 10, payment card or financial account numbers, health records, or biometric identifiers used for unique identification.
Two things this does not prohibit. First, the customer's own tax and engagement paperwork for the people it hires, including a completed W-9 or an equivalent form carrying a taxpayer identification number, is ordinary business administration that the Service is built to hold, and the customer may store it. Second, a government identifier that appears incidentally inside footage, a scan, or an attachment the customer uploads is not a breach of this bullet. In both cases the customer remains responsible for restricting who in its workspace can see the record, and for any state law that imposes specific duties on the holder of a social security or equivalent number.
Health and education data. Cutvey is not a HIPAA business associate, does not enter business associate agreements, and is not a school official under FERPA. The Service is not designed to hold protected health information or education records, and the customer will not use it as a system of record for either. Where a shoot for a healthcare or education client captures an identifiable patient or student, the consent, the release, and the lawful basis are the customer's responsibility, and the resulting footage is ordinary Customer Personal Data under this DPA.
The parties acknowledge that ordinary production records held in the Service may contain data that Data Protection Law treats as special category data, in particular trade union membership in crew records and, where the customer records them, dietary, accessibility, or medical requirements on call sheets, and that release records may relate to minors. The Service is designed to hold that data as part of ordinary production administration, the measures in Annex II apply to all Customer Personal Data without distinction, and the customer remains responsible for its own lawful basis, for the condition in Article 9(2) or its local equivalent, and for not using the Service where the risk requires controls beyond those in Annex II;
where it uses the Service to send email with open and click tracking, to collect e-signatures, or to record a call sheet or release, it is responsible for the lawfulness of doing so.
2.4 The native apps. Cutvey's native apps can sign in to a Cutvey workspace and sync content with it. Content an app pushes into the workspace, and content the workspace sends to an app, is Customer Personal Data and is covered by this DPA in the same way as anything else in the workspace. Content that stays on a user's device, or in that user's own iCloud (CloudKit private database), is not processed by Cutvey at all, and Cutvey cannot access it.
Product usage analytics and crash reports that the apps send to Cutvey, and the sign-in and device records described in the Cutvey App License Agreement, are processed by Cutvey as an independent Controller under its Privacy Policy, not under this DPA. They are technical and, by default, anonymous, and they are designed and filtered so that they do not contain workspace content. Where they can be linked to an individual, Cutvey is responsible for informing that individual under its Privacy Policy. The Cutvey App License Agreement governs the apps themselves.
Biometrics. No Cutvey product sends a biometric identifier, or face or hand geometry, to Cutvey, and no Cutvey product stores a biometric template. Where an app detects a face, a hand, or a body on the device, that detection stays on the device, is used for that moment only, and is not retained.
A person who only bought an app has no account. Where a person unlocks an app by a one-time purchase in a platform store and never signs in, Cutvey receives nothing about that purchase and creates no account, so there is no personal data of theirs for Cutvey to hold, disclose, or delete.
2.5 Cutvey is not a party to the customer's own contracts. Cutvey is not a party to any agreement between a customer and that customer's clients, crew, or talent, and takes no responsibility for them.
3. Processing of Customer Personal Data
3.1 Documented instructions. Cutvey processes Customer Personal Data only on the customer's documented instructions, which are: this DPA, the Terms of Service, the customer's configuration and use of the Service through its interfaces and APIs, and any other written instruction the parties agree. Providing, securing, maintaining, and supporting the Service are within those instructions, as is generating the usage and account records Cutvey needs to bill the customer, which Cutvey then processes as Controller under Section 2.2.
Cutvey also produces aggregated statistics about how the Service is used, in order to operate and improve it. Those statistics are irreversibly aggregated, identify no person and no customer, and no output can be attributed to a customer's workspace. Cutvey does not use Customer Personal Data for any other purpose of its own.
The customer's documented instructions also include connecting a third party to the Service, whether by an API key, a webhook, an integration or an AI assistant. Where the customer does that, the customer instructs Cutvey to make the Customer Personal Data that connection is authorized to reach available to the recipient the customer appointed. Section 5.8 describes what that means.
3.2 Where the law requires otherwise. Cutvey may process Customer Personal Data where EU, member state, UK, or other applicable law requires it to. In that case Cutvey will inform the customer of the requirement before processing, unless that law forbids telling the customer on important grounds of public interest.
3.3 Unlawful instructions. If Cutvey considers that an instruction infringes Data Protection Law, it will inform the customer immediately, and may suspend performance of that instruction until the parties resolve it.
3.4 No sale, no advertising, no training. Cutvey does not sell Customer Personal Data, does not share it for cross-context behavioral advertising, does not disclose it to data brokers or advertising networks, and does not use it to build, train, or fine-tune artificial intelligence models. Two things are outside that sentence rather than exceptions to it: a feature the customer switches on that expressly does so, in which case Cutvey processes only within that instruction and the customer may withdraw it at any time, and a customer-appointed recipient under Section 5.8, which is not Cutvey processing at all. Cutvey does not use Customer Personal Data for any purpose outside providing the Service, except as Sections 3.1, 3.2, and 10.5 permit.
3.5 AI features and connected assistants. There are two different things here and they have different answers.
(a) Cutvey's own AI features. Where a customer's user invokes an AI feature that Cutvey provides, the content that user directs the feature at, which may include text the user types and workspace records the user selects, together with the output generated from it, is processed by an AI Subprocessor named on the published subprocessor list, solely to produce the requested output. Under that provider's commercial terms, inputs and outputs are not used to train models and are retained only as long as needed to deliver the response and to meet the provider's own trust and safety obligations. No AI feature runs unless a user invokes it. Output can be wrong, and the customer is responsible for checking it before relying on it.
(b) An AI assistant the customer connects. Where the customer connects its own AI assistant to its workspace, that assistant's provider is a customer-appointed recipient under Section 5.8, not a Cutvey Subprocessor. Cutvey answers that assistant's requests on the customer's documented instruction under Section 3.1, and does not otherwise transmit Customer Personal Data to that provider, does not select it, holds no agreement with it, receives nothing back from it, and calls no model. The customer is the Controller for that disclosure and for everything the provider does with what it receives. The customer's own agreement with that provider governs the provider's retention, its security, and whether it uses what it reads to train or improve models, which some consumer and personal plans do by default. Paragraph (a) does not apply to that provider, and Cutvey's commitments about training in Section 3.4 and in the Terms of Service do not extend to it. Cutvey applies to a connected assistant the same access controls it applies to the Service itself, described in Annex II, including the seat's own permissions, workspace isolation, rate limiting and immediate revocation. Cutvey records the connection, the disconnection and every change the assistant makes; it does not currently record each record the assistant reads.
3.6 Confidentiality. Cutvey ensures that every person authorized to process Customer Personal Data is bound by a duty of confidentiality, contractual or statutory, that survives the end of their engagement, and that access is limited to those who need it to do their job.
3.7 Diagnostics. Cutvey and its native apps generate crash and error reports so that faults can be diagnosed and fixed. This covers both the Service and the apps, and the reports are processed by Cutvey and by the crash-reporting provider named on the published subprocessor list, which is listed for both.
Those reports carry technical diagnostics: the software and operating system version, the device or server context, the operation that failed, memory and timing figures, and a stack trace. They are designed and filtered so that they do not contain Customer Personal Data or customer content, and Cutvey applies redaction on the paths it controls, including removing account names, volume names, file and folder names, and access tokens before a report is sent. Cutvey does not promise that no personal data ever appears in the text of an error, and treats any report that does contain Customer Personal Data as Customer Personal Data subject to this DPA, including for deletion and for Section 7. Where a user can turn crash reporting off, the setting is in the product's privacy settings.
3.8 Details of processing. Annex I sets out the subject matter, duration, nature and purpose of processing, the categories of Data Subject, and the types of Personal Data.
4. Security
4.1 Measures. Cutvey implements and maintains appropriate technical and organizational measures to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, and unauthorized access, taking into account the state of the art, the cost of implementation, and the nature, scope, context and purposes of processing and the risks involved. Those measures are described in Annex II.
4.2 Changes. Cutvey may update its security measures as technology and threats change, provided it does not materially reduce the overall level of security.
4.3 No certification is claimed. Cutvey holds no third-party security certification and makes no claim to one. Cutvey is not certified under SOC 2, ISO 27001, or any equivalent scheme, and is not certified under the EU-US Data Privacy Framework, the UK Extension, or the Swiss-US Data Privacy Framework. Annex II describes what Cutvey actually does. Nothing in this DPA should be read as claiming an audit, attestation, certification, or seal that Cutvey does not hold.
5. Subprocessors
5.1 General authorization. The customer gives Cutvey general written authorization to engage Subprocessors, subject to this section.
5.2 Current list. Cutvey's Subprocessors are listed at https://cutvey.com/legal/subprocessors. That list is incorporated into this DPA by reference and forms part of it. The list at the effective date is reproduced in Annex III. If the two differ, the published list is current.
5.3 Terms with Subprocessors. Cutvey enters a written contract with each Subprocessor before it processes any Customer Personal Data. That contract imposes data protection obligations no less protective than those in this DPA, to the extent they apply to the service that Subprocessor provides. It includes:
- the obligations Clause 9 of the Standard Contractual Clauses requires of a sub-processor;
- the requirements the CCPA and its regulations place on a contract between a service provider and another service provider; and
- where the Subprocessor processes outside the EEA, the UK, or Switzerland, a valid transfer mechanism satisfying Clause 8.8.
Cutvey will provide a copy of the data protection terms of any such contract to the customer on request, with commercial terms redacted.
An affiliate of Cutvey is a Subprocessor. Where a company in Cutvey's corporate group processes Customer Personal Data, it is engaged, listed, and notified under this Section 5 in the same way as any other Subprocessor.
5.4 Liability for Subprocessors. Cutvey remains fully liable to the customer for a Subprocessor's performance of its data protection obligations, subject to Section 13.
5.5 Notice of changes and the right to object. Cutvey will give every customer at least 14 days' written notice by email, and a notice in the Service, before a new Subprocessor begins processing Customer Personal Data, or before an existing Subprocessor takes on a materially different role. Notice goes to the workspace owner and the billing contact on record, who are enrolled automatically and cannot be unenrolled while the subscription is live. Cutvey will also update the published subprocessor list and its "last updated" date on or before the date of the notice. A notice may be a short summary with a link to that list. A customer may add further recipients by emailing contact@cutvey.com with "Subprocessor notifications" in the subject line.
The customer may object on reasonable data protection grounds within 14 days of that notice, by emailing contact@cutvey.com and explaining the grounds. The parties will discuss it in good faith, and Cutvey will try to offer a reasonable alternative or a change of configuration. If Cutvey cannot, the customer may terminate its subscription by written notice given within that 14-day window, with effect on the date the notice names or, if it names none, at the end of the current paid period. Cutvey will refund the part of what the customer has already paid that covers the period after the subscription ends, calculated pro rata by whole days, as Section 35 of the Terms of Service provides. Until the termination takes effect, where technically possible, Cutvey will keep that customer's Customer Personal Data off the new Subprocessor. Where that is not technically possible, the customer may instead end the subscription with immediate effect by saying so in its notice, with the same refund, and Cutvey will not transfer that customer's Customer Personal Data to the new Subprocessor.
A Subprocessor used only by an optional feature. Where a Subprocessor receives Customer Personal Data only through a feature that stays off until a person the customer allows to manage its workspace turns it on, and the Service names that Subprocessor and what it receives before the feature is turned on, turning the feature on is the customer's specific authorization of that Subprocessor for its workspace, and no advance notice is needed for that workspace. Cutvey adds the Subprocessor to the published list no later than the day the feature is first offered. Turning the feature off withdraws the authorization.
Termination under this section is the customer's remedy for the objection itself. Nothing in this section limits any right the customer has under Clause 9 or Clause 16 of the Standard Contractual Clauses, or any other right or remedy it has for a breach of this DPA by Cutvey.
5.6 Urgent replacement. Where a Subprocessor fails, is compromised, or ceases to provide its service without warning, and Cutvey must appoint a replacement to keep the Service running or to protect its security, Cutvey will give the customer notice by email at the same time as it makes the appointment, together with the reason and a description of the safeguards applied. The objection right in Section 5.5 applies from the date of that notice, and where the customer objects Cutvey will, so far as technically possible, suspend the transfer of that customer's Customer Personal Data to the replacement while the objection is discussed. Where the transfer is subject to the Standard Contractual Clauses, this Section 5.6 does not reduce the notice Clause 9(a) requires, and Cutvey will not rely on this Section in a way that contradicts Clause 9.
5.7 Recipients that are not Subprocessors. Some recipients of data act on their own account for part of what they do, and are independent Controllers for that part rather than Cutvey's Subprocessors. The published subprocessor list identifies them and explains which part is which. Payment processors acting under their own regulatory and financial-crime obligations, and platform operators acting under their own terms with the end user, are the present examples. Cutvey is not responsible for processing a recipient carries out as an independent Controller, and this DPA does not apply to it.
The weather service and the stock photo service. Two recipients are engaged by Cutvey without a contract of the kind Section 5.3 describes. The forecast, sunrise and sunset shown on a call sheet come from a weather service, Open-Meteo, operated by OpenMeteo GmbH in Switzerland. Cutvey pays for its commercial plan and uses it under the terms its operator publishes for that plan. The operator publishes no data processing agreement, and Cutvey has none with it and no Standard Contractual Clauses. Cutvey limits what it receives instead: Cutvey's servers, never a user's device, send it the latitude and longitude found for a shoot location and the date of the shoot, and nothing else from the customer's workspace. No request carries the text of a place, or anything that identifies the customer or a user: no name, no identifier, no account and no IP address. A request carries the key of Cutvey's own account with the operator. The published subprocessor list and Annex III say the same, and Cutvey gives notice under Section 5.5 before another recipient on this footing receives Customer Personal Data by default. Whether the coordinates of a place are Customer Personal Data depends on the place: those of a private home can be.
Stock photo search on a moodboard comes from Pexels or Pixabay, both operated by Canva Germany GmbH in Berlin, Germany, which Cutvey uses under the terms and API guidelines their operator publishes. The operator is not Cutvey's processor: its published terms let it use the words of a search to develop and improve its own services, including by machine learning, so for what it receives it is an independent controller. Cutvey has no data processing agreement and no Standard Contractual Clauses with it. Cutvey's servers, never a user's device, send it the words a user searches for, as typed, and the address of each photo Cutvey's servers fetch, and nothing else from the customer's workspace: no name, no identifier, no account and no IP address. A request carries the key of Cutvey's own account with the operator. Search words are Customer Personal Data where they name a person. This Section is the customer's documented instruction for that disclosure, which a user's own search carries out.
5.8 Customer-appointed recipients. A customer-appointed recipient is a third party the customer chooses, contracts with, and connects to the Service, so that Customer Personal Data reaches it on the customer's instruction rather than on Cutvey's. The present examples are an AI assistant the customer connects to its workspace, an automation platform or application the customer authorizes with its own API key, a webhook endpoint the customer nominates, and any storage or delivery destination the customer configures.
A customer-appointed recipient is not a Subprocessor. Cutvey does not engage it, does not instruct it, holds no contract with it, pays it nothing, receives nothing from it, and cannot control what it does. It is therefore not listed in Annex III or on the published subprocessor list, and connecting one does not trigger the notice or objection rights in Section 5.5, because Cutvey is not appointing anybody. Section 5.4 does not apply to it.
For each customer-appointed recipient the customer connects, the customer:
(a) is the Controller for the disclosure, and remains the Controller for everything the recipient does with the data;
(b) confirms that it has a lawful basis for the disclosure, has given the notices Data Protection Law requires to the Data Subjects concerned, which will usually include its own clients, leads, crew and talent, and has any consent that law requires;
(c) confirms that its agreement with the recipient contains the data protection terms Data Protection Law requires of it, and, where the disclosure is a restricted transfer under Section 9, a valid transfer mechanism for it; and
(d) accepts that Cutvey is not responsible for the recipient's processing, retention, security, availability, or use of the data for its own purposes, including to train or improve models.
Cutvey will stop answering a customer-appointed recipient promptly when the customer revokes it, and may stop answering one where Section 17 or Section 34 of the Terms of Service applies.
6. Assistance to the customer
6.1 Data subject requests. Taking into account the nature of the processing, Cutvey will help the customer by appropriate technical and organizational measures, so far as possible, to respond to requests from Data Subjects exercising rights of access, rectification, erasure, restriction, portability, objection, or the right not to be subject to automated decision making.
The Service gives the customer self-service tools that do most of this directly: access to and editing of every record in the workspace, a per-record erasure tool that erases an individual client, lead, crew member, talent or vendor record and the personal data in it, machine-readable export of workspace data, and workspace deletion. A person who holds a seat in the customer's workspace can also leave it and close that seat themselves. The customer will use those tools first. Where a request needs an erasure the workspace tools cannot complete, Cutvey will carry it out on the customer's written instruction under Section 6.3 and confirm when it is done.
6.2 Requests that reach Cutvey. If a Data Subject contacts Cutvey directly about Customer Personal Data, Cutvey will not respond to the substance except to say that the request should go to the customer, and will forward the request to the customer without undue delay, unless the customer has instructed otherwise or the law requires a different response.
6.3 Further help. Where the customer needs help beyond the self-service tools, Cutvey will provide reasonable assistance. Cutvey may charge a reasonable fee for assistance that is not attributable to a failure by Cutvey and that takes significant effort, after telling the customer the fee in advance. Cutvey will not charge for assistance that takes fewer than four hours in any twelve-month period, and will not charge at all where the request arises from a Personal Data Breach or from Cutvey's failure to perform.
6.4 Impact assessments and prior consultation. Cutvey will provide the customer with reasonable information and assistance for data protection impact assessments under GDPR Article 35 and prior consultation with a Supervisory Authority under Article 36, so far as they relate to Cutvey's processing and the customer cannot get the information itself. Annex II, Section 9.5, and this DPA are the starting point for most such assessments.
6.5 Government and law enforcement requests. If a public authority asks Cutvey for Customer Personal Data, Cutvey will do all of the following, unless legally prohibited.
- Notify the customer without undue delay.
- Tell the authority that Cutvey is a processor and that the customer is the appropriate recipient of the request.
- Challenge a request that is unlawful or overbroad, including by seeking interim measures and exhausting available appeals, where there is a reasonable prospect of success.
- Disclose only the minimum the applicable legal process requires.
Cutvey will keep a record of such requests and make it available to the customer on request, so far as the law allows. Where a non-disclosure order prevents notice, Cutvey notifies the customer as soon as the bar lifts, and asks the authority to shorten or end the order where there are grounds.
6.6 Requests from private parties, and the legal process policy. Cutvey requires valid legal process before it discloses anything, served at the notice address at the head of this DPA.
- Civil litigants. United States federal law, 18 U.S.C. 2702(a), prohibits Cutvey from disclosing the contents of a customer's communications and files to a private party in a civil case, including under a subpoena, and Cutvey will not do so. A private party who wants workspace contents must obtain them from the customer. Where a civil subpoena seeks only basic account records, Cutvey tells the customer before responding and gives it a reasonable opportunity to object, unless a court orders otherwise.
- Requests from outside the United States. Cutvey is a United States company and the data is in the United States. A request from an authority outside the United States reaches Cutvey only through United States legal process, a mutual legal assistance treaty, or an agreement the United States has entered into. Cutvey does not respond directly to a foreign authority's demand.
- Preservation. A letter from a private party demanding preservation is not legal process; Cutvey forwards it to the customer and takes no other action. Cutvey honors a preservation request from a governmental entity under 18 U.S.C. 2703(f) for the limited period the law provides, and honors the customer's own written litigation hold under Section 10.5.
- Costs. Cutvey may charge its reasonable costs of responding to legal process about a customer, and tells the customer the cost first.
The fuller statement of this policy is in the Cutvey Terms of Service and the Cutvey Privacy Policy, and this Section is the version that binds Cutvey as processor. Where they differ as to Customer Personal Data, this Section applies.
7. Personal Data Breach
7.1 Notice. Cutvey will notify the customer of a Personal Data Breach affecting that customer's Customer Personal Data without undue delay after becoming aware of it, and in any event within 48 hours of becoming aware. Cutvey becomes aware when it has a reasonable degree of certainty that a security incident has occurred that led to Personal Data being compromised. Cutvey will not delay the notice in order to complete its investigation; where information is still being established, Cutvey will notify with what it has and supplement it under Section 7.2.
This Section applies whether the breach occurred in systems Cutvey operates or in those of a Subprocessor. Cutvey will notify the customer on the same timetable, running from Cutvey's own awareness, and will pass on what the Subprocessor tells it as it receives it.
7.2 Content of notice. The notice will describe, so far as Cutvey knows at the time: the nature of the breach, including where possible the categories and approximate number of Data Subjects and records concerned; the likely consequences; the measures taken or proposed to address it and to mitigate its effects; and a contact point for more information. Where Cutvey cannot provide everything at once, it will provide what it has and the rest as it becomes available.
7.3 Cooperation. Cutvey will cooperate reasonably with the customer, and take the reasonable steps the customer directs, to investigate, mitigate, and remedy the breach.
7.3A The customer's cooperation. The customer will cooperate reasonably with Cutvey's investigation of an incident affecting it, will preserve the logs, devices, and records on its own side that are relevant to it, and will name a single contact for the incident. The customer will not make a public statement attributing the incident to Cutvey before the parties have established the facts, unless the law requires the statement or the customer must make it to meet its own notification duty. Nothing in this Section delays or limits any notice the customer must give under Data Protection Law.
7.4 Who notifies whom. The customer, as Controller, is responsible for notifying Supervisory Authorities and Data Subjects where the law requires it. Cutvey will not notify the customer's Data Subjects or a Supervisory Authority on the customer's behalf unless the customer asks in writing or the law requires Cutvey to.
7.5 Not an admission. Cutvey's notice of a breach, and the steps it takes, are not an acknowledgment of fault or liability.
7.6 Cutvey's own obligations. Cutvey will comply with the breach notification duties that apply to it directly, including under Florida Statutes section 501.171 and the breach notification laws of any other jurisdiction whose law applies to the incident.
8. Audit
8.1 Information first. Cutvey will make available to the customer the information needed to show compliance with GDPR Article 28 and this DPA. The first route is documentary: this DPA, Annex II, the published subprocessor list, Cutvey's Privacy Policy, and Annex II of this DPA.
8.2 Questionnaire. Once in any twelve-month period, and in addition after a confirmed Personal Data Breach affecting that customer, the customer may send a reasonable written security questionnaire. Cutvey will answer within 30 days. Cutvey may answer with an industry-standard questionnaire it has already completed, such as a CAIQ or SIG Lite, where that covers the questions asked.
8.3 Third-party reports. If Cutvey obtains a third-party audit report or certification in the future, it will make the current report available to the customer under confidentiality, and that report will satisfy the customer's audit right for the period it covers. Cutvey holds no such report today.
8.4 On-site audit. Where Data Protection Law gives the customer or a Supervisory Authority a right to an on-site inspection that Sections 8.1 to 8.3 cannot satisfy, Cutvey will allow one. It is subject to the following.
- At least 30 days' written notice.
- No more than once in any twelve-month period. That limit does not apply where a Supervisory Authority requires more, where a confirmed Personal Data Breach affecting the customer has occurred, or where the customer has reasonable and documented indications that Cutvey is not complying with this DPA.
- A scope, date, and duration the parties agree, each acting reasonably and neither withholding agreement unreasonably. If they have not agreed within 30 days of the customer's notice, either party may refer the disagreement to a single independent auditor the parties appoint, who fixes a scope that is reasonable and proportionate, and that scope applies. Neither party may use this bullet to obtain access the last bullet of this Section excludes.
- Conduct during business hours, in a way that does not disrupt the Service or affect other customers.
- An auditor who is not a competitor of Cutvey and who signs a confidentiality agreement.
- No access to other customers' data, to Cutvey's source code, or to information whose disclosure would compromise the security of Cutvey or another customer.
Each party bears its own costs. The customer bears the fees of any third-party auditor it appoints, except where the audit uncovers material non-compliance by Cutvey, in which case Cutvey reimburses the customer's reasonable costs. An inspection required by a Supervisory Authority is not subject to the frequency or notice limits in this section. Nothing in this Section limits Clause 8.9 of the Standard Contractual Clauses, which prevails for the transfers it governs.
8.5 Supervisory Authorities. Cutvey will cooperate with a Supervisory Authority exercising its powers over the customer's processing.
8.6 Records of processing. Cutvey maintains a record of the categories of processing it carries out on behalf of its customers, as GDPR Article 30(2) requires, and will make it available to a Supervisory Authority on request, and to the customer so far as it concerns the customer's processing, on written request.
8.7 Customer security testing. The customer may test the security of its own workspace with Cutvey's written agreement, which Cutvey will not unreasonably withhold, once in any twelve-month period. Ask at contact@cutvey.com at least 10 business days beforehand, with the scope, the dates, the source addresses, and the name of the tester. Testing must stay inside the customer's own workspace, must not target another customer's data or shared infrastructure, must not include denial of service or load testing, and must stop if Cutvey asks it to stop. The customer gives Cutvey the full findings, each party treats the other's information as confidential, the customer bears its own costs, and Cutvey tells the customer what it is doing about anything found. Once Cutvey holds a third-party penetration test summary it may offer that instead, and where that summary covers the question being asked, it satisfies this Section.
9. International transfers
9.1 Where data is processed. Cutvey processes Customer Personal Data in the United States, on infrastructure operated by the hosting provider named on the published subprocessor list. Annex III records the provider and the region as at the effective date. Subprocessors process in the countries shown in the subprocessor list and in Annex III. By using the Service, the customer instructs Cutvey to transfer Customer Personal Data to the United States and to those countries. A change of hosting provider or region is a subprocessor change and follows Section 5.5.
9.2 Transfer mechanism. Where Cutvey's processing of Customer Personal Data is a restricted transfer out of the EEA, the UK, or Switzerland, the transfer is made under the Standard Contractual Clauses as set out in Section 11, together with the UK Addendum and the Swiss adaptations in Section 12, and Cutvey applies the supplementary measures in Annex II and the assessment in Section 9.5.
9.3 No Data Privacy Framework certification. Cutvey is not certified under the EU-US Data Privacy Framework, its UK Extension, or the Swiss-US Data Privacy Framework, and does not rely on them.
9.4 Alternative mechanisms. If a competent authority or court invalidates, suspends, or replaces a transfer mechanism relied on in this Section, or if a new mechanism becomes available that the parties can lawfully use, Cutvey will notify the customer and the parties will work in good faith to adopt a lawful replacement without undue delay. Cutvey will publish an updated version of this DPA incorporating the replacement mechanism in its default, unamended form, and that version applies from the date stated in the notice unless the customer objects in writing within 30 days, in which case the parties will agree an alternative or the customer may terminate. Cutvey will not amend, and does not have authority to amend, any transfer mechanism on the customer's behalf. Where a mechanism cannot be replaced, Cutvey will suspend the affected transfer or offer the customer termination on the basis set out in Section 5.5.
9.5 Transfer impact assessment. The parties have assessed the transfer under Clause 14 of the Standard Contractual Clauses and record the following.
(a) What is transferred. Ordinary business contact, project, scheduling, commercial and media data of the categories in Annex I. No special category data is requested by the Service, subject to what Section 2.3 records about ordinary production records. The data is not of a kind that United States intelligence authorities have shown any interest in collecting.
(b) Who receives it. Cutvey LLC, a small private Florida limited liability company with no government contracts, hosting a business software product for video production companies.
One Subprocessor processes media outside Cutvey's own hosting: netcup GmbH, a company established in Germany, on a virtual server with dedicated processor cores in Manassas, Virginia, United States (Annex III). The server receives one uploaded file at a time through a short-lived link valid for that single object, holds it only while the job runs, typically minutes, on temporary storage encrypted with a key generated at each boot and held only in the server's memory, and deletes it when the job ends. That encryption protects the file on netcup's disks; like any hosted virtual server, the server's memory is within reach of its host. It has no database access and holds no database or storage credentials. netcup's group companies in Germany and Austria, named on the published subprocessor list, may access the server from the EU for support and infrastructure work. netcup has not yet confirmed to Cutvey which company operates the Manassas data center facility.
(c) The relevant United States law. The provisions capable of applying are section 702 of the Foreign Intelligence Surveillance Act (50 U.S.C. 1881a), Executive Order 12333, and the Clarifying Lawful Overseas Use of Data Act. Cutvey does not assert that it falls outside the definition of an "electronic communication service provider" in 50 U.S.C. 1881(b)(4), and it therefore assesses section 702 as potentially applicable rather than inapplicable. Executive Order 14086 and the redress mechanism established under it, together with the Data Protection Review Court, apply to any such collection, whether or not Cutvey participates in the Data Privacy Framework.
(d) Practical experience. As at the effective date of this DPA, Cutvey had received no order or directive under section 702, no national security letter, no request under Executive Order 12333, and no other request from a public authority for Customer Personal Data. Cutvey keeps a record of any such request under Section 6.5 and makes it available to the customer so far as the law allows. Cutvey gives no commitment to restate or update this paragraph, because a legal prohibition on disclosure could prevent it from doing so.
(e) Supplementary measures. Those in Annex II, in particular encryption in transit, encryption at rest of files and backups by the storage provider, tenant isolation, minimization, the government request policy in Sections 6.5 and 6.6, and the commitment in Section 9.6. Cutvey does not encrypt backups client-side today, so the keys for backup storage are held by the storage provider and this measure does not defeat legal process served on that provider. Annex II states the position exactly.
(f) Conclusion. The parties consider that, taking (a) to (e) together, the transfer does not prevent Cutvey from complying with the Standard Contractual Clauses. Cutvey will re-perform this assessment at least annually, and whenever it becomes aware of a change in United States law or practice, or of any request from a public authority, that affects it, and will notify the customer under Clause 14(e) and Clause 15 if it can no longer comply.
9.6 No back doors, and challenge commitment. Cutvey warrants that it has not been required to modify the Service, or to build any facility or capability, to give a public authority access to Customer Personal Data, and that it has installed no back door and holds no cryptographic key or process for the purpose of giving a public authority such access. Cutvey will challenge any request it considers unlawful or overbroad, including by seeking interim measures, and will exhaust available appeals where there is a reasonable prospect of success.
9.7 Region selection. Where Cutvey offers a customer the choice of a processing region, the region selected in that customer's workspace settings is the primary place of processing for that customer's Customer Personal Data, and Annex I is read accordingly. Sections 9.2 to 9.6 and Section 11 apply to any transfer out of that region, including transfers to Subprocessors. Selecting a region does not change where a Subprocessor processes unless the subprocessor list says so for that region.
9.8 Customer-appointed recipients and onward transfers. Where the customer connects a customer-appointed recipient under Section 5.8, the parties record the following.
(a) What the disclosure is. Cutvey makes Customer Personal Data available to the recipient on the customer's documented instruction under Section 3.1, in the same way as when the customer instructs the Service to email a proposal to a recipient the customer named. Cutvey selects nobody, transmits nothing on its own behalf, and receives nothing back.
(b) The module that applies between the parties is unchanged. Where the customer is a Controller, Module Two applies between the customer and Cutvey. Where the customer is itself a Processor, Module Three applies. Connecting a recipient does not change which module applies to the transfer of Customer Personal Data to Cutvey, and does not make Cutvey a Controller for anything.
(c) Clause 8.8. To the extent a disclosure to a customer-appointed recipient is an onward transfer for the purposes of Clause 8.8 of the Standard Contractual Clauses, Cutvey makes it only on the customer's documented instruction, and relies on the customer's confirmation under Section 5.8(c) that the recipient is bound by an appropriate safeguard under Chapter V of the GDPR, which for the present examples is the recipient's own data processing terms and Standard Contractual Clauses with the customer. Cutvey does not verify that confirmation and does not have the means to. Where the customer cannot give it, the customer must not connect the recipient.
(d) The relationship the customer has to paper. The relationship between the customer and a customer-appointed recipient is a separate one, to which Cutvey is not a party. Where that recipient processes on the customer's behalf, the customer is responsible for its own Article 28 contract with it, for its own record of processing, and for any transfer mechanism it needs. Where that recipient acts as an independent Controller for its own purposes, including where it uses what it receives to train or improve models under the customer's account settings, the customer is responsible for the lawfulness of that disclosure. Neither case is processing by Cutvey and neither is covered by this DPA.
(e) No Clause 9 notice arises. Because a customer-appointed recipient is not a Subprocessor, Clause 9 of the Standard Contractual Clauses and Section 5.5 of this DPA do not apply to it, and Cutvey owes no notice and no objection right when a customer connects one.
10. Deletion and return
10.1 During the subscription. The customer can export its workspace data in machine-readable form at any time through the Service, and can delete records and files itself, including erasing an individual client, lead, crew member, talent or vendor record with the per-record erasure tool described in Section 6.1. Where a request needs an erasure those tools cannot complete, the customer can ask Cutvey to carry it out under Section 6.1.
10.2 After termination. The customer chooses. At the end of the subscription or trial, the customer may instruct Cutvey in writing to (a) return Customer Personal Data in a machine-readable export and then delete it, or (b) delete it immediately, or (c) retain it for the grace period described below (30 days, or 60 days after a trial that ended without a paid plan) and then delete it. The customer may give that instruction at any time before the end of the subscription and up to the end of the grace period.
Cutvey deletes or returns, and keeps nothing else. Whichever option applies, Cutvey deletes all copies of Customer Personal Data at the end of it, as Clause 8.5 and Clause 16(d) of the Standard Contractual Clauses require, subject only to Sections 10.4 and 10.5. Cutvey does not retain a copy for its own purposes, and does not keep a workspace after the customer has left.
If the customer gives no instruction, option (c) applies by default: Cutvey keeps Customer Personal Data after the subscription or trial ends, so the customer can export it or reactivate, and then deletes it permanently. The period is 60 days when a trial ended without a paid plan, and 30 days when the customer canceled or Cutvey canceled the subscription for non-payment under the Cutvey Terms of Service, which happens 30 days after the payment failed; while an unpaid workspace is paused before that, nothing is deleted. Export remains available to the customer through the Service throughout the grace period at no charge. Where the customer chooses (a), Cutvey will provide the data in a commonly used machine-readable format within 30 days, charging only its reasonable costs where the request goes beyond the standard export. Sections 10.4 and 10.5 apply to every option.
10.3 Self-service deletion. The customer can delete its whole workspace at any time from the Service. Deletion is confirmed by email and takes effect after a 7-day cooling-off period, during which it can be canceled.
10.4 Backups. Deleted data persists in backups until those backups age out on a rolling schedule of up to 30 days, after which it is gone. Those backups are encrypted at rest by the storage provider, using keys the provider manages. They are not restored except to recover the Service, and they remain subject to this DPA until deleted.
10.5 Retention required by law, and holds. Cutvey may keep Customer Personal Data where the law requires it, including financial and tax records, and data subject to a legal hold that Cutvey is required to observe or that the customer has asked for in writing under the Cutvey Terms of Service. It will keep only what the law requires, only for as long as required, and this DPA continues to apply to it.
Electronic signature records are not an exception. A signed document and its signature audit record live inside the customer's workspace, and they are deleted with the workspace, like everything else in it. Cutvey keeps no separate archive of them after a customer leaves. Signers are told at the time of signing to download or email themselves a copy of what they signed and its signing record, and Cutvey emails a copy to every signer on completion. The customer should keep its own copies of signed documents and not rely on Cutvey as its archive.
10.6 Confirmation of deletion. Cutvey will confirm in writing that deletion has taken place, including the date it completed and the date on which the last backup containing the data aged out, on the customer's written request made at any time within twelve months after the end of the subscription. Cutvey will also send that confirmation without a request where the customer instructed immediate deletion under Section 10.2(b).
11. Standard Contractual Clauses
11.1 Incorporation. Where the GDPR applies to a transfer of Customer Personal Data to Cutvey, whether because the data exporter is established in the EEA or because the exporter is subject to the GDPR under Article 3(2), the Standard Contractual Clauses are incorporated into this DPA by reference and form part of it. The full text is published by the European Commission at https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj. Cutvey will provide a copy on request.
11.2 The choices, pre-filled. The parties agree that:
| Item | Choice |
|---|---|
| Modules used | Module Two (controller to processor) where the customer is a Controller, and Module Three (processor to processor) where the customer is itself a Processor. The module that applies follows the customer's actual role for the data transferred, as Section 2.1 explains. Every selection below applies to whichever module applies |
| Data exporter | the customer |
| Data importer | Cutvey LLC |
| Clause 7, docking clause | included. An entity that is not a party may accede as an additional data exporter by completing the Signature Page in Annex IV, marking it "Accession under Clause 7", and delivering it to contact@cutvey.com. Accession takes effect on Cutvey's written acknowledgment |
| Clause 9, subprocessors | Option 2, general written authorization, with the notice period in Clause 9(a) set to 14 days, operated as described in Section 5 of this DPA. The same selection applies for Module Three |
| Clause 11(a), redress | the optional independent dispute resolution body paragraph is not included |
| Clause 13, supervisory authority | as identified in Annex I.C |
| Clause 17, governing law | Option 1 is used. The Clauses are governed by the law of Ireland, being an EU member state that allows for third-party beneficiary rights |
| Clause 18(b), forum | the courts of Ireland, without prejudice to a Data Subject's right under Clause 18(c) to bring proceedings in the member state of their habitual residence |
| Annex I.A, parties | as set out in Annex I of this DPA, in the customer's account record, and on any executed Annex IV Signature Page |
| Annex I.B, description of transfer | as set out in Annex I of this DPA |
| Annex I.C, competent authority | as identified in Annex I.C of this DPA |
| Annex II, technical and organizational measures | as set out in Annex II of this DPA |
| Annex III, list of subprocessors | as set out in Annex III of this DPA and, as updated from time to time, at the published subprocessor list |
| Frequency of transfer | continuous, for as long as the customer uses the Service |
11.3 Precedence. If the SCCs conflict with any other part of this DPA or the Terms of Service, the SCCs prevail as to the transfers they govern.
11.4 Signature. Acceptance of the Terms of Service, which incorporate this DPA, constitutes execution of the SCCs and their Annexes by both parties, and no separate signature is required. A customer whose process requires a signed copy uses Annex IV, and Cutvey will countersign it without changing any term.
11.5 Affiliates. Where the customer's affiliates use the Service under the customer's subscription, the customer enters this DPA on their behalf as well as its own, and the customer remains responsible for their compliance and is the single point of contact for every right and obligation under this DPA. An affiliate that requires its own contractual relationship may accede under Clause 7 as set out above.
12. UK and Switzerland
12.1 United Kingdom. For transfers subject to the UK GDPR, the SCCs as incorporated in Section 11 apply as amended and supplemented by the UK Addendum, including Part 2 of the UK Addendum (the Mandatory Clauses), which is incorporated into this DPA in full and unamended. For the purposes of Part 1:
| Table | Entry |
|---|---|
| Table 1, parties and start date | the customer as Exporter and Cutvey LLC as Importer, with the details in Annex I and the customer's account record. Start date: the date the customer first accepted the Cutvey Terms of Service, or the date shown on an executed Annex IV Signature Page. Key contact for the Importer: contact@cutvey.com |
| Table 2, selected SCCs | the SCCs incorporated by Section 11, with the modules and options selected in Section 11.2 |
| Table 3, appendix information | Annex I, Annex II, and Annex III of this DPA |
| Table 4, ending the Addendum when the Approved Addendum changes | Exporter |
References in the SCCs to the GDPR are read as references to the UK GDPR, references to EU member state law are read as references to UK law, the governing law is the law of England and Wales, the courts are the courts of England and Wales, and the supervisory authority is the Information Commissioner's Office.
12.2 Switzerland. For transfers subject to the Swiss FADP, the SCCs as incorporated in Section 11 apply with these adaptations, consistent with the recognition given by the Federal Data Protection and Information Commissioner: references to the GDPR are read as references to the FADP and its ordinance; the competent supervisory authority under Clause 13 and Annex I.C is the Federal Data Protection and Information Commissioner; and the term "member state" must not be read to prevent Data Subjects in Switzerland from bringing proceedings in their place of habitual residence under Clause 18(c). The revised FADP, in force since 1 September 2023, protects the personal data of natural persons only.
12.3 Brazil. For transfers subject to the LGPD, the parties adopt the standard contractual clauses approved by the ANPD in Resolution CD/ANPD No. 19 of 23 August 2024, in their approved form, which are incorporated into this DPA by reference for those transfers. Cutvey is the operator and the customer is the controller. Where those clauses conflict with this DPA, they prevail for the transfers they govern. Cutvey will provide a copy on request.
13. Liability
13.1 Each party's liability under or in connection with this DPA, including under the Standard Contractual Clauses as between the parties, is subject to the exclusions and limitations in the Cutvey Terms of Service, except as set out in Section 13.2.
13.2 For claims arising from Cutvey's breach of this DPA or of the Standard Contractual Clauses, including a Personal Data Breach caused by Cutvey's failure to implement the measures in Annex II, Cutvey's aggregate liability will not exceed the greater of (a) three times the fees paid by the customer in the twelve months before the event giving rise to the claim, or (b) US$5,000. That limit is the same limit as the security cap in the Terms of Service, not an additional one: a single amount shared between this DPA and the Terms, so that the two can never be added together for the same incident. The exclusion of liability for lost or corrupted data in the Terms of Service does not apply to a Personal Data Breach caused by Cutvey.
13.3 Nothing in this DPA limits a Data Subject's rights under the Standard Contractual Clauses, a party's liability to a Data Subject, or a party's liability to a Supervisory Authority, and nothing limits liability that the law does not allow to be limited.
13.4 Liability between the parties is apportioned so that each bears the share of any damage, fine, or compensation that corresponds to its responsibility for the event, consistent with Clauses 12(d) and 12(e) of the Standard Contractual Clauses.
13.5 Carve-outs. The limits in this Section do not apply to liability for Cutvey's fraud or willful misconduct, or for gross negligence to the extent applicable law does not allow liability for it to be limited. Where the law does allow it to be limited, the limits apply to gross negligence to the maximum extent permitted.
13.6 Insurance. Cutvey makes no representation in this DPA about insurance it carries. It will answer honestly if asked.
13.7 Who these limits protect. The limits and exclusions in this Section, and those in the Cutvey Terms of Service that this Section applies, protect Cutvey LLC and its members, managers, officers, employees, contractors and agents, taken together as one, and a claim against any of them counts against the same single amount. Nothing in this Section limits a Data Subject's rights under the Standard Contractual Clauses, a party's liability to a Supervisory Authority, or any liability the law does not allow to be limited.
14. CCPA and other US state privacy laws
14.1 Roles. Where the CCPA applies, the customer is a Business and Cutvey is a Service Provider processing Personal Information on the customer's behalf under a written contract, which is this DPA.
14.2 Cutvey's commitments. Cutvey:
- will not sell or share Personal Information as those terms are defined in the CCPA;
- will retain, use, and disclose Personal Information only for the following limited and specified purposes, and for no other purpose: (i) providing, operating, and making available the Service to the customer as described in the Terms of Service and configured by the customer; (ii) securing the Service and detecting, preventing, and responding to security incidents, fraud, and illegal activity; (iii) debugging and repairing errors that impair intended functionality; (iv) maintaining and improving the quality and safety of the Service, without building or training any model on Personal Information and without using Personal Information to develop anything outside the Service; (v) providing support to the customer; (vi) billing the customer for the Service; and (vii) complying with law. Cutvey will not retain, use, or disclose Personal Information for any commercial purpose of its own, or outside the direct business relationship with the customer, except where the CCPA expressly permits a service provider to do so;
- will not combine Personal Information received from the customer with Personal Information received from another source, except as the CCPA permits a Service Provider to do;
- will comply with the obligations the CCPA places on a Service Provider and will provide the same level of privacy protection the CCPA requires;
- will tell the customer if it determines it can no longer meet those obligations, and, on notice, will stop the processing concerned or take other reasonable steps to remedy it;
- grants the customer the right to take reasonable and appropriate steps to ensure that Cutvey uses Personal Information in a manner consistent with the customer's CCPA obligations, exercised through Section 8 of this DPA;
- grants the customer the right, upon notice to Cutvey, to take reasonable and appropriate steps to stop and remediate any unauthorized use of Personal Information by Cutvey, including requiring Cutvey to cease the processing concerned, to delete the Personal Information affected, and to provide a written account of what occurred and what has been done about it;
- will help the customer respond to verifiable consumer requests to know, delete, correct, and opt out, as described in Section 6; and
- will, on the customer's direction to delete Personal Information in response to a consumer request, delete it and direct any Subprocessor that received it to delete it, and will confirm to the customer when it has done so.
Cutvey certifies that it understands the restrictions in this Section 14 and will comply with them.
14.3 No monetary or other valuable consideration. The parties acknowledge that no Personal Information is disclosed by the customer to Cutvey as consideration for the Service or for anything else of value.
14.4 Deidentified data. If either party gets deidentified data, it will not try to reidentify it, will keep it deidentified, and will contractually oblige anyone it gives it to do the same.
14.5 Other US state laws. Where the Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Florida, or another comparable US state privacy law applies, the customer is the controller and Cutvey is the processor, and this DPA sets out the processing instructions, duty of confidentiality, security obligations, subprocessor terms, assistance, deletion and return, and audit rights those laws require of a processor contract. Cutvey processes only on the customer's instructions and helps the customer meet its own obligations under those laws.
14.6 Other jurisdictions. Where Quebec's Law 25, PIPEDA, the Australian Privacy Act, Japan's APPI, or Korea's PIPA applies to a customer's use of the Service, Cutvey acts on the customer's behalf and behind the customer's own obligations. It processes only on the customer's instructions, keeps the information confidential, applies the measures in Annex II, uses Subprocessors only under Section 5, assists with access, correction, and deletion requests under Section 6, notifies confidentiality incidents under Section 7, and returns or deletes the information under Section 10. For Quebec, this Section, Annex II, and Section 9.5 are the information the customer needs for its privacy impact assessment before communicating personal information outside Quebec.
15. General
- Term. This DPA takes effect when the customer accepts the Terms of Service and continues while Cutvey processes Customer Personal Data. Provisions that by their nature should survive, do.
- Changes to this DPA. Cutvey may update this DPA where the law changes, where the Service changes, or to keep it accurate. Every version carries a version number and effective date. A change that takes nothing from the customer, including one that describes a new optional feature, takes effect when posted. A new Subprocessor follows Section 5.5 (at least 14 days' notice and the right to object), and updating the subprocessor list, or an Annex, to reflect current fact is not a change to this DPA. A change that materially reduces the customer's protections, including the level of security described in Annex II, takes effect at least 30 days after Cutvey gives notice of it by email and in the Service, and the customer may terminate the subscription before then, with the refund Section 35 of the Terms of Service provides. A change needed for security, to stop abuse or to comply with the law may take effect at once, with notice at the same time. A notice may be a short summary with a link to this DPA. Continuing to use the Service after a change takes effect is acceptance of it, and a version Cutvey asks the customer to accept applies from the moment it is accepted. Where the law gives the customer more notice or more rights, the customer keeps them. No change to this DPA alters the Standard Contractual Clauses.
- Order of precedence. SCCs, then this DPA, then the Terms of Service.
- Assignment. Cutvey may assign this DPA together with the Terms of Service to an affiliate, or to a successor in a merger, acquisition, reorganization, or sale of assets, provided the assignee assumes every obligation in this DPA and in the Standard Contractual Clauses incorporated by it. Cutvey will notify the customer at least 30 days beforehand. Where the assignment would place Customer Personal Data in a country without an adequacy decision and without a transfer mechanism already in force, the customer may terminate before the assignment takes effect.
- Governing law and disputes. As set out in the Terms of Service, with four exceptions.
- Disputes governed by the Standard Contractual Clauses are subject to Clauses 17 and 18 of those Clauses, meaning the law and the courts of Ireland.
- Disputes governed by the UK Addendum are subject to the law and the courts of England and Wales.
- A Data Subject may always bring proceedings in the courts of the member state in which they have their habitual residence.
- No arbitration agreement in the Terms of Service applies to any of those disputes, or to any claim a Data Subject brings as a third-party beneficiary of the Clauses.
- Severability. If a provision is unenforceable, the rest stays in force.
- Language. This DPA is written in English, and the English version controls. A translation is for convenience only, except to the extent the law where the customer is established requires the translation to prevail, in which case it prevails to the extent that law requires. A customer in Quebec may ask at contact@cutvey.com for a French version, and by accepting this DPA in English expressly requests and agrees that it, and every related document, be drawn up in English. Vous avez expressément demandé que cette convention et tous les documents qui s'y rattachent soient rédigés en anglais. (Charter of the French Language, section 55.)
- Contact and security contact. contact@cutvey.com is the single address for everything, including privacy, legal, data protection, and security. Legal notices to Cutvey should be emailed there with a copy by mail to Cutvey LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702, USA. A security or privacy incident reported to that address reaches the Founder of Cutvey LLC, who is the person responsible for security at Cutvey. Cutvey aims to acknowledge such a report within one business day. The rules for reporting a vulnerability safely are in the Cutvey Acceptable Use Policy.
- Representatives. Cutvey is established in the United States. Section 17.1 of the Cutvey Privacy Policy says how to reach Cutvey about personal data, and names a representative in the European Union and the United Kingdom where one is appointed, and is kept current there rather than here. Data Subjects and Supervisory Authorities may also contact Cutvey directly at contact@cutvey.com.
- Data Protection Officer. Cutvey has not appointed a Data Protection Officer. Its core activities do not consist of processing operations that require regular and systematic monitoring of Data Subjects on a large scale, nor of large-scale processing of special category data, so GDPR Article 37(1) does not require one. Data protection questions go to contact@cutvey.com.
Annex I: description of the processing
A. The parties
- Data exporter: the Cutvey customer, identified by the account and billing details in its Cutvey workspace. Activities relevant to the transfer: use of the Cutvey Service to run a video production business. Contact: the account owner's email address on record. Role: Controller, or Processor where Section 2.1 applies.
- Data importer: Cutvey LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702, USA, principal place of business Orlando, Florida, USA. Activities relevant to the transfer: providing the Cutvey Service. Contact: contact@cutvey.com. Role: Processor, or Subprocessor where Section 2.1 applies.
The data exporter's name, registered address, contact person, and the date on which it accepted this DPA are recorded in Cutvey's systems at the time of acceptance, and Cutvey will issue that record to the customer on request as a completed Annex I.A. Where the parties execute the Signature Page in Annex IV, the details on that page are the completed Annex I.A, and the Clauses take effect from the date the customer first accepted the Terms of Service.
B. Description of the transfer
| Item | Detail |
|---|---|
| Categories of Data Subject | the customer's own personnel and workspace users; the customer's clients and client contacts; leads and prospects; crew and freelancers; on-screen talent and people who sign releases, including a minor named in a release and the parent or guardian who signs it; vendors, and the contact people the customer records for a location or a supplier; recipients of the customer's emails, proposals, invoices, call sheets, galleries, deliveries, and review links; people appearing in media the customer uploads |
| Categories of Personal Data | name, business and personal contact details, job title and role, company, mailing and billing addresses; project, booking, and scheduling data; call sheet details including call times and locations; message and email content, including open and click events for emails the customer sends through the Service; proposal, contract, invoice, and payment metadata; electronic signature records including signer name, email, signature image, timestamp, and IP address; files, images, video, and documents the customer uploads, and any personal data inside them; comments and timecoded review notes; approvals and sign-offs of a cut, including the name given and any signature image; records that a link was opened or a delivered file was downloaded, including, on a delivery limited to invited people, the email address that was confirmed; rates of pay, time, and expense records, including receipts; bookkeeping records the customer keeps in the Service, including the bank and card transaction lines it enters or imports (date, amount and the bank's description, which can name a person), bills, payments and advances to vendors, crew and team members, and whether a vendor is marked for a 1099; what the customer's own connected payment provider account reports about the payments the customer collects (refunds, disputes and fees) and about its payouts; account and login records for the customer's own users; usage and in-workspace audit log entries |
| Sensitive data | Trade union membership in crew and contact records; where the customer records them, dietary, accessibility, or medical requirements on call sheets; personal data of minors where the customer records a release for one. Restrictions applied: the measures in Annex II apply to all Customer Personal Data without distinction, and access is role-based and workspace-scoped. No other special category data is requested or required, and the customer agrees not to use the Service as a system of record for the categories listed in Section 2.3 |
| Frequency of transfer | continuous, for as long as the customer uses the Service |
| Nature of processing | collection, recording, organization, structuring, storage, retrieval, use, transmission, display, backup, and erasure, by automated means, in order to operate the Service |
| Purpose of processing | providing, securing, maintaining, and supporting the Cutvey Service, and the features the customer chooses to use |
| Retention | for as long as the customer's subscription lasts, then as the customer elects under Section 10.2, and otherwise 30 days (60 days after a trial that ended without a paid plan) followed by deletion, subject to backup aging of up to 30 days and to retention required by law. Signed documents and their signature audit records are deleted with the workspace, as Section 10.5 says |
| Subprocessor processing | each Subprocessor in Annex III processes for the purpose and duration stated in that table, and for no longer than needed for that purpose |
C. Competent supervisory authority
The competent supervisory authority is the supervisory authority of the EU member state in which the data exporter is established, as identified in the customer's account record and confirmed on any executed Annex IV Signature Page. Where the data exporter is not established in the European Union but has appointed a representative under GDPR Article 27, it is the supervisory authority of the member state in which that representative is established. Where the data exporter is not established in the European Union and relies on GDPR Article 3(2), it is the supervisory authority of the member state in which the Data Subjects whose Personal Data is transferred are located, and the parties record that authority as the Irish Data Protection Commission unless the customer names a different competent authority on the Annex IV Signature Page.
For transfers subject to the UK GDPR, the competent authority is the Information Commissioner's Office. For transfers subject to the Swiss FADP, it is the Federal Data Protection and Information Commissioner.
Annex II: technical and organizational security measures
These are the measures Cutvey actually applies. No certification, audit, or attestation is claimed, and none is held. Cutvey may improve or replace a measure so long as the overall level of security is not materially reduced.
Access control and authentication
- Passwordless authentication using single-use codes sent to a verified email address. Codes expire after a short period, are single use, and are rate limited, and sign-in attempts are logged. Cutvey stores no user passwords. Because the email address is the primary authentication factor, Cutvey offers optional time-based one-time password two-factor authentication, and optional OIDC single sign-on for Enterprise customers, and recommends that customers require one of them for administrator accounts.
- Role-based access control inside each workspace, so a user sees only what the role assigned by the customer permits.
- Trusted device records for the companion apps, which the user or an administrator can list and revoke.
- Access to production systems is limited to the small number of people who need it, is granted individually rather than through a shared credential, and is removed when the need ends.
Tenant isolation and authorization
- Every query against workspace data is scoped to a single workspace identifier at the data access layer, so one customer's data cannot be returned in another customer's request.
- File storage is sandboxed per workspace, and every download is authorized against the requesting session before the file is served.
- Links shared with a customer's clients and crew use unguessable tokens scoped to one document or one recipient, and can be revoked.
Encryption
- TLS 1.2 or higher for all data in transit, including between the application and every Subprocessor.
- Traffic to the web application and to custom domains is encrypted in two stages. The connection from a person's device ends on the network of the Subprocessor that stands in front of the Service (Cloudflare, Annex III), where it is decrypted so that it can be inspected and protected, and a second encrypted connection carries it from that network to Cutvey's servers. It is encrypted on both stages and is not encrypted end to end between the device and Cutvey's servers.
- Encryption at rest for uploaded files in object storage and for all database backups, provided by the storage provider with provider-managed keys. Cutvey does not encrypt backups client-side today, and does not claim that it does. The production database itself runs on provider infrastructure; Cutvey does not claim application-level encryption of it.
- Third-party credentials that customers store in the Service, such as integration keys, are sealed with an application-managed key and are never displayed again after entry.
Data governance
- Minimization and quality. Fields are limited to what a feature needs. The customer can correct any record in its workspace directly, so data can be kept accurate without Cutvey's involvement.
- Pseudonymization. Product usage analytics are collected without a persistent identifier that can be tied to a person, and without storing the IP address alongside the event. Identified usage data is collected only where it is needed to operate, meter, or secure the Service, or with the user's opt-in consent.
- Accountability. A single scripted deployment path, a change history for all source code, an in-workspace audit log of significant actions, and a record of processing under GDPR Article 30(2).
Logging, monitoring, and accountability
- An audit log of significant actions inside each workspace, visible to the customer.
- Support access to a customer workspace by Cutvey personnel is possible only through an impersonation mechanism that displays a persistent banner to anyone in the session and writes an audit log entry.
- Application and infrastructure monitoring with alerting on error rates, data integrity, and capacity conditions.
Resilience and backup
- Continuous replication of the production database to off-site storage that the storage provider encrypts at rest.
- A documented restore procedure, exercised on a defined schedule against the replicated copy rather than against production, with the date and the result recorded. Cutvey does not claim a completed independent restore audit.
- Backups age out on a rolling schedule of up to 30 days.
- Recovery objectives. Cutvey targets restoration of the Service within 8 hours of a total failure, with data loss limited to the last few minutes of writes. These are targets, not a contractual commitment, and no document in the Cutvey suite promises an availability level.
Secure development and change management
- Version-controlled source code with change history.
- Automated type checking, unit tests, and a large automated pre-deployment check suite that must pass before any release reaches production.
- A single scripted deployment path, so releases are reproducible and reversible.
- Dependencies are kept deliberately minimal to reduce the supply chain attack surface.
Infrastructure
- Production hosted with DigitalOcean in the United States (New York).
- Media processing (streaming versions, posters, thumbnails and previews, including watermarked previews, of uploaded videos and photos) runs on a virtual server with dedicated processor cores with netcup GmbH in the United States (Manassas, Virginia). The server has no database access and holds no storage credentials. It receives one file at a time through a short-lived link valid for that single object, uploads its results the same way, and keeps the file only on temporary storage for that job, which is deleted after every job. Nothing is played or served from it. It is administered by SSH key only; its host firewall allows SSH and nothing else inbound; security updates install automatically; the processing runs under a dedicated unprivileged service account with systemd sandboxing; its ffmpeg is built from signature-verified source with network protocols disabled; and the access token it presents to Cutvey is stored by Cutvey only as a hash and is accepted only from that server's IP address. netcup's own technical and organizational measures, in its data processing agreement, name its Karlsruhe, Nuremberg and Vienna facilities and not yet the Manassas location; until netcup confirms measures for that location, Cutvey relies on the controls above, which it runs itself.
- Web traffic is routed to Cutvey's servers through the network of the Subprocessor named in Annex III for that purpose (Cloudflare), which helps filter attack and abusive traffic before it arrives. Cutvey's servers are configured to accept web traffic only through that network: the host firewall is configured to admit web traffic from its published address ranges only, and the server requires and verifies a client certificate that the network presents on every HTTPS connection. Cutvey may relax either control for as long as is needed to restore or protect the Service during an incident or maintenance.
- On Cutvey's servers, a reverse proxy terminating that second TLS connection with modern ciphers, a publicly trusted certificate that the network in front validates, and automatic certificate renewal.
- Bot and abuse protection on public-facing forms.
- Operating system and platform patches applied on a regular basis.
Personnel
- Everyone with access to Customer Personal Data is bound by confidentiality obligations.
- Access is granted on a need-to-know basis and revoked when the need ends.
- Everyone with production access completes security awareness training on joining and annually, and is subject to background checks to the extent the law permits before being granted that access.
- Contractors with access to Customer Personal Data are engaged under written confidentiality and data protection terms no less protective than those applying to employees, are individually attributed on production systems, and have access removed at the end of the engagement. A contractor who processes on its own account rather than under Cutvey's direction is engaged as a Subprocessor under Section 5 instead.
Vulnerability and patch management
- Dependencies and the operating system are monitored for published vulnerabilities. Critical vulnerabilities affecting production are patched within 7 days of a fix being available, and others at the next regular release.
- Penetration testing. Cutvey has not commissioned an independent penetration test. It says so here rather than implying otherwise, and will publish the fact and the date when it does.
- Administrative access. Access to the hosting, storage, and email provider consoles requires multi-factor authentication.
- Customer testing. Section 8.7 sets out how a customer may test its own workspace.
Subprocessor management
- Each Subprocessor is engaged under a written contract with data protection terms and is selected for the specific function described in Annex III.
- Each Subprocessor is required by contract to apply technical and organizational measures appropriate to the processing it performs, to assist Cutvey in meeting the obligations in Sections 6 and 7 of this DPA so far as its service is concerned, to notify Cutvey of a personal data breach without undue delay, and to delete or return data at the end of its engagement.
- Before each release, Cutvey reconciles the outbound network destinations of its shipped software and its servers against this Annex and the published subprocessor list, so that no recipient reaches production before it is listed.
Supplementary measures for international transfers
- Data minimization: Cutvey asks for no more personal data than the Service needs.
- Encryption in transit for all transfers, and encryption at rest of files and backups by the storage provider with provider-managed keys. Cutvey does not encrypt backups client-side today, so this measure does not defeat legal process served on that provider. Traffic to the web application and to custom domains is decrypted on the network of the Subprocessor that stands in front of the Service, at an edge location that may be in or outside the United States, before it is encrypted again to Cutvey's servers, so encryption in transit does not keep that content from that Subprocessor, which is bound by its own data processing addendum and transfer clauses.
- The policy on requests for data in Sections 6.5 and 6.6: notify the customer where lawful, direct the authority to the customer, refuse a private civil litigant under 18 U.S.C. 2702(a), challenge unlawful or overbroad requests, and disclose only the minimum required.
- Cutvey is a small private company with no government contracts. As at the effective date of this DPA, Cutvey had received no order, directive, or request for Customer Personal Data from any public authority, including under section 702 of the United States Foreign Intelligence Surveillance Act or Executive Order 12333. Cutvey gives no commitment to restate or update that statement, because a legal prohibition on disclosure could prevent it from doing so. Section 9.5 sets out the full transfer impact assessment and Section 9.6 the no-back-door warranty.
Incident response
- A defined process for triaging, containing, investigating, and remediating security incidents, and for notifying customers under Section 7.
Annex III: subprocessors
This annex reproduces the published subprocessor list at https://cutvey.com/legal/subprocessors as at the effective date. The published list is the current one and is incorporated by reference. Where a provider trades under a brand, the published list names the contracting entity where Cutvey has confirmed it from the executed vendor agreement.
| Subprocessor | Purpose | Personal data touched | Location of processing | Duration of processing |
|---|---|---|---|---|
| DigitalOcean, LLC | Application hosting and database | All Customer Personal Data in the workspace | USA (New York) | For the life of the subscription, plus the retention and backup periods in Section 10 |
| netcup GmbH | Media processing: streaming versions, posters, thumbnails and previews, including watermarked previews, of uploaded videos and photos. The originals and every result are stored with Cloudflare, 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. No account data, no database access, and no storage credentials | USA (Manassas, Virginia) | While a file is being processed, typically minutes. The copy is deleted when processing ends and no copy is retained |
| Cloudflare, Inc. | File storage for uploads and deliverables, backup storage, bot protection on forms, DNS and CDN, and inbound email routing for messages addressed to a workspace. Reverse proxy and network security in front of the Service: Cloudflare's network receives the traffic to the web application and to customers' custom domains, protects it against attacks and abuse, passes it to Cutvey's servers, and issues and renews the TLS certificates presented to visitors of the application and of custom domains | Uploaded files and their contents, database backups, both encrypted at rest by Cloudflare with keys Cloudflare manages, IP address and request metadata for bot protection and routing, and, for inbound email, the sender, subject and body of a message sent to a workspace's Cutvey address, which the routing provider sees before Cutvey does. For traffic to the web application and to custom domains: the content of each request and response in transit, which can include any Customer Personal Data being sent or viewed through the Service at that moment, and the IP address and connection details of the person's device. That traffic is decrypted on Cloudflare's network, inspected and protected, and encrypted again to Cutvey's servers | United States for stored objects and backups. Request routing, bot protection and the reverse proxy operate at Cloudflare edge locations worldwide: a request is received and processed at an edge location near the person making it, which may be outside the United States, and is then passed to Cutvey's servers in the United States. Request content and request metadata including IP address are processed there in transit | For the life of the subscription, plus the retention and backup periods in Section 10. Request and response content at the edge is processed in transit; Cloudflare may hold a temporary cached copy of static application files and of files a workspace has made public, and keeps security and traffic records for its own retention periods |
| Stripe, Inc. | Subscription billing for the customer's Cutvey plan and App licenses. Separately, where the customer connects its own Stripe account through Stripe Connect, Stripe acts for the customer directly under the customer's own agreement with Stripe and is not Cutvey's Subprocessor for that flow; Cutvey transmits invoice and payer details to the customer's connected account at the customer's instruction, reads back from that account what it reports about those payments (their status, refunds, disputes and their outcome, and the fee on each payment and each dispute) and the amount, date and status of each payout from that account, so that the customer's invoices and books are right, and never holds funds | Names, email addresses, billing addresses, payment metadata. Card numbers go directly to Stripe and never reach Cutvey | United States, with regional processing by Stripe group entities including in the European Union, under Stripe's own data protection terms | For the life of the subscription, plus the record retention periods Stripe applies as a regulated payment processor |
| Resend, Inc. | Transactional and product email delivery | Recipient names and email addresses, email content, delivery, bounce, open and click events | USA | For the period needed to deliver the message and report delivery events, then per the provider's retention schedule |
| Postmark (ActiveCampaign, LLC) | Fallback delivery of sign-in code emails, used only when the primary provider is unavailable | Recipient email address, sign-in code email content | USA | As above |
| Google LLC (Google Workspace) | Business email for contact@cutvey.com, which is how Cutvey receives and answers support, privacy, legal, and abuse correspondence | The content of email sent to Cutvey and Cutvey's replies, the sender's email address, and any attachment sent | USA, with Google's global infrastructure | For the support correspondence retention period in the Cutvey Privacy Policy |
| Anthropic, PBC | AI assistant features, invoked by a user | The text or workspace data a user points an AI feature at, and the generated output. Not used to train models | USA | For the duration of the API call, with no retention for training |
| OpenAI, L.L.C. | Standby provider for AI assistant features, invoked by a user, used only when the primary AI provider is unavailable | The text or workspace data a user points an AI feature at, and the generated output. Not used to train models | USA | For the duration of the API call, with no retention for training |
| Sentry (Functional Software, Inc.) | Crash and error reporting for the native apps and 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, with system library names. Reports are designed and filtered so that they do not carry customer content, and account names, volume names, file and folder names, and access tokens are removed on the paths Cutvey controls before a report is sent. Where personal data nevertheless appears in the text of an error, Cutvey treats that report as Customer Personal Data | USA | For the provider's configured retention period for error events |
| Apple Inc. | Push notification delivery through APNs for the native apps and the companion app | Device push tokens | USA and Apple's global infrastructure | For as long as the Apple service requires |
| KEPTAGO LTD (Geoapify) | Place search and routing: finding the coordinates of a place the customer typed, finding the nearest hospital for a call sheet, and working out the driving distance of a mileage trip | The address or name of a shoot location as typed, or the workspace's own business address where the day has no location, and up to two shorter forms of that text; for mileage, the places typed for a trip or the saved address of a saved place; the latitude and longitude found for a place; and two pairs of latitude and longitude for a route. Requested by Cutvey's servers, with no identifier of the customer or of a user and no user IP address. The place text is sent as the customer typed it, so it can include a private home's address, or a person's name if the customer typed one into a place | European Union, through the provider's European Union endpoint. The provider is established in Cyprus | For the duration of the request, then per the provider's data processing agreement |
| GitHub, Inc. (Microsoft) | Source code hosting and continuous integration | None. No Customer Personal Data is stored in the repository | USA | Not applicable, no Customer Personal Data |
netcup GmbH is established in Germany and processes for Cutvey under its data processing agreement under Article 28 of the GDPR, concluded on September 28, 2026. Its group companies in Germany and Austria, which it names as its own subprocessors, may access the Manassas server for support and infrastructure work: 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 processes for Cutvey in the European Union under its data processing agreement under Article 28 of the GDPR. For the endpoint Cutvey uses, it names BunnyCDN in Slovenia, and Hetzner in Germany and Finland, as its own subprocessors.
A recipient the customer appoints itself is deliberately not in the table above. The clearest present example is the provider of an AI assistant a customer connects to its own workspace, such as OpenAI or Anthropic under the customer's own account. Cutvey answers that assistant on the customer's instruction and is not the party engaging the provider, so the provider is a customer-appointed recipient under Section 5.8 rather than a Subprocessor. Anthropic appears in the table above for a different reason: Cutvey's own AI features, which Cutvey invokes under its own commercial agreement.
The weather service and the stock photo service described in Section 5.7 are listed separately, because Cutvey has no data processing agreement with either operator. Each request is made by Cutvey's servers and carries no identifier of the customer or of a user and no user IP address. A weather request carries no text of a place; a stock photo search carries the words the user typed.
| Service | Operator | Purpose | What is sent | Location of the operator |
|---|---|---|---|---|
| Open-Meteo forecast (customer-api.open-meteo.com) | OpenMeteo GmbH | Weather, sunrise and sunset for call sheets | Latitude, longitude and the shoot date | Switzerland |
| Pexels API (api.pexels.com, images.pexels.com) | Canva Germany GmbH | Stock photo search on a moodboard | The search words as typed, and the address of each photo fetched | Germany, and outside the EU as its operator states |
| Pixabay API (pixabay.com) | Canva Germany GmbH | Stock photo search on a moodboard | The search words as typed, and the address of each photo fetched | Germany, and outside the EU as its operator states |
Cutvey does not control what these operators log or for how long. The weather service's published terms say that it keeps a log of requests, including the requesting server's address and the request itself, for 90 days. The stock photo service's published terms set no period for keeping requests, and they let it use the words of a search to improve its own services, including by machine learning; it decides that for itself, which is why Cutvey sends it nothing else.
Apple also acts as an independent controller, not as Cutvey's Subprocessor, for App Store distribution and purchases, for the end user's Apple Account, and for the end user's own private CloudKit database, which Cutvey cannot read. Stripe likewise acts as an independent controller for its own fraud prevention, financial-crime, and regulatory obligations. Apple's and Stripe's own terms and privacy policies govern that processing, and Section 5.7 applies to it.
Crash and error reports also go to an endpoint Cutvey operates itself on app.cutvey.com. That is Cutvey, not a third party, so it is not a Subprocessor and is not in the table above.
Cutvey's professional advisers, such as its accountants and lawyers, act under their own professional duties of confidentiality and are not Subprocessors, provided they receive Customer Personal Data only incidentally and not for the purpose of processing it on Cutvey's behalf.
Annex IV: Signature Page (optional)
This page, when signed by both parties, evidences the Data Processing Addendum and the Standard Contractual Clauses incorporated by it, completes Annex I.A, and takes effect from the date the customer first accepted the Cutvey Terms of Service. The terms are the published terms and are not negotiated.
Data exporter
- Legal entity name: ______________________
- Registered address: ______________________
- Country of establishment: ______________________
- Contact person for data protection (name, position, email): ______________________
- Role (tick one): ( ) Controller ( ) Processor acting for another controller, see Section 2.1
- Competent supervisory authority (see Annex I.C): ______________________
- Cutvey workspace name or account email: ______________________
- Signature: ____________ Name: ____________ Title: ____________ Date: ______
Data importer
- Cutvey LLC, 7901 4th St N, Ste 300, St. Petersburg, FL 33702, USA
- Contact: contact@cutvey.com
- Signature: ____________ Name: ____________ Title: ____________ Date: ______
Accession under Clause 7 (docking). An additional entity may accede as a data exporter by completing this page, marking it "Accession under Clause 7", and delivering it to contact@cutvey.com. Accession takes effect on Cutvey's written acknowledgment.
End of Data Processing Addendum.