Age assurance guidance separates declaring from proving

What happened

Regulators in two countries have published guidance defining age assurance methods, separate from any specific companion app's practice. The UK Information Commissioner's opinion on the Children's code defines 'age verification' as a method to confirm exact age or over-18 status, 'age estimation' as an algorithmic estimate of an age range, and 'self-declaration' as a method where a user states their age with 'no further evidence' required. Ofcom's guidance on age checks, retrieved via an archived capture on 16 September 2026, states that self-declaration and payment checks that 'don't require a person to be 18' are 'not highly effective'. Australia's government-commissioned Age Assurance Technology Trial tested '48 vendors and over 60 distinct technologies' for accuracy, privacy and security.

What the documents show

The ICO opinion and Ofcom's guidance agree that self-declaration is the weakest category: a user's own typed birthdate, unverified, is treated by both regulators as providing no real assurance. The trial report goes further, stating the evidence base shows age assurance 'can be done' to a 'highly effective' standard using estimation or verification methods, while adding that 'no single solution fits all contexts'. None of the three documents states that any specific companion app has adopted a verification or estimation method; they describe the regulatory and technical landscape those apps operate inside.

The mechanism

The distinction that matters is between a method that asks and a method that checks. Self-declaration and parental confirmation both rely on someone's unverified statement; age estimation applies an algorithm, often to a face image or behavioural signal, to infer a likely range; age verification checks an external credential, such as an ID document or a mobile network record, against a threshold. A companion app that only asks a birthdate at signup is using the category both regulators say offers the least assurance, regardless of what its marketing implies about safety for minors.

What it leaves open

None of these documents states which method, if any, a specific companion app in this directory currently uses; that would require checking each app's own signup flow and policy pages directly, an editorial check outside the scope of this comparison.

• Does the app ask for a birthdate only, or does it apply an estimation or verification step?
• Is the same age-assurance method applied at signup and again later, or only once?
• Does the app's own documentation say which category of method it uses, in these terms?

Regulatory guidance now gives a shared vocabulary for age assurance; whether a given companion app's own practice matches the stronger end of that vocabulary is a separate, per-app question this record does not settle.