See
Find cookie names, domains, scopes, expiration, security flags, and stores without exposing cookie values.
Inspect which cookies are stored, understand their possible role, and remove the ones you no longer need. Metadata stays local and cookie values are never requested or displayed.
Browser-side evidence only: this cannot show a company's private server logs, account history, or data inferences.
Privacy Radar does not claim to know everything a company knows about you. It helps you inspect the browser evidence you can control and decide what should stay.
Find cookie names, domains, scopes, expiration, security flags, and stores without exposing cookie values.
Use categories and possible capabilities to distinguish session, security, consent, analytics, advertising, and identifier signals.
Filter categories, inspect the evidence, and request deletion when the possible benefit no longer outweighs the site behavior it supports.
Privacy Radar cannot see a company's private server logs, account history, data partnerships, or inferences. A cookie name is not proof of tracking, and no visible cookie does not prove that no data is collected.
These are the origins the current page loaded. Likely trackers are flagged with extra signals, but final removal still depends on the browser's site-data controls.
The website never receives cookie values. With the extension bridge, you can review heuristic purpose and risk signals, then explicitly request deletion from the browser.
Privacy tools are more useful when their limits are explicit.
It inspects the current page for third-party scripts, images, iframes, beacons, and other loaded resources that can reveal tracking activity.
Not by itself. The website needs the Privacy Radar extension and your explicit confirmation to request cookie deletion. Without the extension, browsers restrict access to other origins.
No. The scan and cookie inventory run in your browser. Cookie values are never requested or displayed.
A website can scan only the page where it is running. Browser security prevents it from inspecting another tab or reading the Cookie headers that browsers send automatically. The Chrome extension runs with your permission and can observe the active tab's requests, show cookie names sent to external destinations, inventory accessible browser cookie stores, analyze metadata heuristically, and request explicit cookie deletion.
The local handshake confirms the installed version, then cookie metadata loads automatically. Scan results and cookie metadata stay in your browser; cookie values are never requested or displayed.
chrome://extensions, enable Developer mode, and choose Load unpacked.The extension asks for broad site access because it must inspect whichever site you choose. It does not upload browsing data, cookie values, or reports. Review the permissions and the privacy policy before installing.