# Ageline
> Online services increasingly need to decide who can access particular content, features and experiences.

## Entries
- [Three Age Assurance Methods: Self-Declaration, Document Checks and AI Estimation](https://ageline-11l.pages.dev/three-age-assurance-methods/): Self-declaration, document checks and AI age estimation approach the age question in three different ways: asking users to state their age, examining evidence.
- [The Age Appropriate Design Code: A Plain-English Guide to Its Main Duties](https://ageline-11l.pages.dev/age-appropriate-design-code-guide/): The UK's Age Appropriate Design Code, also called the Children's Code, sets out 15 standards for online services likely to be accessed by children.
- [Why a Date-of-Birth Field Is Not an Age Gate: Design Principles for Neutral Age Screens](https://ageline-11l.pages.dev/date-of-birth-age-gate-design/): A date-of-birth field asks users to report their age; it does not independently establish that the answer is accurate.
- [App Store Age Ratings Explained: How Apple and Google Play Differ](https://ageline-11l.pages.dev/age-rating-labels-app-stores/): Apple and Google Play use different systems to describe the age suitability of apps, and their labels are not interchangeable.
- [How to Design an 18+ AI Companion Sign-Up: An Age Assurance Checklist](https://ageline-11l.pages.dev/ai-companion-sign-up-age-checklist/): An 18+ AI companion platform needs to decide what age its service requires, what level of confidence is appropriate and how that decision affects access to its.
- [Device-Level Parental Controls: What They Can and Cannot See Inside Apps](https://ageline-11l.pages.dev/device-level-parental-controls-apps/): Device-level parental controls help families manage app downloads, screen time, age-rated content and certain device activities.

## About
- [About Ageline](https://ageline-11l.pages.dev/about/): what the site covers and how entries are made

## Optional
- [RSS feed](https://ageline-11l.pages.dev/feed.xml)