The agreement sets a minimum age of 13 for service access and requires parental or guardian consent for users under 18. Users represent by accepting the terms that they meet the age requirement and have not been previously suspended from the service.
This analysis describes what OpenRouter'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
This provision establishes age-based eligibility conditions for service access. The minimum age of 13 engages COPPA obligations for users under 13, while the requirement for parental consent for users aged 13-17 creates a representation-based gate rather than a verified consent mechanism. The document does not describe verification procedures for age or parental consent.
Interpretive note: The terms do not describe active age verification or parental consent collection mechanisms; the compliance posture with respect to COPPA and state minor protection laws depends on implementation details not described in the document.
Severity was downgraded from 'medium' to 'low' while the actual provision text remained identical.
View full change record →Under this clause, users under 13 are not permitted to use the service, and users between 13 and 17 must have parental or guardian consent. The terms rely on user representation of compliance rather than describing active age verification or parental consent verification mechanisms.
How other platforms handle this
You must be at least 13 years old (or the minimum age required in your country) to use Threads. If you are under 18, you must have your parent or legal guardian's permission to use Threads.
Our Services are not directed to children under 13. If you learn that anyone younger than 13 has unlawfully provided us with personal data, please contact us at privacy@medium.com.
The Service is intended for general audiences and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe that your child under the age of 13 has provided us with personal information without your cons...
Monitoring
OpenRouter has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"You must be at least 13 years of age to use the Service. By agreeing to these Terms, you represent and warrant to us that: (a) you are at least 13 years of age; (b) you have not previously been suspended or removed from the Service; and (c) your registration and your use of the Service is in compliance with all applicable laws and regulations. If you are under 18 years of age, you must have your parent or guardian's permission to use the Service.— Excerpt from OpenRouter's OpenRouter Terms of Service
1) REGULATORY LANDSCAPE: COPPA (Children's Online Privacy Protection Act) applies to online services directed at children under 13 or with actual knowledge of users under 13, and is enforced by the FTC. The agreement's minimum age of 13 is consistent with COPPA thresholds, but the absence of described age verification mechanisms creates potential exposure if minors access the service. State laws such as California's Age-Appropriate Design Code (AADC) may impose additional obligations for services accessible to users under 18. 2) GOVERNANCE EXPOSURE: Medium. Representation-based age gates without active verification are common in digital services but may create COPPA and state law exposure if the service is accessible to minors in practice. The AI model routing context, which may include access to generative AI models capable of producing age-inappropriate content, elevates the practical significance of this provision. 3) JURISDICTION FLAGS: California's Age-Appropriate Design Code imposes specific obligations on services likely to be accessed by users under 18. EU GDPR sets a minimum age for consent at 16 in most member states (with flexibility down to 13), and national implementations vary. UK Age Appropriate Design Code imposes additional requirements. 4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise customers deploying OpenRouter in products accessible to minors should assess whether their own age verification and parental consent mechanisms satisfy applicable law independently of OpenRouter's representation-based approach. 5) COMPLIANCE CONSIDERATIONS: The absence of described age verification procedures for users between 13 and 17 may warrant review by compliance teams, particularly for consumer-facing applications built on the OpenRouter API that may be accessed by minors.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes age-based eligibility conditions for service access. The minimum age of 13 engages COPPA obligations for users under 13, while the requirement for parental consent for users aged 13-17 creates a representation-based gate rather than a verified consent mechanism. The document does not describe verification procedures for age or parental consent.
Under this clause, users under 13 are not permitted to use the service, and users between 13 and 17 must have parental or guardian consent. The terms rely on user representation of compliance rather than describing active age verification or parental consent verification mechanisms.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by OpenRouter.