Explaining visitor analytics in a privacy notice.
Say what you collect, why, how long you keep it, and who else sees it. Say it in language a customer can read. What follows is how to describe the analytics part — not a template, and not advice about whether your particular setup is lawful.
This is not legal advice, and we are a vendor with an interest in you using our product. Requirements differ by where your visitors live, not where your business is, and the rules in the EU and UK are considerably stricter than in the US. Have someone qualified review your notice.
Describe what is collected, in plain terms
Analytics tools generally record the pages someone views, where they arrived from, an approximate location derived from their network, and their device and browser. Say that, rather than reproducing a vendor's feature list.
If your tool does not identify individuals by name, say so plainly. Readers assume the worst about tracking, and a specific sentence saying what you do not collect is more reassuring than a paragraph of hedging.
Say why, specifically
"To improve our services" tells a reader nothing and reads as evasion. "To see which pages people find useful and to respond to enquiries more quickly" is a real reason, and it is the actual one.
Say how long you keep it, and who else sees it
Name a period. If your analytics provider holds the data, say that a third party processes it on your behalf and name them, because a reader is entitled to know whose systems their visit ends up in.
If you do not know your retention period, find out before writing a number. A privacy notice with an invented figure in it is worse than one that is vague.
Where this gets complicated
Whether you need consent before analytics runs at all — and what a valid consent banner looks like — depends on jurisdiction and on the specific technology used. It is genuinely complicated, it changes, and getting it wrong carries real penalties.
That is the point to stop reading pages like this one and talk to someone who advises on it professionally for the places your customers live.
Find what is costing you search clicks, then watch the fix work.
VisitorPing reads your own Search Console data for the pages losing clicks, then rings your phone the moment someone lands on your website.