PATENT PENDING - WORLD FIRST
Real consent enforcement for third-party cookies
Guard is the first product on the market that gives a first-party publisher real control over the third-party cookies a third party has written to the visitor's browser, removing them the moment consent is withdrawn and blocking new ones at write time.
PATENT PENDING - WORLD FIRST
Your cookie banner has been lying for twenty years.
WebSentinel Guard is the first product on the market that gives a first-party publisher real control over the third-party cookies a third party has written to the visitor's browser, removing those cookies the moment the visitor withdraws consent and blocking new ones at write time, which is the consent state every visitor has assumed they were getting when they click Reject and which, twenty years into the cookie banner industry, they have never actually had.
WHY THE CMP INDUSTRY HAS NEVER FIXED THIS
Same-origin principle - cookies can only be removed by the party that set them.
Cookie deletion in the browser is governed by the same-origin principle, a security rule from the late 1990s and early 2000s that limits cookie deletion to the party that wrote the cookie, so when a third-party tag fires from doubleclick.net and sets a cookie at the doubleclick.net origin, only doubleclick.net can delete it. The Consent Management Platform running on the first-party domain has no way to reach across origins, and that limit applies just as much to OneTrust, TrustArc, Usercentrics, CookieYes and every other CMP that has shipped since the cookie banner industry began.
The industry has built and sold this product knowing full well that it cannot do what it claims, because when the visitor clicks Reject after pageload, the third-party cookies that were already set remain on the browser, the data inside them remains too, and the visitor walks away believing their data has been deleted while every one of those third parties continues to track them on the next request.
CONSUMER PROTECTION EXPOSURE
Deception under consumer-protection law.
A reasonable visitor who clicks Reject expects the cookies to be deleted, because that is what Reject means in plain English, and where the cookies actually remain, where the visitor's data continues to sit in them, continues to identify the visitor, continues to flow to the third party on the next request, the operator of the website is representing something to the visitor that is simply not true.
In US consumer law that is a deceptive act or practice under section 5 of the Federal Trade Commission Act, and in EU consumer law it is a misleading commercial practice under the Unfair Commercial Practices Directive (2005/29/EC) implemented across every member state, with both regimes treating deception about a material attribute of a service as actionable. The exposure sits on every operator that has deployed an incumbent CMP, and it does not need regulator action to land in court, because a class-action plaintiff in the United States, a national consumer authority in any EU member state, or an advertising-standards regulator can act on the documented gap between what the cookie banner represents and what the browser actually contains.
Guard closes that gap by giving the first-party publisher real control over third-party cookies, so for the first time the reject button on a cookie banner actually produces the cookie state the banner has been claiming for the past twenty years.
WHAT IT DOES
- Blocks new third-party cookie writes at write time, before they land on the browser
- Removes existing third-party cookies the instant the visitor revokes consent
- Continuously reconciles against the visitor's current consent state, not a one-off scrape at pageload
- Keeps an audit-grade record of every third-party cookie Guard has blocked or removed
- Operates alongside your existing cookie banner, whichever vendor you use
WHY IT MATTERS
- OneTrust, TrustArc, Usercentrics, CookieYes and every other CMP on the market cannot remove a third-party cookie once it has been set
- Browser same-origin restrictions limit cookie deletion to the party that wrote the cookie, and a CMP on the first-party domain has no reach across origins
- When the visitor clicks Reject after pageload, the cookies stay on the browser and so does the data inside them, while the third parties keep tracking
- Guard is the first product on the market that closes that gap
AVAILABILITY
Free with WebSentinel SaaS.
Guard is included at no extra cost in every WebSentinel SaaS subscription, so any organisation running continuous monitoring on the platform gets real third-party cookie enforcement as part of the same deployment, alongside whichever cookie banner it already uses.
The technology is patent pending and is currently available only inside WebSentinel SaaS. A standalone Consent Management console, for publishers who want Guard without the full monitoring platform, is arriving in Q3 and Q4 2026. If you want to be first in the queue when it ships, tell us about your properties and we will keep you posted.
NEXT STEP
Make Reject mean what it says.
Tell us about your properties and the cookie banner you run today, and we will show you what Guard removes the moment a visitor withdraws consent and what it blocks before it ever lands on the browser.