Website privacy is one of those topics that gets put off until a complaint arrives or an attentive customer points out that something is missing. The rules are complex and this isn’t the place to replace a lawyer: if you handle sensitive data, for example in healthcare, or you run an online shop, it’s right that a professional assesses your situation. Here, though, you’ll find the basic rules, explained for someone with a brochure site or a blog.
Technical cookies and cookies that require consent
Cookies are small files that a site stores in the visitor’s browser. In simplified terms, they fall into two groups:
- Technical cookies. They’re needed for the site to work: remembering the language, keeping a shopping basket, maintaining a session. They don’t require prior consent, but they must be listed in the privacy information.
- Profiling cookies and non-anonymised analytics cookies. Social media pixels, advertising tools and, generally, Google Analytics as it’s normally used. They require consent before being activated.
If your site uses only technical cookies and no third-party tools, you don’t need a banner. As soon as you add Analytics, a Meta pixel, a map that loads external services or an embedded video, the situation changes.
How a compliant banner should behave
The guidelines of the Italian Data Protection Authority (the Garante per la protezione dei dati personali), in force since 2021, are quite clear about what to avoid and what to do:
Banner to avoid
- Scrolling the page counts as consent
- The “Reject” button is hidden or missing
- Tools start before the choice is made
- Pre-ticked boxes
Compliant banner
- Accept and Reject are equally prominent
- Tools start only after consent
- Choices can be changed at any time
- Links to the full information
Consent must be freely given and informed, and the choice must be remembered for a reasonable time before asking again. A consent management plugin, if configured properly, takes care of most of these aspects, including blocking tools before the choice is made. But be careful: installing it isn’t enough. You need to check that the tools don’t start anyway, by opening the site in a private window and checking what gets loaded before you accept.
The privacy policy
This is the page that explains which data you collect, why, for how long, who you share it with and how users can exercise their rights. You must have one if you have a contact form, a newsletter, a members’ area or analytics tools. It must be linked from the footer and from every point where you collect data, particularly below forms. Avoid text copied from other sites: it describes processing you may not carry out and leaves out other processing that you do.
Forms and newsletters
- Below every form, a link to the privacy policy and a short, clear sentence.
- Signing up to a newsletter requires separate consent, not pre-ticked and not tied to sending a simple contact request.
- Keep messages only for as long as you need them and decide who has access to them.
Small things that make a difference
- Keep a list of the third-party tools you use: analytics, maps, fonts, videos, chat.
- State the details of the data controller on the site: company name, address, VAT number (Partita IVA), contact details.
- Review your cookies and privacy policy whenever you add a new tool. That’s the moment people forget.
Privacy isn’t a badge you put up once: it’s a list of true things that the site declares and maintains.
Where to start
Open your site in a private window, don’t accept anything and see what happens: does a banner appear? does it have a button to reject? Then check the privacy policy page: is it yours, is it up to date, can it be reached from every page? If you have doubts about your specific situation, ask a consultant who specialises in data protection. It’s a modest cost compared with the trouble it can spare you.
Further reading: Google Analytics 4 for a small business: what to measure and what to ignore · A contact form that works: fields, wording and what happens next.




