The terms should cover accounts and credentials
The requirementstatement
The terms of service must include a clause covering accounts, registration and credential security.
- Severityseverity
- LowLOWBest practice. Worth fixing, rarely fatal on its own.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- terms of service body
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- TCR
- When it appliesapplicabilityText
- Applies when the use case is NOT M2M.
Why this rule existsrationale
How to fix itremediation
Add the accounts clause where the service has user accounts. Done when the document says who is responsible for a login and what happens when it is misused.
A compliant exampleexample
You are responsible for keeping your Acme Coffee account password secure and for anything done using your account. Tell us at once if you think someone else has used it.
Notesnotes
Rules you will hit next
6 other rules read terms of service 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-203 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.