Will It Vibe?No privacy policy findable (heuristic)
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
The repo has analytics/tracking or authentication code (both imply personal-data collection) but no privacy-policy route, page, or link was found anywhere. Heuristic: the policy may live outside this repo.
Why it matters
A site that runs analytics/tracking or has user accounts and logins is collecting personal data, and most privacy laws (GDPR, CCPA, and similar) require a published privacy policy describing what is collected and how it is used before that collection happens. This finding is a heuristic: it means no privacy-policy page, route, or link was found in the parts of the repository this scan can read, not that one does not exist anywhere. It is common for the policy to be hosted on a separate marketing site or CMS this scan has no visibility into, so treat this as a prompt to double check rather than a confirmed gap.
How to fix it
Publish a privacy policy page and link to it from the site footer and from any signup/login form, and keep it in sync with what the code actually collects (forms, analytics, cookies). If the policy already exists outside this repository, add a link to it so at least the reference is discoverable in source.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo