FrameFight
ArenaExploreLeaderboardPredict
Search comparisonsLog inSign up
Draft — pending legal review. This text has not been checked by a lawyer yet and may change before launch.
Legal

Privacy policy

Last updated 21 October 2026

FrameFight is a blind comparison site for AI video: the same prompt is rendered on several models, and people vote for the better clip without seeing which model made it. This page explains what personal data that involves, why, who helps us run it, and what you can ask of us under the EU General Data Protection Regulation (GDPR).

  1. 01 Who we are
  2. 02 The short version
  3. 03 What we collect and why
  4. 04 Cookies
  5. 05 Analytics
  6. 06 Service providers
  7. 07 Transfers outside the EU
  8. 08 What is public
  9. 09 Automated checks
  10. 10 How long we keep data
  11. 11 Your rights
  12. 12 Minimum age
  13. 13 Security
  14. 14 Changes
01

Who we are

The controller responsible for your data is [Operator name and address], based in Berlin, Germany (“FrameFight”, “we”).

For anything about your data, email [email protected]. We answer within one month, usually much sooner.

02

The short version

  • We collect what the site needs to work: your account, the duels you judge, the comparisons you create, and basic usage data.
  • Your individual votes are never public — not to other users, labs or sponsors. Only totals per model are published. Why
  • We don't sell personal data and don't run ads.
  • Prompts and start images are sent to AI model providers only to render your comparison.
  • You can see, correct, export or delete your data — email us.
03

What we collect and why

Account
When you sign in with Google, X or Discord we receive an account id from that provider and, where available, your email address, display name and profile picture. We create a handle and a profile from it.
Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR)
Profile and settings
Handle, display name, bio, avatar colour, the scene types you picked when you joined (interests), privacy and email preferences.
Legal basis: Art. 6(1)(b) GDPR
Votes, tasks and XP
Which duels you were shown, your vote, how long you watched, flags, scene descriptions, predictions, the XP they earned and how our checks rated them. Used to run the arena, compute rankings and your level, and to detect vote manipulation.
Legal basis: Art. 6(1)(b) GDPR; fraud and manipulation detection: our legitimate interest in fair rankings (Art. 6(1)(f) GDPR)
Guest visits
If you vote without an account, a random guest id (cookie) links your votes and guest XP. When you sign up, that guest XP moves to your account.
Legal basis: Art. 6(1)(f) GDPR (offering voting without sign-up); § 25(2) TDDDG for the cookie
Comparisons you create
Prompts, the expanded scene description, start images you upload or edit, the rendered clips, and whether you published them. Published comparisons are public and show your handle.
Legal basis: Art. 6(1)(b) GDPR
Moderation
Results of automated checks on prompts and images, moderator decisions, strikes and reports.
Legal basis: legal obligations (Art. 6(1)(c) GDPR) and our legitimate interest in a safe service (Art. 6(1)(f) GDPR)
Emails
Your email address and which optional emails you want (fight updates, weekly digest, new models, streak reminders). Render, payment and rejection emails always go out because they are part of the service.
Legal basis: Art. 6(1)(b) GDPR; optional emails: your choice in settings, switch off any time (Art. 6(1)(a) GDPR)
Payments (when enabled)
Top-ups, balance, the renders they paid for, and invoices. Paid features may be switched off; while they are, we process no payment data.
Legal basis: Art. 6(1)(b) GDPR; retention of invoices: Art. 6(1)(c) GDPR with § 147 AO and § 257 HGB
Technical data
IP address, browser, request times and error logs, needed to deliver pages, rate-limit abuse and fix problems.
Legal basis: Art. 6(1)(f) GDPR (secure and stable operation)
04

Cookies

We use a few cookies that the site needs to work. They are strictly necessary (§ 25(2) no. 2 TDDDG), so they don't need consent:

  • ff_at — your session (15 minutes, renewed automatically).
  • ff_rt — keeps you signed in (30 days).
  • ff_s — tells the site you have a session, so it can skip a request when you don't (30 days).
  • ff_anon — random guest id for voting without an account (1 year).
  • ff_ds — protects the Discord sign-in against forged requests (10 minutes).
  • Cloudflare Turnstile — may store data in your browser to tell people from bots on sign-in.

Analytics cookies are described in the next section.

05

Analytics

We use Google Analytics 4 to understand which pages people use. It is loaded through our own domain (a first-party proxy), with advertising features, ad personalisation and Google signals switched off. Until you accept, and if you reject, Google Analytics runs without cookies: nothing is stored on your device, and every page load is counted under a new random id, so separate visits are never linked. If you accept, Google Analytics sets the cookies _ga and _ga_* (up to 2 years).

We also use PostHog (EU cloud, through our own domain) to see how the site is used: page views, clicks, actions such as voting or starting a fight (never their contents), load times and errors. Until you choose, and if you reject, PostHog runs without cookies: nothing is stored on your device, and visits are counted with a hash of your IP address and browser that PostHog's server salts daily and then discards. If you accept, PostHog stores an id in the cookie ph_*_posthog and in local storage (1 year), links the visits of a signed-in account to its account id and public handle (no email or name), and may record session replays with every input masked.

The banner stores your choice in the cookie ff_consent (1 year); Cookie settings in the footer opens it again. You can also block these cookies in your browser; the site works the same without them. Google and PostHog act as our processors; data may be transferred to the USA (see transfers below).

Legal basis: for the cookieless measurement without stored ids, our legitimate interest in knowing how the site is used and where visitors come from (Art. 6(1)(f) GDPR); for cookies and session replays, your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG), which you can withdraw at any time with effect for the future.

06

Service providers

We use these providers to run FrameFight. Where they process personal data on our behalf, we have data processing agreements with them (Art. 28 GDPR).

Hetzner Online GmbH
Germany
Servers and databases that run FrameFight, including our own GPU machines for free renders and the AI checks.
Cloudflare, Inc.
USA / global edge
CDN, DNS, DDoS protection, Cloudflare Tunnel between our servers, Turnstile bot protection on sign-in, and R2 object storage for videos and images. Some media is also stored on our own SeaweedFS storage at Hetzner.
Google Ireland Ltd. / Google LLC
EU / USA
Firebase Authentication (sign-in with Google, X or Discord) and Google Analytics 4.
PostHog Inc.
EU (Frankfurt) / USA
Product analytics: page views, clicks and actions on the site, errors, and — only with your consent — session replays with every input masked. Data is stored in the EU.
Brevo (Sendinblue SAS)
France (EU)
Sending emails: render ready, results, weekly digest and other emails you can switch off in settings.
fal.ai (Features & Labels, Inc.)
USA
Premium renders on commercial video models. Receives the prompt and, if you added one, the start image — no account details.
Runway AI, Inc.
USA
Premium renders on Runway models. Receives the prompt and start image — no account details.
Anthropic, PBC
USA
Expands short prompts into detailed scene descriptions. Receives the prompt text only.
OpenAI, L.L.C.
USA
Automated moderation of prompt text (omni-moderation), when enabled. Receives the prompt text only.
Paddle.com Market Ltd.
United Kingdom
Payments, as merchant of record — only once paid features are switched on. Paddle collects payment details itself; we never see card numbers.

Free renders run on open models on our own GPUs; the prompt doesn't leave our servers for them. Uploaded start images are checked for faces and nudity on our own servers before anything else happens with them.

Google, X and Discord are independent controllers for the sign-in they provide; their own privacy policies apply.

07

Transfers outside the EU

Some providers above are based in the USA or the United Kingdom. Transfers to the UK rely on the European Commission's adequacy decision. Transfers to US providers rely on the EU–US Data Privacy Framework where the provider is certified, and otherwise on the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). You can ask us for a copy of the safeguards.

08

What is public

  • Comparisons you publish, with your handle.
  • Your public profile: handle, name, bio, level, badges and activity — you can hide parts of it or the whole profile in settings.
  • Leaderboards built from everyone's votes. Votes are counted anonymously; nobody can see which clip you picked.
  • Anonymised research datasets about where video models fail (duels, flags, descriptions) — without names, emails or handles. You can opt out in settings.
09

Automated checks

Prompts and uploaded images are checked automatically before rendering (for example for sexual content, real people, minors and gore). Votes and tasks are checked by an automated reviewer, which can reduce or withhold XP for careless or made-up answers. A person reviews flagged comparisons before they go public.

None of this has legal effects on you in the sense of Art. 22 GDPR, but if you think a check got it wrong, email us and a person will look at it.

10

How long we keep data

  • Account, profile and your content: as long as your account exists. After you ask us to delete it, we delete it within 30 days.
  • Votes: when an account is deleted, its votes stay only as anonymous counts in the rankings — they can no longer be linked to you.
  • Guest data: linked to the guest cookie for up to one year, or moved to your account when you sign up.
  • Moderation records and strikes: up to two years after the last strike, to stop banned users from coming back.
  • Server logs: up to 30 days, unless we need them to investigate abuse.
  • Invoices and payment records: 10 years, as German tax law requires.
11

Your rights

Under the GDPR you have the right to:

  • access the data we hold about you and get a copy (Art. 15) in a portable format (Art. 20);
  • have wrong data corrected (Art. 16) and data deleted (Art. 17);
  • restrict processing (Art. 18);
  • object to processing based on our legitimate interests (Art. 21);
  • withdraw any consent you gave, with effect for the future (Art. 7(3)).

Email [email protected] from the address on your account (or tell us your handle) and we'll handle it within one month. Many settings — public profile, emails, datasets — you can change yourself in settings.

You can also complain to a data protection authority. Ours is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, Germany — or the authority where you live.

12

Minimum age

FrameFight is for people aged 16 and over. We don't knowingly collect data from younger children; if you think a child has an account, email us and we'll delete it.

13

Security

Connections are encrypted (HTTPS). Session cookies can't be read by scripts. Each database query runs with only the rights of the person making it (row-level security), and production servers are reachable only through encrypted tunnels.

14

Changes

When we change this policy we update the date at the top. If a change matters for you, we'll tell you by email or on the site before it applies. See also our terms of use.

FrameFight

The open arena for AI video. Same prompt, every model, judged by people.

Product
  • Arena
  • Explore
  • Leaderboard
  • Predict
Models
  • PixVerse V5 vs Veo 3.1
  • Kling vs Runway
  • Wan 2.2 (free)
  • All models
  • All comparisons
Company
  • How we make money
  • Blog
  • Privacy
  • Terms
  • Imprint
© 2026 FrameFight · Every clip on this site is a real model render