Short answer
A fast-growing list of markets now legally requires adult websites to verify that visitors are 18 or over, including the United Kingdom (Ofcom), France (ARCOM), Italy (AGCOM), Germany (KJM), around half of US states, and Australia and Brazil under newer rules. A checkbox no longer counts. Build one configurable age-assurance layer with more than one method, route users by jurisdiction, and keep only a pass or fail result.
Why age verification became mandatory
For most of the web's history, adult sites relied on a splash page asking visitors to confirm they were 18. Regulators in many countries have now decided that self-declaration is not enough, and they have given themselves powers to fine, block or delist sites that do not use stronger checks. The direction of travel is the same almost everywhere: more markets, stricter standards, and a growing focus on privacy so that proving your age does not mean handing your identity to every site you visit.
For an adult platform this is now an engineering problem as much as a legal one. Each market describes the goal slightly differently, accepts different methods and sets different data rules. A platform that sells into ten countries needs a single system that can apply ten sets of rules without ten separate builds.
The main regimes at a glance
| Market | Main rule | Regulator | Self-declaration accepted? |
|---|---|---|---|
| United Kingdom | Online Safety Act 2023: highly effective age assurance | Ofcom | No |
| France | SREN law 2024 and ARCOM technical standard | ARCOM | No |
| Italy | Decree-Law 123/2023 and AGCOM rules (double anonymity) | AGCOM | No |
| Germany | JMStV: closed user groups for adult content | KJM and state media authorities | No |
| United States | State laws in roughly half of states; upheld in Free Speech Coalition v. Paxton (2025) | State attorneys general | No, where a state law applies |
| Australia | Online Safety Act 2021 industry codes | eSafety Commissioner | Being phased out under the codes |
| Brazil | ECA Digital (Law 15.211/2025) | ANPD and other authorities | No |
| EU-wide | Digital Services Act Article 28 and Commission guidelines | National Digital Services Coordinators and the Commission | Discouraged for adult content |
Several other markets are in transition. Spain and Poland have been working on national rules, Canada's Parliament has debated federal bills more than once, and the Nordic countries are watching the EU approach closely. Our country pages carry a short summary for each market, including the regulator and links to official sources.
United Kingdom: the strictest benchmark
The Online Safety Act requires services that publish pornographic content, and user-to-user services that allow it, to use highly effective age assurance so that children cannot normally encounter it. Ofcom has said self-declaration, general terms of service and simple debit card checks without further steps do not meet the bar. Methods it has described as capable of being highly effective include facial age estimation, photo ID matching with a liveness check, open banking, credit card checks, mobile network operator checks and digital identity services.
Ofcom has been enforcing these duties since July 2025 and can fine up to 10% of qualifying worldwide revenue or ยฃ18 million, whichever is greater. Because the UK standard is detailed and well documented, many platforms use it as their global baseline.
European Union: national rules plus the DSA
Inside the EU there are two layers. National laws, such as France's SREN law, Italy's AGCOM rules and Germany's JMStV, set specific duties for adult sites. On top of that, the Digital Services Act requires online platforms that under-18s can access to ensure a high level of privacy, safety and security, and the European Commission has published guidelines that treat strong age verification as appropriate for adult content.
France and Italy both favour double anonymity: an independent provider confirms the user is an adult, and the site receives only a proof of age, without learning who the user is. Germany has historically required a closed user group in which users are verified once and then authenticated on every visit. These models are compatible if your architecture treats the age check as a separate service that returns a token.
United States: a state-by-state patchwork
There is no federal age-verification law for adult websites. Instead, states have passed their own laws, typically requiring commercial sites where a substantial share of content is harmful to under-18s to verify age with government ID or a commercially reasonable method. In June 2025 the Supreme Court upheld Texas's law in Free Speech Coalition v. Paxton, which removed much of the legal uncertainty and encouraged more states to act.
The practical consequence is geolocation. A site must know, with reasonable confidence, which state a visitor is in, then apply that state's rules. Some laws allow private lawsuits as well as enforcement by the attorney general, and most prohibit keeping identifying information after the check.
Which methods pass, and what they cost in conversion
| Method | How it works | Strengths | Watch-outs |
|---|---|---|---|
| Facial age estimation | Selfie analysed to estimate age; image not stored | Fast, no documents | Needs a buffer age (for example 23+) and a fallback |
| ID document with liveness | Photo ID matched to a live selfie | High assurance, widely accepted | Highest drop-off; sensitive data |
| Credit card check | Card validated with issuer | Familiar to users | Not accepted everywhere on its own |
| Open banking | Bank confirms the account holder is an adult | Strong, low data | Coverage varies by country |
| Mobile operator check | Operator confirms no age restriction on the account | Low friction | Coverage and accuracy vary |
| Digital identity wallet | Reusable credential proves age only | Privacy-preserving, reusable | Adoption still growing |
No single method works for every user. The platforms with the best pass rates offer two or three methods, explain clearly why the check exists, and let a verified user stay verified across sessions where the rules allow.
Designing one flow for many markets
- Map each market you serve to its rule, accepted methods and data restrictions, and have counsel confirm the map.
- Put age assurance behind a single internal service with a policy table keyed by jurisdiction.
- Detect location conservatively. If you cannot place a user reliably, apply your strictest policy.
- Integrate at least two independent providers so a user who fails one method can try another.
- Store a signed pass or fail token with method, provider, timestamp and jurisdiction. Do not store images or documents.
- Keep a public, non-explicit layer of pages (home, category descriptions, legal pages) that search engines and unverified users can see.
- Log every check in an audit trail you can export for a regulator or payment partner.
- Review the policy table whenever a market announces new rules.
Common mistakes
- Gating the whole domain, including pages that contain nothing explicit, which hurts search visibility for no compliance benefit.
- Relying on one provider, so an outage or policy change stops all sign-ups.
- Keeping document images 'just in case', which turns a compliance feature into a data breach risk.
- Treating VPN users as compliant by default instead of applying a conservative policy.
- Hard-coding rules per country, so each legal change becomes a development project.
Age verification is now a permanent part of running an adult platform. Treated as a configurable service rather than a one-off integration, it becomes a manageable cost, and one that payment partners increasingly expect to see before they will work with you.
Frequently asked questions
Is a 'Are you 18?' button still legal anywhere?
In markets without a specific law it may not be unlawful in itself, but the UK, France, Italy, Germany and many US states reject self-declaration. Payment partners also expect stronger checks, so we do not recommend relying on it.
Do I need to verify users from countries without an age-verification law?
Not always by law, but many platforms apply one global standard because it simplifies the product and satisfies card network expectations. Your counsel should confirm the position for your markets.
Can I store a verified user's status so they do not repeat the check?
Usually yes, if you store only the result and the rules in that market allow reuse. Some regimes expect re-authentication on each visit, which a secure login can satisfy.
How do VPNs affect compliance?
Regulators generally expect reasonable measures, not perfection. Apply your strictest policy when location is uncertain and do not encourage users to bypass checks.
Who is responsible if the age-verification provider makes a mistake?
Responsibility normally stays with the platform. Choose providers that publish accuracy data and certifications, and keep logs that show you used the method properly.
About this guide
Written by Adult Digital Agency editorial team
Last reviewed 19 November 2026. We build software for legal adult businesses; we update guides when laws or provider terms change.
Official sources
- Protecting children online (Online Safety Act guidance)Ofcom
- Free Speech Coalition, Inc. v. Paxton, opinion of the CourtSupreme Court of the United States
- Regulation (EU) 2022/2065 (Digital Services Act)EUR-Lex, Publications Office of the EU
- Technical youth media protectionCommission for the Protection of Young People in the Media (KJM)
- AGCOM official siteAutoritร per le Garanzie nelle Comunicazioni
Written by engineers, not lawyers. Laws and platform policies change; confirm your obligations with qualified counsel in each market.