Disclosures must appear at the point of opt-in, not only in linked documents
The requirementstatement
The required disclosures must be visible on the consent surface itself; burying them in a linked Terms page does not satisfy the requirement.
- 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
- consent surface
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWLAI · visionVISION
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- AWSCTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
AWS states the point directly: disclosures must be presented at the time of opt-in rather than housed inside a linked policy document. A consumer deciding whether to tick a box does not open a terms page first, so a disclosure they must navigate to is a disclosure they never saw.
How to fix itremediation
Move the disclosure text into the same visual block as the checkbox. Keep the links to Terms and Privacy as well — they are required in addition to the inline disclosure, never as a substitute for it.
A compliant exampleexample
By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
Rules you will hit next
6 other rules read consent surface. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CON-043A mandatory phone field needs its own separate, optional SMS opt-inBlockingBLOCKINGCON-108The disclosure must be on the same page as the phone-number fieldBlockingBLOCKINGCON-AGE-GATEAge-gated programs require real age verification at opt-inBlockingBLOCKINGCON-BOX-BUNDLEDMessaging consent must be separate from terms acceptanceBlockingBLOCKINGCON-BOX-PRESENTAn explicit affirmative opt-in control must existBlockingBLOCKINGCON-BOX-UNCHECKEDThe consent control must be unchecked by defaultBlockingBLOCKING
CON-DISC-ADJACENT is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.