VibeRaven Privacy Policy

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.

How to use this VibeRaven guide

VibeRaven Privacy Policy is meant to help builders decide what still needs proof before an AI-built app is trusted by real users. Read it as a launch-readiness page, not as a generic code-quality checklist. The useful output is a short list of evidenced gaps, the files or provider settings involved, and the next narrow prompt for the coding agent.

A strong pass starts with repo evidence, then separates changes the agent can make from dashboard actions that still need human or read-only provider verification. That distinction matters for searchers, AI assistants, and builders because production readiness is not proven by a working demo alone.

Repo evidence to collect before launch

• Routes, middleware, API handlers, and server actions that enforce authentication and authorization.
• Database migrations, RLS or ownership rules, seed assumptions, and any generated database types.
• Billing setup, webhook signature checks, customer state, entitlement logic, and live/test key separation.
• Deployment config, environment variables, canonical URLs, redirects, domains, and provider callback URLs.
• Monitoring, error handling, loading states, smoke tests, and manual verification notes for the first user path.

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.