# The proof report: audit evidence for your DPO

Turn any refusal scan into a dated, printable proof report: method, findings, violation tables, Consent Mode analysis and a timestamped screenshot.

> Canonical: https://www.flowconsent.com/en/doc/proof-report
> Last updated: 2026-07-30
The proof report is a document, not a screen: the dated record of a "consent refused" scan, formatted to be handed to a DPO, an auditor or a supervisory authority. Everything in it was archived **at scan time** — verdict, detailed violations, Consent Mode analysis, timestamped screenshot — the report only lays that evidence out, ready to print.

## What the report contains

- **Header** — the scanned URL, the verdict badge, the exact date and time of the check, and a one-line summary.
- **Method** — what makes the document defensible: the page was loaded in a real browser from a **European vantage point**, consent was **refused** (or, absent a reject button, nothing was interacted with), and everything that still executed was recorded. The refusal mode used and the second navigation URL, if any, are stated.
- **Findings** — four counters: tracker domains contacted, trackers identified by signature, non-essential cookies set, storage entries written.
- **Violation tables** — one table per finding type: tracker domains with the service, request count and a sample URL; signature detections with the identifiers found; cookies with domain, party and expiry; local/session storage keys (same legal regime as cookies).
- **Google Consent Mode** — cookieless `gcs=G100` pings are listed as **compliant with the refusal, not counted**; any hit announcing a granted consent to Google despite the refusal is flagged as an **aggravated violation**.
- **Visual evidence** — the screenshot captured during the scan, straight from the archived evidence store.
- **Footer** — check ID, banner ID, and the previous check it regressed from, when applicable.

## How to generate it

Open **Scan history** in the dashboard (`/dashboard/scan-history`), or a banner's Compliance tab, and click the **Report** button on any verification. The report lives at `/dashboard/scan-report/<check-id>` — a stable address you can revisit as long as the check exists in your workspace.

## PDF: just print it

The report page renders without dashboard chrome — no sidebar, no navigation. Click **Print / PDF** (or press ⌘P / Ctrl+P) and save as PDF from the browser dialog. There is no export pipeline to configure: the printed page **is** the document.

## Why it holds up

- The data is **archived by the scan**, not recomputed later: the report shows what was observed at that date, even if the site has changed since.
- The screenshot is captured **during** the scan, from the same session that recorded the network traffic.
- The check ID printed in the footer links the document back to the raw record in your workspace.

> [!TIP]
> For recurring proof, put your key pages under [continuous monitoring](/en/doc/compliance-monitoring): each automatic verification is archived the same way, so evidence accumulates weekly without anyone remembering to scan.