Levels of assurance
There are different levels of reliability and accuracy required by the various legislation – referred to as “levels of assurance.”
Broadly these fall into two categories:
- Strict verification is where an actual date of birth is required to be legally compliant. This is either because the law specifies an exact age, or the level of risk of harm to a child is high enough to warrant the strongest forms of due diligence about their age. An example of a specific age is the Digital Age of Consent” where if you are 12 years and 11 months old in the UK, it will not be legal for a website to process your data on the basis of consent without your parents’ approval. Likewise, to sign a contract that can be enforced, you must be at least 18 years-old. A day short, and the other party will fail in court so the contract is worthless
- Basic age verification allows for an estimate of a user’s age to be sufficient to keep regulators happy. The Age-Appropriate Design Code is the best example. The ICO goes as far as setting out five age-bands as guidance, but services can choose their own age bands, and indeed, they may specify overlapping bands.
Other examples could be the processing of children’s data based on legitimate interest where the nature of the processing is not a significant risk to a child of 8½ but would normally be more reasonably considered acceptable once they reach 10.
The UK Online Safety Bill is also a proportionate requirement, with risk assessments guided by the regulator through published risk profiles for different types of service, and codes of conduct for each new duty. But there is a wide degree of discretion for the services to determine what level of protection, if any, is required for children of different ages. This introduces, again for lower levels of potential harm, the opportunity to use softer estimation techniques.