How we handle your scan data

Authenticated scans store scores, tracker inventories, consent findings, gap labels, generated templates, report summaries, and limited HTML or text snippets needed to produce results. Free public scans return findings and keep a shareable tokenized report for 14 days, then delete it. Security logs (for example IP rate limits) may persist 30–90 days.

Only limited HTML or text snippets required to produce the report. We do not keep a full site archive or a copy of the target’s entire JavaScript bundles.

Scan results and generated artifacts stay while they are tied to an active account; you can delete individual scans in the product. Closed accounts follow the account window (up to 24 months, or sooner on a valid deletion request). Free public scan reports expire after 14 days.

You can access scans in your account. Production systems are access-controlled and limited to Vassbrekke AS operators on a least-privilege basis. Other customers cannot see your dashboard. Passwords and API keys are stored hashed.

Application hosting and the database are operated by Vassbrekke AS in Norway / the EU. Recipients include Stripe (payments), optional Google and GitHub OAuth, optional Google Ads conversion after marketing consent, xAI for AI summaries on authenticated scans, Proton Mail for transactional email, and optional Resend. You may also send alerts to endpoints you configure.

Primary application hosting is operated by Vassbrekke AS in Norway / the EU. Some subprocessors process data in the United States (Stripe, Google, GitHub, xAI, and optional Resend).

We do not use customer scan data to train foundation models. Authenticated scans may send scan metadata (URL, score, tracker names, gap labels) to xAI (Grok) in the United States to draft a summary or policy text. We request that xAI does not store the prompt or response. We do not use OpenAI or a self-hosted Ollama instance for PrivBeacon production AI features.

There is no per-customer AI opt-out today. Authenticated scans may use xAI to draft summaries; if that request fails, we fall back to templates.

TLS in transit. The Proxmox host that stores application volumes uses LUKS. The application VM is not separately encrypted. We do not claim application-level field encryption of scan snippets.

No independent pentest, SOC 2, or ISO 27001 certification is published yet. That absence is honest, not a claim that those reviews exist privately.

The on-prem agent source is published at https://github.com/Vassbrekke/PrivBeacon-On-Prem. It is offline-first: reports stay on disk unless you enable optional cloud sync. We have not published a third-party audit of the agent.

No. 75 is PrivBeacon’s own qualifying score after a real scan. Certified Private is our product badge with a public verify page. It is not a regulator certification and is not legal advice.

Cloud scans run on the PrivBeacon application host in Norway/EU. Headless Chromium fetches the public URL, executes JavaScript, waits for hydration, and scrolls for lazy content. It does not click consent, fill forms, or log in. Outbound requests block private and metadata IPs. Scans use the host’s provider IP, not a rotating proxy pool.

Paid sites get a monthly baseline scan; Pro/Enterprise can enable daily or weekly. Scheduled failures retry once. Pending scans are recovered after restart; scans stuck running over 20 minutes are marked failed. Email/webhook alerts are best-effort with no delivery SLA. Statuses: not scanned, queued/scanning, scan failed, no issue found, or issues found. “No issue found” is not a legal all-clear.

No screenshots are taken. Cookie values are not stored; cookie names may be read in memory to detect a CMS and are not saved on the scan record. The scanner does not fill or submit forms. Stored snippets strip input/textarea/select contents and redact email-like strings and long digit sequences. Full HTML and JavaScript bundles are not archived.

Authenticated scans keep results JSON, generated policy/banner/DSAR drafts, and the AI or template summary while the scan exists on your account. You can delete individual scans in the dashboard. Free public reports expire after 14 days. Closed accounts follow the account retention window (up to 24 months, or sooner on a valid deletion request).

Delete scans from Dashboard → Scans. Remove a site to delete that site and its scans. For account deletion, use the DSAR form or email privacy@privbeacon.com. We delete or anonymize personal data we control, subject to legal retention (for example billing records).

Hosting and PostgreSQL are operated by Vassbrekke AS in Norway / EU. Recipients: Stripe, Google (OAuth), GitHub (OAuth), Google Ads, xAI, Proton Mail (SMTP), Resend, Hosted infrastructure operated by Vassbrekke AS, Customer-configured endpoints. TLS in transit. The Proxmox host uses LUKS; the application VM is not separately encrypted; we do not claim field-level encryption of snippets. Access is limited to Vassbrekke AS operators on a least-privilege basis. Other customers cannot see your dashboard. Passwords and API keys are stored hashed. Revoked API keys cannot authenticate.