Commercial provider whose evidence contributed to acceptance of an assurance method

VerifyMy Limited

VerifyMy Limited, company 12050874, supplies age-assurance services including email-based estimation. Its product page describes email ownership checks and digital-footprint analysis in background account-creation or checkout flows and explicit age gates. It also appears as an AgeAware design participant and contributor to Ofcom's evidence base.

Product, design and regulatory contribution

The company reports ACCS certification under requirements incorporating ISO/IEC 27566-1; the actual certificate and algorithm were not independently inspected. euCONSENT's January 2025 account credits it with detailed AgeAware design work. Ofcom's January decision expressly credits AVPA and VerifyMy evidence for the method addition, conditional on effective implementation. The sources give no customer-specific deployment link to Reddit, price or exclusive award.

What the records show

VerifyMy LimitedEmail-based age estimation as a HEAA-capable method

supplied evidence expressly relied upon in method acceptance

16 January 2025 statement; current provider identity separately read 9 September 2026.

Ofcom paragraphs 3.85–3.87 explicitly credit AVPA and VerifyMy evidence when adding email-based estimation. This connects the named provider to a method-level decision; it does not endorse a vendor, establish performance in a particular deployment, or identify Reddit’s unnamed email supplier.

VerifyMy LimitedAgeAware interoperability proposal and proof of concept

is credited with detailed design work for

Recipient account9 January 2025, following5 August 2024 draft.

January 2025 project account identifies provider as ASBL member from original project team helping design proof of concept. Draft2024 reviewer listing is a separate proposed-role record. No compensation, exclusive award, veto or customer deployment shown.

VerifyMy LimitedAge Check Certification Scheme Ltd

reports its platform has certification incorporating ISO27566-1 from

Current product page captured9 September 2026; not backdated to January 2025.

Provider says ACCS1:2025 technical requirements incorporate ISO27566-1, classifying its email and face methods highly effective. Actual certificate, independent method evaluation and fee are not obtained; not Ofcom product endorsement.

From the investigation

3. A standards editor is also a certification-business principal

VerifyMy's current product page names its legal operator as VerifyMy Limited, 12050874. It sells email-age estimation using an email, ownership checks and digital-footprint analysis, with background account-creation/checkout and explicit age-gate variants. It reports ACCS certification of its platform under ACCS1:2025 incorporating ISO27566-1. This is a provider's certification claim, not independent inspection of its certificate or algorithm. It supplies no price, profit, customer list or assignment to Reddit.

Read the research & sources ↗
3. A standards editor is also a certification-business principal

Policy lane separately owns the Ofcom January2025 disposition crediting AVPA/VerifyMy evidence for adding email estimation. That is actual method-level uptake; it is not evidence VerifyMy supplies every platform using the method. Ofcom's refusal to make independent certification compulsory or automatically sufficient must accompany any combined narrative.

Read the research & sources ↗
What consultation actually changed

Paragraphs 3.85–3.87, PDF 27: AVPA/VerifyMy evidence supported adding email-based estimation, conditional on effective implementation. Paragraphs 3.103–3.105, PDF 30–31: token references were added, retaining responsibility for the underlying check and sharing process. The preceding response summary, paragraphs 3.66–3.68 and footnote 94 on PDF 24, attributes the token recommendation to 5Rights, Yoti and the ACT App Association. Paragraph 3.108, PDF 31, and 3.350–3.353, PDF 76–77: certification can evidence compliance but is neither compulsory nor automatic; Ofcom did not adopt Yoti's request to mandate independent testing/certification. Paragraphs 3.243–3.259, PDF 54–57: requested numerical thresholds were declined at that stage, citing inadequate comparable evidence/testing and market-development concerns. Paragraphs 3.277–3.290, PDF 62–65: 5Rights' separate privacy-criterion proposal was declined because existing data-protection law applied; design/minimisation guidance was strengthened. None of these outcomes proves a private bargain or sole authorship.

Read the research & sources ↗

Further reading

UK age-assurance market: instruments, interests and limits

UK age assurance: statutory chain and consequential choices

Read the original sources 4

What the connections say

3 relationships
1

VerifyMy Limitedreports its platform has certification incorporating ISO27566-1 fromAge Check Certification Scheme Ltd

Current product page captured9 September 2026; not backdated to January 2025.

Reported by the cited source

Provider says ACCS1:2025 technical requirements incorporate ISO27566-1, classifying its email and face methods highly effective. Actual certificate, independent method evaluation and fee are not obtained; not Ofcom product endorsement.

Read the original source 1
2

VerifyMy Limitedis credited with detailed design work forAgeAware interoperability proposal and proof of concept

Recipient account9 January 2025, following5 August 2024 draft.

Reported by the cited source

January 2025 project account identifies provider as ASBL member from original project team helping design proof of concept. Draft2024 reviewer listing is a separate proposed-role record. No compensation, exclusive award, veto or customer deployment shown.

Read the original sources 2
3

VerifyMy Limitedsupplied evidence expressly relied upon in method acceptanceEmail-based age estimation as a HEAA-capable method

16 January 2025 statement; current provider identity separately read 9 September 2026.

Ofcom paragraphs 3.85–3.87 explicitly credit AVPA and VerifyMy evidence when adding email-based estimation. This connects the named provider to a method-level decision; it does not endorse a vendor, establish performance in a particular deployment, or identify Reddit’s unnamed email supplier.

Read the original sources 2