Privacy notice
What VibeShield collects, why, and how long we keep it.
Effective date: 2026-05-21. Operator: VibeShield Security (operator). For questions, open a GitHub issue on the repository. There is no monitored email inbox.
1. Data we process
- Account data: email, hashed password (bcrypt), display name, workspace name.
- Scan inputs: repository URL, branch reference, pasted code, manifest files. Source files are processed in an ephemeral worker and discarded after the scan completes — only redacted findings and metadata are persisted.
- Scan outputs: rule id, severity, title, file path, line number, redacted evidence snippet, fix guidance, confidence score, suppression flags.
- Operational data: API key hashes, session ids, audit log entries (action, actor, timestamp), rate limiting buckets.
- GitHub App data: installation id, repository full name, default branch, webhook secret. We never store the GitHub App private key in the database; it lives only as an environment variable on the runtime.
2. What we do not store
- Raw source files after a scan completes.
- Plain-text secret values. Secret-like strings are masked before findings are written.
- Plain-text API keys. Only a salted SHA-256 hash and a non-secret prefix are stored.
- Production environment variables of customer repos. Manifest files are read solely for CVE matching.
3. Legal basis (GDPR Art. 6)
Performance of contract (Art. 6(1)(b)) for delivering the scanner. Legitimate interest (Art. 6(1)(f)) for fraud prevention, abuse mitigation, and security audit logs. Consent (Art. 6(1)(a)) is requested separately before sending optional product email.
4. Subprocessors
- Vercel Inc. — hosting, edge network, function execution.
- Neon / Supabase / Vercel Postgres (whichever you point
DATABASE_URL at) — managed PostgreSQL for findings and metadata.
- GitHub, Inc. — source retrieval over the GitHub App API.
- osv.dev (Google) — public CVE advisory lookup for dependency scanning.
- SMTP provider (configurable via SMTP_HOST) — outbound email delivery if you enable email reports.
A current subprocessor list is maintained at /dpa.
5. Retention
- Scan findings and audit logs: retained for the lifetime of the workspace, deletable by the workspace owner via
DELETE /api/scans/<id> or workspace closure.
- Sessions: 14 days, refreshed on use.
- Rate limit buckets: 60 seconds in process memory.
- Ephemeral worker directories: removed at the end of every scan (or one hour idle, whichever is sooner).
6. Subject rights
Workspace owners can self-serve full deletion from the dashboard ("Close workspace") which removes every scan, API key, suppression, repository connection, and audit log we hold for that workspace within seconds. EU/UK/CA residents who cannot access the dashboard can open a GitHub issue referencing the email used at signup; we respond within 30 days.
7. Security
Passwords are hashed with bcrypt (cost 10). API keys are stored as SHA-256 hashes. Sessions are HttpOnly; Secure; SameSite=Lax. Webhooks must be signed with X-Hub-Signature-256. CSP, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy are enforced at the edge.
8. Changes
Material changes to this notice are announced at least 30 days in advance via in-product banner and email to workspace owners.