A banner with two buttons does not establish whether a website respects visitors’ choices. What matters is what loads before a choice, what changes after refusal and whether consent can be withdrawn. For a small website, a useful starting point is an inventory of its tools. That supports clear explanations and an informed discussion with your technical and legal advisers about applicable requirements.
Find out what runs on the page
Include analytics, advertising, maps, chat, videos and other external services, not only your own cookies. Check whether a theme or plugin adds them automatically. Record the provider, purpose, information transmitted and relevant duration. A plugin’s “functional” label does not establish necessity. Something useful to the business is not automatically necessary for the service requested by a visitor.
Explain concrete purposes
Separate basic operation from measurement and advertising when their purposes differ. Explain what you do in language customers understand. Do not hide the decision behind a general reference to “better experiences”. Where consent is the applicable basis, it must be informed and expressed through a clear action. Simply continuing to browse is not a substitute for a valid choice.
Make refusal and preference changes usable
Visitors should understand the options without deciphering contradictory wording or ambiguous buttons. Avoid preselected choices for purposes requiring agreement. Keep settings easy to reach after the banner closes, for example in the footer. Withdrawing consent must be as easy as giving it. Check the experience on a phone and with a keyboard, not only on the implementer’s monitor.
Test behaviour as well as appearance
Start in a browser without saved preferences. Check outgoing requests before a choice, after refusal, after accepting one purpose and after withdrawal. Test subdomains separately rather than assuming they share a preference. A provider that has already loaded may require tracking to stop or the page to reload. The technical team must determine and verify the appropriate mechanism.
Maintain explanations as the website changes
Adding chat or an advertising platform can change the inventory while leaving the banner looking identical. Include verification in your publishing process and retain relevant version records. The policy should describe reality. This supports responsible implementation but does not certify compliance: obligations depend on services, purposes, audiences and applicable rules.
Sources and further reading
A CloudCity editorial guide informed by the documentation below. Check the official source for rules and procedures that may change.
