privacy-policy-check

Detects missing, broken, or placeholder privacy policy links in iOS and macOS apps.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/tvh25082004/Badminton --skill privacy-policy-check-tvh25082004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: privacy-policy-check
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/privacy/privacy-policy-check
Command: npx skills add https://github.com/tvh25082004/Badminton --skill privacy-policy-check-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? iOS apps are frequently rejected from the App Store under Guideline 5.1.1(i) because their privacy policy link is missing, broken, uses HTTP instead of HTTPS, or only exists in App Store Connect metadata rather than inside the app itself. This Skill scans your project before submission to catch these issues early. ## Core Features & Use Cases - Privacy Policy URL Detection: Greps Swift and Objective-C sources for privacy policy URL references and flags their complete absence as a critical rejection risk. - Placeholder and Insecure Link Detection: Identifies placeholder domains like example.com and non-HTTPS privacy policy URLs that Apple reviewers will reject. - In-App Accessibility Verification: Checks for a dedicated privacy policy screen or link within the app experience, not just in App Store Connect. - Use Case: Before submitting your iOS app, run this check to receive a prioritized findings list (critical, high, medium, low) with exact file paths and line numbers for each privacy policy issue. ## Quick Start Scan my iOS project for missing, broken, or placeholder privacy policy links before App Store submission.

Frequently Asked Questions about privacy-policy-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my iOS app privacy policy link will pass App Store review?▼

Scan your Swift and Objective-C sources for privacy policy URL references, verify they use HTTPS, and confirm no placeholder domains like example.com remain. The link must be accessible within the app itself, not only in App Store Connect metadata.

Why was my app rejected under Guideline 5.1.1(i)?▼

Common causes include a privacy policy URL returning 404, a placeholder URL left in code, or a policy only present in App Store Connect but not accessible inside the app. Apple reviewers click the link during review, so it must be live and functional.

Does this privacy policy check work with React Native or Flutter projects?▼

Yes, the check works on Swift, Objective-C, React Native, and Flutter projects. It uses file globbing and grep patterns rather than compiling code, so it applies across these frameworks.

Does the privacy policy check modify my code or make network requests?▼

No, the check is strictly read-only and makes no network calls. It only searches source files and reports findings, so you must manually verify that the privacy policy URL returns a live 200 response.

What counts as a critical privacy policy issue in an iOS app?▼

A critical issue is having no privacy policy URL reference anywhere in your Swift sources, or using a placeholder URL like example.com or yourcompany.com. Both guarantee rejection under Guideline 5.1.1(i) because the link is missing or non-functional.