Skip to content
IE OSC · IE-OSC-AGE-ASSURANCE

IE OSC Part B - Specific Obligations, Section 7

Implement robust age assurance mechanisms to prevent children from accessing content that may impair their development

CRITICALRequirementAge verificationBinding regulationIn forceApplies from 15 February 2024

Where this comes from

Provision: Part B - Specific Obligations, Section 7

Instrument: Ireland Online Safety Code

Citation: Online Safety Code (Coimisiun na Mean), Part B, Section 7 - Age Assurance Obligations, made under the Online Safety and Media Regulation Act 2022, Section 139K(3)

Text version: Coimisiún na Meán Online Safety Code (2024), made under the Online Safety and Media Regulation Act 2022 (irishstatutebook.ie)

Read the official text ↗

Who it applies to

Child audience (designed for OR likely accessed by children) — any one of these:

  • Service is specifically designed for children under 18
  • Service is likely to be accessed by children under 18

Remaining applicability scope — all of these:

  • Youngest user age is Under 13 or 13-15
  • Service requires/offers account registration

Scope in the source's own terms

  • Online service likely accessed by children
  • Service available in Ireland

What engineering work it implies

  • Age Gate with Self-DeclarationCovers part of it

    Simple age verification using date of birth entry with validation and session storage.

Sample acceptance criteria Landfall generates for this obligation:

  • Age gate appears before accessing age-restricted content/features
  • DOB input uses dropdowns (not free text) to reduce typos
  • System calculates age from DOB, not from user-entered age
  • Age is stored and doesn't need to be re-entered on each visit
  • Age verification cannot be bypassed by direct URL access

Evidence an auditor expects

  • Technical controlTechnical audit

    Age verification mechanism

    Implementation of age verification meeting Irish regulatory requirements

  • Assessment documentDocument review

    Age verification impact assessment

    Assessment of age verification method effectiveness and privacy impact

Questions people ask

Does IE OSC Part B - Specific Obligations, Section 7 apply to my service?
It applies when at least one of: Service is specifically designed for children under 18; Service is likely to be accessed by children under 18; and Youngest user age is Under 13 or 13-15; Service requires/offers account registration.
From when does this apply?
IE OSC Part B - Specific Obligations, Section 7 applies from 15 February 2024. Its current status is: in force.
What evidence does an auditor expect?
Age verification mechanism; Age verification impact assessment.

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