So funktioniert der Scan-Score

Where scans run. Authenticated and scheduled scans run on the PrivBeacon application host operated by Vassbrekke AS in Norway / EU. Free public scans use the same host but a static HTTP fetch (no headless browser) and a tighter time budget. The Raspberry Pi / on-prem agent is a separate trust boundary: it runs on your network and only talks to PrivBeacon if you set an API key and sync URL.

How browsers are controlled. Cloud scans launch headless Chromium (Playwright). Outbound requests are DNS-resolved, pinned to those addresses, and blocked if they resolve to private, loopback, link-local, or metadata IPs. Heavy resources (images, media, fonts) are skipped. The browser uses a desktop Chrome user-agent, waits for hydration, and scrolls to load lazy content. It does not click Accept/Reject, fill forms, type credentials, or submit personal information.

Pages and interactions. Each scan fetches the URL you add, then discovers privacy, cookie, and legal pages (typically up to 24 additional URLs, fewer on public/fast scans). Optional path exclusions skip prefixes such as /account or /checkout. Authenticated or staging sites that are not on the public internet cannot be reached by the cloud scanner — use the on-prem agent on a network you are authorized to test.

JavaScript. When Chromium launches, JavaScript on the page runs. Trackers injected after load, iframe pixels, and inline snippets (gtag, fbq, _paq) can be observed. If the browser cannot start, the scan falls back to a static HTML fetch and records that limitation. JavaScript-only banners and tags that never appear in HTML or network requests may be missed.

IP addresses. Scans originate from the application host’s provider-assigned public IP in Norway/EU. PrivBeacon does not use a rotating residential proxy pool. The address may change if the host is rebuilt. We do not publish a guaranteed allowlist from this page — email support@privbeacon.com for the current egress IPs if you need to permit our scanner.

Sensitive sites. Do not put real passwords in scan URLs. URLs with embedded credentials are rejected. Do not point the cloud scanner at pages that display other people’s personal data. Use path exclusions for account, checkout, and admin areas. Form fields in stored snippets are stripped; emails and long numbers in snippets are redacted. Never submit real personal information during a scan — the scanner will not fill forms for you.

PrivBeacon ruft die öffentliche Website ab, die Sie autorisieren, und prüft Tracker, Cookies, Einwilligungssignale und Richtlinientexte, die tatsächlich erscheinen. Ein Einwilligungsbanner gilt nicht als Nachweis, dass Tracker blockiert bleiben.

Das Scoring startet bei 100 und zieht Befunde ab. Die Zahlen entsprechen der Produkt-Engine.

Every score point maps to evidence: a tracker request or snippet, a consent issue (banner, pre-consent tags, missing privacy or opt-out link), or a failed keyword check on a policy page. Trackers, cookies, scripts, and network hosts are technical findings. Failed law checks are heuristic presence tests on the text we fetched — they are not a legal conclusion about your contracts, lawful basis, or DPIAs. The score is a PrivBeacon heuristic, not a percentage of legal compliance, and it is not legal advice.

Schedules. Every paid site that is not on-prem is due for a monthly baseline scan (720 hours). Pro and Enterprise can enable daily or weekly scans per site. Cancelled or unpaid accounts are not scanned. Removed sites are deleted and are not scanned.

Retries. If a scheduled scan fails, the worker retries once after a short delay. Scans left pending after a process restart are re-queued. Scans stuck in “running” for more than 20 minutes are marked failed.

Outages. If the monitor cron or the application is down, due sites are not scanned during the outage. After recovery, sites that are still due are picked up on the next cron run. Missed ticks are not backfilled beyond “is this site due now?”. There is no promised scan SLA.

Alerts. Score drops of more than 5 points and newly detected tracker vendors create in-app alerts. Optional email and HTTPS webhooks are best-effort: one attempt, 10-second timeout, private-IP webhooks blocked. Delivery is not guaranteed and is not an SLA.

Timestamps. Each scan stores created time, completed time (when successful), trigger (manual, scheduled, CI, or agent), and status. Historical complete and failed scans remain in your account until you delete them or the account retention window ends.

Statuses. Not scanned — no scan record yet. Scan queued / scanning — in progress. Scan failed — the fetch did not finish (reason stored). No issue found — a complete scan with no listed trackers, consent issues, or focused law gaps. Issues found — a complete scan that listed at least one finding. “No issue found” is not a legal all-clear.

Eine Site kann das Abzeichen anzeigen, nachdem ein echter Scan 75+ erreicht und die Zertifizierung aktiviert ist. Score 75+ qualifiziert nach einem echten Scan für das eigene Certified Private-Abzeichen von PrivBeacon. Es ist keine Regierungs- oder ISO-Zertifizierung.

Ein Website-Scan kann Ihre Rechtsgrundlage, Verträge, Rollen als Verantwortlicher/Auftragsverarbeiter, Übermittlungsmechanismen, Aufbewahrungsentscheidungen, Interessenabwägungen oder interne Prozesse nicht feststellen. Dafür sind Beratung und Ihre eigenen Unterlagen nötig.

KI-Zusammenfassungen bei authentifizierten Scans sind eine Schreibhilfe. Die Produktion nutzt xAI (Grok) auf Scan-Metadaten. Erkennung und Scoring sind regelbasiert. KI ist keine Rechtsberatung.