How to Assess a Website’s Privacy Risk with Patrol: Basic, Standard, and Deep Checks
You don’t need a privacy background to tell whether a website carries tracking-related risk. This guide shows how to read a Patrol scan at three levels of depth, so you can spend two minutes on a low-stakes review and half an hour on a decision that matters. It is written for anyone who has to judge a website they don’t run, for example during due diligence, a vendor review, or a policy application or renewal.
Level | Time | What you look at | What you get |
|---|---|---|---|
Basic | About 2 minutes | The verdict, tiles, and counters at the top of the report | A quick sort into lower, medium, or higher concern |
Standard | About 10 minutes | The findings, scan coverage, and state-by-state view | A reasoned view of what is wrong and how serious it is |
Deep | 30 minutes or more | The cookie tables, screenshots, network records, and repeat scans | Evidence you can keep on file and defend |
Start with the basic check on every site. Move to the next level when you see a red flag, when the result is unclear, or when the decision is large enough to justify the time.
Why website tracking creates risk
Most websites load tools from other companies: advertising networks, analytics services, social media pixels, video players, and chat widgets. These tools, called trackers, send information about each visitor to those companies. Privacy laws and a growing number of lawsuits focus on whether the site told visitors about this, gave them a real choice, and respected the choice they made.
The patterns that draw complaints are consistent, and Patrol tests for each of them:
Trackers that run without any notice or choice.
A banner that offers a choice the site then ignores.
A browser-level opt-out signal that the site doesn’t honor.
A banner designed to steer visitors toward accepting.
Terms you need
Term | Plain meaning |
|---|---|
Consent banner | The pop-up that asks visitors whether they accept cookies and tracking. |
Tracker | A tool from another company that collects data about the visit, usually for advertising or analytics. |
Third-party cookie | A small file stored in the visitor’s browser by a company other than the site’s owner, often used to recognize the visitor across websites. |
Pre-consent | Anything that happens before the visitor has made a choice. |
Ungated script | A tracker that runs no matter what the visitor chooses, because nothing holds it back until consent is given. |
Opt-out link | A link, often in the footer, such as Do Not Sell or Share My Personal Information or Your Privacy Choices. |
Global Privacy Control (GPC) | A browser setting that automatically tells every site the visitor opts out of the sale or sharing of their data. |
For more definitions, see Glossary of Consent and Privacy Terms.
Before you start
Run a scan of the site’s home page. For a site with U.S. visitors, keep the default regulation, United States (all state laws). See How to Run a Website Scan in Patrol.
Open the report when the scan shows Completed.
If the report says Scan blocked, you have no result. Don’t treat it as a pass. Scan again, or select Report Issue.
Level 1: basic check (about 2 minutes)
Stay at the top of the report and read the six tiles and four counters under the verdict.
Signal | Lower concern | Higher concern |
|---|---|---|
Banner shown | Yes | No, while trackers or third-party cookies are present |
Reject button | Present | Missing |
GPC honored | Yes | No, with advertising trackers present |
Pre-consent trackers | 0 | Any. The more there are, the greater the exposure |
3rd-party cookies | 0 or a handful | Dozens or hundreds |
Pre-checked categories | None | Any |
Findings | Informational only | One or more marked strong |
Don’t stop at the verdict line. Two sites can both read Likely Non-Compliant in 20 states and be far apart in practice. One may set hundreds of third-party cookies and fire a dozen advertising trackers with no banner at all. Another may set no third-party cookies and fire no trackers, and be flagged only because it lacks an opt-out link. The counters tell them apart.
Use the tiles and counters to sort the site:
Sort | Typical pattern | Next step |
|---|---|---|
Higher concern | No banner or no reject option, with trackers before consent. Or GPC not honored, with advertising trackers present. | Do the standard check, and consider the deep check. |
Medium concern | A banner is present, but there are strong findings or pre-consent trackers. | Do the standard check. |
Lower concern | No pre-consent trackers and no third-party cookies, or a working banner with no strong findings. | Record the result. Go deeper only if the decision is large. |
Level 2: standard check (about 10 minutes)
The standard check explains what is behind the numbers.
Read every finding marked Strong. Each one explains the issue in a sentence or two and names the trackers or cookies involved.
Note who receives the data. Advertising and retargeting companies weigh more heavily than analytics tools, because sharing data for advertising is what most opt-out rights are aimed at.
Set aside informational findings that describe permitted behavior. On a United States scan, cookies that are permitted under the opt-out model are not a violation by themselves. They become one when they continue after a visitor opts out.
Read Scan coverage. Confirm that the banner was detected and that the Accept, Reject, and GPC tests ran. Any check marked Not tested is unknown, not passed.
Open By jurisdiction. Note how many states show Findings present, and open the states where the business has the most customers to see the specific requirements and citations.
Add what you know about the business. A scan can’t see context, and context changes the picture.
These are the strong findings that matter most and what each means in plain terms:
Finding | Plain meaning | Why it matters |
|---|---|---|
No consent/opt-out mechanism detected | The site shares visitor data with trackers and gives visitors no way to say no. | The most basic requirement of U.S. state privacy laws is missing. |
Tracker fires despite rejection, or cookies persist after rejection | The banner offers Reject, but rejecting doesn’t stop the tracking. | The site made a promise and didn’t keep it. This is easy for an outsider to document. |
Targeting trackers ignore GPC signal | The visitor’s browser said do not sell or share my data, and advertising trackers kept running. | The report cites California’s requirement to treat GPC as a valid opt-out. |
Third-party cookies persist despite GPC signal | Advertising cookies stayed in place after the opt-out signal. | The same requirement, seen in the cookies instead of the trackers. |
Dark pattern: consent categories pre-checked | The banner made the choice for the visitor. | Regulators treat consent obtained through steering designs as invalid. |
No privacy opt-out link found | There is no dedicated opt-out link on the page. | The report notes that California, Minnesota, and Maryland require one. |
TCF consent string is invalid or missing | The site’s advertising partners aren’t receiving a valid consent signal. | It suggests the consent setup is broken or incomplete. |
When you weigh the result, these business facts raise the stakes of any tracking finding:
The site serves consumers, and has significant traffic from California or other states with privacy laws.
The site deals with health, finances, children, or other sensitive subjects.
The site has features that send what visitors type or watch to other companies, such as site search, chat, video, or session recording. These features are frequent subjects of tracking lawsuits. See How to Avoid Network-Traffic-Based Privacy Litigation.
The site has visitors in the European Union or United Kingdom, where consent is generally required before non-essential tracking starts. See How to Choose Between Opt-In and Opt-Out Consent Models.
Level 3: deep check (30 minutes or more)
The deep check confirms the findings against the evidence and builds a record you can keep.
Compare the phases under Cookies & Trackers. Each phase shows two numbers: cookies stored and third-party hosts contacted. After Reject and With GPC should be clearly lower than Before consent. If the numbers barely move, the visitor’s choice isn’t being applied.
Read the cookie table for the Before consent phase. Look for cookies in the Targeting category with long lifetimes, set by advertising domains. A large number of Unclassified cookies suggests that nobody has inventoried what the site loads.
Open the screenshots. Confirm with your own eyes whether a banner appeared, what its buttons say, and whether Reject is as visible as Accept. Banner anatomy gives the button sizes and colors.
Check the request log when a finding names a tracker. It lists every request the browser made, in order, so a technical reviewer can confirm that a specific tracker was contacted before consent or after rejection.
Scan more than the home page. Run scans of the pages that matter most, such as product, checkout, sign-up, and any page with video or forms. A scan covers only the page you enter.
Scan against another regulation if the business has visitors there, for example European Union (GDPR).
Scan again later and select Compare to see what changed. A site that fixes its issues after they are raised is a different risk from one that doesn’t.
Keep the record. Download the PDF, note the scan number and hash, and add the scans to a project. See How to Export, Share, and Compare Patrol Scan Reports and How to Scan Multiple Websites and Organize Scans with Projects in Patrol.
For a manual spot check, open the site in a private browser window, look for the banner, and select Reject. To test the GPC signal yourself, see How to Use the Captain Compliance GPC Extension.
Red flags at a glance
Red flag | Where Patrol shows it |
|---|---|
No consent banner while trackers load | Banner shown: No, with Pre-consent trackers above 0 |
No way to decline | Reject button: Missing |
Ungated scripts | Pre-consent trackers above 0, and 3rd-party cookies pre-consent: Fail |
Reject doesn’t work | Findings: tracker fires despite rejection, or cookies persist after rejection |
Opt-out signal ignored | GPC honored: No, and findings that name trackers ignoring GPC |
Choices made for the visitor | Pre-checked categories, or Accept & reject equal weight: Fail |
No opt-out link | Opt-out / Do-not-sell link: Fail |
Heavy advertising footprint | 3rd-party cookies in the dozens or hundreds, and many advertising trackers named in the findings |
Unknowns | Scan blocked, or checks marked Not tested |
What a scan can’t tell you
A scan is a snapshot of one page at one moment, for a logged-out visitor on a desktop browser, from one location.
It can’t see inside the business: its contracts with vendors, how it answers privacy requests, or whether its privacy notice is accurate.
The verdict is an automated assessment, not legal advice. Treat it as one input alongside your other review steps.
If the website is yours
Each red flag has a fix in Captain Compliance:
No banner or no reject option: How to Publish a Consent Banner on Your Website
Trackers before consent or after rejection: How to Block Scripts Before Consent with Auto Blocking and Strict Mode and How to Gate Non-Essential Scripts and Beacons Using Explicit Consent Logic
GPC not honored: How to Use Bucket Mode to Customize Consent Categories and GPC Behavior
No persistent way to change a choice: How to Add a “Cookie Preferences” Option to Your Website Footer
