원클릭으로
privacy-policy
Use when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.
Use when reviewing templates, rendered HTML, or shared components related to Declare UTF-8 character encoding. Validate the final browser-facing markup, not just the source framework abstraction.
Use when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.
Use when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the rule's frontmatter.
| 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/en/rules/privacy/privacy-policy"} |
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.
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.
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 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.
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/en/rules/privacy/privacy-policy