A cart-reminder programme must say how abandonment is detected
The requirementstatement
Where the programme sends shopping-cart reminders, the policy must state explicitly how cart abandonment is detected.
- 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
- 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
- T-MobileCTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
T-Mobile asks for this in almost these words, because a cart reminder is triggered by watching what someone did rather than by anything they asked for — so the policy has to say that cookies, a plugin or an account session are doing the watching. A retailer who switched an abandoned-cart flow on inside a platform has usually never seen the mechanism, let alone described it.
How to fix itremediation
Add a sentence naming the mechanism — website cookies, a store plugin, a logged-in session — and what triggers the message. Done when the policy explains how the business knows a cart was left.
A compliant exampleexample
If you add items to your basket on acmecoffee.com and leave without checking out, a cookie on your browser lets us link that basket to your number so we can text you a reminder.
Common mistakespitfalls
- The T&C has to reflect the cart programme as well (POL-110), and the opt-in disclosure has to name it (WEB-068). Fixing only the policy leaves two of the three.
Notesnotes
Conditional on cart-reminder traffic, which no applicability dimension expresses — there is no cart-reminder attribute. The criteria pass immediately when nothing indicates the programme sends them. Severity divergence: T-Mobile and TCR grade it BLOCKING, CTIA SCMH Sev-2 MEDIUM. Strictest kept.
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-050Privacy policy must state mobile opt-in data is not shared or soldBlockingBLOCKINGPOL-063A policy that says mobile opt-in data is shared is refused outrightBlockingBLOCKINGPOL-078A political brand is held to the same data-sharing banBlockingBLOCKINGPOL-079A charity policy must bar anyone but the charity from using subscriber dataBlockingBLOCKINGPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGHPOL-061The non-sharing prohibition must hold even with consumer consentHighHIGH
POL-109 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.