How to Read a Patrol Scan Report
A Patrol scan report runs from summary to evidence. The top of the page gives a verdict and a handful of headline numbers, and each section below adds detail until you reach the raw network records. This article explains each section in order and how to interpret it. To run a scan first, see How to Run a Website Scan in Patrol.
Report header
The header identifies the scan and holds the report’s actions.
Item | What it shows |
|---|---|
Scan number | A reference for the scan, in the form SCN- followed by eight characters. |
Captured | The date and time the scan ran. |
Region | The location the scan ran from, for example California. A site that changes its banner by location may behave differently for visitors elsewhere. |
Took | How long the scan ran. |
Hash | A SHA-256 fingerprint of the scan record. Select Copy to copy it. |
The buttons beside the header are Compare, Add to Project, Share, and Download PDF. See How to Export, Share, and Compare Patrol Scan Reports and How to Scan Multiple Websites and Organize Scans with Projects in Patrol.
Some reports show a Flagged for internal review notice. It means the Captain Compliance team has marked the scan for a closer look and the results may change. Select Report Issue to send the reviewer a correction or extra context.
Verdict and headline numbers
The verdict is a single line, for example Likely Non-Compliant in 20 states on a United States scan. The word Likely matters: the verdict is an automated assessment of what the scanner saw, not a legal conclusion.
Six tiles under the verdict summarize the consent experience:
Tile | What it tells you |
|---|---|
Banner shown | Whether a consent banner appeared and, if so, how quickly. |
Reject button | Whether the banner offers a way to decline. |
GPC honored | Whether tracking changed when the browser sent the Global Privacy Control signal. |
3rd-party cookies | How many cookies were set by domains other than the site’s own. |
IAB TCF v2 | Whether the advertising industry’s consent framework was detected. |
Pre-checked categories | Whether any consent categories were already switched on when the banner opened. |
Four counters follow: Cookies set, 3rd-party cookies, Pre-consent trackers, and Findings. The Findings counter breaks the total down by severity, for example 4 strong, 3 informational.
Two sites can share the same verdict and still be very different. Read the counters and the findings before you draw a conclusion. See How to Assess a Website’s Privacy Risk with Patrol: Basic, Standard, and Deep Checks.
What we check for
This section lists the twelve checks behind the verdict. Each tile shows a result and a sentence that states what the scanner saw. Select a tile to jump to the finding or evidence behind it.
Check | The question it answers |
|---|---|
Consent banner | Did a consent banner appear? |
Reject button present | Is there a reject option alongside accept? |
Opt-out / Do-not-sell link | Can a visitor find an opt-out link, such as Do Not Sell or Share My Personal Information? |
Honors GPC | Did trackers stop when the browser sent the |
Pre-checked categories | Do consent categories arrive already selected? |
Neutral banner copy | Is the banner’s wording neutral? |
IAB TCF v2 string | Does the site expose the IAB Transparency and Consent Framework API? Optional. |
IAB GPP signal | Does the site expose the IAB Global Privacy Platform API? Optional. |
Accept & reject equal weight | Are the accept and reject buttons presented with equal prominence? |
3rd-party cookies pre-consent | Were third-party cookies set before the visitor made a choice? |
Privacy policy linked | Does the page link to a privacy policy? |
Sensitive-data flow | Does the page collect sensitive personal information? A standard scan doesn’t trigger these flows. |
Each check shows one of four results:
Result | Meaning |
|---|---|
Yes | The check passed. For example, 3rd-party cookies pre-consent shows Yes when zero cross-site cookies were set before a choice. |
Fail | The check didn’t pass. |
Not in use | The site doesn’t use an optional capability, such as an IAB framework. This is not a failure and doesn’t affect the verdict. |
Not tested | The check couldn’t run. For example, banner wording can’t be tested when no banner is detected. Treat it as unknown, not as a pass. |
Banner anatomy
When the scanner detects a banner, this section records how it was built: the background color, text color, font size, and size of the buttons, and any categories that arrived pre-checked. Use it to judge whether Reject is as easy to see and select as Accept.
Findings
Findings are the core of the report. Each numbered finding has a severity, a title, a plain-language explanation, the statutes it likely implicates, and the evidence captured, such as the names of the trackers or cookies involved. Under Related files, each finding links to its supporting material, such as the pre-consent screenshot, the after-reject screenshot, the banner’s HTML, and the network archive (.har).
Severity describes how strong and reproducible the captured evidence is. It is not a recommendation or a legal ruling.
Severity | How to read it |
|---|---|
Strong | The scanner captured clear evidence of the issue. Start here. |
Moderate | The issue was observed, with less direct evidence of impact. For example, no opt-out mechanism on a page where no trackers fired. |
Informational | Context, not a problem in itself. Informational findings often record permitted or good behavior, such as GPC signal is honored. |
Findings you may see include:
Finding | What it means |
|---|---|
No consent/opt-out mechanism detected | The page gives visitors no way to decline tracking. The finding states how many trackers were active. |
No privacy opt-out link found | The page has no dedicated link such as Do Not Sell or Share My Personal Information or Your Privacy Choices. |
Targeting trackers ignore GPC signal | Advertising trackers kept loading after the browser sent the GPC signal. The finding names them. |
Third-party cookies persist despite GPC signal | Third-party cookies weren’t cleared or blocked when the GPC signal was present. |
Tracker fires despite rejection | A tracker kept running after the scanner selected Reject. |
Third-party cookies persist after rejection | Cookies from other companies remained after Reject. |
Dark pattern: consent categories pre-checked | The banner opened with consent categories already switched on. |
TCF consent string is invalid or missing | The site exposes the IAB framework, but the consent signal that advertising vendors read is missing or malformed. |
Third-party cookies active (permitted under opt-out model) | Informational. U.S. state laws generally allow these cookies by default, as long as they stop when a visitor opts out. |
Analytics trackers remain active with GPC signal | Informational. GPC targets the sale or sharing of personal information for advertising, so analytics trackers generally aren’t required to stop. |
GPC signal is honored | Informational and positive. Trackers and third-party cookies were reduced or eliminated when GPC was on. |
If a tile near the top of the report and a finding seem to disagree, rely on the finding and its evidence, and select Report Issue so the Captain Compliance team can review the scan.
Scan coverage
Scan coverage lists exactly which tests ran, so you know how much weight the verdict can bear. It confirms whether a banner was detected, whether Accept and Reject were selected, whether the GPC pass ran, whether cookies and trackers were inventoried in each phase, how many screenshots were captured, and whether the network archive was saved. It also states what the scan didn’t cover: signed-in pages, mobile layouts, forms that collect sensitive data, and children’s flows.
By jurisdiction
On a United States scan, this section maps the findings to 20 state privacy laws: California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, and Virginia.
Use the filters All, Findings present, Adjacent, and Compliant to narrow the list.
Sort by severity, state name, or statute name.
Select a state to see each requirement the scanner checked, what it observed, and the legal citation.
Cookies and trackers
This section shows what was stored and what was contacted in each phase of the scan. Each phase tab shows two numbers: cookies stored and third-party hosts contacted.
Phase | What it captures |
|---|---|
Before consent | The first visit, before the visitor has interacted with a banner. |
After Accept | The page after the scanner accepted. |
After Reject | The page after the scanner rejected. |
With GPC | The page loaded with the Global Privacy Control signal on. |
When no banner is detected, there is nothing to accept or reject, so only Before consent and With GPC appear.
For each phase, a table lists every cookie with its name, domain, category, and expiry. The categories are Strictly Necessary, Functionality, Performance, Targeting, and Unclassified. A second list, Third-party hosts contacted, names every outside domain the browser reached.
Screenshots, request log, and scan record
Screenshots are grouped by scan phase. Select a thumbnail to open the full-size capture.
The request log lists every request the browser made, in order.
The scan record is the machine-readable output of the scan, a file named
scan-record.json, shown with its SHA-256 hash.
Keep these limits in mind
A report describes one page at one moment, from one location, for a logged-out visitor on a desktop browser.
Not tested means unknown. It doesn’t mean the site passed.
The verdict and statute references are automated assessments, not legal advice. Have counsel review anything you plan to act on.
