Export must carry a visible not-legal-advice disclaimer

JSONMarkdown

The requirementstatement

A generated policy or terms document must be exported with a visible disclaimer that it is not legal advice and should be reviewed by counsel.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
document export
Where it liveslayer
Policy pagesPOLICY_PAGE
How Ekas settles itdetectability
Human checkHUMAN
Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass
Supply evidenceTERMINAL_EVIDENCE
Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities
TCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

A document that arrives formatted and complete reads as advice whether or not it was meant as such, and the businesses most likely to rely on it are the ones least able to absorb the consequences of it being wrong. Every vendor in this space carries the disclaimer, which is a fair indication of what happens without it.

How to fix itremediation

Show the disclaimer where the document is exported, not buried in a terms page nobody opens. Done when the person pressing export has read that it is not legal advice.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Did the person exporting this document see, and read, that it is not legal advice?

  1. 1Show the disclaimer where the export happens, not buried in a terms page nobody opens.
  2. 2Treat the output as a starting draft and route it for review — the dispute-resolution clauses first.

What wrong looks like: A document that arrives formatted and complete reads as advice whether or not it was meant as such, and the businesses most likely to rely on it are the least able to absorb it being wrong.

Notesnotes

A product obligation with no registration surface: nothing in a submission records what the export screen said. The user has to treat any generated document as a starting draft and have it reviewed, particularly the dispute-resolution clauses POL-214 flags.

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-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH

All policy pages rules

POL-246 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works