Skip to content

Privacy and retention

Short version: samples are stored only to analyse them, reports keep technical findings, and public reports do not reveal who submitted them.

What is stored

  • Sample bytes in isolated object storage under a random key derived from the SHA-256, never inside a web root.
  • Hashes (SHA-256, SHA-1, MD5) attached to the report permanently.
  • Technical findings: detected type, metadata, static findings, YARA matches, vendor statuses and timings.
  • Account data when you register: email, display name, password hash (PBKDF2-SHA256, 210,000 iterations).
  • A salted hash of the client address for rate limiting and abuse detection. The raw IP is not stored.

Retention

Sample files are removed by the maintenance job after the configured window (48 hours by default). Reports keep their technical results so a hash can be re-checked later. Password reset tokens expire after 30 minutes and are stored only as a hash.

Who can see a report

Anonymous scans produce unlisted reports: anyone who has the report ID can open the report, but it is not listed anywhere and its owner is shown as anonymous. Scans created while signed in are visible only to their owner and to administrators. Sample bytes are never downloadable through a report.

Security practices

How submissions are handled

Upload handling

Size limits are enforced while streaming, content is identified from magic bytes, and files are written with random names outside any served directory. Files are never executed on the API host.

URL fetching

Loopback, private, link-local, reserved and cloud metadata addresses are blocked. Resolved IPs are pinned, redirects are re-validated, proxy environment variables are ignored, and responses are size-capped.

Credentials and keys

Provider API keys live in server-side environment variables and are never sent to the browser. The browser only receives public provider availability flags.

Application security

Parameterised database queries, strict response security headers, rate limits on scans and authentication, no cookie-based sessions (bearer tokens only, stored by the client), and escaped output in the report renderer.

Third-party services

When an operator configures a provider, hashes, URLs or file content may be sent to that provider for analysis, subject to that provider's own terms and privacy policy. Providers used by default are only called when configured: VirusTotal, MetaDefender Cloud, Google Safe Browsing, URLhaus, PhishTank and RDAP. Local analysis (static inspection, YARA, ClamAV) stays on your infrastructure.

Deletion. To remove a report, contact the operator of this deployment with the report ID. Deleting an account removes its scans and history from the account view; unlisted reports are removed with their samples by the retention job.

This page describes the reference deployment. Operators may change limits, retention and provider configuration; the values above reflect the defaults in the repository.