Coursera does not allow children under 13 (or 16 in some countries) to use its platform, and states it will delete data if it discovers it has been collected from a child below the applicable age threshold.
This analysis describes what Coursera's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The age threshold of 16 in certain jurisdictions (consistent with GDPR requirements) is a legally significant distinction that parents and guardians of teenagers should be aware of when considering platform access.
Interpretive note: The specific jurisdictions in which the 16-year threshold applies are not enumerated in the document, and the operational age verification mechanism is not described.
Minors at or near the age thresholds may have accounts or data collected without full legal authorization, and the policy relies on reactive deletion rather than proactive age verification mechanisms.
How other platforms handle this
Our Services are not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13 without parental consent, we will take steps to delete such information. In some juris...
Our services are not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If we become aware that we have collected personal information from a child under 13 without parental consent, we will take steps to delete that information.
The Waze App is not intended for use by children. We do not knowingly collect personal information from children under the age of 13 (or the applicable age of digital consent in your jurisdiction, which may be higher, such as 16 in certain EU member states). If we become aware that we have collected...
Monitoring
Coursera has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"We do not knowingly collect personal data from children under the age of 13 (or 16 in certain jurisdictions). If we learn we have collected personal data from a child under those ages, we will take steps to delete such information.— Excerpt from Coursera's Coursera Privacy Notice
REGULATORY LANDSCAPE: This provision engages COPPA (U.S., applying to children under 13), GDPR Article 8 (which permits member states to set consent ages between 13 and 16, with many EU states setting 16), and the UK Age Appropriate Design Code (Children's Code). The FTC enforces COPPA in the U.S.; EU supervisory authorities enforce GDPR Article 8; the UK ICO enforces the Children's Code. GOVERNANCE EXPOSURE: Medium. The notice states a reactive rather than proactive approach to age verification, which may be insufficient under stricter regulatory interpretations, particularly the UK Children's Code, which expects services to consider the best interests of child users by design. The dual threshold (13 vs. 16) is appropriate for regulatory compliance but operational implementation of jurisdiction-specific age gating is not described. JURISDICTION FLAGS: EU member states that have set the digital consent age at 16 (including Germany and the Netherlands) create heightened exposure if Coursera enrolls users in that age range without parental consent. The UK Children's Code creates additional design obligations for services likely to be accessed by minors. Illinois and other U.S. states with student privacy laws may impose additional obligations. CONTRACT AND VENDOR IMPLICATIONS: Educational institution clients deploying Coursera for students should assess whether any enrolled students may be under the applicable age threshold and what contractual protections exist. FERPA and state student privacy laws may impose additional obligations on institutional clients. COMPLIANCE CONSIDERATIONS: Coursera should document its age verification and detection mechanisms. Institutional clients should contractually confirm the minimum age of enrolled learners. Where campus programs may include students under 16 in EU jurisdictions, parental consent mechanisms should be reviewed.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The age threshold of 16 in certain jurisdictions (consistent with GDPR requirements) is a legally significant distinction that parents and guardians of teenagers should be aware of when considering platform access.
Minors at or near the age thresholds may have accounts or data collected without full legal authorization, and the policy relies on reactive deletion rather than proactive age verification mechanisms.
ConductAtlas has identified this type of provision across 9 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Coursera.