VibeShieldVibeShield

Privacy Policy

Last updated: October 17, 2026

This policy explains what data VibeShield ("VibeShield", "we", "us") collects through the hosted web app at usevibeshield.com, why, and the choices you have. Website audits inspect URLs you submit. Business also supports GitHub repository scans and configured pull-request monitoring. Website audits do not require login credentials for the target app.

1. Information we collect

  • Free scans without an account — the URL you submit, findings, check outcomes, coverage notes, scan timing and request counts, and your IP address (used for rate limiting and abuse/audit records). The results can only be opened in the browser that started the scan, using a random token stored in that browser. If you don't save the scan to an account, it's deleted automatically after 30 days.
  • Account information — your name, email address, date of birth, and password. Date of birth is used only to confirm you are at least 16. It is not shown on your public profile and is not used for marketing. Passwords are hashed (bcrypt) before storage; we never store or can look up your password.
  • Domain verification — hostnames you add, a stable verification key we generate for each, and whether verification succeeded (including which method you used). To verify ownership we fetch your public homepage or a /.well-known/vibeshield-verification.txt file from the hostname you claim — we do not store the full page HTML long term, only the verification outcome and timestamp.
  • Scan data — the target URLs you submit, findings and reports, attack-surface data, and a log of the requests a scan made. Secret values found in a scan (API keys, tokens) are redacted before they're stored — website findings may retain a short prefix; Gitleaks secret evidence is fully redacted.
  • GitHub repository scans — repository owner/name, selected commit, file paths, line numbers, findings and coverage notes. We fetch source/configuration files through GitHub to run static checks and Gitleaks locally; repository code is not executed. Temporary snapshot files are removed after the scan succeeds, fails or is cancelled. Reports may retain source excerpts for non-secret findings. Dependency names and versions are sent to OSV.dev to look up known advisories.
  • Your app's Supabase project — when your app's public code contains a Supabase URL and public key, the scan asks your Supabase project which tables that key can read and how many rows each has. We request row counts only — never the rows themselves — and we don't store your key.
  • Shared reports — if you create a public share link, anyone with that link can view that report (without the request log) until you turn sharing off.
  • Paid-plan integrations — if you use them: your company name and logo URL for white-label reports (Pro and Business); and on Business, a GitHub token (encrypted at rest), a Slack or Discord webhook URL (encrypted at rest), deploy-hook secrets, and CI API keys (we store only a hash of each key).
  • Billing data — Pro and Business are sold through our third-party payment provider, which acts as the merchant of record. We never receive your card number; we only receive the customer and subscription ids that provider assigns, the subscription status, and its renewal or end date.
  • Security & audit logs — sign-ins, scans and account changes, with a timestamp and IP address, to detect abuse and investigate incidents. These logs never contain passwords, tokens or secrets.
  • Cookies & browser storage — one essential, HTTP-only session cookie keeps you signed in. Your browser's local storage holds a few preferences (sidebar layout, the AI tool you build with) and free-scan tokens. Google Analytics may set a cookie so we can see how the site is used (pages viewed, roughly where a visit came from, and the device type). That cookie is set only if you accept analytics on the banner. Rejecting leaves the session cookie and does not load Analytics. We do not sell personal information and we do not use advertising pixels.

2. How we use this information

  • Run the scans you ask for, and show you your scans, verified domains, projects and reports;
  • Run the monitoring you turn on — scheduled scans, deploy scans, and alerts about new serious issues;
  • Maintain your account and enforce plan limits, such as the monthly scan quota and free-scan rate limit;
  • Secure the service — rate limiting, abuse detection and incident investigation;
  • Measure the website with Google Analytics, and review search performance in Google Search Console;
  • Answer AI-assistant questions and enhance technology detection on eligible scans when configured; and
  • Send email only about your account or something you asked for — verification, password reset, contact replies, and scan alerts you turned on. We do not send marketing newsletters.

"Copy AI fix prompt" builds the prompt in your browser from your report. It isn't sent to us or to any AI provider — you choose where to paste it.

3. Who we share data with

We don't sell your data. We share it only with the providers needed to run VibeShield:

  • Our database and hosting infrastructure, to store your account and scan data;
  • Our email provider, to send account and alert emails — your email address and the message content;
  • Slack, Discord or ClickUp, when you configure an integration — selected alert content is sent to that destination;
  • Anthropic and/or OpenRouter, for AI-assistant questions and scan context, or eligible AI technology detection using filtered page-head tags, script/stylesheet paths and selected headers. Technology detection does not send the page body or JavaScript source;
  • GitHub, for repository scans, configured Watch events and pull-request comments. A token is required for private repositories and actions needing repository permissions;
  • OSV.dev, for dependency package names and versions used in advisory lookups; Gitleaks runs in our backend without sending source files to a Gitleaks service;
  • Our payment provider (acting as merchant of record), to sell Pro or Business, take payment, handle tax and manage your subscription;
  • Google, for Analytics and Search Console. Search Console is a site report for us — it does not follow a visitor around the web; and
  • Law enforcement or other parties, only where required by law or to protect our legal rights.

4. Data retention

Unsaved free scans are deleted after 30 days. Account and scan data is kept while your account is active so your history stays available, subject to product retention limits. GitHub scan history keeps the newest 100 scans per account; temporary source snapshots are not retained as repository archives. You can delete your account and its data yourself from Settings. If you cannot sign in, email contact@usevibeshield.com and we'll process it within a reasonable time.

5. Security

Passwords are hashed with bcrypt; GitHub tokens and alert webhooks are encrypted at rest; API keys are stored only as hashes; session cookies are HTTP-only; and secrets found during a scan are redacted before storage. No method of storage or transmission is 100% secure, but we build VibeShield the way we'd expect an app we scanned to be built.

6. Your rights and choices

You can update your profile, turn off sharing, disconnect integrations and revoke API keys from Settings and your reports. PDF and JSON report downloads are available on eligible plans. For access, correction, deletion or portability requests beyond the available product controls, contact contact@usevibeshield.com. Depending on where you live you may have further rights under laws like the GDPR or CCPA; we honor equivalent requests from everyone, regardless of location.

7. International users

Your data may be processed in a country other than the one you live in. For Pro and Business payments, our third-party payment provider handles the tax and payment-compliance obligations of international billing as the merchant of record.

8. Changes to this policy

We'll update the "Last updated" date above when this policy changes, and for material changes we'll make a reasonable effort to let you know.

9. Contact

Questions about this policy? Email contact@usevibeshield.com.

This policy is written in plain language for clarity and does not constitute legal advice.