Skip to content
Back to skills

Privacy Policy

ASecurity

Use when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill privacy-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Privacy Policy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Privacy Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-privacy-policy/badge)](https://www.skillsdirectory.com/skills/thedaviddias-privacy-policy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: privacy-policy
description: "Use when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation."
metadata:
  category: privacy
  priority: high
  difficulty: beginner
  estimatedTime: "15"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/privacy/privacy-policy
---

# Link to your privacy policy in the footer

Collecting user data without a publicly accessible privacy policy violates GDPR (EU), CCPA (California), PIPEDA (Canada), and other regulations — even if the policy is technically published but not linked from the site.

## Quick Reference

- Link to a published privacy policy from the footer of every page
- The privacy policy must be written in plain language and accessible to all users
- Required when you collect any personal data: names, emails, IP addresses, cookies, analytics data
- GDPR requires the policy to be easily accessible — a footer link satisfies this requirement
- The link text should be 'Privacy Policy' (or locale equivalent) for SEO and accessibility
- Disclose retention periods and whether analytics, logs, or monitoring receive personal data

## Check

Check whether the website footer contains a link to a privacy policy page. Verify the linked page contains an actual privacy policy with contact information, what data is collected, and user rights. Check that the link is present on all pages, not just the homepage. Confirm the policy discloses retention periods and whether analytics, logging, or monitoring vendors receive user data.

## Fix

Add a 'Privacy Policy' link to the site footer that appears on every page. Ensure the linked page describes what personal data is collected, why, how it is used, who it is shared with, how long it is kept, and how users can exercise their rights.

## Explain

Explain why a publicly accessible privacy policy is legally required under GDPR and CCPA, what information it must contain, and how to make it genuinely accessible to users.

## Code Review

Review server config, headers, forms, and integration points related to Link to your privacy policy in the footer. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.

---

For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.

Rule page: https://frontendchecklist.io/rules/privacy/privacy-policy

Files in this skill

  • SKILL.md2.4 KB
  • references/rule.md5.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…