An uploaded policy document must fit the provider file constraints
The requirementstatement
Where a policy is uploaded rather than linked, the file must be a PDF, PNG or JPEG within the tightest provider size cap.
- 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
- campaign policy document upload
- 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 fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- AWSTCRBandwidthTelnyx
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Uploading is the sanctioned route for a brand with no website or an offline opt-in, and the caps differ by an order of magnitude — 500 KB at AWS against 10 MB at TCR — so a file that uploads cleanly at one destination is rejected at another with an error about the campaign rather than about the file. A scanned policy from an office printer is several megabytes without anyone intending it to be.
How to fix itremediation
Re-export the document as a PDF under 500 KB — print to PDF rather than scanning, or downsample the scan to 150 dpi — and re-upload. Done when the file is one of PDF, PNG or JPEG and under half a megabyte.
A compliant exampleexample
acme-privacy-policy.pdf · application/pdf · 210 KB
Common mistakespitfalls
- A hosted URL is preferred wherever a website exists; WEB-054 fails a PDF that stands in for a page the brand could have published.
Notesnotes
Applies only where a document was uploaded, which no applicability dimension expresses — the check passes immediately when the registration carries none. The 500 KB ceiling is AWS's, taken as the tightest cap so a submission survives a destination that has not been chosen yet.
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-001A privacy policy URL is required on the campaignBlockingBLOCKINGPOL-002A terms and conditions URL is required on the campaignBlockingBLOCKINGPOL-005The terms and conditions attestation must be setBlockingBLOCKINGPOL-010Both policy URLs must resolve and return content anonymouslyBlockingBLOCKINGPOL-015The policy host must serve a valid certificate of its ownBlockingBLOCKINGPOL-016The privacy policy URL must open an actual privacy policyBlockingBLOCKING
POL-003 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.