01
Observe browser activity
Inspect external hostnames, recognized tracking endpoints, cookie names and storage key names from a real Chromium session.
Requests · Cookies · Storage keysWEBSITE PRIVACY OBSERVABILITYYour banner tells one story.
Your banner tells one story.
What does your website do?
See the browser behavior behind your consent setup. Compare scenarios, inspect observed services and spot third-party changes that deserve a closer look.
No banner to install. Domain ownership required.
ILLUSTRATIVE SCAN · SAMPLE DATA
example.com DNS
Consent behavior, side by side.
Separate Chromium contexts for each scenario.
SCENARIOINTERACTIONEXTERNAL HOSTS
01Before a choiceNo choice made4 observed
02After rejectionClick confirmed2 observed
03After acceptanceUntestedNot assessed
Tracking observed after rejection
A technical finding to investigate, not a legal conclusion.
No confirmed accept interaction. This scenario is untested.
Real Chromium observations DNS-verified domains No cookie values stored Separate consent scenarios
LOOK BEYOND THE BANNER
Understand the behavior. Keep the evidence in context.
A consent banner is an interface. TruCookie helps your technical team investigate what happens around it.
02
Compare consent scenarios
Run separate contexts before a choice and after reject or accept attempts. An unconfirmed interaction is recorded as untested.
Before choice · Reject · Accept03
Notice third-party changes
Compare newly observed external hosts with a previous scan. Use the change as a starting point for investigating a release or integration.
Previous scan · New hosts · Review04
Keep a reviewable history
Use your organization’s site inventory, scan history and finding details to revisit the observations behind a technical question.
Sites · Scan details · FindingsFROM DOMAIN TO OBSERVATION
A practical check for your website workflow.
Start with a domain you control. Verify ownership before collecting any browser observations.
Verify your domain
Publish the supplied DNS TXT record to demonstrate control. Scanning is restricted to verified domains.
Run the scenarios
Queue a scan that opens independent Chromium contexts and attempts the configured consent choices.
Investigate the evidence
Review observed services, cookie names, interaction results and changes against previous scans.
FOR THE PEOPLE RESPONSIBLE FOR THE WEBSITE
A shared view for technical and privacy conversations.
Web & digital agencies
Check authorized client domains and investigate consent behavior after website or tag changes.
Engineering & QA teams
Connect findings with releases and integrations. Separate a confirmed interaction from an untested scenario.
Privacy & operations teams
Bring concrete technical observations to reviews with developers and consent-platform providers.
CLEAR SCOPE. USEFUL SIGNALS.
Know what a scan can tell you.
An observation is not a verdict.
A scan describes the behavior encountered in a particular run. It does not determine legal compliance or guarantee full tracker coverage.
Untested means untested.
A banner interaction may fail. TruCookie records that limitation rather than reporting a consent outcome it did not confirm.
Collect the names, not the values.
The scanner records cookie and storage key names, not cookie values, request bodies, form input or full browsing histories.
PRACTICAL GUIDES
Make the evidence useful.
Understand the scenarios, build a reviewable inventory and investigate changes without overstating what a scan proves.
PRODUCT EVALUATION
Make website privacy a technical conversation.
Explore how scenario-based observations could fit your team’s website review process.