Release QA
Does “Reject all” actually stop the observable trackers?
ScanBell runs the page in fresh browser contexts, attempts the visible reject path, and compares bounded technical signals. No signup is required.
What the check compares
Before a choice
Request domains, recognized tracker heuristics, cookie attributes, storage key names, and visible consent controls.
After reject
The same evidence from a new context after an automated reject or necessary-only action is found and clicked.
What it cannot prove
A browser observation cannot determine a cookie’s legal necessity or certify compliance. Geo-specific behavior, delayed tags, custom labels, iframes, and login states can change the outcome. ScanBell keeps those limits visible.