Most cookie banners
ask a question and
change nothing.

The default notice is a bar at the bottom of the page. It doesn't block browsing, doesn't cover your Add to Cart button, sits in a fixed layer that can't move your layout, and never appears at checkout. If you'd rather have a notice that stops everything until it's answered, that option exists — but you have to choose it.

No. Shoppers who accept get analytics exactly as before, and Consently sends Google Consent Mode v2 signals either way, so consent-aware conversion modelling keeps working. Shoppers who decline aren't measured — which is the point, and is what the law asks of you.

It really blocks. Requests from a gated service are refused before they leave the browser, the tag's globals are buffered so its calls are held rather than run, Consent Mode is set to denied, and the cookies it set are deleted if the shopper says no. There is one honest exception, and we'd rather you hear it from us: a tracking script pasted directly into your theme's header runs before any app's code exists on this platform, so its very first call happens before Consently is on the page. From that moment on it's blocked and its cookies are cleared — and the app tells you which of your tags is in that position and how to move it.

If you have shoppers in California, Colorado, Connecticut, Virginia or a growing list of other states, you need a way for people to opt out of the sale or sharing of their data, and you have to honour the Global Privacy Control signal their browser sends. Consently does both. Choose "Mostly the United States" in setup and it applies the opt-out model rather than asking first.

Almost nothing, deliberately. Daily counts of how often the notice was shown and answered, and — if you keep the consent record — a row holding a random id the shopper's own browser generated, which categories they allowed, a rough region from their device time zone, and the date. No IP address, no user agent, no fingerprint, no email, no page URL. A consent tool that quietly profiled people in order to prove they'd refused profiling would have failed at the only job it has.

One thing: your store's name and owner email, so the notice can be branded and privacy requests can reach you. Consently asks for a single permission, users:read. It cannot see your products, your orders or your customers, and it can't write anything to your store at all.

No, and that's on purpose. Consently verifies the request is genuinely from the person it claims to be, files it with its statutory deadline, and reminds you it's open. Actually erasing a customer stays your decision, made with your own hands — an app that deleted records on an emailed instruction would be a much bigger liability than the one it set out to solve.

No. Consently is a tool that does the technical work — asking, blocking, recording, and tracking requests — and it's built around what the GDPR, UK GDPR and CPRA actually require. What your particular business needs to disclose is still a question for you, and for a lawyer if the stakes are high.