Verification policy

Email verification — active

Registration confirmation checks control of the email inbox used for the account. A verified email is required for the member experience. It does not establish real-world identity, legal age, venue authority or trustworthiness.

Age assurance — not yet operational

Current registration uses an 18+ declaration, and represented people have an adult date-of-birth constraint. These are not independent age assurance and are not presented as satisfying Ofcom's highly effective age-assurance standard.

A suitable age-assurance process, access restrictions, vendor/security assessment and applicable Online Safety Act obligations require specialist review before any in-scope adult-content public launch. A username-and-ID selfie, by itself, is not claimed to meet Ofcom requirements.

Manual authenticity checks — planned

The profile model has a system-managed verification state, but a complete evidence-submission, reviewer and appeal workflow is not implemented. Do not interpret a badge or a member's own verification claim as proof that every person or photograph has been independently checked.

Any future process must say what was checked, when it was checked and what the badge does not cover. Verification can never establish ongoing consent or guarantee someone's behaviour.

Identity evidence must be protected

There is no member ID-submission route in the current app. Do not send identity documents through member chats or upload them as public/profile photos. A member asking for them is not an official verification service.

If evidence collection is introduced, it needs restricted reviewer access, data minimisation, secure storage/transmission, an approved short retention/deletion schedule, access auditing and a rights/appeals process. No retention duration, provider certification or secure-review service is invented by this policy.