Privacy Policy Check
Verifies a privacy policy page exists, is linked from the footer, and has a lastUpdated date under 12 months.
Entry verified April 21, 2026
The short answer
Companion to /legal-sweep. Checks three things: the page exists at a predictable route (/privacy-policy, /privacy, or /legal/privacy), the footer links to it, and the lastUpdated date isn’t stale. Catches the three most common audit failures.
When to use it
Before launch. Before adding analytics, forms, or any user data collection. As a quarterly hygiene check.
Setup
- 1
Save as ~/.claude/commands/privacy-policy-check.md. Stack-aware (Next.js Pages Router, Astro, WordPress — same logic as /legal-sweep).
- 2
Checks for a privacy-policy.js / .astro / .md file at common routes; grep footer component for the link; scan page content for a Last Updated date within the last 365 days.
- 3
Reports missing / stale items; does not auto-generate policy text (human liability lives on the policy’s wording).
Example
You: /privacy-policy-check
Claude: ✅ Page exists: pages/privacy-policy.js
❌ Footer link: missing (checked components/layout/Footer.js)
⚠️ Last Updated: 2024-06-15 (22 months old — flag for refresh)
Recommendation: add footer link, schedule policy review.Source & attribution
- Author
- Bryan Collins
- Licence
- MIT (author's own work)
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
This is a presence-and-freshness check, not a legal review — policy wording is a lawyer job, not a skill.
56 skills across 10 categories, all licence-verified.