CYBER WELFARE

Protect your Digital Privacy

Proving only what is asked: sharing the minimum when a site checks your age or identity

Mark is twenty-seven, and one evening on the sofa he wants to watch an 18-rated film on a platform he has used for years. Before it starts, a new screen asks him to confirm his age. There are four buttons: “Upload your ID”, “Take a selfie”, “Confirm with your mobile network”, “Use a digital identity app”. His first instinct is the quickest one: photograph his identity card, front and back, and be done with it.

Then he stops. The site needs to know one thing only: that he is over eighteen. His identity card, on the other hand, carries his full name, date of birth, address, document number, photo and signature. Why hand all that over to prove a single fact?

This recommendation, R39 of the Cyber Welfare Framework, invites you to do what Mark did that evening: prove only what is asked online. When a site or an app checks your age or your identity, read how the check works before you tap the first button, and choose, from the methods on offer, the one that proves the required fact while sharing the least. It does not ask you to refuse checks, only to pause for a minute before handing over part of yourself.

What this recommendation says

Recommendation R39 states that when a site asks you to prove something about yourself, you give it only what is needed to prove that fact.

Three terms to clarify straight away:

  • age assurance is the set of checks a service uses to establish that you are over a certain age, with a document, an estimate from your face or a confirmation from someone who already knows you, such as your bank or your mobile network;
  • identity verification is the check a service uses to establish that you really are who you say you are, for example when you open an account, hire a car or recover a login;
  • data minimisation is the principle that only the data needed for the purpose is used: the GDPR (and the UK GDPR) sets it out in Article 5(1)(c), which requires data to be “adequate, relevant and limited to what is necessary”.

In practice, the recommendation comes down to three habits:

  • asking yourself what fact you need to prove: “I am over 18”, “it really is me”, “I can drive”;
  • reading how the check works: who carries it out, what the site receives, what is kept and for how long;
  • choosing the method that hands over least, and sending a document only where the process genuinely requires one.

What it is not. It is not a way to get round checks that the law requires, and it is not a judgement on the laws that require them: when a check is mandatory, the recommendation helps you pass it while sharing the minimum. It is not about children’s ages, accounts or safety: for that there are specialist organisations, which our course points to. It does not cover “Sign in with…” buttons, which are the subject of the recommendation on limiting social login, nor sending documents in general, which is covered by the recommendation on sharing documents with only what is needed.

Where it applies. To every age or identity check you meet online: video platforms, shops selling alcohol, hire services, forums that introduce a check for some sections. It is about you, as an adult, and the data you hand over about yourself.

Why it matters

Think of an “over 18” stamp on an entry ticket. Whoever checks at the door sees the stamp and learns nothing else about you. Now imagine that, to get that stamp, someone asks you to leave a copy of your identity card in a drawer. At the door the result is the same. Afterwards, it is very different: that copy stays somewhere, and you no longer know who looks at it.

Online checks can work either way, and the button does not show which. A check usually involves three parties: you, the site you want to use and, often, an outside company carrying out the check on its behalf. The useful question is: at the end, what does each of the three know?

The rules are changing, and it helps to date them:

  • in the UK, Ofcom, the online safety regulator, explains that from 25/07/2025 all sites and apps that allow pornography must have strong age checks in place, and that ticking a box is no longer enough; it also advises users to exercise caution and judgement when giving over personal information;
  • in Italy, AGCOM, the communications regulator, adopted age verification rules for sites distributing adult content on 08/04/2025, fully in force since 12/11/2025 according to its announcement that day, with a “double anonymity” model: whoever certifies your age does not know which site it is for, and the site does not receive your identifying details;
  • in the European Union, the Commission, in its questions and answers updated on 18/05/2026, expects its age verification solution to be available across the EU by the end of 2026; according to its digital identity page, Member States will make European Digital Identity Wallets available by the same date.

Data protection authorities point the same way. The European Data Protection Board (EDPB) notes, in its statement of 11/02/2025, that a service may only need to know whether a user is over or under an age threshold. The ICO, the UK’s data protection regulator, expects organisations running these checks to keep only the minimum necessary and for no longer than needed. But the options in front of you still differ, and the EDPB itself writes that security breaches should be expected.

The concrete consequences show up on four fronts:

  • copies that stay: a document or selfie sent for a check may be kept, sometimes for longer than you imagine;
  • data that adds up: your name, date of birth and address, combined with what you do on that site, say far more about you than “over 18”;
  • more openings for identity theft: every copy of your document out there is a copy someone might try to use;
  • less control over who knows what: if you do not know who ran the check, you do not know whom to ask for deletion.
Benefit of proving only what is askedWhy it matters
The site receives a fact, not a fileWhat you do not hand over cannot be kept, reused or lost
Fewer copies of your document aroundFewer openings for identity theft
Your identity stays separate from what you doThe site knows you are an adult, not who you are
You know whom to contactYou have read who runs the check and what it keeps
A choice, not a reflexYou decide which route to take, even when the check is mandatory

A concrete example

Back to Mark, on the sofa.

He opens the page explaining the four methods. The check is run by an outside company named in the privacy notice. His document would be photographed and compared with a selfie, and the notice says the images are kept “for as long as needed to handle any disputes”, with no precise period. The selfie alone would be used to estimate his age: the image is deleted afterwards, the notice says, but it passes through the company’s servers. The digital identity app would send a yes-or-no answer, but Mark has not installed it. The mobile network check looks only at whether his line has the restrictions set for under-18s: if it does not, the site receives confirmation that he is an adult. It needs his phone number, which the platform already has, but not his document or his face.

Mark chooses the mobile network. It takes him a minute longer than the document, and on his age the platform receives a single piece of information: “over 18”.

The same week Mark joins a car club. Here the fact to prove is different: being an adult is not enough, he must be allowed to drive. The driving licence is genuinely needed, and Mark uploads it. But he reads the process and notices that only the front is required: he does not send the back as well, which the first form had suggested as “optional”.

Two checks, two different facts, and both times Mark handed over only what was needed.

When to apply it

There are moments when the rule makes an obvious difference.

  • When a site you have used for a while introduces a new check. This is when people tend to pick the first button.
  • When you are offered the option of uploading a document. It is the route that hands over the most: it is worth checking whether there is another.
  • When the request arrives by email, text or chat. A real check happens inside the site or app, not from a link that turns up out of the blue.
  • When a check gets it wrong. If a face-based estimate puts you younger than you are, ask for an alternative method rather than sending everything you have straight away.

How to apply it

A short sequence, to repeat.

  1. Stop on the fact. Ask yourself what the site is asking you to prove: an age, your identity, an entitlement.
  2. Read how the check works. Many sites explain the methods before you start; Ofcom expects UK services to do so. Look for three answers: who runs the check, what the site receives, what is kept and for how long.
  3. Compare the methods on offer. A yes-or-no confirmation from someone who already knows you, or a proof generated by a digital identity app, usually hands over less than a document and a selfie.
  4. Choose the one that proves the fact and nothing more. If the choice is not clear, prefer the method in which the site receives neither your document nor your image.
  5. If a document is needed, send only what the process asks for. The front if the front is enough; and, where it is allowed, cover the details that are not needed, as explained in the recommendation on sharing documents with only what is needed.
  6. Do the check only inside the site or app. Do not start from a link that came in a message: open the service yourself and find the request there.
  7. If no option feels right, stop and ask. Write to the service to ask for an alternative or to find out what is kept. The EDPB recommends that alternative methods be made available to users when reasonably possible.

The steps in the right order, with what to do if you have already sent more than needed, are in the guide on how to verify your age without oversharing. The methods you may come across, with what each one hands over and its limits, are described in the post on age assurance methods.

Common mistakes to avoid

  • Thinking that, if it is mandatory, every option is the same. The rule may require the check, but the methods on offer can hand over very different amounts of data.
  • Sending front and back “just in case”. If the process asks for one side, the second is extra data someone will have to look after.
  • Replying to a message asking you to “verify your account”. A legitimate check is found inside the service; an unexpected link deserves suspicion, not haste.

How this connects to the Cyber Welfare Framework

R39 replaces a reflex with a question: “what do I need to prove?”. It follows the same principle as the recommendation on limiting social login, giving a site no more of your identity than it needs, and it links to the one on sharing your phone number only where needed, because some checks go through the network your line is on.

PillarHow this contributes
SkillsKnowing how to read a check’s explanation, identify who runs it and compare the methods on offer
AwarenessUnderstanding that a site usually needs one fact, and that methods differ in what they hand over and keep
Secure BehaviourChoosing the method that shares least, sending a document only where it is genuinely needed and doing checks only inside the service

Digital maturity levels.

  • FL1 — Basic. You pick the first method offered, often the document, to get it over with. It is the most common starting point, not a fault.
  • FL2 — Beginner. Before choosing, you ask yourself what fact you need to prove and read how the check works.
  • FL3 — Autonomous. You compare methods, choose the one that hands over least, keep a note of where you have sent a document and know how to ask for deletion.
  • FL4 — Skilled. You can spot a fake verification request, know what to do if a document has been exposed and know which authorities to turn to.
  • FL5 — Expert-Guide. You help family, colleagues or adult learners read a check calmly, without judging anyone who has already sent a document.

R39 is a key step at the FL2 — Beginner level, and it remains an active habit at every level after that.

How to check you are applying it properly

Three questions, to be answered honestly.

  • The last time I proved my age online, did I know what the site received?
  • Could I say which services I have sent a copy of my document to in the past two years?
  • Faced with several methods, do I choose the quickest or the one that hands over least?

Quick checklist

  • ☐ Before a check I ask myself what fact I need to prove
  • ☐ I read who runs the check and what is kept
  • ☐ From the methods on offer I choose the one that hands over least
  • ☐ I send a document only where the process genuinely requires it
  • ☐ I do checks only inside the site or app, never from a link I received
  • ☐ I keep a note of the services I have sent a document to

If a box stays empty, you already have your next step. For a more structured measure of your level, take the digital resilience self-assessment.

In short

Age and identity checks are becoming more common. Often the site needs one fact, but some methods hand over much more.

In practice: ask yourself what fact you need to prove, read how the check works, choose the method that hands over least and send a document only where it is genuinely needed. If no option feels right, you can stop and ask.

The checks may be here to stay. What you hand over about yourself, though, is your decision.

Something to think about. The last time a site asked you to prove who you are, or how old you are, did it need everything you gave it?

Explore this recommendation

This recommendation is the pivot of a content unit. Each post looks at a different aspect.

Related resources

Short reads from the Resources section, for anyone who wants to focus on a single aspect:

Start with the first step: the Cyber Welfare Programme guides you free of charge, one recommendation at a time.