VibeGuard Legal
Privacy Policy
Effective October 23, 2026
This policy explains what VibeGuard collects, why it is needed, and the choices available to you.
Source code and audit data
VibeGuard analyzes submitted source code in application memory and does not persist raw source code in its database by default. Saved audit history contains report metadata and detected rule identifiers, not the submitted file contents. Repository files imported from GitHub or GitLab are fetched for the requested analysis and are not stored as a source-code archive.
Account and learning data
When you create an account, VibeGuard stores account identifiers, profile details, usage totals, audit history metadata, learning progress, and subscription status so it can provide quotas, saved progress, and account features.
Repository connections
If you connect GitHub or GitLab, VibeGuard stores the minimum connection details needed to access repositories you authorize. Access credentials are encrypted before database storage. You can disconnect a provider to remove the saved connection.
Payments
Stripe processes card details and payments. VibeGuard stores Stripe customer, subscription, price, status, and renewal references, but does not receive or store complete payment card numbers.
Service providers and disclosure
VibeGuard uses service providers such as Supabase for application data and authentication, Stripe for billing, and GitHub or GitLab when you request repository access. Data is shared only as needed to operate those features, comply with law, protect users, or investigate abuse.
Retention and your choices
Account and subscription records are retained while needed to provide the service, meet legal obligations, resolve disputes, and prevent fraud. You may disconnect repository providers, cancel billing through Stripe, or contact support to request account-data access or deletion.
Security and changes
VibeGuard uses access controls, row-level database policies, encrypted integration credentials, and signed billing webhooks. No system is perfectly secure. Material policy changes will be reflected on this page with an updated effective date.