An offline opt-in does not relax the policy content requirements
The requirementstatement
The policy pages must satisfy the full content requirements even where opt-in never happens on the web.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- privacy policy body + terms body
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- 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
- AWSTwilioBandwidth
- When it appliesapplicabilityText
- Applies when consent was collected by live verbal, IVR, paper form, point of sale and imported list.
Why this rule existsrationale
Programmes that collect consent on a call, on paper or at a counter tend to treat the website as decoration, so the policy is whatever was published years ago — and the reviewer applies exactly the same content checks to it as to an e-commerce brand. Nothing about collecting consent offline reduces what the consumer is entitled to read.
How to fix itremediation
Bring the published policy and SMS terms up to the same standard a web opt-in would need — the mobile non-sharing clause, the programme description, frequency, rates, STOP and HELP — before submitting the offline flow. Done when the documents would pass on their own, with the consent method left out of it.
Notesnotes
An anti-exemption rule: it exists to be applied to registrations that assume the requirements are lighter, and it points at the rest of the layer rather than adding a requirement of its own.
Rules you will hit next
One other rule reads privacy policy body + terms 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-156Published policy must not contain unreplaced template tokensHighHIGHPOL-001A privacy policy URL is required on the campaignBlockingBLOCKINGPOL-002A terms and conditions URL is required on the campaignBlockingBLOCKINGPOL-003An uploaded policy document must fit the provider file constraintsBlockingBLOCKINGPOL-005The terms and conditions attestation must be setBlockingBLOCKINGPOL-010Both policy URLs must resolve and return content anonymouslyBlockingBLOCKING
POL-045 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.