Privacy
What we store
PluginView keeps the minimum needed to run scans, show your history, bill hosted usage, and meet security/audit obligations.
- Account data
- Email, optional display name, password hash (scrypt with documented parameters), email verification state, optional TOTP MFA secret, and session tokens.
- Scan data
- Submitted URL, scan metadata, sanitized detection results, visibility (private by default for signed-in users), optional share-token hash, and plan-based retention (
historyDays). Anonymous scans are unlisted with short TTL. - Security & billing events
- Security event log (logins, MFA, admin impersonation, deletions), billing/credit ledger entries required for accounting, and admin audit actions.
- Never sold
- Scan data is not sold. Private scans are not publicly enumerable; share links are deliberate and revocable.
- Retention & deletion
- Cron purges expired scans and rows past plan retention. You can delete individual history rows or request full account deletion in Settings (DSAR). Soft-deleted org data is purged after a grace period.
- SQLite at rest
- Hosted deployments currently use SQLite. Encrypt disks/backups at the infrastructure layer; see
docs/security/backup-restore.md. - Contact
- privacy@pluginview.com