Data Processing Agreement
This Data Processing Agreement (DPA) is an annex to the Filmsquare Terms of Service and forms part of them. It applies to personal data that Dream Ops B.V. processes on behalf of a customer as part of customer content. It meets the requirements of article 28 of the General Data Protection Regulation (GDPR).
How we handle personal data for which we are ourselves the controller (such as account, billing and analytics data) is described in our Privacy Policy and Cookie Policy, not in this DPA.
1. Parties and definitions
1.1 The parties are the customer, being the owner of a Filmsquare workspace, as controller, and Dream Ops B.V., Hamerstraat 3D, 1135 GA Edam, the Netherlands, KVK 42047001, as processor ("we", "us").
1.2 The customer enters into this DPA by accepting the Terms of Service. No separate signature is needed. A customer that wants a signed copy can ask at hello@filmsquare.ai.
1.3 Words defined in the Terms of Service have the same meaning here. Words such as personal data, processing, controller, processor, data subject, personal data breach and supervisory authority have the meaning given in the GDPR.
1.4 Where the customer is itself a processor for another controller (for example a production company working for a client), we act as its sub-processor, and the customer makes sure its own instructions are in line with those of its controller.
2. Subject matter, duration, nature and purpose
2.1 Subject matter. We process personal data in customer content to provide the Filmsquare service to the customer.
2.2 Nature. Hosting and storing, organising, structuring, copying, making renditions (such as thumbnails, proxies and previews), displaying to workspace members and to guests on share links the customer or its members make, transmitting to AI providers to generate output, exporting, backing up and deleting.
2.3 Purpose. Providing the service as described in the Terms of Service: managing productions, scripts, breakdowns, elements, shots and takes, AI generation, review comments, sign-offs, the cut and export, and the security and support of the service.
2.4 Duration. For as long as the Terms of Service apply between the customer and us, and after that until the customer content has been deleted as described in section 11.
3. Personal data and data subjects
3.1 Types of personal data. Depending on what the customer and its members put into the service:
- account data of members as it appears in the workspace (name, email address, role, avatar, activity, assignments and sign-offs);
- names, descriptions and other details of people named in scripts, breakdowns, briefs and element descriptions;
- images and video showing people, including their likeness, as reference material or generated output;
- voice recordings and generated voices;
- review comments, mentions and other messages between members;
- names, optional email addresses and notes of guests on share links;
- voice consent records (the speaker's name, the statement, the recording and the speaker's own consent);
- maker briefs, assignments, fee agreements and payment records;
- crew analytics, where the customer has switched them on (who changed what, when and through which channel, and the summaries made from that);
- any other personal data the customer chooses to include in customer content.
3.2 Categories of data subjects.
- members of the customer's workspace (owners, producers, directors, makers, reviewers, viewers);
- actors, performers, voice talent and other people whose likeness or voice is used in references or output;
- people named, described or depicted in scripts and media;
- guests the customer or its members invite through share links;
- clients, collaborators and other contacts of the customer mentioned in customer content.
3.3 Special categories. We do not need special categories of personal data to provide the service, and we do not process images or voices to identify people. If the customer includes special categories (for example, health information in a script, or images used in a way that reveals sensitive information), the customer is responsible for having a legal basis for it.
4. Instructions
4.1 We process personal data only on documented instructions of the customer, unless EU or Dutch law requires otherwise. In that case we tell the customer about that legal requirement before processing, unless the law forbids it.
4.2 The customer's documented instructions are: the Terms of Service and this DPA, the settings the customer and its members choose in the service, and the actions they take in it (such as uploading, generating with a chosen model, inviting members, exporting and archiving). Further instructions must be in writing and in line with the service.
4.3 We tell the customer straight away if we believe an instruction infringes the GDPR or other data protection law.
4.4 The customer is responsible for the lawfulness of the processing it instructs, including having a legal basis, informing data subjects, and obtaining the consents of people whose likeness, voice or other personal data it uses.
4.5 We do not use customer content to train AI models and we do not sell it. We do not process it for our own purposes, except as set out in 4.6.
4.6 Trust and safety. Where needed, we look at customer content to detect and stop abuse of the service (such as free-credit farming, multiple accounts or prohibited content), to handle reports we receive, and to report illegal content to the authorities where the law requires it. For this limited processing we act as controller, on the basis of a legal obligation or our legitimate interest, as described in our Privacy Policy. We do it only as far as needed for those purposes.
5. Confidentiality
5.1 We ensure that everyone we authorise to process personal data in customer content is bound by a duty of confidentiality, by contract or by law.
5.2 Our staff access customer content only where needed to provide, secure or support the service, for example when the customer asks for help, or where the law requires it.
6. Security
6.1 We take appropriate technical and organisational measures to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access, as required by article 32 GDPR. Annex 1 lists them.
6.2 We review the measures regularly and may update them, provided the overall level of protection does not go down.
6.3 The customer is responsible for security within its own control: managing members and their roles, protecting logins and API keys, and the security of connections it sets up (such as its own Claude account connected over MCP).
7. Sub-processors
7.1 The customer gives us general authorisation to engage sub-processors. The sub-processors we use at the effective date of this DPA are listed in Annex 2.
7.2 We tell the customer at least 30 days in advance about any intended addition or replacement of a sub-processor, by email to the workspace owner and by updating Annex 2 at /dpa.
7.3 The customer may object to a new sub-processor on reasonable data protection grounds within those 30 days, by email to hello@filmsquare.ai. We then discuss the objection in good faith. If we cannot resolve it, for example by not using the new sub-processor for that customer, the customer may end the agreement for the affected service before the change takes effect, and we refund prepaid fees for the unused period.
7.4 We impose on each sub-processor, by contract, data protection obligations that offer at least the same level of protection as this DPA. We remain responsible to the customer for the performance of our sub-processors.
7.5 AI providers. AI providers in Annex 2 receive personal data only when a generation runs on one of their models, or when a member asks the assistant in the app (Anthropic, reached through OpenRouter), and only the input needed for that (prompt, references, script text, or the question and what the assistant read from the workspace to answer it). AI providers may keep input and output for a limited time under their own terms, for example to deliver results or to monitor abuse. A member can pick the model for a generation; where the member leaves the choice to Filmsquare, Filmsquare picks a model that can do the job.
7.6 The customer's own tools. A member's own Claude account connected over MCP, or other tools a member connects with an API key, are not our sub-processors. They act for the member, under the member's own agreement with that provider.
8. International transfers
8.1 We host customer content primarily in the European Union.
8.2 Some sub-processors are established in, or can access data from, countries outside the European Economic Area. We transfer personal data there only:
- to a country with an adequacy decision of the European Commission, including recipients certified under the EU-US Data Privacy Framework; or
- under the standard contractual clauses adopted by the European Commission (Implementing Decision (EU) 2021/914), together with supplementary measures where a transfer assessment shows they are needed.
8.3 Annex 2 shows for each sub-processor where it processes data and which transfer mechanism applies. On request we give the customer a copy of the relevant transfer terms.
9. Assistance
9.1 Data subject requests. Taking into account the nature of the processing, we help the customer to respond to requests from data subjects who exercise their rights (access, rectification, erasure, restriction, portability and objection). Most requests the customer can handle in the service itself, through editing, archiving and export. If a request needs more, such as erasing personal data from versioned production records or backups that are otherwise kept unchanged, the customer asks us and we carry it out.
9.2 If a data subject contacts us directly about customer content, we forward the request to the customer without undue delay and do not respond ourselves, unless the customer asks us to or the law requires it.
9.3 Other assistance. We help the customer, taking into account the information available to us, to meet its obligations on security, personal data breaches, data protection impact assessments and prior consultation with a supervisory authority (articles 32 to 36 GDPR). We may charge reasonable costs for assistance that goes beyond what the service and this DPA normally include, after telling the customer in advance.
10. Personal data breaches
10.1 We notify the customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting personal data in customer content.
10.2 The notification describes, as far as known at that time: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact person. Where we do not have all information at once, we provide it in phases.
10.3 We take reasonable steps to contain the breach and limit its consequences, and we keep the customer informed. The customer decides whether to notify the supervisory authority and data subjects.
10.4 We document every personal data breach, including the facts, effects and remedial action taken.
11. Deletion and return
11.1 When the agreement ends, the customer can export its customer content during the export window of 30 days described in the Terms of Service.
11.2 After the export window ends, we delete the personal data in customer content within 60 days, unless EU or Dutch law requires us to keep it.
11.3 Backups are not changed individually; personal data in them is deleted as the backups roll off in our normal backup cycle. Until then, backups stay protected under this DPA and are not used for any other purpose.
11.4 On request, we confirm the deletion in writing.
12. Audits and information
12.1 We make available to the customer all information necessary to demonstrate compliance with article 28 GDPR and this DPA. We do this first by providing documentation, such as a description of our security measures, answers to reasonable security questionnaires, and reports or certifications of our sub-processors where available.
12.2 If the documentation is not enough to demonstrate compliance, or a supervisory authority requires it, the customer may carry out an audit or have it carried out by an independent auditor bound by confidentiality. The customer gives at least 30 days' written notice, the audit takes place during business hours, does not disrupt the service unreasonably, and does not give access to data of other customers.
12.3 The customer bears the costs of an audit, including our reasonable time, unless the audit shows a material breach of this DPA by us, in which case we bear our own costs.
12.4 We remedy any shortcomings found in an audit within a reasonable time.
13. Liability
13.1 The liability of each party under or in connection with this DPA is governed by the liability provisions of the Terms of Service (section 17), including their limits and exceptions.
13.2 This does not limit the rights of data subjects under article 82 GDPR.
14. Term, precedence and law
14.1 This DPA applies for as long as we process personal data in customer content for the customer, and it ends automatically when that processing ends.
14.2 For personal data in customer content, this DPA prevails over the Terms of Service where they differ. A custom plan agreement prevails over this DPA only where it expressly says so.
14.3 We may change this DPA in line with section 19 of the Terms of Service. Changes may not lower the protection of personal data.
14.4 This DPA is governed by Dutch law. Section 21 of the Terms of Service applies to disputes.
Annex 1. Security measures
- Encryption in transit. All connections to the service and between our systems and sub-processors use TLS.
- Encryption at rest. Our database and storage providers encrypt stored data at rest.
- Access control. Every request is authenticated. Access to workspaces, productions and content is enforced in the database itself with row-level security, so a member only sees what their role and productions allow.
- Least privilege. Staff and systems get only the access they need. Administrative access to production systems is limited to a small number of authorised people.
- Upload integrity. Files are stored content-addressed; a member can register a file only by uploading its bytes, never by referring to a file they did not upload.
- Credentials. Passwords are handled by our authentication provider and stored hashed. API keys and MCP connections are tied to a person, can be revoked at any time, and are stored in a form that does not reveal the key.
- Logging and monitoring. We log access and security-relevant events, keep an activity record per workspace, and monitor the service for errors and abuse.
- Backups. The database is backed up regularly, and backups are protected like production data.
- EU database. The database that holds workspaces, scripts, comments and account data is hosted in the European Union (Ireland). Files are stored with Cloudflare R2 (Annex 2).
- Separation. Customer data is logically separated per workspace.
- Secure development. Code changes pass an automated test suite before release; dependencies are kept up to date.
- Suppliers. Sub-processors are selected for their security and bound by data protection terms (section 7).
- Incident response. We have a procedure to detect, investigate, contain and report personal data breaches (section 10).
- Confidentiality. Everyone with access to customer content is bound to confidentiality (section 5).
Annex 2. Sub-processors
Infrastructure and service operation:
- Supabase, Inc. Database, and authentication for sessions from before 6 November 2026. Data stored in the EU (Ireland). Company in the United States; transfers under the standard contractual clauses.
- Clerk, Inc. Authentication: sign-in accounts, password hashes, sign-in sessions, sign-in through Google, Apple or Microsoft, and sign-in code emails. United States. EU-US Data Privacy Framework and standard contractual clauses.
- Cloudflare, Inc. Application hosting (Workers), file storage (R2), live collaboration (Durable Objects), media processing such as thumbnails, previews and renders (Containers), content delivery, network security and Turnstile. Requests are handled on Cloudflare's global network. EU-US Data Privacy Framework and standard contractual clauses.
- Resend. Email (invitations, sign-in links, notifications, dailies and the studio report). EU region. Standard contractual clauses for any access from the United States.
- PostHog, Inc. Product analytics, EU cloud. Cookies only with the member's consent; without it visits are counted without cookies. Only usage data, not customer content. Listed for completeness.
- Stripe. Payments. Stripe acts as an independent controller for payment processing and receives only billing data, not customer content. Listed for completeness.
AI providers, used only when a generation runs on one of their models (a model a member picked, or one Filmsquare chose because the member left the choice to us), or, for Anthropic and OpenRouter, when a member asks the assistant in the app:
- BytePlus (ByteDance group). Video and image generation (Seedance, Seedream). Processing in Singapore. Standard contractual clauses with supplementary measures.
- Kling (Kuaishou group). Video and image generation, through its international service in Singapore. Standard contractual clauses with supplementary measures.
- Google (Gemini API). Image generation and retouching, on Google's paid service, under which prompts and responses are not used to improve Google's products. Data may be stored briefly in any country where Google has facilities. Standard contractual clauses.
- fal.ai (Features and Labels, Inc.). Upscaling and smooth-motion tools. United States. Standard contractual clauses.
- Topaz Labs. Upscaling. United States; not used for training; inputs and outputs deleted 7 days after processing. Standard contractual clauses.
- Runware. Still upscaling and background removal. Standard contractual clauses.
- ElevenLabs. Voices, speech, sound and voice cloning. United States. Standard contractual clauses.
- Higgsfield AI. Image and video generation, and a member's own Higgsfield connection where the member makes one. United States. Standard contractual clauses.
- A GPU hosting provider we rent for our own model workflows. Runs open models we operate ourselves for some tools. Standard contractual clauses where it is outside the EEA.
- Anthropic. Claude, for script breakdown when a member asks for an AI breakdown and we have that feature switched on, and for the assistant in the app where it is switched on. Not used to train its models. United States. Standard contractual clauses.
- OpenRouter, Inc. Passes the assistant's requests to Anthropic's own service and the answers back. We ask it to use only providers that do not train on prompts; OpenRouter and Anthropic may keep requests for a limited time under their own terms, for example to detect misuse or where the law requires it. United States. Standard contractual clauses.
We keep this list up to date at /dpa and announce changes as described in section 7.