10 children's privacy skills: COPPA compliance, UK AADC, age verification, parental consent, profiling limits, EdTech assessment

version
1.0.0
GitHub stars
340

Install

/plugin install children-privacy-skills@privacy-data-protection-skills

Run it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.

Contents

Discovered from source

Skills 10

Age-Gating Implementation for Online Services

Overview

Age-gating is the practice of restricting or adapting access to an online service based on the user's age. It serves as the enforcement mechanism that translates age verification results into access control decisions. Age-gating can take the form of a hard gate (complete denial of access below a specified age), a soft gate (modified experience with reduced features or enhanced protections for younger users), or an adaptive gate (progressively adjusting the service experience based on age brackets). Effective age-gating must balance child protection, user experience, accessibility, and compliance with GDPR Art. 8, COPPA, the UK Online Safety Act 2023, the EU Digital Services Act Art. 28, and the UK AADC Standard 3.

Types of Age Gates

Hard Gate — Complete Access Denial

Description: Users below a specified age are entirely prevented from accessing the service.

When to Use:

  • Age-restricted products and services regulated by law (gambling: 18+, alcohol sales: 18+/21+, adult content: 18+)
  • Services where the risk to children cannot be adequately mitigated through design measures
  • Where the business model is fundamentally incompatible with child safety (e.g., real-money trading, cryptocurrency exchanges)

Implementation Requirements:

  • Display a clear message explaining why access is denied: "This service is only for people aged 18 and older"
  • Do not collect or retain the personal data of users who are denied access (beyond what is needed for the gate)
  • Provide information about alternative age-appropriate services where possible
  • Do not use the denied user's data for any purpose including analytics

Regulatory Basis:

  • UK Gambling Act 2005: Age verification mandatory for remote gambling operators
  • UK Online Safety Act 2023 Section 11: Providers must prevent children from encountering primary priority harmful content
  • EU DSA Art. 28(1): Online platforms accessible to minors must implement age-appropriate measures

Soft Gate — Modified Experience

Description: Users identified as below a certain age are permitted access to the service but with modified features, enhanced privacy protections, or restricted content.

When to Use:

  • Services with mixed audiences (adults and children)
  • Services where children benefit from access but require additional protections
  • Educational platforms, social media platforms, and content-sharing services

Implementation:

  • Define age tiers with specific feature sets for each tier
  • Apply the UK AADC "high privacy by default" standard for child users
  • Disable features that pose elevated risks to children (direct messaging with strangers, public profiles, behavioural advertising)
  • Enable features appropriate to the age group (moderated forums, educational content, age-appropriate recommendations)

Example (BrightPath Learning):

FeatureUnder 88-1213-1516-1718+
Account creationParent-managed onlyParent-approvedIndependent with parental notificationIndependentIndependent
Profile visibilityNot applicablePrivate onlyPrivate (default), friends-only availablePrivate (default), public availableUser choice
Direct messagingDisabledPre-set messages onlyModerated text with contacts onlyUnmoderated with contactsUnrestricted
Content recommendationsCurated by editorsContent-based algorithmContent-based algorithmContent + behavioural (opt-in)Full personalisation
Data sharingNoneNoneNone (default)Optional with consentPer privacy policy
AdvertisingNoneNoneContextual onlyContextual onlyBehavioural (with consent)

Adaptive Gate — Progressive Access

Description: The service dynamically adjusts the user experience based on the estimated or verified age of the user, applying progressively fewer restrictions as the user ages.

When to Use:

  • Services designed for long-term user relationships where the user will age through multiple tiers
  • Platforms that want to provide a seamless experience without sharp access changes

Implementation:

  • Define age-linked feature unlocking schedule
  • Notify the user (and parent, if applicable) when new features become available due to ageing
  • Require re-verification of age at key threshold transitions (e.g., when a user reaches 13, 16, or 18)
  • Document the rationale for each feature unlock in terms of the child's best interests

Neutral Age Prompt Design

A neutral age prompt collects the user's age without signalling the "correct" answer or the age threshold being applied. This is critical to preventing trivial circumvention.

Design Principles

  1. Do not reveal the threshold: The prompt must not indicate what age is required. Avoid: "You must be 13 or older to use this service. Enter your date of birth." Instead: "Enter your date of birth."

  2. Use a date-of-birth field, not an age field: Date of birth is harder to game than a simple "How old are you?" field, which children can answer with any number above the threshold.

  3. Use a scrollable date picker with a neutral default: The date picker should not default to a date that suggests the "correct" answer. Default to no selection or to the current date (which would result in age 0, prompting a genuine entry).

  4. Do not provide immediate feedback: If the user enters a date that makes them below the threshold, do not immediately display "You are too young." This teaches the child to re-enter with a false date. Instead, complete the registration flow and then inform the parent.

  5. Implement cooling-off periods: If a user is denied access due to age, set a cookie or device fingerprint that prevents immediate re-attempt with a different date. A 24-hour cooling-off period is a common minimum.

  6. Do not ask leading questions: Avoid "Are you 13 or older?" which tells the child exactly what to say. Use "What year were you born?" or "Enter your date of birth."

ICO Guidance on Neutral Prompts

The ICO's Age Assurance guidance (published alongside the AADC) states: "If you use age self-declaration you should not design it in a way that encourages, or makes it easy for, a child to input a false age. Your age gate should not present the age required, or make it obvious what a child should enter to circumvent the gate."

COPPA FTC Guidance

The FTC has stated in enforcement actions (e.g., Musical.ly/TikTok 2019) that age gates must be designed so that "the age screen does not encourage the child to enter a false age." The FTC views a non-neutral age gate as evidence of actual knowledge that the service is collecting data from children.

Circumvention Prevention

Technical Measures

MeasureDescriptionEffectiveness
Cookie-based lockoutSet a persistent cookie when a user fails the age gate, preventing re-attempt for 24-72 hoursModerate — cookies can be cleared
Device fingerprintingUse browser/device characteristics to identify re-attempts from the same deviceModerate-High — more difficult to circumvent than cookies
IP-based rate limitingLimit the number of age gate attempts from the same IP address within a time windowLow — IP addresses change; shared IPs (schools) create false positives
Email verification loopRequire email verification before account creation; underage users who fail the gate cannot reuse the same emailModerate — children can create new email addresses
Progressive escalationAfter a failed self-declaration, require a higher-assurance verification method for subsequent attemptsHigh — escalates the difficulty of circumvention
Parental consent as backstopEven if a child circumvents the gate, parental consent is required before meaningful data collection beginsHigh — shifts the verification burden to the parent

Organisational Measures

  1. Staff training: Customer support staff must be trained to handle age-related inquiries without revealing the age threshold
  2. Monitoring: Regularly analyse registration data for patterns suggesting circumvention (e.g., disproportionate number of users declaring exactly the minimum age)
  3. Complaint handling: Establish a process for parents to report that their child has circumvented the age gate
  4. Periodic re-verification: At key milestones (annual account review, feature unlock), re-verify the user's age

Re-Verification Triggers

Age gates should not be a one-time check. The following events should trigger re-verification:

TriggerActionRationale
User reaches a new age tier (e.g., turns 13, 16, 18)Confirm age and unlock/modify featuresEnsures age-appropriate experience as user matures
Account recoveryVerify age before restoring accessPrevents account sharing or transfer to a younger user
Request to change date of birthRequire parental verification for changes to age dataPrevents children from aging themselves up
Suspicious activity patternsEscalate to higher-assurance verificationBehavioural signals inconsistent with declared age
Annual account reviewConfirm continued accuracy of age declarationRegular hygiene check
Feature upgrade requestVerify age if the feature is restricted to older usersPrevents premature access to age-restricted features

BrightPath Learning Inc. — Age-Gating Architecture

Registration Flow

User visits brightpathlearning.eu
│
├─ "Enter your date of birth" [scrollable date picker, no default selection]
│
├─ Age calculated from DOB and current date
│
├─ Age >= applicable threshold (country-dependent, 13-16)?
│  ├─ YES → Standard registration flow for independent user
│  │         ├─ Verification: email confirmation
│  │         └─ Experience: Standard features with AADC-compliant defaults
│  │
│  └─ NO → Child registration flow
│           ├─ "Please ask a parent or guardian to help you sign up"
│           ├─ Child enters parent's email address
│           ├─ Parent receives direct notice with consent request
│           ├─ Parent completes verification (credit card micro-transaction)
│           ├─ Parent reviews and approves processing purposes
│           └─ Child account created with age-appropriate restrictions
│
├─ Age < 8?
│  ├─ YES → Parent-managed-only account
│  │         ├─ Parent sets up account entirely
│  │         ├─ Child cannot modify settings
│  │         └─ Simplified interface (illustrated, limited text)
│  │
│  └─ NO → Child-managed account with parental oversight
│           ├─ Child can navigate the app independently
│           ├─ Parent dashboard shows activity and can modify settings
│           └─ Age-appropriate interface (text with icons)
│
└─ User enters DOB indicating age < 5?
   └─ "This app is designed for children aged 5 and older.
       Please come back when you're a bit older!"
       [No data retained from this interaction]

Circumvention Prevention Implementation

  1. Cookie lockout: If a user's entered DOB results in age below 5, a secure cookie is set preventing re-attempt for 48 hours
  2. No threshold exposure: The app never states the minimum age. The registration flow adapts seamlessly based on age
  3. Parental backstop: Even if a child enters a false DOB to skip the consent flow, the service collects only minimal data until email verification is completed. Without verified email, the account is limited to a demo mode with no persistent data
  4. Anomaly detection: Weekly automated analysis of registration data flags accounts where the declared DOB is exactly at the threshold (e.g., exactly 13 years old), prompting manual review

Regulatory Compliance Matrix

RequirementGDPR Art. 8COPPAUK AADC Std 3UK OSAEU DSA Art. 28
Age screening requiredYesYesYesYesYes
Neutral prompt requiredImpliedFTC guidanceICO guidanceOfcom codesImplied
Parental consent below thresholdYesYesRecommendedN/AN/A
Hard gate for restricted contentNoNoNoYes (harmful content)Implied
Soft gate for mixed servicesImpliedImpliedYesYesYes
Re-verification requiredImpliedImpliedRecommendedImpliedImplied
Data minimisation at gateArt. 5(1)(c)312.7Standard 8ImpliedImplied

Common Compliance Failures

  1. Non-neutral age gate: Displaying the minimum age requirement or using "Are you over 13?" prompts that teach children to lie
  2. No circumvention prevention: Allowing unlimited re-attempts with different dates of birth
  3. Collecting data before gating: Running analytics trackers, setting advertising cookies, or collecting device identifiers before the age gate is completed
  4. Hard gate when soft gate is appropriate: Denying all children access to a service that could safely serve children with modified features
  5. No re-verification: Treating the initial age declaration as permanent without any mechanism for ongoing verification
  6. Age gate as compliance theatre: Implementing an easily circumvented age gate and then treating it as full compliance with COPPA or GDPR Art. 8

Integration Points

  • Age Verification Methods: Age-gating is the enforcement layer that acts on the results of age verification or estimation
  • GDPR Parental Consent: The age gate determines whether parental consent is required and routes the user accordingly
  • UK AADC Implementation: AADC Standard 3 requires age-appropriate application, which is implemented through age-gating
  • Children's Privacy Notice: The age gate result determines which privacy notice version is displayed
  • Children's Data Minimisation: Data collection at and before the age gate must comply with data minimisation principles

Age Verification and Estimation Methods

Overview

Age verification and age estimation are distinct but complementary approaches to determining whether a user is a child for the purpose of applying appropriate data protection safeguards. Age verification provides a definitive confirmation of age through documentary or transactional evidence. Age estimation provides a probabilistic assessment of age using technological methods such as facial analysis, behavioural analysis, or device signals. The selection of an appropriate method requires balancing accuracy, privacy impact, accessibility, and proportionality. This skill covers the full spectrum of available methods, their regulatory context under the GDPR, UK AADC, COPPA, and emerging legislation such as the EU Digital Services Act (DSA) and the UK Online Safety Act 2023, and provides implementation guidance based on ICO and CNIL recommendations.

Regulatory Context

GDPR Article 8(2)

"The controller shall make reasonable efforts to verify in such cases that consent is given or authorised by the holder of parental responsibility over the child, taking into consideration available technology."

The "reasonable efforts" standard is context-dependent. The EDPB has not prescribed specific technologies but expects controllers to adopt verification proportionate to the risk of the processing.

UK AADC Standard 3 — Age-Appropriate Application

"Take a risk-based approach to recognising the age of individual users and ensure you effectively apply the standards in this code to child users." The ICO guidance states that the level of certainty required depends on the risks to children from the processing. Higher risks demand more robust age assurance methods.

UK Online Safety Act 2023

Section 11(3) requires providers of regulated user-to-user services and search services to use "proportionate systems or processes" designed to prevent children from encountering primary priority content that is harmful to children. Ofcom's codes of practice specify age verification as a recommended measure for pornographic content and age estimation for broader content categories.

EU Digital Services Act — Article 28

Providers of online platforms accessible to minors must put in place appropriate and proportionate measures to ensure a high level of privacy, safety, and security of minors on their service. This includes age verification for services with content restrictions.

France — Loi SREN (2024)

France's law to regulate and secure the digital space requires age verification for access to pornographic websites, mandating technical solutions certified by CNIL that verify age without identifying the user. The CNIL-approved reference system requires a "double-blind" architecture where the identity verification provider and the content provider cannot link the user's identity to the content access.

Age Verification Methods

Method 1: Document-Based Verification

Description: User uploads or presents a government-issued identity document (passport, national ID card, driver's licence) which is verified against document security features and optionally against government databases.

Technical Implementation:

  • Optical Character Recognition (OCR) extracts date of birth and document details
  • Machine Readable Zone (MRZ) validation for passports and ID cards conforming to ICAO Doc 9303
  • Document authenticity checks: hologram detection, microprint analysis, UV feature verification (for physical presentation)
  • Optional: NFC chip reading for ePassports conforming to ICAO 9303 Part 10
  • Optional: Liveness check to confirm the person presenting the document matches the photo

Accuracy: Very high (99%+ when combined with liveness detection)

Privacy Considerations:

  • Collects highly sensitive identity data (ID number, full name, address, photo)
  • Data minimisation: extract only date of birth, discard full document image immediately after verification
  • Storage: do not retain the document image or full identity data; retain only a binary age-confirmed flag and a verification token
  • DPIA required under Art. 35 due to large-scale processing of identity documents

Accessibility: Excludes individuals without government-issued ID (estimated 1.5 million UK adults lack photo ID per Electoral Commission 2021 data). Not appropriate as the sole method.

Use Cases: Age-restricted content (gambling, alcohol, adult content), high-risk services

Method 2: Facial Age Estimation (AI-Based)

Description: Machine learning models estimate a user's age from a facial image captured by the device camera. The estimation provides an age range (e.g., "over 18" or "13-17") rather than a precise age.

Technical Implementation:

  • Convolutional Neural Network (CNN) trained on large-scale age-labelled facial datasets
  • Real-time processing on-device (edge computing) to avoid transmitting facial images to servers
  • Liveness detection to prevent spoofing via photographs or video replay
  • Age estimation outputs a confidence interval (e.g., estimated age 14 +/- 2 years with 95% confidence)
  • The facial image is processed in volatile memory and not stored

Accuracy: Mean Absolute Error (MAE) of 1.5-3 years depending on the model and demographic. Accuracy varies by: age group (lower accuracy for children under 8 and adults over 65), ethnicity (documented bias in some commercial systems), lighting and image quality.

Privacy Considerations:

  • Facial images constitute biometric data under GDPR Art. 4(14) and Art. 9(1) if used for unique identification
  • When used solely for age estimation (not identification), the processing may not constitute "biometric data for the purpose of uniquely identifying" under Art. 9 — the ICO has confirmed this interpretation in its Children's Code guidance
  • On-device processing with no server transmission significantly reduces privacy risk
  • DPIA is recommended even when processing is on-device due to sensitivity of facial data

Key Providers: Yoti (Age Estimation), VerifyMyAge (EstimateMyAge), Privately SA

ICO Position: The ICO has stated that facial age estimation technology that processes images locally, does not store images, and does not identify the individual can be a proportionate method for age assurance. The ICO conducted a joint audit with the Australian Information Commissioner (OAIC) of Yoti's age estimation technology in 2022 and concluded it met data protection requirements when implemented with appropriate safeguards.

Method 3: Digital Identity Verification

Description: User authenticates through a trusted digital identity provider (eID, digital wallet, Open Banking) that confirms age without disclosing full identity to the relying party (service provider).

Technical Implementation:

  • OpenID Connect for Identity Assurance (OIDC4IDA) protocol for attribute-based verification
  • The identity provider confirms a specific attribute (e.g., "is_over_18": true) via a signed assertion
  • The relying party receives only the age attribute, not the user's name, address, or other identity data
  • EU Digital Identity Wallet (eIDAS 2.0 Regulation, expected 2026 rollout) will enable selective attribute disclosure
  • UK Digital Identity and Attributes Trust Framework (DIATF) provides a certification scheme for identity providers

Accuracy: Very high (dependent on the identity provider's verification of the underlying identity)

Privacy Considerations:

  • Minimal data disclosure: only the specific age attribute is shared
  • The identity provider knows the user's identity but not which service they are accessing (if double-blind architecture is used)
  • The service provider knows the user is accessing their service but not their full identity
  • Aligns with CNIL's recommended "double-blind" approach for age verification

Use Cases: EU/EEA services preparing for eIDAS 2.0 Digital Identity Wallet; UK services using DIATF-certified providers

Method 4: Self-Declaration with Risk Mitigation

Description: User declares their age through a date-of-birth field or age-range selector. The declaration is treated as the baseline, supplemented by risk-based measures to detect false declarations.

Technical Implementation:

  • Neutral age prompt: "What is your date of birth?" with a scrollable date picker (no calendar default to current date)
  • No indication of the "correct" answer or the age threshold being applied
  • Behavioural signals that may indicate false declaration: immediate re-entry with a different date, cookie evidence of prior declaration, typing speed patterns inconsistent with the declared age
  • If false declaration is suspected, escalate to a higher-assurance verification method

Accuracy: Low as a standalone method. Children commonly misrepresent their age online. Ofcom's 2023 research found that 33% of UK 8-17 year olds have a social media profile despite being below the platform's minimum age.

Privacy Considerations: Minimal data collection (only declared date of birth). No biometric processing. No identity document collection.

Use Cases: Low-risk services as a first-line screening measure, always combined with additional safeguards for medium and high-risk services

Method 5: Credit Card or Payment Verification

Description: User's age is inferred from possession of a credit card (typically issued only to adults 18+) through a monetary transaction.

Technical Implementation:

  • Micro-transaction (USD/EUR/GBP 0.50) charged and refunded within 48 hours
  • The card must be a credit card (not a debit card or prepaid card, which may be issued to minors)
  • Transaction notification sent to the cardholder provides an audit trail
  • Some implementations use 3D Secure (3DS2) authentication for additional identity assurance

Accuracy: Moderate. Establishes that the person has access to a credit card, which correlates with being over 18. Does not verify the specific age of the cardholder. Children may use a parent's card.

Privacy Considerations: Payment card data is subject to PCI DSS requirements. The service should not store full card details. Only the transaction confirmation and a binary "has credit card" flag should be retained.

Method 6: Mobile Network Operator (MNO) Verification

Description: The mobile network operator confirms the user's age bracket based on the subscriber information associated with the SIM/eSIM, without disclosing the user's identity to the requesting service.

Technical Implementation:

  • API call to MNO (via aggregator such as GBG, boku, or Sinch) with the user's mobile number
  • MNO returns a binary response (e.g., "is_over_18": true/false) without disclosing identity
  • Relies on the age data the MNO collected during subscriber registration (ID check at point of sale)

Accuracy: High for determining over/under 18, since MNO registration typically involves ID verification. Lower certainty for granular age (e.g., distinguishing 13 from 15) as MNOs may not record precise birth dates.

Privacy Considerations: The service learns only the age bracket. The MNO learns which service the user is accessing (unless intermediary architecture prevents this). DPIA recommended for the MNO's processing.

Accuracy vs. Privacy Tradeoff Matrix

MethodAccuracyPrivacy ImpactProportionate For
Document-BasedVery HighVery High (ID collection)Age-restricted products (gambling, alcohol)
Facial Age EstimationHigh (MAE 1.5-3y)Medium (on-device) to High (server-side)General online services, social media
Digital IdentityVery HighLow (attribute-only disclosure)Any service; best privacy-accuracy balance
Self-DeclarationLowVery LowInitial screening; low-risk services only
Credit CardModerateMedium (payment data)Supplementary verification for parental consent
MNO VerificationHighLow-MediumMobile-first services; supplementary check

Risk-Based Selection Framework

Step 1: Classify Service Risk Level

Risk LevelCriteriaExamples
HighDirect messaging with strangers, user-generated content visible to strangers, age-restricted content, monetisation features targeting childrenSocial media, dating apps, gambling, online marketplaces
MediumContent personalisation, in-app purchases, community features with moderation, educational services with profilingEdTech platforms, gaming, streaming services
LowStatic content delivery, no social features, no data sharing, no profilingInformational websites, single-player offline games

Step 2: Select Minimum Verification Level

Risk LevelMinimum VerificationRecommended Approach
HighDocument-Based OR Facial Estimation + LivenessDocument-based with digital identity as alternative
MediumFacial Age Estimation (on-device) OR Self-Declaration + Risk SignalsFacial age estimation with escalation path
LowSelf-Declaration + Neutral PromptSelf-declaration with cookie-based re-entry detection

Step 3: Apply Proportionality Test

For each selected method, document:

  1. Why is this method necessary to protect children?
  2. Could a less intrusive method achieve the same level of protection?
  3. What safeguards minimise the privacy impact of the method (data minimisation, on-device processing, immediate deletion)?
  4. How does this method account for accessibility (users without ID, users with disabilities)?

BrightPath Learning Inc. — Age Verification Implementation

BrightPath Learning Inc. operates an educational platform classified as Medium risk (educational content with progress tracking and personalisation, no social features with strangers).

Implemented Approach: Layered Verification

  1. Layer 1 — Self-Declaration: During registration, a neutral date-of-birth prompt with scrollable date picker. Determines initial routing (child vs. adult account).
  2. Layer 2 — Parental Account: For users declaring an age below the applicable threshold, the parental consent flow is triggered. The parent creates an account and verifies via credit card micro-transaction.
  3. Layer 3 — Anomaly Detection: Behavioural signals monitored for inconsistencies: IP address mismatch between child and parent accounts, identical email domains suggesting self-verification, multiple child accounts from the same parent in short succession.
  4. Layer 4 — Escalation: If anomalies are detected, the parent is asked to complete a video verification call or upload a government-issued ID (with immediate deletion after verification).

Data Retention for Age Verification:

  • Self-declared date of birth: retained for account lifecycle
  • Credit card transaction record: retained for 90 days (reconciliation), then deleted; only "parent verified" flag retained
  • Government ID image: processed in memory, not stored; verification outcome retained
  • Facial images: not collected (BrightPath does not use facial age estimation)

Emerging Standards and Legislation

IEEE 2089.1-2024 — Age-Appropriate Digital Services Framework

Published standard providing a framework for implementing age-appropriate design in digital services, including guidance on age assurance methods and their application across different risk contexts.

ISO/IEC 27566 — Age Assurance Systems (Under Development)

Working draft standard for age assurance systems covering both age verification and age estimation. Addresses accuracy, privacy, accessibility, interoperability, and governance requirements.

EU Digital Identity Wallet (eIDAS 2.0)

The revised eIDAS Regulation mandates that EU Member States offer digital identity wallets to citizens by 2026. The wallet will support selective attribute disclosure, enabling users to prove they are over a specific age without revealing their full identity or date of birth. This will become the preferred age verification method for EU services.

Integration Points

  • GDPR Parental Consent: Age verification is a prerequisite for determining whether parental consent is required under Art. 8
  • UK AADC Implementation: AADC Standard 3 requires risk-proportionate age assurance
  • Age-Gating Services: Age verification results drive the age-gating decision (admit, redirect, or block)
  • COPPA Compliance: COPPA requires age screening as part of the parental consent flow
  • Children's Privacy Notice: The age verification result determines which version of the privacy notice to display (child-friendly vs. standard)

Children's Data Minimisation and Retention Limits

Overview

Data minimisation for children's data requires a stricter interpretation of GDPR Article 5(1)(c) ("adequate, relevant and limited to what is necessary") than the standard adult context. Recital 38 states that children merit specific protection with regard to their personal data, as they may be less aware of the risks, consequences, and safeguards concerned and their rights in relation to the processing of personal data. The UK AADC Standard 8 explicitly requires that services collect and retain "only the minimum amount of personal data needed to provide the elements of the service in which a child is actively and knowingly engaged." COPPA Section 312.7 prohibits conditioning a child's participation on the collection of more personal information than is reasonably necessary. This skill provides a comprehensive framework for applying these heightened standards.

Legal Framework

GDPR Article 5(1)(c) — Data Minimisation Principle

"Personal data shall be adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed."

When applied to children's data, "necessary" is interpreted strictly. The EDPB has confirmed that the vulnerability of children as data subjects (WP248rev.01 Criterion 7) elevates the data minimisation obligation.

GDPR Article 5(1)(e) — Storage Limitation Principle

"Personal data shall be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed."

For children's data, retention periods should be shorter than for adult data given that: (a) the purposes of processing often have a shorter useful life for children (e.g., educational progress in a specific grade), (b) the risk of harm from data exposure increases with retention duration, and (c) the child may not have meaningfully consented to long-term retention.

GDPR Recital 38 — Specific Protection for Children

"Children merit specific protection with regard to their personal data, as they may be less aware of the risks, consequences and safeguards concerned and their rights in relation to the processing of personal data. Such specific protection should, in particular, apply to the use of personal data of children for the purposes of marketing or creating personality or user profiles and the collection of personal data with regard to children when using services offered directly to children."

UK AADC Standard 8 — Data Minimisation

"Collect and retain only the minimum amount of personal data you need to provide the elements of your service in which a child is actively and knowingly engaged. Give children separate choices over which elements they wish to activate."

Key ICO interpretations:

  • "Actively and knowingly engaged" means the child is intentionally using a specific feature, not passively generating data through background collection
  • "Separate choices" means children must be able to use core service features without being forced to activate data-intensive optional features
  • Background data collection (location, microphone, contacts, gyroscope) is prohibited unless the child actively triggers a feature requiring it

COPPA Section 312.7 — Data Minimisation

"An operator is prohibited from conditioning a child's participation in a game, the offering of a prize, or another activity on the child disclosing more personal information than is reasonably necessary to participate in such activity."

Strict Necessity Test

For each data element collected from a child, the controller must apply the Strict Necessity Test — a more demanding evaluation than the standard proportionality assessment used for adult data.

Test Questions

#QuestionPass Criteria
1Is this data element required for the specific feature the child is actively using?The feature cannot function without this specific data element
2Could the feature work with less precise data?No less granular alternative exists (e.g., age range instead of exact DOB, city instead of precise location)
3Could the feature work with anonymised or pseudonymised data?Anonymisation or pseudonymisation would make the feature non-functional
4Is this data element collected for the child's benefit or the controller's benefit?Primary beneficiary must be the child; controller benefit alone is insufficient
5Would a reasonable parent expect this data to be collected for this feature?The collection aligns with parental expectations for the service
6Is the data retained only for the duration the feature is in active use?Data is deleted when the feature session ends or the shortest defensible retention period expires

Application to Common Data Categories

Data CategoryTypical JustificationStrict Necessity Outcome
Full nameAccount identificationMinimise to first name or username only. Full legal name needed only for parental verification.
Exact date of birthAge verificationCollect for age gate, then retain only age band (e.g., "10-12") or a boolean "is_under_threshold". Do not retain exact DOB unless legally required.
Email addressAccount recovery, notificationsFor children under the applicable consent threshold, collect only the parent's email. Child email collected only if the child is above the consent threshold.
Precise geolocationContent localisationCountry or region-level derivation from IP sufficient for localisation. Precise GPS never collected from children unless the feature specifically requires it (e.g., emergency location service) and the child actively triggers it.
Device identifiers (IDFA, GAID)Analytics, advertisingNever collected for advertising. Collected for analytics only if anonymised at collection point. Use session-based or first-party identifiers instead.
Photos/videos/audioProfile picture, content creationProfile: use pre-set avatars, not photo upload. Content creation: process in session, do not store server-side unless the child explicitly saves. Delete on session end.
Browsing historyPersonalisationDo not retain browsing history for children. Use session-only context for recommendations.
Contact listSocial featuresNever access or upload the child's contact list. Use invite codes or usernames instead.
Purchase historyTransaction recordsRetain for legal compliance (tax, consumer protection) only. Minimise to transaction ID and amount, not item details.

Retention Period Framework

Children's data must be subject to shorter retention periods than adult data. The following framework establishes maximum retention periods for common categories.

Retention Schedule

Data CategoryMaximum RetentionJustificationDeletion Method
Age verification data (DOB, verification outcome)Duration of account + 30 daysRequired to maintain age-appropriate experienceAutomated purge on account deletion + 30 days
Account data (name, username, parent email)Duration of account + 30 daysRequired for service delivery and parental oversightAutomated purge on account deletion + 30 days
Learning/activity progressDuration of account or academic year, whichever is shorterEducational purpose expires at end of learning periodParent-triggered or automated end-of-year deletion
Session data (pages viewed, features used)30 daysService improvement analyticsRolling 30-day automated deletion
Content created by child (drawings, text, projects)Duration of accountCreated by the child for their own useReturned to parent/child on account deletion
Communication data (messages within platform)90 daysSafety moderation and abuse preventionRolling 90-day automated deletion
Error/crash logs7 daysTechnical debuggingRolling 7-day automated deletion
Parental consent recordsDuration of account + 6 yearsLegal compliance (statute of limitations for GDPR claims)Automated purge 6 years after account deletion
Parental verification data (credit card, ID)Verification outcome retained; source documents deleted within 48 hoursVerification purpose fulfilled immediatelyImmediate deletion of source; outcome flag retained

End-of-Academic-Year Deletion

For educational platforms, the end of the academic year represents a natural data lifecycle milestone. BrightPath Learning implements the following end-of-year protocol:

  1. 30 days before academic year end: Parent receives notification that learning data will be archived
  2. End of academic year: Learning progress data is exported to a parent-downloadable report (PDF)
  3. 14 days after year end: If parent has not requested retention, granular activity data is deleted; only aggregate progress scores are retained for the next year's placement
  4. 60 days after year end: Aggregate scores deleted unless the child continues to the next year's service

Parental Dashboard Design

The parental dashboard is the primary mechanism for parental oversight and control over children's data. It must provide meaningful transparency and actionable controls.

Required Dashboard Features

FeatureDescriptionGDPR Basis
Data inventoryVisual display of all personal data held about the child, organised by categoryArt. 15 (access right, exercised by parent under Art. 8)
Purpose displayFor each data category, show the specific purpose and lawful basisArt. 13(1)(c) transparency
Consent controlsPer-purpose toggles to grant or withdraw consentArt. 7(3) withdrawal mechanism
Data downloadOne-click export of all child's data in machine-readable format (JSON, CSV)Art. 20 portability (exercised by parent)
Data deletionOne-click account and data deletion with confirmationArt. 17 erasure (exercised by parent)
Activity logSummary of child's recent activity on the platform (features used, time spent)AADC Standard 11 (parental controls)
Privacy settingsControls for profile visibility, data sharing, communication featuresAADC Standard 7 (default settings)
Notification preferencesControl over what notifications the child receivesAADC Standard 13 (nudge techniques)
Child age displayShows the child's current age and the date when they will reach the next age thresholdAADC Standard 3 (age-appropriate application)

BrightPath Learning — Dashboard Implementation

┌─────────────────────────────────────────────────────────┐
│  BrightPath Learning — Parent Dashboard                 │
│  Child: Alex (Age 11, France — threshold: 15)           │
│  Account created: 2025-09-01                            │
│  Next age review: 2026-09-01 (age 12)                   │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  DATA WE HOLD                                           │
│  ┌──────────────────┬─────────────────┬──────────────┐  │
│  │ Category         │ Purpose         │ Status       │  │
│  ├──────────────────┼─────────────────┼──────────────┤  │
│  │ First name       │ Account ID      │ Required     │  │
│  │ Age band (10-12) │ Content level   │ Required     │  │
│  │ Learning scores  │ Progress track  │ ✓ Consented  │  │
│  │ Game activity    │ Recommendations │ ✗ Not active │  │
│  └──────────────────┴─────────────────┴──────────────┘  │
│                                                         │
│  PRIVACY CONTROLS                                       │
│  [✓] Share progress reports with me (parent)            │
│  [ ] Allow content-based recommendations                │
│  [✓] Show learning badges on Alex's profile             │
│                                                         │
│  ACTIONS                                                │
│  [Download Alex's data]  [Delete Alex's account]        │
│  [View activity log]     [Contact DPO]                  │
│                                                         │
│  ACTIVITY THIS WEEK                                     │
│  Mon: 25 min — Maths Level 3                            │
│  Tue: 30 min — Reading Comprehension                    │
│  Wed: 15 min — Science Quiz                             │
│  Total: 1h 10min                                        │
│                                                         │
│  Alex will reach the French consent threshold (15)      │
│  on approximately 2029-06-15. At that point, consent    │
│  authority will transfer to Alex.                       │
└─────────────────────────────────────────────────────────┘

Automated Deletion Implementation

Technical Architecture

  1. Retention metadata: Every data record includes a retention_category field mapped to the retention schedule and an expires_at timestamp
  2. Deletion scheduler: A daily batch job identifies all records where expires_at < current_timestamp and executes deletion
  3. Cascade deletion: Account deletion triggers cascade deletion across all related tables (activity logs, content, communications, consent records subject to their own retention schedule)
  4. Deletion verification: Post-deletion audit confirms that records are removed from primary storage, backup systems, and any caches
  5. Backup purge: Backups containing children's data are subject to a maximum 30-day retention cycle. Backup restoration procedures include a re-deletion step for expired children's data.

Deletion Logging

Every deletion event is logged for accountability:

{
  "deletion_id": "DEL-2026-0047821",
  "trigger": "automated_retention_expiry",
  "data_category": "session_data",
  "child_identifier": "child_bp_8f3a2d",
  "records_deleted": 847,
  "deletion_timestamp": "2026-03-14T02:00:00Z",
  "deletion_scope": "primary_database, elasticsearch_index, redis_cache",
  "backup_purge_scheduled": "2026-04-13T02:00:00Z",
  "verified_by": "automated_verification_check"
}

Common Compliance Failures

  1. Adult-equivalent retention: Applying the same retention periods to children's data as adult data, without justification for why shorter periods are not feasible
  2. Indefinite retention until deletion request: Retaining children's data indefinitely unless a parent specifically requests deletion violates Art. 5(1)(e) storage limitation
  3. Background data collection: Collecting device identifiers, location, accelerometer, or microphone data in the background without the child actively using a feature that requires it
  4. Contact list access: Requesting access to the child's device contact list for "find friends" features without strict necessity
  5. No parental dashboard: Failing to provide parents with a meaningful mechanism to view, control, and delete their child's data
  6. Backup retention gap: Deleting data from production systems but retaining it indefinitely in backups

Enforcement Precedents

  • TikTok (DPC Ireland, 2023): EUR 345 million fine included findings on excessive data collection from children, including default public profiles exposing children's content to all users, violating Art. 5(1)(c) data minimisation.
  • YouTube/Google (FTC, 2019): USD 170 million settlement for collecting persistent identifiers from child-directed channel viewers for advertising purposes — data not necessary for the service the child was using.
  • Epic Games/Fortnite (FTC, 2022): USD 275 million for collecting personal information from children beyond what was necessary, including enabling real-time voice communications by default.

Integration Points

  • GDPR Parental Consent: Parental consent scope should be limited to data collection justified by the necessity test — parents should not be asked to consent to unnecessary collection
  • UK AADC Implementation: AADC Standard 8 is the primary operational standard for children's data minimisation in the UK
  • Children's Profiling Limits: Data minimisation directly limits the data available for profiling, reinforcing AADC Standard 12 restrictions
  • Children's Deletion Requests: The retention framework defines what data exists to be deleted and when automatic deletion occurs
  • EdTech Privacy Assessment: Educational platforms must balance data minimisation with legitimate educational record-keeping needs

Managing Deletion Requests for Children's Data

Overview

Deletion of children's personal data operates under heightened obligations compared to adult data deletion. Under GDPR Article 17, the right to erasure applies with particular force when data was collected from a child — Article 17(1)(f) explicitly creates a right to erasure where personal data has been collected in relation to the offer of information society services to a child under Article 8(1). COPPA Section 312.6 requires operators to provide parents with the ability to review and delete personal information collected from their child. The UK AADC Standard 15 requires prominent and accessible tools to help children exercise their data protection rights. This skill provides a comprehensive framework for processing deletion requests involving children's data, including the complex questions of who can request deletion, verification procedures, scope determination, and third-party notification.

Legal Framework

GDPR Article 17(1)(f) — Right to Erasure for Children's Data

"The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay where [...] the personal data have been collected in relation to the offer of information society services directly to a child referred to in Article 8(1)."

This ground for erasure is distinct from the other Art. 17(1) grounds because:

  • It does not require that the original lawful basis has been withdrawn (unlike Art. 17(1)(b) consent withdrawal)
  • It does not require that the data is no longer necessary (unlike Art. 17(1)(a))
  • It applies specifically because the data was collected from a child, regardless of whether the data subject is still a child at the time of the request
  • The CJEU has confirmed in Case C-131/12 (Google Spain) that the right to erasure is especially important where the data was collected when the data subject was a minor

GDPR Article 17(2) — Third-Party Notification

"Where the controller has made the personal data public, the controller shall, taking account of available technology and the cost of implementation, take reasonable steps, including technical measures, to inform controllers which are processing the personal data that the data subject has requested the erasure [...] of any links to, or copy or replication of, those personal data."

GDPR Article 12(3) — Response Timeline

"The controller shall provide information on action taken on a request under Articles 15 to 22 to the data subject without undue delay and in any event within one month of receipt of the request."

COPPA Section 312.6 — Parental Access and Deletion Rights

  • 312.6(a): Operator must provide a parent, upon request, with a description of the specific types of personal information collected from the child, and the opportunity to refuse to permit the operator's further use or future online collection of personal information from that child, and to direct the operator to delete the personal information collected from that child
  • 312.6(b): The operator must delete the child's personal information within a reasonable time after receiving the parental request

UK AADC Standard 15 — Online Tools

"Provide prominent and accessible tools to help children exercise their data protection rights and report concerns."

Who Can Request Deletion

Parental-Initiated Deletion

Applicable When: The child is below the age at which they can independently exercise data protection rights.

JurisdictionAge Below Which Parent ActsLegal Basis
GDPR (default)16 (or national threshold 13-16)Art. 8(1) — parental consent grounds extend to parental exercise of rights
UK13 (DPA 2018 Section 9)ICO guidance: parent exercises rights for children who cannot understand the implications
US (COPPA)1316 CFR 312.6 — explicit parental right to direct deletion
France15Loi Informatique et Libertes Art. 45
Germany16GDPR default
Spain14Organic Law 3/2018 Art. 7

Verification Requirements:

  • Verify that the requester is the parent or legal guardian of the child
  • Verification methods (proportionate to risk): match against existing parental account, email verification to registered parent email, knowledge-based questions, government ID (for high-risk scenarios)
  • Verify the identity of the child whose data is to be deleted (match against account records)

Child-Initiated Deletion

Applicable When: The child has reached sufficient maturity to understand and exercise their data protection rights independently.

Age of Capacity Assessment:

The capacity of a child to independently exercise data protection rights is not determined solely by the Art. 8 age threshold. The ICO has stated that a child who is competent to understand their rights may exercise them independently, regardless of the Art. 8 threshold. This is analogous to the Gillick competency principle in UK common law.

ScenarioWho InitiatesCapacity Assessment
Child aged 10 requests deletionParent must submit the requestChild below Art. 8 threshold in all jurisdictions; lacks capacity
Child aged 14 in Belgium (threshold 13) requests deletionChild can submit independentlyAbove national threshold; presumed competent
Child aged 14 in Germany (threshold 16) requests deletionDepends on maturity assessmentBelow national threshold; controller may accept if child demonstrates understanding
Former child (now 18) requests deletion of childhood dataFormer child submits independentlyAdult; full capacity; Art. 17(1)(f) explicitly protects this scenario

Former Child (Adult) Requesting Deletion of Childhood Data

Art. 17(1)(f) does not require the data subject to still be a child at the time of the request. An adult may request deletion of personal data collected when they were a child. This is particularly relevant for:

  • Social media posts from adolescence
  • Educational records from childhood
  • Health data from paediatric treatment
  • Photos and videos uploaded by the child or their parents during childhood

The GDPR explicitly supports this by creating Art. 17(1)(f) as a standalone ground — the passage of time does not diminish the right.

Deletion Request Processing Workflow

Step 1: Receive and Log Request

Request received
│
├─ Channel: email / parental dashboard / in-app tool / postal mail
├─ Requester identity: parent / child / former child (adult)
├─ Child identifier: account ID / name / email
├─ Scope requested: full account deletion / specific data categories
├─ Timestamp: [logged automatically]
├─ Reference number assigned: DEL-CHILD-[YEAR]-[SEQ]
│
└─ Acknowledgement sent within 48 hours

Step 2: Verify Requester Identity and Authority

RequesterVerification MethodEscalation
Parent (existing account)Match request email against registered parent email + security questionIf match fails, request government ID
Parent (no existing account)Request proof of parental relationship (birth certificate or equivalent) + matching identificationManual review by DPO
Child (above threshold, existing account)Match request against child's registered email + account securityIf match fails, involve parent
Child (below threshold)Redirect to parent; inform child their parent can submit the requestProvide parent contact mechanism
Former child (adult)Standard identity verification (email + security question or ID)Manual review if account is historical

Step 3: Determine Scope of Deletion

Scope ElementDefault InclusionExceptions
Account profile data (name, DOB, email)YESNone
Activity/usage logsYESAnonymised aggregate retained for analytics
Content created by child (posts, projects, uploads)YESOffer download before deletion
Communication records (messages, chats)YESMay retain if needed for ongoing safeguarding investigation
Parental consent recordsRETAINED for 6 yearsLegal compliance: statute of limitations for GDPR enforcement
Financial transaction recordsRETAINED for applicable periodLegal compliance: tax and accounting obligations
Safety/moderation logsRETAINED if active investigationSafeguarding obligation override per Art. 17(3)(d)
Backup copiesYES (scheduled purge)Deleted within backup rotation cycle (max 30 days)
Third-party copiesNOTIFIED for deletionArt. 17(2) obligation to inform third-party controllers

Step 4: Execute Deletion

Timeline: Within one month of verified request (Art. 12(3)). Extension of up to two additional months permitted for complex requests, with notification to the requester within the initial one-month period.

Technical Deletion Process:

  1. Primary database: Execute DELETE operations across all tables containing the child's personal data
  2. Search indices: Remove the child's data from Elasticsearch, Solr, or equivalent search indices
  3. Caches: Invalidate all cached entries containing the child's data (Redis, CDN, application cache)
  4. File storage: Delete uploaded files (photos, documents, audio) from primary storage (S3, Azure Blob, GCS)
  5. Analytics databases: Remove or anonymise records in analytics systems (BigQuery, Redshift, Snowflake)
  6. Logs: Purge application logs containing the child's personal data (ELK stack, Splunk, CloudWatch)
  7. Machine learning models: If the child's data was used to train ML models, assess whether the model must be retrained or whether the training data inclusion is irreversible (document the assessment)
  8. Backups: Schedule deletion from backup systems within the next backup rotation cycle (max 30 days)
  9. Third-party notification: Send deletion requests to all third parties that received the child's data per Art. 17(2)

Step 5: Confirm Deletion

{
  "deletion_reference": "DEL-CHILD-2026-0284",
  "child_identifier": "child_bp_8f3a2d",
  "requester": "parent_bp_c7e4f1",
  "requester_type": "parent",
  "request_date": "2026-02-15T09:00:00Z",
  "verification_date": "2026-02-16T11:30:00Z",
  "deletion_scope": {
    "account_data": "deleted",
    "activity_logs": "deleted",
    "content": "deleted (download offered, declined by parent)",
    "communications": "deleted",
    "consent_records": "retained (legal compliance, expiry 2032-02-16)",
    "backups": "scheduled_purge_2026-03-16"
  },
  "third_party_notifications": [
    {
      "recipient": "AWS (hosting provider)",
      "notification_date": "2026-02-17",
      "scope": "all stored objects for child account",
      "confirmation": "pending"
    }
  ],
  "deletion_completed_date": "2026-02-17T14:00:00Z",
  "backup_purge_date": "2026-03-16T02:00:00Z",
  "confirmation_sent_to_requester": "2026-02-17T14:30:00Z"
}

Step 6: Post-Deletion Verification

  1. Attempt to retrieve the child's data from all systems listed in Step 4
  2. Confirm that no personal data is returned from any system (except legally retained records)
  3. Log the verification outcome
  4. Schedule backup purge verification for 30 days after primary deletion

BrightPath Learning Inc. — Deletion Implementation

Deletion Channels

ChannelDescriptionResponse Time
Parental dashboardOne-click "Delete Account" button with confirmation dialogImmediate processing
In-app (child)"Delete my stuff" button in privacy centre (for children above threshold)Immediate processing
Emailprivacy@brightpathlearning.euAcknowledgement within 48 hours
PostalBrightPath Learning Inc., 200 Education Lane, Amsterdam, 1012 AB, NetherlandsAcknowledgement within 5 business days

Deletion Flow (Parental Dashboard)

Parent clicks "Delete Alex's Account"
│
├─ Confirmation dialog:
│  "This will permanently delete Alex's account and all their data,
│   including learning progress and any work they've saved.
│   This cannot be undone."
│  [Download Alex's data first]  [Delete everything]  [Cancel]
│
├─ If "Download first" selected:
│  ├─ Generate data export (JSON + PDF progress report)
│  ├─ Email download link to parent (valid for 7 days)
│  └─ Return to deletion confirmation
│
├─ If "Delete everything" selected:
│  ├─ Re-verify parent identity (password or security question)
│  ├─ Execute deletion across all systems
│  ├─ Send confirmation email to parent
│  └─ Display confirmation: "Alex's account and data have been deleted.
│      Backup copies will be removed within 30 days."
│
└─ If "Cancel" selected:
   └─ Return to dashboard (no action taken)

Handling Competing Interests

ScenarioOutcomeRationale
Parent requests deletion; child wants to keep accountParent's request takes priority for children below thresholdParent holds consent authority under Art. 8
Child (16+) requests deletion; parent wants to retainChild's request takes priorityChild above UK threshold; autonomous rights holder
School requests deletion of student data; parent wants to retainDelete from BrightPath; inform parent they may retain their own copiesSchool's FERPA/contractual authority governs school-directed data
Safeguarding investigation active on the child's accountRetention of relevant data permitted under Art. 17(3)(d)Vital interests / public interest in protection of the child
Child's data needed for ongoing legal claimRetention permitted under Art. 17(3)(e)Legal claims exception

Exception Grounds — When Deletion Can Be Refused

Art. 17(3) provides exceptions where the right to erasure does not apply:

ExceptionArt. 17(3) ReferenceApplication to Children's Data
Freedom of expressionArt. 17(3)(a)Rarely applies to children's data; would require compelling journalistic or artistic purpose
Legal obligationArt. 17(3)(b)Tax records of transactions; mandatory educational records under national law
Public healthArt. 17(3)(c)Vaccination records; public health surveillance data
Archiving in public interestArt. 17(3)(d)Educational research (with ethical approval and anonymisation)
Legal claimsArt. 17(3)(e)Data needed for establishment, exercise, or defence of legal claims

Important: Even where an exception applies, the controller should delete as much data as possible and retain only the minimum necessary to satisfy the exception.

Common Compliance Failures

  1. No child-accessible deletion tool: Requiring children to navigate adult-oriented privacy settings or contact forms to exercise deletion rights
  2. Parental deletion blocked by verification failure: Overly burdensome verification requirements that prevent parents from exercising deletion rights
  3. Incomplete deletion scope: Deleting the account profile but retaining activity logs, analytics data, or cached copies
  4. No backup deletion: Deleting from production systems but retaining data indefinitely in backups
  5. No third-party notification: Failing to notify third parties that received the child's data per Art. 17(2)
  6. Exceeding the one-month timeline: Processing deletion requests beyond the Art. 12(3) one-month deadline without notifying the requester of an extension
  7. No deletion of historical data on adult request: Refusing to delete childhood data when the (now adult) data subject requests it, on the grounds that the data is "old" or "archived"

Enforcement Precedents

  • Google (CJEU, C-131/12, Google Spain, 2014): Established the right to erasure including for data published during minority; the Court emphasised the importance of erasure for information that is "inadequate, irrelevant or no longer relevant, or excessive"
  • TikTok (ICO, 2023): GBP 12.7 million fine included findings on failure to provide adequate mechanisms for parents and children to exercise rights including deletion
  • Musical.ly/TikTok (FTC, 2019): USD 5.7 million settlement required TikTok to delete all information collected from children under 13 and provide a mechanism for parents to request deletion going forward
  • Edmodo (FTC, 2023): USD 6 million penalty; order required Edmodo to delete children's personal information collected in violation of COPPA and establish a deletion program
  • Google (CNIL France, 2022): EUR 150 million fine for making it difficult for users to refuse cookies; the CNIL noted the platform's large child user base as an aggravating factor, and the difficulty children would face in exercising opt-out rights

Integration Points

  • Children's Data Minimisation: Data minimisation reduces the scope and complexity of deletion — less data collected means less data to delete
  • COPPA Compliance: COPPA Section 312.6 provides explicit parental deletion rights that operate alongside GDPR Art. 17
  • GDPR Parental Consent: The parent who gave consent under Art. 8 has the authority to request deletion by withdrawing consent under Art. 7(3)
  • EdTech Privacy Assessment: School-directed EdTech must handle deletion requests from both parents and schools, with end-of-year deletion as standard
  • UK AADC Implementation: AADC Standard 15 requires prominent, accessible deletion tools designed for children

Children's Privacy Notice Design

Overview

Privacy notices directed at children must meet heightened transparency standards under GDPR Articles 12-14, UK AADC Standard 4 (Transparency), and COPPA Section 312.4. Article 12(1) GDPR requires that information be provided "in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in particular for any information addressed specifically to a child." Recital 58 reinforces this by stating that given children's specific protection needs, any information and communication should be in such clear and plain language that the child can easily understand. This skill provides a comprehensive framework for creating privacy notices that children of different ages can genuinely comprehend and act upon.

Legal Requirements

GDPR Article 12(1) — Transparent Communication

"The controller shall take appropriate measures to provide any information referred to in Articles 13 and 14 and any communication under Articles 15 to 22 and 34 relating to processing to the data subject in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in particular for any information addressed specifically to a child."

GDPR Article 12(7) — Standardised Icons

"The information to be provided to data subjects pursuant to Articles 13 and 14 may be provided in combination with standardised icons in order to give in an easily visible, intelligible and clearly legible manner a meaningful overview of the intended processing."

GDPR Article 13 — Information at Point of Collection

Requires provision of: controller identity and contact details, DPO contact details, purposes and lawful basis, legitimate interests (if applicable), recipients, international transfer details, retention period, data subject rights, right to withdraw consent, right to lodge a complaint, whether provision is statutory/contractual/obligatory, and automated decision-making details.

UK AADC Standard 4 — Transparency

"Provide privacy information in a way that is suitable for the audience. The clarity, prominence, and language of information should be tailored so that a child is able to understand: what data is being collected, what it is being used for, and by whom."

COPPA Section 312.4 — Notice Requirements

Requires operators to post a clear, complete, and understandable online notice of information practices with respect to children, and provide direct notice to parents before collecting personal information from a child.

Age-Segmented Communication Framework

Segment 1: Pre-Literate and Early Readers (Under 8)

Cognitive Characteristics: Cannot read lengthy text. Understanding through images, simple icons, and verbal explanation. Concrete thinking — cannot grasp abstract concepts like "data processing" or "third parties."

Notice Design Principles:

  • Primarily visual: use illustrations, animations, or short video clips (under 60 seconds)
  • Use a character or mascot to guide the child through privacy concepts
  • Maximum 5-7 words per visual frame
  • Use concrete metaphors: "your picture" instead of "image data"; "your toys" instead of "your account information"
  • Present privacy choices as simple physical analogies: "lock your diary" for private mode; "tell your friend" for sharing

Vocabulary Level: Maximum Year 2 reading level (UK) / Grade 1 (US). Short sentences (4-6 words). Common monosyllabic words.

Format: Animated walkthrough during onboarding; no separate document. Parent receives the full Art. 13 notice.

Example Content:

[Illustration: Character with a backpack]
"When you play here, we remember your name and your favourite games."

[Illustration: Character with a padlock]
"We keep your things safe. Only you and your grown-up can see them."

[Illustration: Character waving goodbye]
"Your grown-up can ask us to forget everything about you."

Segment 2: Primary School Children (8-11)

Cognitive Characteristics: Can read simple text. Beginning to understand cause and effect. Limited understanding of commercial motivations or institutional relationships. Concrete operational thinking — can understand rules but not abstract policies.

Notice Design Principles:

  • Illustrated text with icons for each concept
  • Short paragraphs (2-3 sentences maximum)
  • Use "you" and "we" language consistently
  • Explain "why" in practical terms: "We ask your age so we can show you the right games"
  • Use interactive elements: expandable sections, hover-over definitions, quizzes
  • Provide a summary version with option to "learn more" for each section

Vocabulary Level: Maximum Year 5 reading level (UK) / Grade 4 (US). Sentences of 8-12 words. Avoid passive voice.

Required Content Blocks:

BlockWhat to CommunicateExample Language
Who we areController identity"BrightPath Learning is the company that makes this app. You can email us at hello@brightpathlearning.eu"
What we collectData categories"When you use our app, we learn: your name, your age, which games you play, and how you're doing in your lessons"
Why we collect itPurposes"We use this to: show you lessons that match your level, tell your parent how you're doing, and make our games better"
Who else sees itRecipients"Only you and your parent can see your progress. Nobody else can see it."
How long we keep itRetention"We keep your information while you have an account. When your parent deletes your account, we delete everything about you within 30 days."
Your choicesRights"You can: see everything we know about you, ask us to fix mistakes, ask your parent to delete your account"
How to complainSupervisory authority"If something worries you, tell your parent. They can also contact the people who check that companies follow the rules (the ICO in the UK)."

Segment 3: Secondary School Children (12-15)

Cognitive Characteristics: Can read and understand structured text. Beginning to think abstractly. Understands commercial relationships at a basic level. Peer influence is significant — privacy framing should include social context.

Notice Design Principles:

  • Layered approach: headline summary, then expandable detail for each topic
  • Use real-world examples and scenarios relevant to their experience
  • Include a "so what does this mean for me?" section for each data practice
  • Use infographics and flow diagrams for data sharing
  • Address common questions directly: "Can my friends see my profile?" "Will I get ads based on what I do?"
  • Include interactive privacy settings directly within the notice

Vocabulary Level: Maximum GCSE reading level (UK) / Grade 8 (US). Sentences up to 15 words. Technical terms permitted if defined immediately.

Structure:

  1. One-Paragraph Summary (30 words): The essential message
  2. Key Facts Table: Who, what, why, who else, how long — one row each
  3. Detailed Sections: Expandable sections for each Art. 13 element
  4. Your Privacy Controls: Direct links to privacy settings
  5. Questions?: Contact details and complaint mechanism

Segment 4: Young Adults (16-17)

Cognitive Characteristics: Near-adult reading comprehension. Can understand abstract and legal concepts with appropriate framing. Developing autonomy — expects to be treated as a competent decision-maker.

Notice Design Principles:

  • Standard privacy notice structure with plain language adaptations
  • Use the adult privacy notice as the base but replace legal jargon with plain equivalents
  • Include a glossary for any retained technical terms
  • Address topics relevant to this age group: employment data, university applications, social media presence, financial data
  • Respect their developing autonomy while noting parental involvement where required

Vocabulary Level: A-Level reading level (UK) / Grade 10 (US). Full sentences. Legal terms permitted with inline definitions.

Layered Notice Architecture

The ICO and EDPB recommend a layered approach to privacy information for all audiences, but this is particularly important for children.

Layer 1: Just-in-Time Notice (At Point of Collection)

Displayed at the exact moment data is collected. Must be:

  • Visible without scrolling
  • Maximum 2 sentences
  • Includes the specific purpose for this collection
  • Links to Layer 2 for more detail

Example (BrightPath Learning — game progress collection):

"We're saving your game score so you can see how you're doing over time.
Your parent can see your scores too. [Learn more]"

Layer 2: Summary Dashboard (Privacy Centre)

A visual summary of all data practices, accessible from a permanent link in the app navigation.

  • Organised by topic (not by legal article)
  • Uses icons and colour coding
  • Each section expandable to Layer 3

Layer 3: Full Privacy Notice

Complete Art. 13 information in plain language. Available as a scrollable web page and downloadable PDF. Includes:

  • All mandatory Art. 13 elements
  • Version number and date
  • Change history summary
  • Contact details and complaint mechanism

Layer 4: Parent/Guardian Notice

Full legal privacy notice with all technical and legal detail. Sent directly to the parent via email at the point of parental consent. Includes:

  • Full Art. 13 notice
  • Art. 8 parental consent details
  • Parental rights under COPPA (if applicable)
  • Parental dashboard access instructions

Readability Testing

Automated Readability Metrics

MetricTarget for Under 12Target for 12-15Target for 16-17
Flesch-Kincaid Grade Level4.0 or below8.0 or below10.0 or below
Flesch Reading Ease80+ (Easy)60-80 (Standard)50-60 (Fairly Difficult)
Gunning Fog Index6 or below10 or below12 or below
Average Sentence Length8-10 words12-15 words15-18 words
Passive Voice Percentage0%Under 10%Under 15%

User Testing with Children

Automated metrics are necessary but not sufficient. The ICO recommends testing notices with children from the target age group:

  1. Comprehension Test: Show the notice to 10+ children in the target age range. Ask them to explain in their own words what data is collected, why, and what they can do about it. Target: 80% of children correctly understand the core messages.
  2. Findability Test: Ask children to find specific information in the notice (e.g., "How do you delete your account?"). Target: 90% find the answer within 30 seconds.
  3. Emotional Response: Ask children how the notice makes them feel. Target: children report feeling informed and in control, not anxious or confused.
  4. Action Test: Ask children to change a specific privacy setting using the information in the notice. Target: 80% complete the task without assistance.

BrightPath Learning Inc. — Privacy Notice Implementation

Notice Architecture

BrightPath serves children aged 8-15 and implements the following notice structure:

For Children 8-11 (Illustrated Interactive Notice):

  • Animated character "PathBot" guides children through privacy information during first use
  • Each screen covers one topic (what we collect, why, who sees it, your choices)
  • Interactive quiz at the end: "Can you remember what we do with your game scores?"
  • Accessible from the main menu under a shield icon labelled "Your Privacy"

For Children 12-15 (Layered Summary with Expandable Detail):

  • Privacy dashboard with icon-based summary cards
  • Each card expandable to 2-3 sentence explanation
  • "Deep dive" link to full notice section
  • Privacy settings controls integrated directly into the notice

For Parents (Full Legal Notice):

  • Sent via email at parental consent stage
  • Complete Art. 13 / COPPA Section 312.4 notice
  • Links to parental dashboard
  • Available in PDF format for record-keeping

Content Inventory

Art. 13 ElementChildren's VersionParent Version
Controller identity (13(1)(a))"BrightPath Learning made this app"Full legal entity name, registration number, address
DPO contact (13(1)(b))"If you're worried, tell your parent"DPO name, email, postal address
Purposes (13(1)(c))"We use your info to show you the right lessons and tell your parent how you're doing"Detailed purpose descriptions with lawful basis
Lawful basis (13(1)(c))Not applicable for child versionArt. 6(1)(a) consent (via parental consent under Art. 8)
Legitimate interests (13(1)(d))Not applicableService security and fraud prevention
Recipients (13(1)(e))"Only you and your parent see your info"Hosting provider (AWS EU), no third-party data sharing
Transfers (13(1)(f))Not applicable (no transfers)Data stored within EEA; no third-country transfers
Retention (13(2)(a))"We keep your info while you have an account. When you leave, we delete it"Account data retained for duration of account plus 30 days. Activity logs retained for 90 days.
Rights (13(2)(b))"You can see your info, fix mistakes, and ask to delete everything"Full Art. 15-22 rights enumerated
Withdrawal (13(2)(c))"Your parent can change their mind about letting us use your info"Consent withdrawal via parental dashboard or email to DPO
Complaint right (13(2)(d))"Your parent can complain to the privacy people"Right to lodge complaint with ICO or relevant SA
Necessity (13(2)(e))"We need your name and age to make you an account"Statutory and contractual requirements specified
Automated decisions (13(2)(f))"Our app picks lessons for you based on how you're doing — it's like a teacher choosing the next exercise"Content recommendation algorithm based on learning progress; no legal or significant effects

Common Compliance Failures

  1. Single adult-format notice for all ages: Providing the same legalistic privacy policy to adults and children violates Art. 12(1)'s requirement for child-specific language
  2. Over-reliance on privacy policy page: Children rarely navigate to a separate privacy policy page; just-in-time notices are essential
  3. Jargon in children's notice: Terms like "data processing," "legitimate interest," "third party," or "data subject" are incomprehensible to children under 15
  4. No user testing: Creating a child-friendly notice without testing it with actual children in the target age range
  5. Missing "so what": Telling children what data is collected without explaining how it affects them in practical terms
  6. No visual elements: Text-only notices fail to engage children under 12 and do not meet AADC Standard 4 expectations

Enforcement Precedents

  • TikTok (DPC Ireland, 2023): EUR 345 million fine included findings that TikTok failed to provide transparent and age-appropriate privacy information to child users, violating Articles 5(1)(a) and 12-13.
  • Instagram (DPC Ireland, 2022): EUR 405 million fine included findings on lack of transparency about how children's data was processed, particularly regarding public-by-default business account settings.
  • YouTube/Google (FTC, 2019): Settlement included requirement to provide clear notice about data collection practices on child-directed channels.

Integration Points

  • GDPR Parental Consent: The notice to children operates alongside the notice to parents — both must be provided, with different content and format
  • UK AADC Implementation: AADC Standard 4 provides detailed requirements beyond Art. 12, including testing with children
  • COPPA Compliance: COPPA Section 312.4 requires both an online notice and a direct notice to parents with specific content requirements
  • Age Verification Methods: The age verification result determines which notice version to display
  • Children's Data Minimisation: The notice must accurately reflect minimised data practices — it is a compliance red flag if the notice describes extensive collection while claiming data minimisation

Children's Profiling Restrictions

Overview

Profiling of children is subject to heightened restrictions under multiple regulatory frameworks. GDPR Recital 71 states that automated decision-making including profiling "should not concern a child." The UK AADC Standard 12 requires profiling to be switched off by default for child users, with exceptions only where the controller can demonstrate a compelling reason and appropriate protective measures. The EU Digital Services Act (DSA) Article 28(2) explicitly prohibits online platforms from presenting targeted advertising based on profiling using the personal data of minors. COPPA prohibits the collection of persistent identifiers from children for behavioural advertising without verifiable parental consent. This skill establishes a comprehensive framework for lawful and ethical data processing that avoids prohibited profiling of children.

Legal Framework

GDPR Recital 71 — Children and Automated Decisions

"In any case, such processing should be subject to suitable safeguards, which should include specific information to the data subject and the right to obtain human intervention, to express his or her point of view, to obtain an explanation of the decision reached after such assessment and to challenge the decision. Such measure should not concern a child."

The EDPB interprets "should not concern a child" as a strong presumption against subjecting children to automated decision-making based on profiling that produces legal or similarly significant effects. While "should not" is weaker than "shall not," the EDPB guidance and DPA enforcement practice treat this as an effective prohibition unless exceptional circumstances apply.

GDPR Article 22 — Automated Individual Decision-Making

Art. 22(1): "The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her."

For children, this prohibition is reinforced by Recital 71. Exceptions under Art. 22(2) (contract necessity, law, explicit consent) are interpreted narrowly for children:

  • Contract necessity (Art. 22(2)(a)): Rarely applicable to children; children's contracts are often voidable
  • Law (Art. 22(2)(b)): May apply for age verification or child safety obligations
  • Explicit consent (Art. 22(2)(c)): Must be parental consent under Art. 8 for children below the threshold; the child's explicit consent alone is insufficient

GDPR Article 4(4) — Definition of Profiling

"Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements."

UK AADC Standard 12 — Profiling

"Switch options which use profiling off by default (unless you can demonstrate a compelling reason for profiling to be on by default, taking account of the best interests of the child). Only allow profiling if you have appropriate measures in place to protect the child from any harmful effects (including but not limited to feeding the child content that is detrimental to their health or wellbeing)."

UK AADC Standard 13 — Nudge Techniques

"Do not use nudge techniques to lead or encourage children to provide unnecessary personal data or weaken or turn off their privacy protections."

EU Digital Services Act — Article 28(2)

"Providers of online platforms shall not present advertisements on their interface based on profiling as defined in Article 4, point (4), of Regulation (EU) 2016/679, using personal data of the recipient of the service when they are aware with reasonable certainty that the recipient of the service is a minor."

COPPA — Persistent Identifiers

COPPA defines persistent identifiers as personal information when used for purposes other than support for internal operations. Using persistent identifiers to serve behavioural advertising to children requires verifiable parental consent.

Types of Profiling and Their Status for Children

Prohibited Profiling

Profiling TypeDescriptionRegulatory BasisStatus
Behavioural advertisingUsing browsing history, interaction patterns, or inferred interests to serve targeted advertisementsDSA Art. 28(2), AADC Std 12, COPPAProhibited for children — no exceptions under DSA
Social scoringEvaluating a child's social standing, popularity, or reputation based on interactionsAADC Std 5, Recital 71Prohibited — detrimental to wellbeing
Emotional profilingInferring emotional state from behavioural signals (typing speed, cursor movement, facial expressions) to adapt content or marketingAADC Std 5, Art. 9 (if inferring mental health)Prohibited — exploits developmental vulnerability
Predictive analytics for commercial targetingPredicting future purchasing behaviour, susceptibility to marketing, or price sensitivityAADC Std 5, Recital 71Prohibited — commercial exploitation of children
Cross-service behavioural trackingCombining data from multiple services or websites to build comprehensive behavioural profilesAADC Std 9, COPPA, DSA Art. 28(2)Prohibited — exceeds any legitimate purpose for children

Restricted Profiling (Permitted with Safeguards)

Profiling TypeDescriptionConditions for Lawfulness
Content-based recommendationsRecommending content based on the characteristics of content the child has engaged with (not the child's personal profile)Default: OFF. May be enabled with parental consent. Content diversity safeguards required.
Educational adaptive learningAdjusting educational content difficulty based on learning progressPermitted where necessary for the educational purpose. Must not extend to non-educational features. DPO review required.
Safety and moderation profilingDetecting grooming, bullying, or abuse patterns in communicationsPermitted under legitimate interest (safeguarding). Must be proportionate and subject to DPIA. Must not be used for commercial purposes.
Age-appropriate content filteringUsing age data to filter inappropriate contentPermitted as necessary for child protection. Must not be used to serve advertising.

Permitted Processing (Not Profiling)

Processing TypeDescriptionWhy It Is Not Profiling
Contextual advertisingServing advertisements based on the current page content, not the user's profileNo personal data used for ad selection; based on content context only
Aggregate analyticsAnalysing anonymised, aggregate user patterns to improve the serviceNo evaluation of individual personal aspects; data is not linked to individual users
A/B testingRandomly assigning users to feature variants to test service improvementsRandom assignment, not based on personal characteristics

Recommendation Algorithm Safeguards

For services that implement content recommendation algorithms for children (where permitted), the following safeguards must be in place:

Content Diversity Injection

  • Recommendation algorithms must include a minimum diversity ratio (e.g., at least 30% of recommended content must be from categories the child has NOT previously engaged with)
  • This prevents filter bubbles and content rabbit holes that can be particularly harmful to children's development
  • The diversity injection must be documented and periodically reviewed

Time-Limitation Mechanisms

  • Recommendation-driven feeds must include natural stopping points (e.g., "You've been browsing for 20 minutes — time for a break!")
  • Autoplay must be disabled by default for children per UK AADC guidance (YouTube implemented this following ICO engagement)
  • Infinite scroll must be replaced with paginated content with clear endpoints

Content Safety Filters

  • All recommended content must pass through content safety filters before being presented to children
  • Filters must be age-tiered: stricter for younger children, proportionate for teenagers
  • Human review for edge cases where automated filtering confidence is low

Mental Health Circuit Breakers

  • If the recommendation algorithm detects engagement patterns associated with harmful content cycles (e.g., repeated engagement with content about self-harm, eating disorders, or extreme body image), the algorithm must:
    1. Stop recommending similar content
    2. Interject wellbeing resources or helpline information
    3. Alert the parent through the parental dashboard (without disclosing specific content details that might violate the child's confidence)

Nudge Technique Prohibition

Prohibited Nudge Techniques for Children

TechniqueDescriptionWhy Prohibited
Confirmshaming"Are you sure you want to miss out?" when declining data collectionExploits social anxiety and fear of missing out
Reward-for-dataOffering in-game currency, badges, or rewards in exchange for personal data or weakened privacy settingsBribes children to surrender privacy; exploits reward-seeking behaviour
Asymmetric choiceMaking the privacy-reducing option larger, brighter, or more prominent than the privacy-protecting optionManipulates choice architecture to exploit limited decision-making capacity
Hidden opt-outBurying the option to decline data collection in sub-menus or requiring multiple clicksExploits limited navigation skills and attention span
Social proof"95% of users allow notifications!" to pressure acceptanceExploits conformity bias, which is stronger in children
Urgency/scarcity"Enable location sharing now or you'll lose your streak!"Exploits impulsivity and loss aversion
Default-to-sharePre-selecting sharing or public options and requiring the child to actively opt outExploits status quo bias and inertia

Required Design Patterns

PatternDescriptionImplementation
Equal-weight choicesAccept and reject options must be equally prominent in size, colour, and placementBoth buttons same size, same visual weight, no colour hierarchy
Neutral languageChoice labels must not favour one option over the other"Turn on" / "Keep off" — not "Yes, personalise!" / "No, I want a boring experience"
Privacy-first defaultsThe default state must be the most privacy-protective optionAll toggles default to OFF for data-intensive features
Friction parityThe number of clicks to enhance privacy must equal or be fewer than the number to reduce privacyIf enabling a feature takes 1 tap, disabling must take 1 tap or fewer
No dark patternsInterface must not use visual tricks, misdirection, or confusing language to influence the child's choiceRegular UX audits with children in the target age group

BrightPath Learning Inc. — Profiling Compliance Implementation

Profiling Status Matrix

FeatureProfiling TypeStatusJustification
Learning content difficulty adjustmentEducational adaptive learningACTIVE (default)Necessary for educational service delivery; adjusts maths and reading levels based on assessment scores
Game recommendationsContent-basedOFF by defaultRecommends games based on subject area, not child's behavioural profile; parent can enable
Progress reportsAggregate scoringACTIVE (with consent)Summarises learning outcomes for parent dashboard; no behavioural profiling
AdvertisingNoneNOT PRESENTBrightPath does not serve advertisements to children
Social featuresNoneNOT PRESENTNo social scoring, popularity metrics, or peer comparison features
Communication moderationSafety profilingACTIVEAutomated detection of inappropriate content in pre-approved message templates; DPIA completed

Algorithmic Impact Assessment

BrightPath conducts an annual Algorithmic Impact Assessment for its learning content recommendation system:

  1. Purpose test: Does the algorithm serve the child's educational interests? YES — adjusts content to appropriate difficulty level
  2. Necessity test: Could the educational purpose be achieved without profiling? NO — adaptive learning requires assessment of current skill level
  3. Proportionality test: Is the profiling limited to what is necessary? YES — only learning assessment scores are used; no behavioural data, no demographic data beyond age
  4. Harm assessment: Could the algorithm produce harmful effects? ASSESSED — risk of discouragement if difficulty increases too rapidly; mitigated by gradual progression and positive reinforcement design
  5. Bias audit: Does the algorithm produce different outcomes based on protected characteristics? TESTED — annual bias audit across age, gender, and language groups; no statistically significant disparities found
  6. Human oversight: Can a human override the algorithm? YES — parents can manually set content difficulty levels; teachers (in school deployments) can override

Enforcement Precedents

  • TikTok (DPC Ireland, 2023): EUR 345 million fine included findings that TikTok's "For You" algorithmic feed profiled children to serve content, with inadequate safeguards against harmful content amplification, violating GDPR Art. 5(1)(a), 5(1)(c), and 25.
  • Instagram (Meta, DPC Ireland, 2022): EUR 405 million fine for failing to restrict profiling and public exposure of children's data, including default public profiles for business accounts used by children aged 13-17.
  • YouTube (FTC, 2019): USD 170 million settlement for using persistent identifiers (cookies) to track children's viewing behaviour on child-directed channels and serve behaviourally targeted advertising.
  • TikTok (CNIL France, 2022): EUR 5 million fine for making it difficult for users, including children, to refuse tracking cookies — constituting a nudge technique that weakened privacy protections.
  • Fortnite/Epic Games (FTC, 2022): USD 275 million for design choices that exposed children to harmful interactions, with dark patterns facilitating in-app purchases by children.

Common Compliance Failures

  1. Profiling on by default: Activating recommendation algorithms, personalisation features, or content curation based on behavioural profiling without requiring explicit opt-in
  2. Behavioural advertising to known children: Serving targeted advertisements based on personal data profiles despite DSA Art. 28(2) prohibition
  3. No algorithmic impact assessment: Deploying algorithms that affect children without assessing their impact on children's rights, wellbeing, and development
  4. Nudge techniques in consent flows: Using dark patterns, confirmshaming, or asymmetric choice design to obtain consent for profiling features
  5. Cross-service tracking: Using persistent identifiers to track children across websites or services for profiling purposes
  6. No content diversity safeguards: Allowing recommendation algorithms to create filter bubbles or content rabbit holes without diversity injection or time limits

Integration Points

  • Children's Data Minimisation: Data minimisation directly limits the data available for profiling — less data collected means less material for profile construction
  • UK AADC Implementation: AADC Standards 5, 7, 12, and 13 collectively govern profiling, defaults, nudge techniques, and detrimental use
  • Children's Privacy Notice: The privacy notice must clearly explain what profiling occurs, its effects, and how the child/parent can object
  • GDPR Parental Consent: Parental consent is required for any profiling of children below the Art. 8 threshold
  • Age-Gating Services: The age gate result determines which profiling restrictions apply to the user account

COPPA Compliance — Children's Online Privacy Protection Act

Overview

The Children's Online Privacy Protection Act (COPPA), codified at 15 U.S.C. Sections 6501-6506 and implemented through the FTC's COPPA Rule at 16 CFR Part 312, regulates the online collection, use, and disclosure of personal information from children under 13 years of age. COPPA applies to operators of commercial websites and online services (including mobile apps) directed to children under 13, or operators with actual knowledge that they are collecting personal information from a child under 13. The FTC's 2013 amendments significantly expanded the scope to cover persistent identifiers used for behavioural advertising, photos, videos, audio recordings, and geolocation data. The FTC issued a Notice of Proposed Rulemaking (NPRM) in December 2023 proposing further amendments including restrictions on push notifications to children and expanded consent requirements for targeted advertising.

Statutory and Regulatory Framework

COPPA Statute — 15 U.S.C. Section 6502

  • Section 6502(a)(1): Unlawful for an operator of a website or online service directed to children, or having actual knowledge of collecting from a child under 13, to collect personal information in a manner that violates the FTC's regulations.
  • Section 6502(b)(1): FTC must issue regulations requiring operators to: (A) provide notice of information practices; (B) obtain verifiable parental consent; (C) allow parents to review information collected; (D) allow parents to refuse further collection/use; (E) limit collection to what is necessary for the activity.
  • Section 6502(b)(2): FTC shall apply regulations considering competitive impact, costs, and benefits, and potential effect on existing safe harbor programs.

COPPA Rule — 16 CFR Part 312

Section 312.2 — Key Definitions
  • Child: An individual under the age of 13
  • Operator: Any person who operates a website or online service and collects or maintains personal information from or about users, or on whose behalf such information is collected or maintained
  • Personal information: Individually identifiable information including: first and last name; home or physical address; online contact information (email); telephone number; Social Security number; persistent identifier that can be used to recognise a user over time and across different websites; photograph, video, or audio file containing a child's image or voice; geolocation information sufficient to identify street name and city; information concerning the child or parents collected and combined with any of the above
  • Website or online service directed to children: Determined by: subject matter, visual content, use of animated characters, child-oriented activities and incentives, music, age of models, presence of child celebrities, ads directed at children, competent evidence regarding the target audience
  • Support for internal operations: Activities necessary to maintain or analyse the functioning of the website or online service, including one-time collection and non-contact use, frequency capping, legal compliance, security, contextual advertising, personalising content (not for advertising)
Section 312.3 — Obligations of Operators
  1. Direct notice to parents (Section 312.4): Before collecting, using, or disclosing personal information from a child, the operator must provide clear and prominent notice on the website/service and directly to the parent
  2. Verifiable parental consent (Section 312.5): Must obtain verifiable parental consent before any collection, use, or disclosure, except for narrow exceptions
  3. Parental access (Section 312.6): Must provide parents with reasonable means to review the personal information collected from their child and to refuse to permit further collection or use
  4. Confidentiality, security, and integrity (Section 312.8): Must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children
  5. Data minimisation (Section 312.7): Must not condition a child's participation in an activity on providing more personal information than is reasonably necessary
  6. Data retention (Section 312.10): Must retain personal information collected from a child only as long as reasonably necessary to fulfil the purpose for which it was collected

Verifiable Parental Consent Methods — Section 312.5(b)

The FTC recognizes the following methods for obtaining verifiable parental consent. Controllers must select the appropriate method based on the sensitivity of data collected and how it will be used.

Method 1: Signed Consent Form

  • Parent prints, signs, and returns a consent form to the operator via postal mail, fax, or electronic scan
  • Form must identify the operator, list all information to be collected, describe uses and disclosures, and state that the parent can revoke consent
  • Suitable for initial high-assurance verification
  • Limitation: Slow turnaround, accessibility barriers for parents without printing capability

Method 2: Credit Card or Other Online Payment Transaction

  • Parent uses a credit card, debit card, or other online payment system that provides notification of each discrete transaction to the primary account holder
  • The transaction must be a bona fide purchase or donation, or a micro-transaction (e.g., USD 0.50) disclosed to the parent
  • Credit card verification alone (without a transaction) is insufficient; there must be an actual monetary transaction
  • Limitation: Excludes unbanked families; may deter participation

Method 3: Toll-Free Telephone Number or Video Conference

  • Parent calls a toll-free number staffed by trained personnel who verify the parent's identity through knowledge-based questions
  • Alternatively, parent connects through a video conference call where identity is confirmed visually
  • Operator must train staff on COPPA requirements and verification protocols
  • Limitation: Resource-intensive; staffing requirements for multi-language support

Method 4: Government-Issued ID with Comparison to Database

  • Parent submits a government-issued identification (driver's license, passport) which the operator checks against a database
  • The ID must be deleted promptly from the operator's records after verification is complete
  • Must comply with Section 312.5(b)(4) requirements for deletion of ID after verification
  • Limitation: Privacy concerns about collecting sensitive identity documents; storage risk

Method 5: Knowledge-Based Authentication

  • Operator uses a series of challenge questions drawn from a third-party database (e.g., TransUnion, Experian, LexisNexis) that only the parent would likely be able to answer
  • Questions must be dynamically generated and different for each verification attempt
  • Must meet threshold of difficulty that prevents a child from successfully answering
  • Limitation: Dependent on third-party data accuracy; may fail for parents with thin credit files

Method 6: Facial Recognition Technology (FTC-Approved Method, 2013)

  • Parent submits a photograph that is compared against a previously verified government-issued photo ID
  • The photograph and ID image must be deleted promptly after the comparison is complete
  • Currently an approved method under the FTC's COPPA Rule but raises significant privacy concerns
  • Limitation: Biometric data collection concerns; accuracy disparities across demographics

Method 7: Email Plus (Limited Use)

  • Parent receives an email from the operator containing a notice and a link or response mechanism
  • The operator sends a confirmatory email to the parent after a reasonable delay
  • This method is approved ONLY for internal uses of collected information — NOT when the operator will disclose personal information to third parties or make it publicly available
  • Limitation: Lowest assurance; child may access parent's email

Consent Method Selection Matrix

Data Use ScenarioMinimum Consent MethodFTC Expectation
Internal use only (no disclosure)Email Plus (Method 7)Acceptable minimum
Sharing with third partiesMethod 1, 2, 3, 4, or 5Higher assurance required
Public posting of child's informationMethod 1, 2, 3, 4, or 5Highest assurance recommended
Behavioural advertisingMethod 1, 2, 3, 4, or 5FTC scrutinises closely
Collection of photos/videos/audioMethod 1, 2, 3, 4, or 5Must verify before publication

Direct Notice Requirements — Section 312.4

Notice on the Website or Online Service — Section 312.4(b)

The operator must post a clear and prominent link to an online notice of its information practices with respect to children on the home page and each area where personal information is collected from children. The notice must state:

  1. Name, physical address, email address, and telephone number of all operators collecting or maintaining personal information through the site/service (or one designated operator with hyperlink to list of all)
  2. Description of what information is collected and whether collected actively or passively
  3. How the operator uses (and may use) the information
  4. Whether personal information is disclosed to third parties; if so, the types of businesses, their general purposes, and whether they have agreed to maintain the confidentiality and security of the information
  5. That the parent can review and have deleted the child's personal information, and can refuse to permit further collection
  6. Procedures for the parent to exercise rights

Direct Notice to Parent — Section 312.4(c)

Before collecting personal information from a child, the operator must send a direct notice to the parent that includes:

  1. Statement that the operator has collected the parent's online contact information for the purpose of obtaining parental consent
  2. The information practices of the operator
  3. That if the parent does not respond within a reasonable time, the parent's online contact information will be deleted
  4. A link to the online notice
  5. The means by which the parent can provide consent

FTC Safe Harbor Programs — Section 312.11

Industry groups or other persons may apply to the FTC for approval of self-regulatory guidelines (safe harbor programs) that implement the protections of the COPPA Rule. Operators subject to an approved safe harbor program are deemed to be in compliance with Section 312.

Currently Approved Safe Harbor Programs

ProgramAdministering OrganisationFocus Area
CARU (Children's Advertising Review Unit)BBB National ProgramsAdvertising and marketing directed to children
kidSAFE Seal ProgramkidSAFE, LLCWebsites and apps with child audiences
ESRB Privacy CertifiedEntertainment Software Rating BoardVideo games and interactive entertainment
Aristotle Integrity (formerly iKeepSafe COPPA Safe Harbor)Aristotle Inc.Cross-sector COPPA compliance
PRIVO (Privacy Vaults Online)PRIVO, Inc.Identity and consent management technology
TrustArc (formerly TRUSTe COPPA/Children's Privacy Program)TrustArc Inc.Cross-sector privacy certification

Safe Harbor Benefits

  • FTC will not bring enforcement action against an operator that is in compliance with an approved safe harbor program's guidelines
  • Safe harbor programs provide independent compliance review and monitoring
  • Programs offer dispute resolution mechanisms and consumer complaint handling
  • Membership signals compliance commitment to parents and regulators

Safe Harbor Obligations

  • Submit annual reports to the FTC on compliance activities
  • Provide effective enforcement mechanisms including consumer redress
  • Perform random, comprehensive compliance audits of members at least annually
  • Maintain publicly available list of members and compliance status

BrightPath Learning Inc. — COPPA Implementation

BrightPath Learning Inc. operates an educational gaming platform available to children in the United States. The platform includes interactive learning games, progress tracking, and parent communication features.

COPPA Compliance Architecture

Pre-Registration Flow:

  1. Landing page prominently links to the Children's Privacy Policy
  2. Registration form asks "Are you 13 or older?" with neutral yes/no options (no age pre-fill)
  3. User selecting "No" is routed to the parental consent flow
  4. User selecting "Yes" proceeds with standard registration (with age verification at Step 5)

Parental Consent Flow:

  1. Child enters parent's email address
  2. BrightPath sends direct notice to parent per Section 312.4(c) including full information practices disclosure
  3. Parent clicks the consent link within 72 hours (contact information deleted if no response)
  4. Parent completes credit card verification via USD 0.50 micro-transaction (refunded within 48 hours)
  5. Parent reviews and provides granular consent for each data use:
    • Account creation and educational content delivery (required for service)
    • Learning progress reports sent to parent (optional)
    • Anonymized aggregate analytics for platform improvement (optional)
  6. Confirmation email sent to parent with link to parental dashboard

Parental Dashboard Features:

  • View all personal information collected from the child
  • Download collected information in machine-readable format (JSON/CSV)
  • Delete specific data elements or the entire account
  • Modify consent preferences for each data use
  • Set usage time limits and content restrictions
  • Receive weekly activity summary reports

Data Minimisation Measures:

  • No persistent identifiers collected for advertising purposes
  • No geolocation data collected (GPS disabled; IP address truncated to /24)
  • No photographs, videos, or audio recordings stored beyond session
  • Profile avatar selected from pre-set options (no photo upload for children under 13)
  • Chat functionality disabled for accounts under 13; moderated text communication only through pre-approved messages

Annual COPPA Audit Checklist

#Audit ItemRegulatory ReferenceStatus
1Privacy policy posted and current312.4(b)Review quarterly
2Direct notice sent before collection312.4(c)Automated system verified
3Verifiable parental consent obtained312.5Credit card method validated
4Parental access mechanism functional312.6Dashboard tested monthly
5No excess data collection312.7Quarterly data mapping review
6Security measures adequate312.8Annual penetration test
7Retention limits enforced312.10Automated deletion verified
8Third-party disclosures documented312.4(b)(4)Vendor list updated quarterly
9Safe harbor membership current312.11kidSAFE renewal date tracked
10Staff training completedInternal policyAnnual COPPA training for all staff

FTC Enforcement Actions

  • Epic Games/Fortnite (FTC, 2022): USD 275 million penalty for collecting personal information from children under 13 without parental consent, enabling voice and text communications with strangers by default, and using dark patterns to induce purchases. Largest COPPA penalty in history.
  • Google/YouTube (FTC, 2019): USD 170 million settlement (USD 136 million FTC, USD 34 million New York AG) for collecting persistent identifiers from viewers of child-directed YouTube channels to serve targeted advertising without obtaining verifiable parental consent.
  • Musical.ly/TikTok (FTC, 2019): USD 5.7 million settlement for collecting names, email addresses, and other personal information from children under 13 without parental consent while knowing that a significant portion of users were children.
  • VTech Electronics (FTC, 2018): USD 650,000 settlement for collecting personal information from children including photos, chat logs, and audio recordings without parental consent, and failing to secure the data leading to a breach exposing 6.4 million children's records.
  • Unixiz Inc./Explore Talent (FTC, 2020): USD 2 million judgment for collecting personal information from children on a talent scouting website without posting a privacy policy, obtaining parental consent, or maintaining reasonable security.

Proposed 2024 COPPA Rule Amendments

The FTC's December 2023 Notice of Proposed Rulemaking proposes significant changes:

  1. Separate consent for targeted advertising: Operators must obtain separate, opt-in parental consent specifically for targeted advertising directed at children — consent for the service itself cannot be bundled with advertising consent
  2. Prohibition on push notification consent: Operators cannot condition access to the service on the parent's consent to send push notifications to the child
  3. Enhanced data security requirements: Operators must implement a written information security program with specific technical safeguards
  4. Expanded definition of personal information: Biometric identifiers added explicitly to the definition
  5. Limits on data retention: Operators must retain children's personal information only for as long as reasonably necessary for the specific purpose for which it was collected
  6. Safe harbor accountability: Enhanced FTC oversight of safe harbor programs including more detailed annual reporting requirements

Integration Points

  • GDPR Parental Consent: For services operating in both the US and EU, COPPA requirements (under-13 bright line) and GDPR Art. 8 requirements (13-16 depending on Member State) must both be satisfied
  • Age Verification Methods: COPPA requires age screening; the method must not incentivise false age claims
  • Children's Data Minimisation: COPPA Section 312.7 aligns with GDPR Art. 5(1)(c) data minimisation principle
  • EdTech Privacy Assessment: COPPA's school exception (Section 312.5(c)(4)) allows schools to consent on behalf of parents for educational technology used in the classroom
  • Children's Deletion Requests: COPPA Section 312.6 requires operators to delete children's information upon parental request

EdTech Privacy Assessment — Children's Data in Educational Technology

Overview

Educational technology (EdTech) platforms that process children's personal data operate at the intersection of multiple privacy frameworks. In the United States, COPPA's school exception (16 CFR 312.5(c)(4)) allows schools to provide consent on behalf of parents for the collection of children's data in educational contexts, but only for school-authorised educational purposes. The Family Educational Rights and Privacy Act (FERPA, 20 U.S.C. Section 1232g) governs education records maintained by educational agencies or institutions receiving federal funding. In the EU, GDPR applies with the heightened protections of Art. 8 (parental consent for children) and Recital 38 (specific protection for children). The UK AADC applies to EdTech services likely to be accessed by children. This skill provides a framework for conducting privacy assessments of EdTech platforms that navigate these overlapping requirements.

Regulatory Frameworks

COPPA School Exception — 16 CFR 312.5(c)(4)

COPPA permits an operator to collect personal information from a child for the use and benefit of the school, and for no other commercial purpose, without obtaining verifiable parental consent directly, when:

  1. The school has authorised the collection of personal information on behalf of the students
  2. The collection is solely for the school's use and benefit in the educational context
  3. The operator does not use the collected information for any commercial purpose unrelated to the educational context
  4. The operator does not disclose the information to non-school third parties

Critical Limitations:

  • The school acts as an agent of the parent; the school does not have unlimited authority
  • The school can only consent to the collection of information necessary for the school-authorised educational activity
  • If the operator wants to use the data for commercial purposes (including advertising), the operator must obtain verifiable parental consent directly from the parent
  • The FTC has stated that schools "should not be able to consent on behalf of the parent to the collection of information that is not needed for the educational purpose" (FTC COPPA FAQ J.2)

FERPA — 20 U.S.C. Section 1232g

FERPA protects education records maintained by educational agencies or institutions that receive federal funding. EdTech platforms may receive education records as "school officials" under the school official exception.

Key Provisions:

  • Education records: Records, files, documents, and other materials directly related to a student that are maintained by an educational agency or institution or by a person acting for such agency or institution
  • School official exception (34 CFR 99.31(a)(1)): An educational agency or institution may disclose education records to a contractor, consultant, volunteer, or other party to whom the agency has outsourced institutional services or functions, provided that: the party performs an institutional service or function; the party is under the direct control of the agency; the party uses the education records only for the purposes for which the disclosure was made; the party meets the criteria specified in the agency's FERPA annual notification
  • Legitimate educational interest: The school official must have a legitimate educational interest in the education records — meaning the official needs to review the record to fulfil their professional responsibility
  • Directory information exception (34 CFR 99.37): Schools may disclose directory information (name, address, telephone number, email, date and place of birth, honours, activities) without consent if parents have been notified and given the opportunity to opt out

FERPA vs. COPPA Interaction

ScenarioFERPA Applies?COPPA Applies?Result
School-directed use of EdTech platformYesYes (school exception available)School consents under COPPA; FERPA school official exception governs data handling
Student independently uses EdTech at homeNo (not maintained by school)Yes (full COPPA applies)Operator must obtain verifiable parental consent directly
EdTech vendor receives education records from schoolYesYes (school exception)FERPA and COPPA both apply; vendor must comply with both
EdTech vendor uses data for advertisingFERPA violation (non-educational use)COPPA violation (exceeds school exception)Both laws violated; school exception does not apply

GDPR Application to EdTech

In the EU, the COPPA school exception does not exist. Schools using EdTech platforms must comply with:

  • Art. 6 Lawful Basis: Schools may rely on Art. 6(1)(e) (public task) for processing necessary for educational purposes, or Art. 6(1)(f) (legitimate interests) where public task does not apply
  • Art. 8 Parental Consent: If the EdTech platform relies on consent as its lawful basis for processing children's data, parental consent is required for children below the applicable national threshold
  • Art. 28 Processor Agreement: If the school is the data controller and the EdTech vendor is the processor, a compliant Art. 28 data processing agreement must be in place
  • Controller Determination: The school is typically the controller for educational processing; the EdTech vendor is the processor. However, if the vendor processes data for its own purposes (product improvement, analytics, advertising), it becomes a controller or joint controller for those purposes

Student Privacy Pledge (FPF/SIIA)

The Student Privacy Pledge, administered by the Future of Privacy Forum (FPF) and the Software and Information Industry Association (SIIA), is a voluntary industry commitment. Signatories commit to:

  1. Not sell student personal information
  2. Not behaviourally target advertising to students using data from the educational context
  3. Not create advertising profiles of students
  4. Not change privacy policies without notice and choice
  5. Enforce strict limits on data retention and deletion
  6. Support access to and correction of student information by authorised parties
  7. Use student data only for authorised educational/school purposes or as directed by parent/student
  8. Maintain a comprehensive data security program
  9. Not disclose student information except for legitimate educational purposes
  10. Require downstream recipients to comply with these commitments

Over 400 EdTech companies are signatories as of 2024.

EdTech Privacy Assessment Framework

Assessment Phase 1: Platform Classification

QuestionSignificance
Is the platform directed to children under 13?COPPA applies fully; age gate and parental consent required
Is the platform used in a school context?COPPA school exception may apply; FERPA may apply
Does the school direct students to use the platform?Strengthens school exception applicability
Does the platform operate in the EU/UK?GDPR/UK GDPR applies; AADC compliance required
Does the platform collect persistent identifiers?COPPA personal information threshold met
Does the platform use collected data for non-educational purposes?School exception does not apply to non-educational uses

Assessment Phase 2: Data Mapping

For each data element collected by the EdTech platform:

Data ElementCollection MethodEducational PurposeNon-Educational UseRetention PeriodShared With
Student nameAccount creationIdentify student in classroomNoneAcademic year + 30 daysTeacher, parent
Email addressLogin credentialAuthenticationNoneAccount durationNone
Learning progressAutomated trackingAdaptive content, gradingProduct improvement (aggregated)Academic year + 30 daysTeacher, parent
Assignment submissionsStudent uploadAssessment, feedbackNoneAcademic year + 30 daysTeacher
Interaction logsAutomatedFeature usage analyticsProduct improvement (aggregated)90 daysNone (internal only)
Device identifiersAutomatedSession managementNoneSession onlyNone

Assessment Phase 3: Legal Basis Evaluation

JurisdictionLawful BasisConditionsDocumentation Required
US (COPPA)School exception consentSchool has authorised use; data used only for educational purposes; operator does not use data commerciallyWritten agreement with school; operator's COPPA-compliant privacy policy
US (FERPA)School official exceptionOperator performs institutional service; under school's direct control; uses records only for authorised purposesSchool's FERPA annual notification names operator as school official
EU (GDPR)Art. 6(1)(e) Public taskSchool's educational mission qualifies as public task; processing necessary for that taskSchool's records of processing (Art. 30); DPA between school and vendor (Art. 28)
UK (GDPR + AADC)Art. 6(1)(e) Public task or Art. 6(1)(f) Legitimate interestsSame as EU GDPR plus AADC compliance for all 15 standardsDPIA; AADC conformance assessment

Assessment Phase 4: Contractual Requirements

The agreement between the school and the EdTech vendor must address:

  1. Scope of data processing: Specific data elements, purposes, and retention periods
  2. Prohibition on commercial use: Vendor may not use student data for advertising, marketing, or non-educational product development
  3. Sub-processor restrictions: Vendor must disclose all sub-processors and ensure they comply with equivalent restrictions
  4. Data deletion obligations: Vendor must delete all student data at the school's request and at the end of the contract period
  5. End-of-year deletion: Vendor must delete or return all student data at the end of each academic year unless the school specifically authorises retention
  6. Security requirements: Specific technical and organisational security measures
  7. Breach notification: Vendor must notify the school within 24-72 hours of a data breach affecting student data
  8. Audit rights: School has the right to audit the vendor's compliance with the agreement
  9. FERPA compliance (US): Vendor acknowledged as school official; data used only for legitimate educational interests
  10. COPPA compliance (US): Vendor acknowledges school exception limitations; does not use data for non-educational commercial purposes

Assessment Phase 5: End-of-Year Data Lifecycle

The end of the academic year is a critical data lifecycle event for EdTech platforms. The following protocol must be implemented:

60 Days Before Year End:

  1. Notify school administrators that the end-of-year data lifecycle process will begin
  2. Provide data export options: school can download all student data in standard formats (CSV, JSON, SIF)
  3. Confirm whether the school authorises retention of any data for the next academic year

30 Days Before Year End:

  1. Notify teachers that student data will be archived
  2. Generate end-of-year student progress reports for school records
  3. Export any student-created content (assignments, projects) to the school's designated storage

Year End (Last Day of Academic Year):

  1. Deactivate all student accounts associated with the ending year
  2. Archive student data to a deletion queue (not immediately deleted, to allow for last-minute school requests)

30 Days After Year End:

  1. Execute deletion of all student data in the deletion queue unless the school has authorised retention
  2. Deletion scope: primary database, search indices, analytics databases, caches, logs
  3. Generate deletion certificates for the school

60 Days After Year End:

  1. Purge archived backups containing deleted student data
  2. Provide final deletion confirmation to the school
  3. Retain only the deletion certificate and the school agreement (no student personal data)

BrightPath Learning Inc. — EdTech Privacy Assessment

Platform Profile

BrightPath Learning Inc. operates an educational gaming platform deployed in schools and available for home use across the US, UK, and EU. The platform serves children aged 5-15.

Assessment Results

Classification:

  • Directed to children under 13: YES
  • Used in school context: YES (deployed in 2,400 schools)
  • Also available for home (non-school) use: YES
  • Operates in US, UK, EU: YES

Dual-Track Compliance:

  • School deployments: COPPA school exception applies for school-directed use; FERPA school official exception applies; GDPR Art. 6(1)(e) public task in EU
  • Home use: Full COPPA applies (verifiable parental consent via credit card); GDPR Art. 8 parental consent required in EU

Data Practices Assessment:

PracticeStatusNotes
Data used only for educational purposesPASSNo advertising, no behavioural profiling, no commercial use
Student data not soldPASSWritten policy prohibition; contractual commitment with schools
Behavioural advertising to studentsN/APlatform is ad-free; no advertising infrastructure
Data retention limited to academic yearPASSAutomatic deletion 30 days after year end; school can request earlier
Sub-processor list disclosed to schoolsPASSAWS (hosting), SendGrid (parent notifications); both under DPA
School agreement includes all required termsPASSAnnual review; covers COPPA, FERPA, GDPR, security, deletion
Breach notification procedurePASS24-hour notification to school; 72-hour to DPA (GDPR)
Parental access mechanism (home use)PASSParental dashboard with data view, download, and deletion
Student Privacy Pledge signatoryYESSigned 2024; annual compliance certification

State Student Privacy Laws

Several US states have enacted student privacy laws that impose additional requirements on EdTech vendors:

StateLawKey Requirements
CaliforniaStudent Online Personal Information Protection Act (SOPIPA, 2014)Prohibits using student data for non-educational advertising; prohibits selling student data; requires deletion when no longer needed
New YorkEducation Law Section 2-d (2014, amended 2020)Requires data privacy and security plans; parental notification of third-party access; breach notification; data encryption
ColoradoStudent Data Transparency and Security Act (2016)Requires school contracts to specify data elements, purposes, and security; prohibits targeted advertising to students
ConnecticutStudent Data Privacy Act (PA 16-189, 2016)Prohibits using student data for targeted advertising; requires operator to delete data within 30 days of request
IllinoisStudent Online Personal Protection Act (SOPPA, 2021)Requires parental notification; prohibits targeted advertising, creating commercial profiles, selling student data; mandates data breach notification
VirginiaStudent Data Governance Plan (2015)Requires schools to adopt data governance plans; vendors must comply with school data governance policies
TexasSCOPE Act (2017)Prohibits using covered information for non-educational purposes; requires security standards; mandates deletion
MarylandStudent Data Privacy Act (2015)Prohibits using student data for advertising; requires data security; mandates deletion at end of contract

Common Compliance Failures

  1. Exceeding the school exception: Using data collected under the COPPA school exception for product improvement, advertising, or other commercial purposes without separate parental consent
  2. No end-of-year deletion: Retaining student data indefinitely after the educational purpose has expired
  3. Inadequate school agreements: Missing key contractual terms such as sub-processor disclosure, deletion obligations, audit rights, or breach notification timelines
  4. Treating all collection as school-authorised: When a student uses the EdTech platform at home for non-school purposes, the school exception does not apply — the operator must obtain direct parental consent
  5. FERPA non-compliance: Failing to ensure the vendor is designated as a school official or using education records for purposes beyond legitimate educational interest
  6. No separate consent for non-educational features: Bundling consent for educational features with optional features (gamification rewards, social features) that require separate consent

Enforcement Precedents

  • Edmodo (FTC, 2023): USD 6 million penalty for collecting and using children's personal information for advertising purposes while operating as a school-directed EdTech platform, exceeding the scope of the COPPA school exception.
  • Google/YouTube (FTC, 2019): USD 170 million included channels used in educational contexts where persistent identifiers were collected for advertising.
  • InBloom (State enforcement, 2014): Data aggregation platform for student records shut down after New York, Louisiana, and other states raised FERPA and privacy concerns about centralised storage of student data with inadequate security and access controls.
  • Chegg (FTC, 2023): FTC ordered Chegg to implement comprehensive data security program after four breaches exposed personal information of millions of students and employees.

Integration Points

  • COPPA Compliance: The school exception is a narrow carve-out from COPPA's general requirements; all other COPPA requirements (notice, security, data minimisation) still apply
  • Children's Data Minimisation: EdTech platforms must collect only data necessary for the educational purpose; data minimisation is both a COPPA and GDPR requirement
  • Children's Deletion Requests: Parents retain the right to request deletion of their child's data even in school-directed contexts; schools can also request deletion under FERPA
  • GDPR Parental Consent: In the EU, the school exception does not exist; schools must rely on Art. 6(1)(e) public task or obtain parental consent under Art. 8
  • Children's Privacy Notice: EdTech platforms must provide privacy notices to both the school (as decision-maker) and parents (as rights holders)

GDPR Parental Consent Verification

Overview

Article 8 of the GDPR establishes that when information society services are offered directly to a child, the processing of personal data based on consent is lawful only where the child is at least 16 years old. Member States may lower this threshold to a minimum of 13 years. Where the child is below the applicable age threshold, consent must be given or authorised by the holder of parental responsibility. The controller must make reasonable efforts to verify that the person giving consent holds parental responsibility, taking into consideration available technology. This skill provides a comprehensive framework for implementing Art. 8 compliance, drawing on EDPB Guidelines 5/2020, national implementations, and enforcement precedents.

Legal Foundation — Article 8 GDPR

Art. 8(1) — Conditions for Child's Consent

Where Article 6(1)(a) (consent) applies in relation to the offer of information society services directly to a child, the processing shall be lawful where the child is at least 16 years old. Where the child is below the age of 16 years, processing is lawful only if and to the extent that consent is given or authorised by the holder of parental responsibility over the child. Member States may provide by law for a lower age for those purposes provided that such lower age is not below 13 years.

Art. 8(2) — Verification Obligation

The controller shall make reasonable efforts to verify in such cases that consent is given or authorised by the holder of parental responsibility over the child, taking into consideration available technology.

Art. 8(3) — Other Lawful Bases Unaffected

Article 8(1) does not affect the general contract law of Member States such as rules on the validity, formation or effect of a contract in relation to a child.

Age Thresholds by EU/EEA Member State

CountryAge ThresholdNational Legislation
Austria14Austrian Data Protection Act (DSG) Section 4(4)
Belgium13Act of 30 July 2018, Art. 7
Bulgaria14Personal Data Protection Act, Art. 25a
Croatia16Implementation Act on GDPR, Art. 19
Cyprus14Law 125(I)/2018, Art. 8
Czech Republic15Act No. 110/2019 Sb., Section 7
Denmark13Danish Data Protection Act, Section 6(2)
Estonia13Personal Data Protection Act, Section 8
Finland13Data Protection Act 1050/2018, Section 5
France15Loi Informatique et Libertes, Art. 45
Germany16GDPR default — no lowering enacted
Greece15Law 4624/2019, Art. 21
Hungary16GDPR default — Act CXII of 2011 amended
Ireland16Data Protection Act 2018, Section 31
Italy14Legislative Decree 101/2018, Art. 2-quinquies
Latvia13Personal Data Processing Law, Art. 10
Lithuania14Law on Legal Protection of Personal Data, Art. 5
Luxembourg16Law of 1 August 2018, Art. 8
Malta13Data Protection Act Cap. 586, Art. 30
Netherlands16GDPR default — UAVG did not lower
Norway13Personal Data Act, Section 5
Poland16GDPR default — Act of 10 May 2018
Portugal13Law 58/2019, Art. 16
Romania16GDPR default — Law 190/2018
Slovakia16GDPR default — Act 18/2018
Slovenia16GDPR default — Personal Data Protection Act
Spain14Organic Law 3/2018, Art. 7
Sweden13Act 2018:218, Chapter 2, Section 4
UK (post-Brexit)13Data Protection Act 2018, Section 9; UK GDPR Art. 8

Determining When Article 8 Applies

Article 8 applies only when ALL of the following conditions are met:

  1. Information society service: A service normally provided for remuneration, at a distance, by electronic means, and at the individual request of the recipient (Directive 2015/1535, Art. 1(1)(b)). Includes social media, gaming platforms, e-commerce, streaming, and educational apps. Does NOT include preventive or counselling services offered to a child.

  2. Offered directly to a child: The service is targeted at children or the controller is aware that the user base includes children. Indicators include child-oriented design, content, marketing, or listed in app stores under children's categories.

  3. Consent as lawful basis: Processing relies on Art. 6(1)(a) consent. If the controller relies on a different lawful basis (legitimate interest, contract performance, legal obligation), Art. 8 does not apply — although the best interests of the child remain relevant under Recital 38.

  4. Child below applicable national threshold: The data subject is below the age threshold set by the applicable Member State.

Parental Verification Mechanisms

Tier 1 — High Assurance (Recommended for sensitive data or high-risk processing)

MethodDescriptionStrengthsWeaknesses
Electronic ID verification (eIDAS)Parent authenticates using national eIDLegally binding, high certaintyLimited cross-border availability
Video call verificationLive video call with parent showing IDStrong visual confirmationResource-intensive, not scalable
Credit card transactionSmall charge to parent's credit card with reversalFinancial identity verificationExcludes unbanked parents
Government ID uploadParent uploads government-issued photo IDDocument-based verificationID document fraud risk, data minimisation concern

Tier 2 — Medium Assurance (Suitable for standard processing)

MethodDescriptionStrengthsWeaknesses
Email-plus verificationEmail to parent with knowledge-based confirmationReasonable effort at scaleEmail can be accessed by child
SMS verification with callbackSMS code sent to parent's mobile numberTies to physical deviceChildren may access parent's phone
Parental account linkingParent creates own verified account and links to childOngoing oversight capabilityParent account creation friction
Digital signatureParent signs consent form electronicallyLegally valid, auditableRequires parent digital literacy

Tier 3 — Basic Assurance (Minimum for low-risk processing)

MethodDescriptionStrengthsWeaknesses
Email verificationVerification email to parent-provided addressLow friction, scalableLowest assurance level
Checkbox declarationParent confirms status via checkboxMinimal implementation costEasily circumvented

Selecting Verification Level — Risk-Based Approach

The appropriate verification level depends on:

  • Nature of data collected: Special category data (Art. 9) requires Tier 1 verification
  • Volume of data: Extensive profiling or monitoring of children requires Tier 1
  • Purpose of processing: Marketing or behavioural advertising requires higher assurance than educational tools
  • Risk to children: Services enabling direct messaging or social interaction with strangers require Tier 1
  • Available technology: Controllers must consider technology available at the time of implementation per Art. 8(2)

Consent Record Requirements

Every parental consent must be documented with the following fields to satisfy Art. 7(1) demonstration obligation:

FieldDescriptionExample
consent_idUnique identifier for the consent recordPC-2026-0001457
child_identifierPseudonymised child identifierchild_a3b7c9d2
child_age_at_consentAge of child at time of consent12
applicable_thresholdNational age threshold applied13 (Belgium)
parent_identifierPseudonymised parent identifierparent_f4e8a1b6
verification_methodMethod used to verify parental responsibilitycredit_card_transaction
verification_outcomeResult of verificationverified
purposesSpecific processing purposes consented to["account_creation", "content_personalization"]
data_categoriesCategories of personal data covered["name", "age", "usage_data"]
consent_text_versionSHA-256 hash of the consent text showna1b2c3d4...
timestampISO 8601 timestamp of consent2026-03-14T10:30:00Z
withdrawal_mechanismHow parent can withdraw consentparental_dashboard
expiry_dateConsent review/expiry date2027-03-14

BrightPath Learning Inc. — Implementation Example

BrightPath Learning Inc. operates an educational gaming platform targeting children aged 8-15 across the EU. The platform is available in France (threshold: 15), Germany (threshold: 16), Spain (threshold: 14), and Belgium (threshold: 13).

Implementation Steps

Step 1: Age Collection (Neutral Design)

  • During account creation, the platform asks "What year were you born?" using a scrollable date selector (not a free-text field)
  • The age prompt does not indicate why the question is asked or what the "correct" answer would be
  • The platform calculates age based on the response and applies the threshold of the child's country of residence

Step 2: Threshold Routing

  • Child in France aged 14 → Below threshold (15). Parental consent required.
  • Child in Belgium aged 14 → Above threshold (13). Child can consent independently.
  • Child in Germany aged 15 → Below threshold (16). Parental consent required.

Step 3: Parental Verification Flow

  • Child enters parent's email address
  • Platform sends verification email to parent with one-time link
  • Parent clicks link, creates a parental oversight account
  • Parent verifies identity via credit card micro-transaction (EUR 0.50 refunded within 48 hours)
  • Parent reviews and approves specific processing purposes
  • Parent receives confirmation with link to parental dashboard

Step 4: Ongoing Parental Oversight

  • Parental dashboard displays all active consents with per-purpose granularity
  • Parent can withdraw consent for any purpose at any time
  • Platform sends annual consent renewal reminder
  • When child reaches the applicable age threshold, the platform notifies both parent and child, and transitions consent authority to the child

Consent Record Example

{
  "consent_id": "PC-2026-0003891",
  "child_identifier": "child_bp_8f3a2d",
  "child_age_at_consent": 12,
  "applicable_threshold": 15,
  "applicable_country": "FR",
  "parent_identifier": "parent_bp_c7e4f1",
  "verification_method": "credit_card_micro_transaction",
  "verification_outcome": "verified",
  "verification_timestamp": "2026-03-14T14:22:00Z",
  "purposes": [
    {
      "purpose_id": "edu_content_delivery",
      "description": "Deliver educational gaming content appropriate to child's learning level",
      "consented": true
    },
    {
      "purpose_id": "progress_tracking",
      "description": "Track learning progress and generate reports for parent",
      "consented": true
    },
    {
      "purpose_id": "personalized_recommendations",
      "description": "Recommend games based on learning progress and preferences",
      "consented": false
    }
  ],
  "data_categories": ["name", "age", "learning_progress", "game_interactions"],
  "consent_text_version": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
  "timestamp": "2026-03-14T14:25:00Z",
  "withdrawal_mechanism": "parental_dashboard",
  "expiry_date": "2027-03-14",
  "controller": "BrightPath Learning Inc.",
  "controller_address": "200 Education Lane, Amsterdam, 1012 AB, Netherlands"
}

Enforcement Precedents

  • TikTok (DPC Ireland, 2023): EUR 345 million fine for violations including failure to implement adequate parental consent mechanisms for children under 13, default public profiles for child accounts, and transparency failures under Articles 5(1)(a), 5(1)(c), 12, 13, 24, and 25.
  • Instagram (DPC Ireland, 2022): EUR 405 million fine for allowing children aged 13-17 to operate business accounts with public-by-default settings, exposing children's contact information. Related to inadequate implementation of Art. 8 and Art. 25 obligations.
  • Google/YouTube (FTC, 2019): USD 170 million settlement for collecting children's personal information (persistent identifiers) to serve targeted advertising without obtaining verifiable parental consent, violating COPPA.
  • Fortnite/Epic Games (FTC, 2022): USD 275 million settlement for collecting personal information from children under 13 without parental notification or consent, and enabling real-time voice and text communications with strangers by default.
  • CNIL France — TIKTOK (2022): EUR 5 million fine for making it difficult to refuse cookies on the platform, with aggravating consideration of the large number of child users.

Common Compliance Failures

  1. Single age threshold for all EU operations: Controller applies one threshold (e.g., 16) across all Member States instead of the locally applicable threshold based on the child's country of residence
  2. Self-declaration only: Relying solely on the child's statement of age without any verification mechanism
  3. No parental verification: Collecting parent's email but not verifying that the email holder actually has parental responsibility
  4. Consent bundling: Obtaining parental consent for all processing purposes in a single checkbox instead of granular per-purpose consent
  5. No consent expiry: Failing to periodically refresh parental consent or transition authority when the child reaches the applicable threshold
  6. Cookie walls for children: Denying access to the service unless all cookies (including analytics and advertising) are accepted

Integration Points

  • Age Verification Methods: Art. 8(2) requires reasonable efforts to verify age before determining whether parental consent is needed
  • Children's Privacy Notice: Art. 12 transparency obligation requires clear communication to both parent and child
  • Children's Data Minimisation: Art. 5(1)(c) data minimisation is interpreted strictly when processing children's data per Recital 38
  • UK AADC Implementation: The UK Age Appropriate Design Code supplements UK GDPR Art. 8 with 15 design standards
  • COPPA Compliance: For services also targeting US children under 13, COPPA requirements run in parallel with GDPR Art. 8

UK Age Appropriate Design Code Implementation

Overview

The Age Appropriate Design Code (AADC), also known as the Children's Code, is a statutory code of practice issued by the UK Information Commissioner's Office (ICO) under Section 123 of the Data Protection Act 2018. It came into force on 2 September 2020 with a 12-month transition period ending 2 September 2021. The Code sets out 15 standards of age-appropriate design that information society services (ISS) likely to be accessed by children must conform to. "Children" under the Code means anyone under the age of 18 in the UK. Non-compliance does not directly create criminal liability, but the ICO takes the Code into account when assessing conformance with the UK GDPR and DPA 2018, and violations can result in enforcement action including fines of up to GBP 17.5 million or 4% of annual worldwide turnover.

Scope — Who Must Comply

The AADC applies to providers of information society services that:

  1. Process personal data: The service processes the personal data of individual users
  2. Are likely to be accessed by children: The service is likely to be accessed by users under 18, even if not specifically directed at children. The ICO interprets "likely to be accessed" broadly — if children form any part of the actual or foreseeable user base, the Code applies
  3. Are information society services: Services normally provided for remuneration, at a distance, by electronic means, and at the individual request of a recipient. Includes apps, games, social media, streaming services, connected toys, news websites, educational platforms, and online marketplaces

Services NOT in Scope

  • Services with no UK users
  • Preventive or counselling services offered directly to a child
  • Services that can demonstrate children do not and cannot access the service (e.g., authenticated corporate intranets)

The 15 Standards

Standard 1: Best Interests of the Child

Requirement: The best interests of the child should be a primary consideration when designing and developing online services likely to be accessed by a child.

Implementation:

  • Conduct a Best Interests Assessment (BIA) documented in writing for each feature or processing activity affecting children
  • BIA must consider: the child's physical safety, mental health, developmental needs, educational benefit, privacy interests, and right to play
  • Reference the UN Convention on the Rights of the Child (UNCRC) Articles 3, 12, 13, 16, 17, and 31
  • Record how children's interests were weighed against commercial interests
  • Update BIA when features change or new risks emerge

BrightPath Learning Inc. Example: Before launching a "leaderboard" feature comparing children's scores, BrightPath conducted a BIA considering potential psychological pressure and bullying risks. The BIA concluded that public leaderboards were not in children's best interests. BrightPath instead implemented private progress reports visible only to the child and their parent.

Standard 2: Data Protection Impact Assessments

Requirement: Undertake a DPIA for any processing likely to result in a high risk to the rights and freedoms of children, considering the different ages, capacities, and developmental needs of children.

Implementation:

  • Conduct child-specific DPIAs that assess risk from the perspective of children at different developmental stages (under 5, 5-9, 10-12, 13-15, 16-17)
  • Consider risks that adults might tolerate but children cannot (commercial pressure, social exclusion, grooming, exposure to inappropriate content)
  • Include children or children's advocates in the DPIA process where possible
  • DPIA must address how the service's design affects children's agency and autonomy
  • Review DPIA annually and after any significant service change

Standard 3: Age-Appropriate Application

Requirement: Take a risk-based approach to recognising the age of individual users and ensure you effectively apply the standards in this code to child users.

Implementation:

  • Establish the age of users with a level of certainty proportionate to the risks arising from the data processing
  • For high-risk processing: use age verification or estimation technologies with high confidence
  • For lower-risk processing: self-declaration may be acceptable if combined with risk-mitigation measures
  • Apply different design standards to different age groups where appropriate (pre-literate children, primary school, secondary school, young adults)
  • Do not use age information collected for this purpose for any other purpose

Standard 4: Transparency

Requirement: Provide privacy information in a clear, prominent, and age-appropriate manner that is suitable for the audience, including for children who are not the primary users but may still access the service.

Implementation:

  • Provide a child-friendly version of the privacy notice using language, illustrations, and formats appropriate to each age group
  • Use bite-sized, just-in-time notices at the point of data collection rather than relying solely on a single privacy policy page
  • For children under 12: use simple vocabulary (maximum Year 5 reading level), illustrations, icons, and interactive elements
  • For children 13-17: use plain English at GCSE reading level with practical examples
  • Explain what data is collected, why, who sees it, and what the child can do about it
  • Make the "so what?" clear — help children understand how data processing affects them in practice

Standard 5: Detrimental Use of Data

Requirement: Do not use children's personal data in ways that have been shown to be detrimental to their wellbeing, or that go against industry codes of practice, other regulatory provisions or Government advice.

Implementation:

  • Do not use children's data for: behavioural advertising targeting, extensive profiling for commercial purposes, social scoring, emotional manipulation, or dark patterns that exploit developmental vulnerabilities
  • Monitor academic research and Government guidance on technology's impact on children's wellbeing
  • Maintain a "detrimental use register" documenting processing activities assessed against this standard
  • Remove or modify features identified as detrimental following review

Standard 6: Policies and Community Standards

Requirement: Uphold published terms, policies, and community standards, including but not limited to privacy policies, age restriction policies, behaviour rules, and content policies.

Implementation:

  • Enforce age restrictions consistently — if the service states it is for 13+, actively enforce this
  • Apply community standards equally and transparently
  • Provide child-accessible reporting mechanisms for policy violations
  • Publish and maintain a transparency report on policy enforcement actions

Standard 7: Default Settings

Requirement: Settings must be "high privacy" by default, unless you can demonstrate a compelling reason for a different default, taking account of the best interests of the child.

Implementation:

  • Profile visibility: default to private or friends-only
  • Location sharing: default to off
  • Search indexing: default to not indexed by external search engines
  • Direct messaging: default to contacts-only or off for younger children
  • Personalised advertising: default to off
  • Data sharing with third parties: default to off
  • Push notifications: default to minimal or off
  • Document the compelling reason if any default is not set to highest privacy

Standard 8: Data Minimisation

Requirement: Collect and retain only the minimum amount of personal data needed to provide the elements of the service in which a child is actively and knowingly engaged.

Implementation:

  • Limit data collection to what is strictly necessary for the specific feature the child is using
  • Do not collect data for future use or speculative purposes
  • Disable background data collection (microphone, camera, contacts, location) unless actively required for a feature the child has requested
  • Implement automated data deletion schedules with short retention periods
  • Regularly audit data collection against stated purposes

Standard 9: Data Sharing

Requirement: Do not disclose children's data unless you can demonstrate a compelling reason to do so, taking account of the best interests of the child.

Implementation:

  • Default to not sharing children's data with third parties
  • Where sharing is necessary, document the compelling reason and conduct a BIA
  • Contractually require third parties to apply equivalent protections to children's data
  • Provide transparent notice to the child and parent about any data sharing
  • Maintain a publicly available list of categories of third-party recipients

Standard 10: Geolocation

Requirement: Switch geolocation options off by default (unless you can demonstrate a compelling reason for geolocation to be switched on by default, taking account of the best interests of the child). Provide an obvious sign to the child when location tracking is active. Options which make the child's location visible to others must default to off.

Implementation:

  • GPS and precise location services: default OFF
  • Display a persistent, visible indicator when any location tracking is active (e.g., a pulsing location icon)
  • Location visible to others: always default to OFF with no exception
  • If location is required for a feature, collect at the lowest precision necessary (city-level rather than street-level)
  • Automatically reset location permissions to OFF after each session ends
  • Provide parents with the ability to disable location features entirely

BrightPath Learning Inc. Example: BrightPath's educational platform does not collect precise geolocation. Country-level location is derived from the IP address (truncated to /16) solely for content localisation (language and curriculum alignment). No location data is shared with third parties or visible to other users. A notice states: "We know which country you're in so we can show you the right lessons. We don't track where you go."

Standard 11: Parental Controls

Requirement: If you provide parental controls, give the child age-appropriate information about this. If your online service allows a parent or carer to monitor their child's online activity or track their location, provide an obvious sign to the child when they are being monitored.

Implementation:

  • Inform children in age-appropriate language that parental controls exist and what they do
  • Display a visible indicator when parental monitoring is active (e.g., an eye icon on the dashboard)
  • Balance parental oversight with the child's evolving right to privacy as they mature
  • For children 16-17: consider whether parental monitoring is proportionate given the young person's developing autonomy
  • Provide children with an age-appropriate way to raise concerns about parental control settings

Standard 12: Profiling

Requirement: Switch options which use profiling off by default (unless you can demonstrate a compelling reason for profiling to be on by default, taking account of the best interests of the child). Only allow profiling if you have appropriate measures in place to protect the child from any harmful effects.

Implementation:

  • All profiling features: default OFF
  • Recommendation algorithms: use content-based (not behavioural) recommendations by default
  • Do not use profiling to amplify features that are detrimental to children's wellbeing
  • Where profiling is enabled (with consent), implement safeguards: content diversity injection, time limits on algorithmic feeds, mental health circuit-breakers
  • Conduct annual impact assessments of profiling on children's wellbeing

Standard 13: Nudge Techniques

Requirement: Do not use nudge techniques to lead or encourage children to provide unnecessary personal data or weaken or turn off their privacy protections.

Implementation:

  • Do not use dark patterns, confirmshaming, or asymmetric choice architecture to extract consent or data from children
  • The "accept all" and "reject all" options must be equally prominent
  • Do not offer rewards, in-game currency, or other incentives in exchange for personal data or weakened privacy settings
  • Privacy-enhancing choices must be presented with at least equal prominence and ease as privacy-reducing choices
  • Test UI/UX designs with children of appropriate ages to identify unintentional nudging

Standard 14: Connected Toys and Devices

Requirement: If you provide a connected toy or device, ensure you include effective tools to enable conformance with this code.

Implementation:

  • Connected devices must comply with all 15 standards
  • Provide clear setup instructions for parents to configure privacy settings
  • Default to offline mode; require explicit activation of online features
  • Clearly indicate when the device is recording, transmitting, or receiving data (LED indicator, audio cue)
  • Provide mechanism to delete all stored data from the device and cloud

Standard 15: Online Tools

Requirement: Provide prominent and accessible tools to help children exercise their data protection rights and report concerns.

Implementation:

  • Provide child-accessible "privacy centre" with visual, age-appropriate controls
  • One-click (or equivalent) mechanisms to: download data, delete data, change privacy settings, report concerns
  • Ensure reporting tools do not require providing additional personal data
  • Respond to children's requests within the UK GDPR's one-month timeline
  • Provide tools that empower children to manage their own privacy as they mature

ICO Enforcement and Engagement

Enforcement Actions

  • TikTok (ICO, 2023): GBP 12.7 million fine for processing personal data of children under 13 without appropriate parental consent, violating UK GDPR Article 8. The ICO explicitly referenced the AADC in its investigation approach.
  • ICO Engagement with Social Media (2021-2022): The ICO wrote to major social media platforms (Instagram, TikTok, YouTube, Snapchat) requiring them to demonstrate AADC compliance. This led to Instagram setting all under-18 accounts to private by default, TikTok disabling direct messaging for under-16s, and YouTube disabling autoplay for children.

ICO Conformance Assessment

The ICO assesses AADC compliance by examining:

  1. Whether the service has conducted a conformance self-assessment
  2. Whether DPIAs specifically address risks to children at different developmental stages
  3. Whether default settings are genuinely "high privacy"
  4. Whether transparency materials are tested with children for comprehension
  5. Whether the service monitors compliance and responds to children's complaints

BrightPath Learning Inc. — AADC Conformance Matrix

StandardConformance StatusImplementation
1. Best InterestsConformingBIA completed for all features; reviewed quarterly
2. DPIAConformingChild-specific DPIA segmented by age group (5-9, 10-12, 13-15, 16-17)
3. Age-Appropriate ApplicationConformingAge verification via parental account; different UI for under-10 and 10-17
4. TransparencyConformingIllustrated privacy notice for under-12; plain English for 13-17
5. Detrimental UseConformingNo behavioural advertising; no social scoring; no emotional analytics
6. Policies and Community StandardsConformingPublished community guidelines; child-accessible reporting
7. Default SettingsConformingAll profiles private; sharing off; push notifications off
8. Data MinimisationConformingOnly learning progress and minimal account data collected
9. Data SharingConformingNo third-party data sharing; hosting provider bound by DPA
10. GeolocationConformingGPS off; country-level IP only for content localisation
11. Parental ControlsConformingDashboard with eye icon when monitoring active; child informed
12. ProfilingConformingContent-based recommendations only; no behavioural profiling
13. Nudge TechniquesConformingNo rewards for data; equal-weight accept/reject; no confirmshaming
14. Connected Toys/DevicesN/APlatform is web and mobile app only; no connected devices
15. Online ToolsConformingChild-accessible privacy centre; one-click data download and deletion

Integration Points

  • GDPR Parental Consent: UK GDPR Art. 8 sets the age threshold at 13; AADC applies to all children under 18
  • Age Verification Methods: AADC Standard 3 requires age-appropriate application with proportionate age verification
  • Children's Privacy Notice: AADC Standard 4 provides detailed transparency requirements beyond UK GDPR Art. 12-14
  • Children's Data Minimisation: AADC Standard 8 reinforces GDPR Art. 5(1)(c) with child-specific strictness
  • Children's Profiling Limits: AADC Standard 12 requires profiling off by default with compelling-reason exceptions

Sponsors

Details

Marketplace
mukul975/Privacy-Data-Protection-Skills
Source
plugins/children-privacy-skills
Author
Mahipal
Category
Compliance
License
Apache-2.0
Keywords
coppa, children-privacy, aadc, age-verification, parental-consent

More from mukul975/Privacy-Data-Protection-Skills

All 21