Cookies still visible in the browser after a consent refusal are inactive: Axeptio blocks the execution of scripts that feed them, but does not delete already-set cookies. Without an active script, a cookie can neither collect nor transmit data.
How does Axeptio's blocking work?
The mechanism is based on script blocking, not cookie deletion:
The visitor accepts a cookie: the third-party service script executes and sets the cookie in the browser.
The visitor then refuses that cookie: Axeptio blocks the script execution. The cookie remains physically present in the browser but becomes inactive — it can no longer collect or transmit data.
Is this residual cookie a risk?
No. A cookie without an active script is technically inert. It cannot:
Collect new browsing data.
Transmit information to the third-party service.
Track visitor behavior.
The cookie will naturally expire at its planned expiration date, or the visitor can manually delete it from their browser settings.
In summary
The presence of a cookie in the browser after a consent change is normal behavior. Axeptio ensures the associated script no longer executes, rendering the cookie inactive with no impact on visitor privacy.
]]>