/ / d / example.com / web-standards / legal
Legal · example.com
pillar failed·Required·0 /2 items passing ·2 n/a
The legal disclosures the site is required to publish for the visitors it serves, based on jurisdiction and what data it collects.
Items
| Item | Status | Backed by | Evidence |
|---|---|---|---|
| Privacy policy published | fail | factor 47 | found=false, source=none, probed=https://example.com/privacy|https://example.com/privacy-policy|https://example.com/privacy-notice |
| Terms of service published | fail | factor 48 | found=false, source=none, probed=https://example.com/terms|https://example.com/terms-of-service|https://example.com/terms-of-use |
| Cookie consent (where required) | na | factor 46 | Not applicable to this site |
| CCPA opt-out link | na | factor 50 | Not applicable to this site |
Why each item matters
- Privacy policy published · methodology →
Any site collecting visitor data — analytics, cookies, forms — is required to disclose it. Personal one-pagers are exempt.
- Terms of service published · methodology →
Commercial sites need ToS to define the relationship with visitors. Read-only blogs and personal sites don't.
- Cookie consent (where required) · methodology →
GDPR and the UK GDPR require a CMP for any site setting non-essential cookies. Hard requirement in those jurisdictions.
- CCPA opt-out link · methodology →
California requires a 'Do Not Sell or Share' link on commercial sites that handle CA-resident data.