Channels
Writing legal content
Legal copy is precise or it is liability. When unsure, flag for review — do not improvise claims.
Principles
- State only what the product does today, not roadmap aspirations
- Match verification language to actual verification levels in the API
- Distinguish public reviews from private feedback in policy text
- No superlatives ("best", "only", "guaranteed") without legal approval
Verification wording
| Do | Don't |
|---|---|
| Verified participant reviews | Certified reviews · 100% authentic |
| Matched to registration or finish data | Impossible to fake |
| Email-trust and roster verification (define each) | Fully verified athletes |
Pages requiring legal review
- Terms of service, privacy policy, DPA, cookie policy
- Pricing page footnotes and plan comparison claims
- Trust / verification marketing pages
- Anything referencing GDPR, consumer rights, or dispute outcomes
Internal vs public
Internal reasoning for claim limits (regulatory context, sample sizes) may live in repo-only legal appendices. Public pages state the claim and qualification — not internal debate.
Organizer-facing legal UI
Dispute flows and moderation copy must describe process and timelines accurately. Do not promise outcomes ("we will remove any negative review").
Sporting Scouter Content Style Guide
Component-enforceable rules: design-system.sportingscouter.com/voice. Tokens from
packages/config/tailwind/theme.css.