GDPR and cookie-free website analytics
What “GDPR-compliant analytics” can and cannot mean, and exactly how quietstats handles visitor data, so you can judge it for your own site.
Not legal advice, and no guarantees. Whether your website meets UK GDPR and PECR depends on everything it runs and how you describe it. This page states facts about quietstats only.
Two different rules
PECR (the UK cookie rules) is about storing or reading information on a visitor’s device. UK GDPR is about processing personal data. A tool can avoid cookies and still process personal data, so it helps to check both separately.
What quietstats does with visitor data
- Nothing is stored on the visitor’s device: no cookies, localStorage, sessionStorage or IndexedDB.
- The IP address and user agent are used in memory for one request to make a daily visitor ID, then discarded. They are never stored.
- The daily random salt behind that ID is deleted the next day, so visits cannot be linked across days.
- Page addresses are stored without the #fragment or query string, except UTM tags and
?ref=. - Do Not Track and Global Privacy Control are honoured: the script sends nothing.
- Groups smaller than 5 visitors are hidden in city totals.
The full list, field by field: compliance and methodology.
Roles, location and sub-processors
- You, the website owner, are the controller for your visitors’ data; quietstats acts as your processor.
- Hosting: Cloudflare Workers and a Cloudflare D1 database created with a Western Europe location hint. Requests are first handled at the Cloudflare data centre nearest the visitor.
- Sub-processors: Cloudflare (hosting) and Stripe (payments for paid plans; no visitor data).
- Data processing agreement: being prepared, not yet available.
What you still need to do
- Describe your analytics in your privacy notice. Wording you can adapt is on the compliance page.
- Give visitors a simple, free way to object; linking to how to switch on Global Privacy Control is one way.
- Use the numbers for aggregate statistics only, never for advertising or decisions about individuals.
- Check the other tools on your site: one cookie-setting embed can still need a banner. Try the cookie banner checker.
Sources
Questions
Is quietstats GDPR compliant?
We do not claim that, because compliance depends on how you run your website as a whole. What we can say is what quietstats does: no cookies or device storage, no stored IP addresses or user agents, a daily visitor ID that cannot be linked across days, and data kept on Cloudflare with a Western Europe location requested for the database.
Is a cookie-free tool automatically GDPR-proof?
No. UK GDPR still applies when personal data is processed, even briefly. quietstats processes the IP address and user agent in memory for one request to make the daily ID, so we say “no personal data is stored”, not “no personal data is processed”.
Do you offer a data processing agreement?
A customer DPA is being prepared and will be reviewed by a solicitor before it is published. It is not available yet; see compliance for the current status.
Is this legal advice?
No. It explains how quietstats works. For a decision about your site, read the ICO guidance or ask a qualified adviser.
Related pages
Try quietstats on your own site
Free for one site and 5,000 pageviews a month, no card needed. No cookies and nothing stored on your visitors’ devices.