The ages in the terms and the privacy policy must not conflict
The requirementstatement
The minimum age in the terms' eligibility clause must not conflict with the age threshold in the privacy policy's children's section.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- ToS eligibility age vs privacy policy minors section
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- What the fix involvesfailureClass
- Fix the policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Terms admitting thirteen-year-olds next to a policy promising to collect nothing from anyone under eighteen is a document pair that cannot both be true, and a reviewer reading them together sees a business that has not read its own paperwork. The two are almost always written by different people from different templates, which is why the numbers diverge without anybody deciding anything.
How to fix itremediation
Pick one age for the business and use it in the terms, the privacy policy and the SMS terms. Done when the same number appears in all three.
A compliant exampleexample
Terms: "You must be at least 18." Privacy policy: "We do not knowingly collect information from anyone under 18."
Notesnotes
The check compares only explicit numbers it can find in both documents. Where either is silent it reports PASS rather than inventing a conflict — the absence of the age itself is POL-202 and POL-113.
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-020A non-English site needs an English policyMediumMEDIUMPOL-027The policy URLs must stay live after approvalMediumMEDIUMPOL-028Keep a dated copy of both documents as submittedMediumMEDIUMPOL-058A service-provider carve-back is required, not prohibitedMediumMEDIUMPOL-076The privacy policy must describe data handling, not sell the programmeMediumMEDIUMPOL-104The policy must say how message content is handledMediumMEDIUM
POL-231 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.