VibeRaven

VibeRaven Privacy Policy

The VibeRaven privacy page explains how the product handles account information, scan-related project evidence, analytics, billing records, and support data.

Privacy context for scanner users

Production-readiness tools touch sensitive parts of the development workflow, so the privacy page should be indexable and understandable. Builders need to know what kind of project evidence is processed, how account and billing records are used, and where provider dashboard verification remains outside repo-code scans.

Important privacy areas

  • Account details used for sign-in, plan status, support, and product access.
  • Repo evidence used to create launch maps, gap summaries, and coding-agent prompts.
  • Operational analytics used to understand product health and improve onboarding.
  • Billing records handled by the configured payment provider rather than copied into crawler pages.
  • Provider dashboard settings that users must verify directly or through approved read-only integrations.
  • The hosted MCP server at viberaven.dev/mcp: no account, tool arguments are not stored, VibeRaven logs only the method, tool name, client name/version and success or error, and Vercel request logs are kept for no more than 30 days.

What does the full privacy policy cover?

Sixteen sections: the data controller, the personal information collected, how it is used, legal bases in the EEA, UK and Switzerland, subprocessors, disclosure, cookies and analytics, international transfers, retention and deletion, security, your rights and choices, children, third-party links, changes, governing law, and contact.

Which subprocessors does the policy list?

Supabase for authentication and database hosting, Google authentication services where used, Polar for payments, OpenAI for AI processing, Vercel for hosting and web analytics, PostHog for product analytics, and cloud hosting and CDN providers.

Do the local checks send my code anywhere?

The local 1.6.3 checks run on your machine. A full check from the Studio shows exactly what will be sent and asks you to confirm before anything leaves your machine.

Does crawler content include secrets?

No. SEO prerendered content describes the product and privacy topics. It must never include customer secrets, tokens, cookies, provider keys, or private repository data.