The policy must state its position on sensitive personal information
The requirementstatement
The privacy policy must state whether sensitive personal information is used beyond the permitted purposes.
- 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
- privacy policy body
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- CCPA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Add the sentence, and where the answer is no, say so plainly rather than omitting the section. Done when the document states the position either way.
A compliant exampleexample
We do not use or disclose sensitive personal information beyond the purposes permitted under California law.
Rules you will hit next
6 other rules read privacy policy body. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
POL-128 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.