Privacy Policy
This Privacy Policy explains how Dream Ops B.V. collects and uses personal data when you visit www.filmsquare.ai, create or use a Filmsquare account at app.filmsquare.ai, connect your own Claude app to Filmsquare, open a review link someone shared with you, buy credits or seats, use our help center, or contact us. It also applies where we offer the same service under another name, such as Dreamsquare at app.dreamsquare.studio. We have written it to be read, not skimmed past. If something is unclear, email us and we will explain.
This policy is part of how we provide Filmsquare under our Terms of Service. How we use cookies and similar technologies is set out in more detail in our Cookie Policy.
1. Who we are
Filmsquare is a hosted AI film production suite: one place where a crew takes a film from script to export, with people assigned to each step and signing off on it. Filmsquare is provided by:
- Dream Ops B.V., a private limited company (besloten vennootschap) registered in the Netherlands
- Address: Hamerstraat 3D, 1135 GA Edam, the Netherlands
- Chamber of Commerce (KVK) number: 42047001
- Email: hello@filmsquare.ai (please use the subject "Privacy")
In this policy, "Dream Ops", "we", "us" and "our" mean Dream Ops B.V. "You" means anyone whose personal data we process as described here: website visitors, account holders, workspace members, invited people, guests on review links, billing contacts and anyone who contacts us.
We have not appointed a Data Protection Officer. We are not required to under Article 37 of the General Data Protection Regulation (GDPR), because our core activities do not involve large-scale regular monitoring of people or large-scale processing of special categories of data. Privacy questions are handled directly by our team at the address above.
2. When we are controller and when we are processor
The GDPR distinguishes between a controller (who decides why and how personal data is processed) and a processor (who processes personal data on behalf of a controller).
We are controller for the personal data this policy describes: data about visitors to our website, about people who hold an account, about members of workspaces in their capacity as users of the service, about billing, support, product analytics and the security of the service.
We are processor for personal data contained in the content that customers put into their workspaces. Examples are scripts, images, reference photos, voices, likenesses of actors, character sheets, generated takes, the text of comments and notes, maker briefs and fee agreements, voice consent records, notes from guests on review links, and the crew analytics of a workspace. That content belongs to the workspace owner, who decides what goes into it and who can see it. We process it only on the workspace owner's instructions, under our Data Processing Agreement. If your personal data appears in someone's workspace content (for example, your face in a reference image or your voice in a recording), please contact the workspace owner first. If you cannot reach them, contact us and we will forward your request.
Trust and safety is our own processing. To keep the service safe and lawful, we act as controller for a limited part of what happens in workspaces. Where needed, we look at accounts, activity and workspace content to detect and stop abuse (such as farming free credits, running several accounts to get more of them, or prohibited content), to handle reports we receive, and to report illegal content to the authorities where the law requires it. We do this only as far as needed for those purposes. Our legal bases are set out in section 5.
3. What personal data we process
Website visitors
- Technical data your browser sends when it loads a page: IP address, user agent (browser and operating system), the page requested, referring page, date and time.
- Your cookie choice, stored in the fs_consent cookie.
- If you accept analytics: pageviews, the features and sections you use, errors the app runs into, device and browser type, and a pseudonymous identifier. See section 4 and the Cookie Policy.
Account data
- Email address.
- Name or display name.
- Password, if you choose one. It is handled by our authentication provider Clerk and stored only as a one-way hash. We never see or store your password in readable form.
- How you sign in (for example a password, a code sent to your email, or Google, Apple or Microsoft), and when you signed up and last signed in.
- Account settings and preferences, such as your last opened workspace and interface layout.
- Which version of our Terms of Service you accepted, and that you confirmed you have the rights to what you upload: the version, the time, and whether you did so at sign-up, in the app or through your connected Claude app. We do not record your IP address with it.
Sign-in with Google, Apple or Microsoft
If you sign in with Google, Apple or Microsoft, that provider confirms who you are to Clerk, and we receive your name, your email address and an identifier for your account with that provider. We use them only to sign you in and to link the sign-in to your Filmsquare account. We do not receive your password for that account, your contacts or anything else from it.
Workspace membership and invitations
- The workspaces and productions you belong to, your role in each (for example owner, producer, director or maker) and the permissions that come with it.
- When someone invites you, the email address they entered, who invited you, to which workspace and with which role, and whether the invitation was accepted.
Activity in the product
- Actions you take in Filmsquare, such as creating, editing, archiving, assigning and moving items.
- Comments and notes you write, mentions, and notifications sent to you. The text of a comment is workspace content (see section 2); the fact that you wrote it, and when, is part of your activity.
- Sign-offs and approvals you give, and review status changes you make.
- Generation history: which generations you started, with which model and settings, their status, and the credits and costs they used.
- An audit trail of security-relevant events, such as sign-ins, role changes and API key creation.
Crew analytics
A workspace owner can switch on crew analytics (Analytics, then Crew) for their workspace. It is off until the owner switches it on, and the owner can only switch it on after confirming that the crew has been told. Every member of the workspace can see whether it is on.
While it is on, we keep a log of each change a member makes in that workspace, in the app, through the API or through a connected Claude app: who, when, through which channel, which action and on which item. The log holds no prompts and no content. From it, Filmsquare shows per person and per quarter of an hour whether they worked hands-on or had an agent working for them, in which departments, how many things ran side by side, and how many agent sessions there were. It also shows numbers per person based on sign-offs, such as how much was delivered and how much came back for a redo.
The workspace owner and producers can see this for the whole workspace. Every other member sees only their own. The detailed log is deleted after 13 months. The crew analytics are workspace content: the workspace owner is controller for them, and we process them on the owner's instructions.
Voice consent records
Before a recording of someone's voice can be cloned in Filmsquare, the person doing it must confirm that the speaker knows about it, has agreed and is an adult. We record that confirmation with the workspace: the speaker's name, that the speaker is an adult, whether the person confirming is the speaker, the wording of the statement and its version, the recording to be cloned, the speaker's own consent (such as a signed form or a recorded yes) unless the person confirming is the speaker, who confirmed it and when. These records cannot be edited afterwards. Directors and people with a higher role in the workspace can see them. They are workspace content, kept for the workspace owner, who is controller for them.
Maker briefs, fee agreements and payment records
When a workspace works with makers (people who take on a piece of the production), Filmsquare keeps the briefs, assignments and deliveries, the fee agreed for an assignment, and a record that a payment was made, with the date and an optional payment reference. Filmsquare does not make or receive these payments; it only keeps the record. These records are workspace content.
Guests on review links
A workspace member can share part of a production, such as a cut, a step, a take, a sheet or an edit, through a review link. To open it, you sign in with your own account (or create one); you do not become a member of the workspace. When you open a link and leave notes, we process:
- your account, as described under account data, and that your account opened the link and joined it as a guest;
- the name of your account at the time you joined, shown with your notes;
- the notes and replies you write on that link, and when.
The name and your notes are visible to the workspace's crew and to other guests of the same link. Guests who joined a link before guests had accounts gave a name and, if they chose, an email address; those stay as they were. They are workspace content, kept for the workspace owner as controller.
API keys and connected apps
- API keys you create: a name, the date of creation and last use, and a short prefix so you can recognise the key. The key itself is stored only as a hash.
- Connections from your own Claude app (made by Anthropic) through our Model Context Protocol (MCP) server. A connection is authorised through OAuth and acts in your own name. We store the connection, the app that connected, the permissions granted, and the requests it makes, like any other API use. Your conversations with Claude take place in your own Anthropic account and are governed by your agreement with Anthropic, not by us.
- If you connect your own Higgsfield account to bring in your work from there: the connection and the access it grants, stored encrypted, so Filmsquare can fetch what you ask it to.
Billing and credits
- Billing details you give at checkout: name, company name, billing address, VAT number and email address for invoices. You give them to Link, the merchant of record for our plans and credit packs (section 7), which shares with us what we need to run your plan.
- Your payment method is entered directly with Link and Stripe. We do not receive or store full card or bank account numbers; we receive only limited details such as card brand, last four digits and expiry date.
- Subscriptions, seats, invoices, payments, refunds and payment failures.
- Your credit ledger: credits bought, granted, used and expired, and the access codes you redeemed.
Support and other contact
- Emails you send us and our replies, including any attachments and the information you choose to include.
- If you contact us for business purposes (for example about a Studio plan), your name, company, role and contact details.
Help center
Our help center at www.filmsquare.ai/help and our docs can answer questions and find articles for you. You do not need an account, and we do not link what you ask there to your account.
- Asking a question. When you ask a question, we send it to Cloudflare Workers AI, together with up to three earlier questions from the same conversation and the help articles they led to. Where our server gave an earlier answer a code, so it can check that the answer was not changed, that answer goes along too. At Cloudflare your question is matched against our help articles, and an open AI model (Gemma, made by Google and run by Cloudflare on its own servers) writes the answer from those articles. Google does not receive your question. We do not store your question or the answer on our servers.
- Searching. When a search finds few articles by their words, we send the search text to Cloudflare Workers AI to find articles with a similar meaning. We keep the list of articles found for 24 hours, under a one-way code made from the search text, so the same search is answered faster. We do not store the search text itself.
- Limits and checks. To stop abuse and to keep the cost of the AI within a daily budget, we count questions, searches and messages per IP address. The counters hold only a one-way code of your IP address, never the address itself, and are deleted after a day (questions and searches) or an hour (messages). Before your first question, and before each message, Cloudflare Turnstile checks that you are a person. After the first check your browser keeps a pass for 30 minutes, so you are not checked again for every question. To stop the help center from being used to send mail to someone else, we also count confirmation emails per email address, under a one-way code of the address, and delete that count a day after the last confirmation.
- Your conversation in your browser. Your conversation (at most three questions and answers; an answer can carry a code from our server so we can check it was not changed), a draft message and whether the panel is open are kept in your browser's session storage, not on our servers. They are deleted when you close the tab. See the Cookie Policy.
- Message us. If you send us a message from the help center, we email your email address, your message, the page you were on and its language to our support inbox. If you leave "Conversation" switched on, the questions and answers of your conversation and the articles they linked to go with it. We use this to reply to you by email. We send one email to that address to confirm that we received your message, and after that only our reply. We do not add your address to any list.
Please do not put personal details, passwords or payment details in a question or a message. Answers in the help center are written by AI. They can be wrong or incomplete. The help articles they link to are what counts, and you can always email us.
The assistant in the app
Where the assistant is switched on, members of a workspace can ask it about their productions and let it prepare changes. The owner of a workspace can switch it off for everyone in it, under Settings, Workspace.
- Asking a question. When you ask a question, we send it to OpenRouter, which passes it on only to Anthropic's own service, where a Claude model writes the answer. With the question go the last questions and answers of your conversation (at most twelve messages in all), the screen you are on (such as the production or episode) and anything you added to the question. To answer, the assistant reads from your workspace what you are allowed to see, such as productions, episodes, scenes, shots, the steps that wait on you, sheets and notes. What it reads goes with the request too, and can include text that other members or guests wrote, such as notes and comments. Pro asks the same question of a larger Claude model and uses the workspace's credits.
- Plans. The assistant can propose changes, such as making shots or applying suggestions on a sheet. Nothing changes until you confirm the plan. We keep the plan (what it would change) and what happened when it ran with the workspace, so that you can see it and undo it.
- What we keep. For each question we keep who asked, in which workspace and production, when, which model answered, how many tokens it used, what it cost and how it ended. We do not keep the text of your question or of the answer on our servers. Your conversation is kept in your browser's session storage and is deleted when you close the tab.
- Limits. We count questions per member and per workspace each month to keep the cost within the plan, and stop questions that come too fast.
Answers from the assistant are written by AI. They can be wrong or incomplete, so check them before you rely on them. A plan shows what it will change before it runs.
Technical and security data
- Request logs at Cloudflare and at our API: IP address, user agent, request path, time, response status and error details.
- Security signals from Cloudflare, including Cloudflare Turnstile when it is enabled on sign-up, on the launch list and in the help center, used to tell people apart from automated abuse.
- Signals we use to detect abuse of the service, such as the access code used at sign-up, how many accounts were made in a short time, and limits that were reached.
Emails we send
- Records of emails sent to you, such as sign-up confirmations, sign-in codes, invitations and notifications, including whether delivery succeeded.
- Dailies and the studio report, only if you turned them on for yourself. Dailies are a digest of what happened in a workspace. The studio report goes only to the owner and producers who turn it on, and carries the crew analytics numbers of the whole workspace. Every one of these mails has a link to change or stop it.
Launch list
- The email address you leave under "Request access" on our website, and when you left it, so we can tell you when Filmsquare opens and send you occasional news about it.
We do not ask for special categories of personal data (such as health, religion or political opinions) for our own purposes. If such data appears in workspace content, it is the workspace owner's responsibility under the Data Processing Agreement.
4. Product analytics
We use PostHog to understand how Filmsquare and our website are used, so we can fix what is confusing and improve what matters. In your browser it runs in one of two forms. Our servers also send it counts per workspace, the third form below.
Without cookies (by default). Nothing is stored on your device. PostHog's EU cloud computes a hash of your IP address, user agent and our hostname on its servers, with a salt that changes daily and is then deleted, so we cannot recognise you across days. We rely on our legitimate interest for this (see section 5).
With cookies (after you accept). If you accept analytics in our cookie banner, or by default when you visit from outside the EU/EEA, the UK and Switzerland, where we do not ask first, PostHog records pageviews, the features you use, errors the app runs into (the error message and where in our code it happened), and your device and browser type, together with a pseudonymous identifier. After you sign in, that identifier is linked to your account ID, so that we can see how a feature is used across sessions. We have configured PostHog so that:
- it runs in PostHog's EU cloud (Frankfurt, Germany);
- session recording is switched off;
- IP addresses are not stored, or are anonymised;
- the data is not used for advertising and is not shared with advertisers.
In the help center, PostHog also records which articles you open from search, whether an answer helped you, and whether you sent us a message. For a search that found nothing, a question the help center could not answer, and an answer you marked as unhelpful, it records the first 80 characters of what you typed. Before it is sent we replace email addresses, links and numbers of four or more digits. This happens only with your consent, like all PostHog events with cookies.
You can withdraw your consent at any time through "Cookie settings" in the footer of the website and in the app. From that moment PostHog uses no cookies and goes back to counting without them, and we delete PostHog cookies from your browser where possible. Withdrawing does not affect processing that took place before.
To object to analytics in your browser, turn on Global Privacy Control or Do Not Track: then no analytics run in your browser at all, in either form. These settings do not reach the counts per workspace below. You object to those by email.
Counts per workspace, from our servers. Our servers send PostHog a short event when one of these things happens in a workspace:
- a workspace is created: its plan, and how its account came in (for example with an access code, an invitation or open sign-up);
- a member joins: their role, and whether they were invited or added;
- a payment succeeds: the plan or credit pack, monthly or yearly, the amount in euros, the credits it gives and whether it is the workspace's first payment;
- a payment fails or a plan is cancelled: the plan or pack;
- a generation is finished and used credits, or made video: how many credits, the kind of take, the model, draft or final, whether it succeeded, how it was started and, for video, how many seconds of video it made;
- the Claude plugin or a connected Claude app is used in a workspace: the app and its version, and which plugin action it took (a request, a note answered or resolved, a take or picks used);
- a take is picked for a shot: the kind of take, the IDs of the shot and the production, whether it is the shot's first pick, and whether it was picked in the app, by the assistant, by a connected Claude app or through the API;
- a department step is signed off: the department, the ID of the production, and where it was signed off;
- a guided production in the Studio is started (its template and mode), or its final is signed off (whether it is complete).
Each event also says which of our sites sent it (live or test). The events are labelled with the workspace's ID, not with a person, and PostHog makes no profile of a person from them. They hold no name, email address, account ID or IP address of yours, and no workspace content: no prompts, titles, scripts or media. The IDs in them are random codes.
When you leave your email address under "Request access" on our website, our server sends PostHog one event that a new request came in. It carries a random ID and not your email address.
These events come from our servers, not from your browser. So cookies, your choice in the cookie banner, Global Privacy Control and Do Not Track do not change them. They are stored in PostHog's EU cloud (Frankfurt, Germany), like the rest of our analytics.
We use them to see which workspaces get value from Filmsquare: how much they make, who keeps working and who pays, so we can plan and improve the service. We rely on our legitimate interest for this (Article 6(1)(f) GDPR, see section 5). A workspace ID is not anonymous: if you are the only member of a workspace, its ID points to you. So we treat these counts as pseudonymous personal data. You can object at any time by emailing hello@filmsquare.ai with the subject "Privacy".
Product analytics are separate from crew analytics (section 3). Crew analytics are a feature a workspace owner switches on for their own workspace; they use no cookies and are not sent to PostHog.
5. Why we process your data and on which legal basis
Under Article 6 GDPR we need a legal basis for each use of personal data. We rely on the following.
Performance of a contract (Article 6(1)(b))
- Creating and running your account, signing you in and keeping you signed in.
- Providing Filmsquare: workspaces, membership and roles, invitations, generations, review and sign-off, review links, notifications and exports.
- Processing API and MCP requests that you or your connected Claude app make.
- Answering your questions with the assistant in the app and running the plans you confirm (section 3).
- Selling and administering credits, seats and subscriptions (through Link, which takes the payment and issues the invoices), and handling refunds.
- Sending dailies and the studio report you turned on.
- Answering your support requests about the service.
Where you are invited to a workspace by someone else, we process your data to perform our contract with the workspace owner and, once you accept, our contract with you.
Legal obligation (Article 6(1)(c))
- Keeping invoices, payment records and other accounting records for seven years, as Dutch tax law requires (Article 52 of the General State Taxes Act, Algemene wet inzake rijksbelastingen).
- Charging and reporting VAT correctly, including checking VAT numbers.
- Acting on orders and reports about illegal content, and reporting illegal content to the authorities where the law requires it.
- Responding to lawful requests from authorities.
Legitimate interests (Article 6(1)(f))
- Security, fraud and abuse prevention: protecting the service, our customers and ourselves through logs, rate limits, sign-up checks, Cloudflare security tools and Turnstile.
- Trust and safety: detecting and stopping abuse such as free-credit farming, multiple accounts and prohibited content, including by looking at workspace content where needed, and handling reports from others (see section 2).
- Keeping a record of what was agreed: which version of the Terms you accepted, and your confirmation that you have the rights to what you upload.
- Service emails: telling you about important changes to the service, your account, security incidents or these policies.
- Improving the service with aggregated data: using aggregated, non-identifying statistics (for example, how many generations ran per model, or how often a review step was signed off) to plan capacity and improve features. This is separate from PostHog analytics.
- Analytics without cookies: counting visits and feature use with PostHog without storing anything on your device, as described in section 4. You can object with Global Privacy Control or Do Not Track.
- Counts per workspace: events our servers send to PostHog, labelled with a workspace's ID, about what happens in it (created, members, payments, credits spent and video made, takes picked, steps signed off, plugin use), so we know which workspaces get value from the service, as described in section 4. You can object by email.
- Business-to-business contact: replying to companies and people that contact us.
- Help center: answering questions about Filmsquare and finding the right help articles with Cloudflare Workers AI, and protecting the help center and its AI budget against abuse with rate limits, counters and Turnstile (section 3). For account holders who ask about their own use of the service, this is also part of performing our contract.
- Establishing, exercising or defending legal claims.
We have weighed these interests against your rights and expectations. You can object to processing based on legitimate interests at any time (see section 10).
Consent (Article 6(1)(a))
- Product analytics with PostHog using analytics cookies. You give this consent in the cookie banner and can withdraw it at any time through "Cookie settings" in the footer of the website and the app.
- News by email. We send news only to people who asked for it: by leaving their address under "Request access" on our website (the launch list), or by choosing to get product news at sign-up or in settings, where we offer that choice. Every news email has an unsubscribe link (the first launch-list email arrives right away). You can withdraw your consent at any time with that link, with the product news switch in settings or by emailing us. For product news we record your address, each choice (on or off), when and where you made it and the words you saw, as proof of your consent. We do not send news to customers who did not ask for it.
6. Where your data comes from
Most data comes from you: what you enter when you sign up, use the service, pay or contact us. Some comes from others:
- Workspace owners and members, when they invite you, assign you a role, mention you in a comment, record a voice consent that names you, or switch on crew analytics.
- Google, Apple or Microsoft, through Clerk, if you sign in with them (section 3).
- Stripe and Link, which tell us the outcome of payments, refunds and disputes, your billing details and limited details about your payment method.
- Your connected Claude app, which sends requests to Filmsquare in your name after you authorise it.
- Cloudflare and our own systems, which produce technical and security logs when you use the service.
- People who report content to us, for trust and safety.
7. Who receives your data
We share personal data only with parties that help us run Filmsquare, under contracts that limit what they may do with it, or where the law requires it. Section 8 explains how data is protected when it leaves the European Economic Area (EEA).
Infrastructure
- Supabase, Inc.: our database, which holds accounts, workspaces and their content records. Data is hosted in the EU (Ireland, eu-west-1). Supabase Auth also still signs in accounts made before 6 November 2026, until their sessions run out. Company in the United States; transfers under standard contractual clauses.
- Clerk, Inc.: sign-in (your sign-in account, password hash, sign-in sessions, sign-in through Google, Apple or Microsoft) and the sign-in codes it emails you. United States; EU-US Data Privacy Framework and standard contractual clauses.
- Google LLC (Google Fonts): only on the sign-in page of Dreamsquare (app.dreamsquare.studio), where your browser fetches the page's fonts from Google. Google receives your IP address and browser details with that request; we send it nothing else. Filmsquare's own pages host their fonts themselves.
- Cloudflare, Inc.: hosting of the website and app (Workers), file storage (R2), live collaboration in the app (Durable Objects), media processing such as thumbnails, previews and renders (Containers), network delivery and protection, Turnstile, and the AI in our help center (Workers AI: it receives the questions and search text described in section 3, does not keep them after the answer, and does not use them to train AI models). Requests are handled on Cloudflare's global network. EU-US Data Privacy Framework and standard contractual clauses.
Payment
- Sold through Link, LLC ("Link", a Stripe affiliate): the merchant of record for our plans and credit packs. Link takes the payment, charges the tax, issues receipts and invoices and handles payment and subscription support. Link acts as an independent controller for that, under the Stripe Privacy Policy.
- Stripe Payments Europe, Limited (Ireland) and other Stripe companies: payment processing and subscriptions for Link. Stripe acts as an independent controller for its own payment processing, fraud prevention and legal obligations, under the Stripe Privacy Policy.
- Resend: delivery of our emails (invitations, notifications, dailies, the studio report, launch-list emails and product news, messages you send us from the help center and the confirmation that we received them), and keeping the launch list and the product news list, from its EU region. Standard contractual clauses for any access from the United States.
Analytics
- PostHog, Inc.: product analytics in PostHog's EU cloud (Frankfurt), as described in section 4. It receives usage data, not workspace content.
AI model providers
When someone generates content in Filmsquare, we send the prompt, settings and any reference material (such as images, audio or text from the workspace) to the AI model provider that runs the model, and receive the result. A provider receives this only when a generation runs on one of its models: either because a member picked that model, or because the member left the choice to Filmsquare and Filmsquare chose it (for example the lowest-priced model that can do the job). These requests contain workspace content, which we process as processor for the workspace owner under the Data Processing Agreement. They do not normally contain your account details. The AI in our help center is not one of these providers: it runs on Cloudflare Workers AI (see Infrastructure above).
- BytePlus (part of the ByteDance group): video and image generation (Seedance, Seedream). Processing in Singapore. It keeps task records for 7 days and result links for 24 hours. It processes the content under its API terms. Standard contractual clauses with supplementary measures.
- Kling (part of the Kuaishou group): video and image generation. We use its international service in Singapore. It keeps results for 30 days. It processes the content under its API terms. Standard contractual clauses with supplementary measures.
- Google (Gemini API): image generation and retouching (Nano Banana models). We use only Google's paid service, under which Google does not use prompts or responses to improve its products. Google logs prompts and responses for a limited time only to detect misuse, and may store data briefly in any country where it has facilities. We ask it not to store our requests. Standard contractual clauses.
- fal.ai (Features and Labels, Inc., United States): upscaling and smooth-motion tools. It keeps a history of requests for up to 90 days. It processes the content under its API terms. Standard contractual clauses.
- Topaz Labs (United States): upscaling. It processes and stores data in the United States, does not use it for training, and deletes inputs and outputs 7 days after processing. Standard contractual clauses.
- Runware: still upscaling and background removal. It processes the content under its API terms. Standard contractual clauses.
- ElevenLabs (United States): voices, speech, sound and voice cloning. It may keep generated audio in its history. It processes the content under its API terms. Standard contractual clauses.
- Higgsfield AI (United States): image and video generation, and the connection to your own Higgsfield account if you make one. It keeps result links for at least 7 days. It processes the content under its API terms. Standard contractual clauses.
- A GPU hosting provider we rent for our own model workflows: runs open models that we operate ourselves for some tools. Results stay on that server until we fetch them. Standard contractual clauses where it is outside the EEA.
- Anthropic (United States): Claude, for script breakdown when someone asks for an AI breakdown of a script and we have that feature switched on, and for the assistant in the app (section 3), which reaches it through OpenRouter. It receives the script text, or the question and what the assistant read from the workspace. Under its API terms Anthropic does not use this content to train its models, and may keep it for a limited time, for example to detect misuse. Standard contractual clauses.
- OpenRouter, Inc. (United States): passes the assistant's requests to Anthropic and its answers back. We ask it to send them only to Anthropic's own service, and only to providers that do not use prompts for training. Under their own terms, OpenRouter and Anthropic may still keep requests for a limited time, for example to detect misuse or where the law requires it. OpenRouter also keeps records of each request, such as the model, token counts and cost, for billing. It processes the content under its API terms. Standard contractual clauses.
Training. We do not use your content to train AI models. Where a provider above has told us that it does not use API content for training or to improve its products, we say so. For the others, its API terms decide what it may do with the content, and we make no promise for it beyond those terms. You can ask us for the terms of a specific provider.
Others
- Other members of your workspace see your name, role, activity, comments and sign-offs within that workspace, according to the roles the workspace owner has set. If crew analytics are on, the owner and producers see yours (section 3).
- Guests on a review link see the notes and replies on that link, with the names of the people who wrote them.
- Professional advisers, such as accountants, auditors and lawyers, under a duty of confidentiality.
- Authorities, courts and regulators, where the law requires us to disclose data or report illegal content, or where it is necessary to protect our rights or the safety of others.
- A buyer or successor, if Dream Ops or Filmsquare is merged or sold, in which case this policy continues to apply to your data.
We do not sell personal data. We do not use it for advertising and do not share it with advertisers or social networks.
8. International transfers
We host our main database in the EU and choose EU regions where providers offer them. Some recipients in section 7, or their support teams, are outside the EEA. Where personal data is transferred outside the EEA, we make sure it stays protected:
- through an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for a company certified under it (we rely on this for Clerk and Cloudflare); or
- otherwise through the European Commission's standard contractual clauses, with supplementary measures where a transfer assessment shows they are needed.
For BytePlus and Kling, which process data in Singapore and belong to groups based in China, we use standard contractual clauses with supplementary measures. Their models receive prompts and reference material only when a generation runs on them, as explained in section 7.
You can ask us for more information about the safeguards for a specific provider by emailing hello@filmsquare.ai with the subject "Privacy".
9. How long we keep your data
We keep personal data only as long as we need it for the purpose it was collected for, or as long as the law requires.
- Account data: for as long as your account exists. You can close your account yourself in the app, under Settings, Account. Your sign-in stops at once, and we email you a link that keeps your account if you change your mind. The link works for seven days. After that we delete or anonymise your account data within 60 days of closing it, except where a longer period below applies. If you are the only member of a workspace, that workspace closes with your account and its paid plan ends.
- Workspace activity: within Filmsquare, items are archived rather than deleted while the workspace exists, so that a production keeps a reliable record of who did and approved what. Some production records cannot be changed once written, such as sign-offs, fee and payment records and voice consent records. When a workspace is closed, its content and activity are deleted as described in the Terms of Service. If you close your account while the workspace continues, these records stay with the workspace, which the workspace owner controls. Once your account is erased, your name and email address are removed from it, so these records no longer show who you were. Text in them that mentions you by name is not changed. On request, we replace it.
- After your account is erased: your name, email address and sign-in links are removed from the hub, including their copies in the audit log and the terms acceptance records, which keep their rows without them. What stays: records we keep for the ledger and for legal duties, such as sign-offs, fee, payment and billing records (invoices for seven years); what you made or wrote in a workspace that continues, without your name, as that workspace's record; text other people wrote that names you, which we replace on request; backups, until they roll off within 30 days; and the records of our payment provider and other independent controllers, which they keep under their own policies (section 7).
- Crew analytics: the detailed log is deleted after 13 months. Daily summaries made from it stay with the workspace.
- Guests on review links: your notes, and the name shown with them, stay with the workspace that shared the link, as part of its production record. If your account is erased, the name on your guest entry is removed.
- Terms acceptance records: for as long as your account exists, and after that for as long as we may need them to show what was agreed.
- Invoices, payments and billing records (including the credit ledger insofar as it supports invoices): seven years, as Dutch tax law requires.
- Technical and security logs: up to 30 days, unless we need them longer to investigate a specific security incident or abuse.
- Trust and safety records: as long as needed to handle the case, and longer only where we need them to prevent the same abuse again or to meet a legal obligation.
- Product analytics (PostHog): up to 12 months.
- Support emails: up to two years after the last message in the conversation.
- Help center questions and searches: not stored on our servers. Lists of articles found for a search: 24 hours. Counters for limits: a day, or an hour for messages, and they hold only a one-way code of your IP address. Your conversation in your browser: until you close the tab.
- The assistant in the app: the record of each question (who, when, model, tokens, cost, outcome, never the text) and the plans with what happened when they ran: as long as the workspace exists, like other workspace activity. The cost of a question is also part of the credit ledger where it was paid from credits. Your conversation in your browser: until you close the tab.
- Messages from the help center: like support emails, up to two years after the last message in the conversation.
- Launch list: until you unsubscribe, or at the latest two years after you joined unless you have since opened an account.
- Backups: our backups roll off within 30 days, so deleted data disappears from them within that period.
- Your cookie choice: 12 months, after which we ask you again.
10. Your rights
Under the GDPR you have the following rights regarding your personal data:
- Access: ask whether we process your data and receive a copy of it.
- Rectification: have inaccurate or incomplete data corrected. You can change most account details yourself in the app.
- Erasure: have your data deleted, unless we must keep it (such as invoices under tax law). You can do this yourself by closing your account in the app, or ask us by email.
- Restriction: ask us to limit processing of your data while a question about it is being resolved.
- Data portability: receive data you provided to us in a structured, commonly used and machine-readable format, or have it sent to another provider where technically feasible. You can download your own data in the app, under Settings, Account. A workspace owner can export the workspace's productions under Settings, Workspace. For anything else, ask us by email.
- Objection: object to processing based on our legitimate interests.
- Objection to direct marketing: you can always object to the use of your data for direct marketing, without giving a reason. We then stop at once.
- Withdraw consent: withdraw your consent for analytics cookies at any time through "Cookie settings" in the footer of the website and the app, and for news by email with the unsubscribe link in every email. To stop analytics in your browser altogether, turn on Global Privacy Control or Do Not Track. To object to the counts per workspace from our servers (section 4), email us.
For any of these rights you can also email hello@filmsquare.ai with the subject "Privacy". We respond within one month. If a request is complex or we receive many, we may extend this by up to two further months, and we will tell you why within the first month. Exercising your rights is free, unless a request is manifestly unfounded or excessive.
To protect your data, we need to make sure a request really comes from you. We normally do this by asking you to send the request from the email address on your account, or to confirm it from within the app. We will not ask for a copy of an identity document unless there is no other reasonable way to verify you, and if we do, we will tell you which details you may cover up.
If your request concerns personal data in workspace content (section 2), we will forward it to the workspace owner, who decides on it, and we will help them respond.
Complaints
If you are unhappy with how we handle your data, please tell us first, so we can try to put it right. You also have the right to lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or with the supervisory authority in the EU country where you live or work, or where the alleged infringement took place.
11. How we protect your data
We take appropriate technical and organisational measures to protect personal data against loss, misuse and unauthorised access. These include:
- encryption in transit with TLS for all traffic to the website, the app and our API;
- encryption at rest by our hosting and storage providers;
- row-level security in our database, so that every request only reaches the data of workspaces the person is a member of;
- role-based access within workspaces, set by the workspace owner;
- least-privilege access for our own team, limited to what is needed for their work;
- passwords handled by Clerk and stored only as hashes, and API keys stored only as hashes;
- audit logging of security-relevant actions;
- protection against automated abuse with Cloudflare, including Turnstile on sign-up and in the help center when enabled.
No system is perfectly secure. If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the Autoriteit Persoonsgegevens within 72 hours and, where the risk is high, inform you without undue delay.
12. Automated decision-making
Some of our checks run automatically and can block you without a person looking first. Sign-up checks can refuse or hold back a new account, for example when an access code is missing or not valid, or when a Turnstile challenge fails. Abuse limits can stop requests or generations when they are reached. In the help center, a failed Turnstile check or a reached limit can stop a question, a search or a message; you can always email us instead. Automated security tools may also block a request or ask for an extra check.
If you think you have been blocked in error, email hello@filmsquare.ai and ask for a human review. A person will look at it, and you can explain your side. Apart from these checks, we do not make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you.
13. Children
Filmsquare is a professional tool for adults. You must be 18 or older to create an account or use Filmsquare. We do not knowingly collect personal data from anyone under 18. If you believe someone under 18 has given us personal data, please contact us and we will delete it.
14. Links to other services
Our website and app link to services we do not control, such as Stripe checkout and billing pages, link.com, Google, Apple and Microsoft sign-in pages, Anthropic's Claude apps, and our community channels. Their own privacy policies apply when you use them.
15. Changes to this policy
We may update this Privacy Policy when our service, our providers or the law changes. The version date at the top always shows the current version. If we make material changes, we will tell you in advance in the app or by email. Where a change requires your consent, we will ask for it.
16. Contact
For any question about this policy or your personal data:
- Dream Ops B.V.
- Address: Hamerstraat 3D, 1135 GA Edam, the Netherlands
- KVK number: 42047001
- Email: hello@filmsquare.ai, subject "Privacy"
See also our Cookie Policy, Terms of Service and Data Processing Agreement.