Skip to content
ISO 27566 · ISO-27566-PRIVACY-MINIMIZATION

ISO 27566 Clause 5.3 - Privacy Characteristics

Minimize personal data in age assurance to only what is needed for age determination; avoid persistent identifiers and delete data after verification

CRITICALRequirementData collectionTechnical standardIn forceApplies from 15 January 2025

Where this comes from

Provision: Clause 5.3 - Privacy Characteristics

Instrument: ISO/IEC 27566-1:2025

Citation: ISO/IEC 27566-1:2025, Age assurance systems -- Framework, Clause 5.3: Privacy Characteristics

Text version: ISO/IEC 27566-1:2025

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • Data categories collected — any answer
  • Data retention period — any answer

…unless:

  • Age verification method: No age verification

What engineering work it implies

  • Data Minimization at CollectionCovers it fully

    Implement data minimization principles by collecting only necessary data with purpose limitation.

Sample acceptance criteria Landfall generates for this obligation:

  • For each field, document WHY it's necessary (link to feature that uses it)
  • Remove fields that have no documented necessity
  • Mark truly optional fields as optional in UI (not required)
  • Implement automatic deletion when retention period expires
  • Don't collect 'nice to have' data - only 'need to have'

Questions people ask

Does ISO 27566 Clause 5.3 - Privacy Characteristics apply to my service?
It applies when Data categories collected — any answer; Data retention period — any answer. It does not apply where Age verification method: No age verification.
From when does this apply?
ISO 27566 Clause 5.3 - Privacy Characteristics applies from 15 January 2025. Its current status is: in force.
What engineering work does this imply?
Typically: Data Minimization at Collection.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations