Data Processing Agreement
Under Art. 28 of the General Data Protection Regulation (GDPR) between the customer as controller ("customer") and AutoDM, owner Julian Gartner, Weikertsham 10A, 83512 Wasserburg am Inn, Germany, info@contentcuts.de, as processor ("we", "us"). This agreement applies upon conclusion of the contract for ContentCuts under the Terms of Service without a separate signature. The governing language version follows Section 25(4) of the Terms of Service.
1 Subject matter, conclusion, term
(1) We process personal data on behalf of the customer to the extent necessary for the services of ContentCuts under the Terms of Service and their service description (main contract). This agreement governs the rights and obligations of both parties in this processing.
(2) The customer accepts this agreement together with the Terms of Service when ordering. Electronic form is sufficient (Art. 28(9) GDPR). The customer can access, save and print it at any time at contentcuts.de/dpa.
(3) This agreement applies for the term of the main contract and beyond until we have deleted or returned all data from the engagement under Section 9.
(4) Data we process as a controller in our own right, such as the customer's own contract, billing and contact data, is not covered by this agreement. Our privacy policy applies to it.
2 Nature, purpose, data, data subjects
| Item | Description |
|---|---|
| Nature of processing | Collection (upload, import from connected folders), storage, reading (transcription, image and audio analysis), editing (cutting, captions, graphics, cut-out of persons, audio processing), transmission to sub-processors, provision for download, publication on connected accounts after the customer's approval, deletion. |
| Purpose | Creating videos, clips, ideas and scripts, post scheduling and analytics for the customer; customer memory for future orders; security, troubleshooting and quality review. |
| Types of data | Image and video recordings of persons (appearance, facial expressions, surroundings), voice and audio recordings, transcripts and texts derived from them, names and other details contained in material, briefings or change requests, contact and profile details in brand settings, content and metrics of social media posts, access tokens of connected accounts, usage and log data of the customer's users. Depending on the material, special categories under Art. 9 GDPR may be affected, such as health information in conversations. |
| Data subjects | The customer and its staff, persons seen or heard in the material (such as guests, the customer's clients, passers-by), persons named in content, users of the customer account. |
We do not perform facial recognition to uniquely identify persons. We only detect where a face or person is located in the image, for example for framing, orientation and cut-out.
3 Instructions
(1) We process the data only on documented instructions from the customer, including with regard to transfers to third countries, unless EU or German law requires us to process; in that case we inform the customer of that legal requirement before processing, unless the law prohibits this.
(2) Instructions result from the main contract, this agreement and the customer's settings and orders in the dashboard. The customer gives individual instructions in text form to info@contentcuts.de. Instructions beyond the agreed scope of services are treated as change requests.
(3) The customer instructs us to derive anonymized, aggregated insights from usage to improve our styles (Section 13(6) of the Terms of Service). These insights are no longer personal data and do not allow conclusions about the customer, persons or content. We do not use the data to train AI models.
(4) If we consider an instruction to infringe the law, we inform the customer without undue delay. We may suspend its execution until the customer confirms or changes the instruction.
4 Our obligations
(1) Persons with access to the data at our company are bound to confidentiality or subject to a statutory duty of confidentiality. They process the data only on instructions.
(2) We implement the technical and organizational measures under Art. 32 GDPR described in Appendix 1. We may adapt them to the state of the art as long as the level of protection does not decrease.
(3) We keep a record of processing activities under Art. 30(2) GDPR.
(4) We are currently not required to appoint a data protection officer. The contact for data protection is Julian Gartner, info@contentcuts.de.
(5) We process the data only in the EU, in the European Economic Area or in third countries under Section 6.
5 Sub-processors
(1) The customer grants general authorization for the engagement of sub-processors. The sub-processors engaged at conclusion of the contract are listed in Appendix 2 and are deemed approved.
(2) Before adding or replacing a sub-processor, we inform the customer by email at least 30 days in advance and update Appendix 2. The customer may object to the change in text form within 14 days of receiving the information for an important reason relating to data protection. If no reasonable solution is found, either party may terminate the main contract for cause with effect from the change. In urgent cases, such as an outage or security vulnerability at the previous provider, we may shorten the period; the right to object remains.
(3) We contractually bind each sub-processor to data protection obligations equivalent to those in this agreement, in particular to sufficient guarantees for appropriate technical and organizational measures. We are liable to the customer for compliance by our sub-processors.
(4) Ancillary services such as telecommunications, postal and transport services and the platforms on which the customer itself maintains accounts and publishes content are not sub-processing.
6 Transfers to third countries
(1) Transfers to countries outside the EEA only take place if the requirements of Art. 44 to 49 GDPR are met, in particular (a) on the basis of an adequacy decision, for the USA the EU-US Data Privacy Framework where the recipient is certified under it, or (b) on the basis of the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914), for sub-processors in Module 3, in each case with any supplementary measures found necessary in an assessment.
(2) The customer instructs us to transfer data on these bases to the countries listed in Appendix 2 for the purposes stated there.
7 Assistance to the customer
(1) We assist the customer with appropriate technical and organizational measures in responding to requests from data subjects under Art. 12 to 23 GDPR. The dashboard offers download and deletion functions for this, including an export of all account data as a JSON file and deletion of the entire account. If data subjects contact us directly, we forward the request to the customer without undue delay and do not respond ourselves unless instructed.
(2) Taking into account the information available to us, we assist the customer with its obligations under Art. 32 to 36 GDPR, for example with a data protection impact assessment or a prior consultation with the supervisory authority.
(3) We may charge reasonably for assistance that goes beyond the dashboard functions and is not caused by a breach on our part, after prior notice.
8 Notification of breaches
(1) We notify the customer of a personal data breach concerning its data without undue delay, where possible within 24 hours and at the latest within 48 hours after becoming aware of it, by email to the address in its account.
(2) The notification contains, as far as known, the information under Art. 33(3) GDPR: nature of the breach, categories and approximate number of data subjects and records, likely consequences and measures taken or proposed. Missing information is provided in phases.
(3) We take the necessary measures without undue delay to secure the data and mitigate possible adverse effects and assist the customer with its notification duties under Art. 33 and 34 GDPR.
9 Deletion and return
(1) During the term, we delete raw footage 30 days and finished videos 60 days after delivery of the last version, with notice at least seven days in advance and an option to extend in the dashboard (Section 21 of the Terms of Service). The customer may delete data itself in the dashboard at any time.
(2) After the end of the services, the customer may download all results until the end of the contract; on request we provide download links (return). Within 30 days after the end of the contract, we delete all data from the engagement unless EU or German law requires storage. Copies in backups of our sub-processors are deleted in their rotation cycles.
(3) On request we confirm deletion in text form.
10 Evidence and audits
(1) We make available to the customer all information necessary to demonstrate compliance with Art. 28 GDPR, in particular this agreement, the measures in Appendix 1 and, on request, current audit reports or certificates of our sub-processors, as far as they release them for disclosure.
(2) The customer or an auditor appointed by it who is bound to confidentiality and is not our competitor may verify compliance with this agreement, including through inspections. Inspections must be announced at least four weeks in advance, take place during usual business hours without avoidable disruption of operations and, except where there is a specific reason, are limited to once per calendar year. We do not grant access to data of other customers or to trade secrets not needed for the audit.
(3) The customer bears the costs of an inspection unless it reveals a material breach on our part.
11 Customer obligations
(1) The customer is responsible for the lawfulness of the processing, in particular for having a legal basis for the material, such as the consents of persons depicted (Section 10(2) of the Terms of Service), and for fulfilling the information obligations under Art. 13 and 14 GDPR. It only uploads material containing special categories of personal data if there is a legal basis under Art. 9 GDPR.
(2) The customer informs us without undue delay if it detects errors or irregularities in the processing.
12 Liability
(1) Towards data subjects, both parties are liable under Art. 82 GDPR.
(2) In the internal relationship, each party bears the damage to the extent it is responsible for the circumstance giving rise to the damage (Art. 82(4) and (5) GDPR). We are only liable if we have breached obligations of the GDPR specifically directed to processors or acted outside or contrary to lawful instructions of the customer.
(3) Otherwise, the liability provisions of the main contract (Section 18 of the Terms of Service) apply between the customer and us to the extent permitted by law.
13 Final provisions
(1) In the event of conflict between this agreement and the main contract, this agreement takes precedence in matters of data protection.
(2) Changes to this agreement are made under Section 23 of the Terms of Service, changes of sub-processors under Section 5.
(3) If a provision is invalid, the remainder remains valid; it is replaced by the statutory rule, in particular Art. 28 GDPR.
(4) Applicable law and place of jurisdiction follow the main contract (Section 25 of the Terms of Service).
Appendix 1: Technical and organizational measures
We do not operate our own data centers. Data is held by the service providers listed in Appendix 2, which operate their data centers according to recognized standards (such as ISO 27001 or SOC 2). On this basis, the following measures apply:
1. Confidentiality
- Physical access: physical protection of data centers by the service providers; the owner's devices with encrypted storage and automatic screen lock.
- System access: user passwords only as salted hashes (PBKDF2 with SHA-256), limits on login attempts, sessions via signed cookies sent only over HTTPS and not accessible to scripts; administrative accounts at service providers with strong passwords and two-factor authentication where offered.
- Data access: only the owner has access to customer data; media can only be retrieved via signed, time-limited links; keys and secrets are kept only in the service providers' secret stores; keys with restricted permissions where possible.
- Separation: each customer's data is logically separated under its own customer identifier; tests run with test data.
- Data minimization: internal notifications to the owner contain only identifiers, links and error messages, no media files and no contact data.
2. Integrity
- Transfer: all data is transmitted only in encrypted form (TLS); storage at the service providers is encrypted at rest.
- Input control: logging of orders, status changes, AI calls and errors per video; access and change logs of the service providers.
3. Availability and resilience
- Redundant infrastructure of the service providers; continuous monitoring of processes with automatic alerts to the owner.
- Rate limits, cost caps and usage limits against overload and misuse.
- New versions are rolled out only after automated tests and a smoke test, with automatic rollback to the last version on errors.
- The originals of raw footage remain with the customer; finished results can be re-rendered from stored project data until it is deleted.
4. Deletion concept
- Automatic deletion of raw footage 30 days and finished videos 60 days after the last delivery, with prior notice.
- Deleting a video or account by the customer removes the data from storage, engine and database.
- Deletion of all data within 30 days after the end of the contract, automatically in the daily run (advance marking, check of the contract end with the payment provider, log without personal data).
- Internal notifications to the owner (Telegram) contain identifiers, links, error messages and the name or company name of the account holder, but no video content and no data of the controller's end customers; email addresses, phone numbers and credentials are automatically masked before sending.
5. Processor control and review
- Data processing agreements with all sub-processors; selection according to security level.
- AI providers only via business interfaces whose terms exclude training on customer data. For internal troubleshooting we only use tools with the same terms.
- Regular review of the measures, security reviews of the code and timely updates of dependencies.
- The editor processes customer texts such as change requests and transcripts as data, not as instructions to the system.
Appendix 2: Sub-processors
As of October 20, 2026. Bases for third countries under Section 6: DPF = EU-US Data Privacy Framework, where the recipient is certified; SCC = Standard Contractual Clauses (EU) 2021/914.
| Company and seat | Service and data | Place of processing | Basis |
|---|---|---|---|
| Anthropic PBC, San Francisco, USA | AI models for directing, review, ideas and clipping: transcripts, texts, single frames and contact sheets from the material, briefings, change requests | USA | DPF, SCC |
| Modal Labs, Inc., New York, USA | Computing: transcription, analysis, rendering of videos; engine project data | USA | DPF, SCC |
| Cloudflare, Inc., San Francisco, USA | Storage (R2) for raw footage and finished videos | location chosen automatically, EU location intended | DPF, SCC |
| Vercel Inc., San Francisco, USA | Hosting of website, dashboard and server functions; server logs | USA and EU | DPF, SCC |
| Upstash, Inc., USA | Database: account, order and metadata, customer memory, credentials of connected accounts | EU (Frankfurt am Main) | SCC for access from the USA |
| Resend, San Francisco, USA | Sending emails: name, email address, content of notifications | USA | DPF, SCC |
| Zernio, operated by ZERNIO SOFTWARE SL, Palamós, Spain | Posting interface: approved videos, texts, schedules, credentials and metrics of connected social media accounts | EU; onward transfers by Zernio only under Art. 44 et seq. GDPR | EU law |
| Google Ireland Limited, Dublin, Ireland | Only if the customer connects Google Drive: retrieval of files from the shared folder | EU, possibly USA (Google LLC) | EU law; for Google LLC DPF |
| Stripe Payments Europe, Ltd., Dublin, Ireland | Payment processing: only the customer's contract and payment data, no content | EU, possibly USA (Stripe, Inc.) | EU law; for Stripe, Inc. DPF, SCC |
Not part of this processing are the Meta services on our website (Meta Pixel and Conversions API), which only concern visitors of the ad landing page and do not process customer content, and the platforms on which the customer itself publishes.