Is there 2257 record keeping in Europe? Not as such: no UK or EU law copies the US rule in 18 U.S.C. § 2257 that requires producers to hold age records for everyone shown in sexually explicit content. But card-scheme rules from Visa and Mastercard, the UK Online Safety Act, the EU Digital Services Act and criminal law combine to make age and consent records a practical necessity, while GDPR dictates how you store them. If you take card payments for adult content, you need them.
This guide is for paysites, fan platforms, studios and creators who publish or host adult content for European audiences. It is general information, not legal advice.
What 18 USC 2257 requires, and does it reach Europe?
The US rule requires "producers" of actual sexually explicit content to check each performer's government ID before production, keep copies indexed to the content, label the content with the location of the records and make them available for inspection. The implementing regulations require records to be kept for seven years from creation or last amendment or addition, and for five years after the producer ceases business.
A European company is not automatically covered, but US law can bite if you produce content for US distribution, sell into the US or work with US-based platforms, many of which ask for 2257-style documents in their contracts. Many European studios therefore keep 2257-compatible records anyway; it is the industry's de facto standard.
Why European operators still need performer records
| Source | What it requires in practice | Who it hits |
|---|---|---|
| Mastercard and Visa rules | Verified age and identity of everyone depicted and every uploader; written consent; content review before publication; complaints resolved in 7 business days; appeals for depicted people | Any merchant taking card payments for adult content, through its acquirer |
| UK Online Safety Act 2023 | Prevent and remove illegal content, including child sexual abuse material and intimate image abuse; providers must be able to act on reports quickly | User-to-user services and porn publishers with UK users |
| EU Digital Services Act | Notice-and-action, statements of reasons, trader traceability on marketplaces | Hosting services and online platforms with EU users |
| Criminal law | Possessing or publishing images of under-18s is a serious offence across Europe; new UK offences from 6 November 2026 | Everyone, including affiliates who republish |
| GDPR / UK GDPR | Lawful basis, minimisation, security and retention limits for the ID data you collect | Anyone processing performers' personal data |
Card-scheme rules are the strictest driver
Mastercard's 2021 standards for adult content, described in its statement on preventing illegal adult content, require merchants to confirm that every person depicted is an adult and to produce supporting documents on request, to accept uploads only from verified content providers, and to hold written consent from everyone depicted. Visa applies comparable expectations to high-risk merchants through its integrity risk programme. Your acquirer or payment processor will translate these into audit checklists, and losing their support usually ends a paysite faster than any regulator.
The UK is moving towards formal verification duties
The Crime and Policing Act 2026 gives the government powers relating to checking that people in online pornography are adults who consented, and requires a report on the role of online providers in age and consent verification. Detailed rules have not yet been made. Treat robust records as the minimum now; see our guide to the Crime and Policing Act 2026 pornography offences.
What performer ID verification records to keep
A defensible file for each performer and each piece of content usually contains:
- Identity: a copy or verified record of a current government-issued photo ID, with legal name, date of birth and document number.
- Liveness and match: evidence the ID belongs to the person, such as a selfie or video match, ideally through a third-party verification provider.
- Stage names and aliases linked to the legal identity.
- Content link: which scenes, sets or streams the person appears in, with production dates.
- Consent: written consent to being recorded, to publication on named platforms, to download if applicable and to any promotional use.
- Co-performer records for everyone else appearing, collected by the uploading creator if you are a platform.
- Withdrawal and complaints history for that content.
Performer consent records and model releases
A model release in the UK is a contract, not a statutory form, so there is no prescribed wording. What matters is that it is specific and evidences genuine, informed consent. Good practice includes:
- separate consent to recording and to distribution, with the platforms and territories named;
- clear payment terms, so consent is not confused with the fee;
- an explanation of how the performer can raise a concern or request removal;
- signature and date, ideally captured electronically with an audit trail;
- re-consent when content is moved to a new platform or used in a new way.
Consent can be challenged. Card-scheme rules require that a depicted person can appeal for removal. If consent cannot be shown, or the person shows it was void, the content must come down. A strong file protects both the performer and your business.
For creators working with collaborators, our guide to creator collaboration safety covers the practical side of collecting co-performer documents.
How long to keep performer records, and GDPR
No European law sets a specific retention period for performer age records. GDPR's storage limitation principle says you keep personal data no longer than necessary for the purpose. In practice, operators set a period that covers the life of the content plus a buffer for legal claims, card-scheme audits and, where relevant, US requirements.
- Lawful basis: usually legitimate interests or legal obligation for compliance, and contract for the release itself. Record your reasoning.
- Biometric data: face matching used to identify someone is special category data and needs an Article 9 condition. See our guide to special category data on adult sites.
- Security: encrypt ID files, restrict access to named staff and log every access.
- Minimise: if your verification provider can give you a verified result plus a retrievable record, you may not need to store raw ID images yourself.
- Transparency: tell performers in a privacy notice what you keep, why and for how long.
Worked example (hypothetical): a studio keeps records for the period the content is on sale plus seven years, which covers its US distribution contracts and the six-year limitation period for most contract claims in England and Wales, then deletes ID images while retaining a minimal log that verification took place.
Common record-keeping mistakes
- Records that cannot be matched to content. An ID scan in one folder and a video in another is not enough; index every file to the scenes it covers.
- Expired or unreadable documents. Check the document was valid on the production date and that the date of birth is legible.
- Consent by message thread. A chat saying "fine to post" is weak evidence. Use a signed release.
- Missing co-performers. Platforms often verify the account holder but not the other people in the content.
- Keeping everything forever. Indefinite retention of ID images increases breach risk and breaches GDPR's storage limitation principle.
Platforms versus producers: who keeps what
Responsibility depends on your role.
- Studios and producers collect records directly from performers.
- Fan and creator platforms verify each creator, require creators to upload co-performer records, and review content before publication to meet card rules.
- Tube sites and hosts should require uploads from verified accounts only and be able to obtain records quickly when challenged.
- Affiliates and reviewers normally rely on the sponsor's compliance, but should only use promotional material supplied by the program, never ripped clips.
Moderation and records work together; see our guide to building a content moderation policy for adult platforms and our piece on intimate image abuse laws.
Frequently asked questions
Do I need a 2257 statement on a European website?
Only if US law applies to you or a partner contract requires one. Many European sites publish a records statement or compliance page anyway, because it reassures payment partners and users.
Can I rely on my verification vendor's records?
You can use a vendor, and most large platforms do, but you remain responsible. Check that the vendor can produce a record quickly, how long it retains data and what happens if your contract ends.
What about AI-generated performers?
Fully synthetic content still raises consent questions if it resembles a real person, and new transparency rules apply in the EU. See our guide to AI Act deepfake labelling.
Next steps
Audit a sample of your content against the checklist above and close any gaps before your acquirer asks. To compare identity and age verification vendors, see our compliance and verification services directory, and find related guides in the laws and regulations hub.