Back home
VibeCompass

Last updated October 19, 2026

Privacy Policy

VibeCompass is project memory for AI-assisted development. That means repository context can be sensitive. This policy explains what is read, what is stored, what may be sent to AI providers, and how deletion works.

What VibeCompass reads

When you use the local package only, project memory files stay on your machine unless you explicitly push or submit hosted review output.

When you connect GitHub or use the hosted dashboard, VibeCompass reads the repository metadata and source files needed to build project memory, run scans, generate proposals, and keep the dashboard current.

When you connect MCP, the MCP server reads project memory so your coding tool can retrieve context during a session.

What may be sent to AI providers

AI-assisted scans and docs-review requests may send relevant repository snippets, diffs, file paths, existing architecture docs, decisions, and session context to Anthropic so a model can generate project-memory output.

VibeCompass sends the minimum practical context for the requested workflow. It does not intentionally send secrets, and you should not commit secrets to repositories or project-memory files.

Anthropic states that standard API inputs and outputs are deleted within 30 days unless a different agreement applies, such as zero data retention, or retention is required for safety, policy enforcement, or law. VibeCompass may enable stricter retention settings where available for its account.

What VibeCompass stores

Account data such as your email, GitHub identity, project records, sync credentials, API key hashes, and billing state when billing is enabled.

Project memory such as domains, features, components, decisions, conflicts, session summaries, sync runs, proposals, docs-review artifacts, and revision metadata.

Waitlist signups, including email address, source, referrer, user-agent, and timestamps, so we can send product updates and beta invitations.

Optional product analytics events processed by PostHog only after you accept optional analytics. These events may include page navigation and usage events. When you are signed in, analytics may be associated with your account user ID and email address.

Error reports processed by Sentry so we can diagnose production failures. Error monitoring runs for every visitor, whatever your analytics choice. A report can include technical context: the error, your browser and operating system, the address of the page where the failure happened, and the steps just before it, such as page changes and network requests.

Session replay processed by Sentry, only after you accept optional analytics. A replay records how the page changed and where you clicked or scrolled, with all text, form inputs, and media hidden. About one in ten visits with analytics allowed is recorded. Otherwise your browser keeps only about the last minute and sends it if an error happens. If you decline, or turn analytics off later, replay stops and anything not yet sent is discarded. Replays already sent are kept under Sentry’s retention terms, and you can ask us to delete them.

Retention and deletion

Local project-memory files remain under your control and can be deleted from your own repository or filesystem.

Hosted project data is retained while your account or project remains active. Account deletion removes hosted account data and associated project records from the live application, subject to backups, security logs, and legal obligations.

You can request deletion or export help by emailing privacy@vibecompass.dev from the address associated with your account or waitlist signup.

Security boundaries

API keys are stored as hashes. VibeCompass cannot show an API key again after creation.

Hosted proposal review does not silently overwrite local-primary project-memory files. You export and apply accepted output locally, then push to confirm canonical state.

VibeCompass uses infrastructure, monitoring, and analytics providers such as Vercel, Supabase, Sentry, and PostHog to host the application, store product data, diagnose failures, and understand product usage.

If you accept optional analytics, PostHog may use first-party browser storage for analytics state and may process analytics data in the United States depending on the configured PostHog project region and provider terms. Sentry session replay keeps a replay identifier in your browser’s session storage so a replay continues across page loads.

Your analytics choice

Optional analytics covers PostHog product analytics and Sentry session replay. Your choice is saved in this browser only, so another browser or device asks again. Error monitoring is not part of this choice.

Checking this browser’s choice…

Contact

Questions or deletion requests: privacy@vibecompass.dev