Age assurance in the U.S., UK and EU: what to build once
Build one system that controls access to restricted content. Give each market its own rules for what counts as evidence, when access expires, and what the site or verifier can retain. The same visitor returning after lunch may need a new check in one market and a different choice of methods in another. Design for those decisions before you choose vendors.

In this article
What to build once
This comparison covers online adult-content services, with selected U.S. states and EU member countries. The official sources were checked on November 22, 2026. Identify which legal category your service falls into, including who publishes the material and where the operator is established, before applying a market profile. [1] [6] [8] [11]
Separate three events. An underlying check establishes someone’s age or age band. A presentation supplies evidence for the current request, such as a wallet proof or a verifier’s response. An access decision lets the visitor into a defined part of your service for a limited period. Store the minimum needed to enforce the access decision. A valid account login or a fresh presentation may still leave an age check due under the applicable rules.
Build the content gate where the server releases restricted material. Use the same controls for page loads, direct media links and previews. Give the gate a shared way to start verification, verify the result, and handle a failed or inconclusive check. Keep the market-specific rules separately versioned. Each version should say which service and content it covers, which evidence and fallback routes it accepts, when to check again, what data each party can see or keep, and which deployment records to maintain.
U.S. state laws change the available routes
Texas requires covered commercial websites to verify that a visitor attempting to access the material is at least 18 when more than one-third of the site is sexual material harmful to minors. The statute names digital identification, which it defines as proof of identity, or a commercial system using government-issued identification or a commercially reasonable method relying on public or private transactional data. Standalone facial age estimation does not appear in that list. Section 129B.002(b) bars the entity or third party performing the required check from retaining identifying information. The Supreme Court upheld the challenged Texas verification requirement against a facial First Amendment challenge. That decision concerned Texas’s law. [1] [2]
Florida requires covered commercial sites or apps to offer standard and anonymous verification and let visitors choose. The anonymous route requires a qualifying independent third party organized under state law with its principal place of business in a U.S. state, subject to ownership restrictions. That provider may not retain identifying information after it verifies age, use it for another purpose, or share it. Check the provider’s qualifications and data handling as well as the buttons on the screen. [3] [4]
Ohio illustrates why an account flag and an access decision need separate rules. The statute addresses access to covered obscene or harmful material and requires an account or subscription check at creation and every two years thereafter. It also distinguishes the data deletion rules for the account and access checks. Treat the two-year interval as an account recheck rule and evaluate the requirements for access separately. [5]
UK performance is judged on the deployed flow
Section 81 of the Online Safety Act requires covered Part 5 services to use highly effective age verification or age estimation so children are not normally able to encounter regulated provider pornographic content. Part 5 here concerns provider-published material. User-to-user services have separate Part 3 duties. [6] [7]
Ofcom’s guidance assesses technical accuracy, robustness, reliability and fairness. It identifies photo-ID matching, digital identity services and facial age estimation as methods capable of being highly effective when used appropriately. If you use estimation, Ofcom recommends a challenge age based on the method’s accuracy and a further qualifying check for visitors estimated below that threshold. Test the fallback and decision flow together. A supplier’s test report covers only part of the evidence for your deployment. [7]
Keep a written record of which methods you use, how you use them, and how you considered privacy. The Act requires a public summary of the aspects relating to the access duty. Ofcom’s guidance says to leave personal data about users out of the written record. That calls for documentation of the system and its performance rather than a recording of individual checks. [6] [7]
EU rules combine a common framework with national requirements
Article 28 of the Digital Services Act requires covered online platforms accessible to minors to take proportionate privacy, safety and security measures. Article 19 exempts qualifying micro and small providers from that section, subject to exceptions. The Commission’s guidelines recommend age verification for high-risk platforms such as pornography platforms. Its April 2026 recommendation urges Member States to make an interoperable age verification solution available by the end of 2026, standalone or through EU Digital Identity Wallets. Treat it as a way to integrate age proofs and confirm local availability, trust and acceptance for each deployment. [8] [9] [10]
Within the EU, confirm where the operator is established and which measures apply to the specific service. In June 2026 the Court of Justice ruled that the E-Commerce Directive precludes applying a general criminal-law obligation of this kind to providers established in another member country. It also held that a destination country can impose a service-specific age verification measure under the directive’s conditions where the provider has failed to take appropriate audiovisual-media safeguards. Look for applicable individual measures and the home-country framework before configuring country rules. [11]
France, Germany and Italy give the gate different jobs
France’s Arcom standard requires covered operators to use a legally and technically independent verifier and keep the data underlying the check away from the adult site. Covered services must offer at least one double-anonymity route. Through that route the issuer cannot learn the destination service, and the service cannot use proof data to identify returning users or learn how the proof was obtained. Arcom specifies at least two ways to generate the proof and availability to at least 80 percent of adults resident in France. This affects both provider selection and the data the site receives. [12]
Germany’s interstate treaty provides for adult-only closed user groups for certain content, including ordinary pornography. KJM’s criteria distinguish one-off use from repeat access. For recurring use they call for initial identification and age verification, followed by authentication of the identified user during each use. KJM can evaluate a complete system or an individual component. Test whether the full deployment keeps restricted content inside the closed group. [13] [14]
Italy’s AGCOM resolution calls for independent third parties and double anonymity for covered services. It requires a check at access and a new one on return after interruption. Under the resolution, verification expires when the session ends, the browser closes, the system goes into standby, or after 45 minutes of actual inactivity. AGCOM publishes a list of operators and different implementation dates depending on where they are established. Check the list and the cross-border rules for the specific service. [15] [16] [11]
One returning visit, three decisions
Imagine an operator has verified a visitor at noon. The visitor leaves the tab open, goes away for 50 minutes, and returns to the same device. Assume this operator is covered in each market and uses an independently vetted method there.
For the UK service, test whether the session still reliably represents the verified adult under the deployed Part 5 flow, including the possibility of a shared device. Set the session policy using that evidence. For Florida, when your policy calls for a check, preserve the choice of both statutory routes and apply the anonymous provider’s data restrictions. Neither example supplies an approval for a 50-minute session. [6] [7] [3] [4]
For the covered Italian service, 50 minutes of actual inactivity exceeds AGCOM’s limit. Trigger a qualifying check before granting access again. A qualifying flow can separate the initial identification from fresh authentication for the current session. Design the return so a previous access decision cannot stand in for that check. [15]
What to verify before launch
Use one test matrix and run it against each version of your market rules. Include ordinary use, a returning visitor, a shared device, an unavailable provider and direct requests for restricted material.
- Scope. Record the service type, content trigger, operator establishment, applicable order and last source check.
- Methods. Verify the underlying evidence, qualifying provider, user choices and fallback available in that market.
- Timing. Test account rechecks separately from session expiry and from proof presentation or authentication.
- Data. Trace what the site, issuer, verifier and analytics can see, link or retain. Include failures and retries.
- Deployment evidence. Save dated test results and publish any required description. Recheck the relevant market profile when rules, providers or content routes change.
Sources
- Texas Civil Practice and Remedies Code, Chapter 129B Texas Legislature
- Free Speech Coalition, Inc. v. Paxton, June 27, 2025 Supreme Court of the United States
- Florida Statutes § 501.1737 Florida Senate
- Florida Statutes § 501.1738 Florida Senate
- Ohio Revised Code § 1349.10 Ohio Laws and Administrative Rules
- Online Safety Act 2023, Part 5, section 81 UK Parliament
- Guidance on highly effective age assurance and other Part 5 duties Ofcom
- Digital Services Act, Regulation (EU) 2022/2065, Articles 19 and 28 European Union
- Guidelines on the protection of minors online under Article 28(4) European Commission
- Commission Recommendation (EU) 2026/1035 on EU-wide age verification technologies European Commission
- WebGroup Czech Republic and Others, C‑188/24 and C‑190/24 (June 16, 2026) Court of Justice of the European Union
- French technical standard for age verification on pornographic services Arcom
- German Interstate Treaty on the Protection of Minors in the Media, § 4 Bavarian State Government
- KJM criteria for age verification systems and closed user groups Commission for the Protection of Minors in the Media (KJM)
- AGCOM Resolution 96/25/CONS (official English courtesy translation) AGCOM
- AGCOM implementation and list of covered services AGCOM