01 — Wrong tool
Google Analytics is not built for [gov] work.
It is built for commercial optimisation. The compliance overhead was added on, not designed in.
// 00 / Announcement May 2026
[gov] is not a sector.
It is a standard.
Analytics vendors own your data. That is the business model: they have the silo, you have the login, and the arrangement lasts as long as the contract does. For a municipality, a ministry, or a hospital in 2026, it is a structural risk dressed as convenience. govanalytics is web analytics at government grade — for governments, and for everyone who chooses to hold themselves to the same standard. Compliant with GDPR and comply-or-explain, by design.
// 01 / The question
Organisations need to know whether their digital services work.
The people they serve should not have to pay for that with their data.
// 02 / The standard
Definition
What [gov] means.
[gov] is how an organisation chooses to handle digital measurement data. Not who it is, but how it acts. Five characteristics:
- 01
Collected in your country.
No edge nodes elsewhere, no "EU-region" with footnotes.
- 02
Measured without cookies.
No consent banners. No fake consent. No tracking pixels.
- 03
Not transferred outside the EU.
No Schrems II risk. No hidden sub-processors in the chain.
- 04
Fully documented.
DPIA, data processing agreement, ROPA, TIA — ready to use, updated quarterly.
- 05
Exportable at any time without us.
Your ownership is architectural, not contractual.
Some must meet this standard. Others choose to. govanalytics is built for both.
// 03 / The reality
Four things that are currently wrong.
02 — False solution
Cookie banners are a symptom, not a solution.
If you need consent to measure your own services, you are measuring the wrong thing — or measuring in the wrong way.
03 — Marketing claim
"GDPR-proof" on a marketing page is not a DPIA.
A valid legal basis sits in a document your DPO can sign, not in a checkbox on a website.
04 — Burden of proof
"We process with care" is not a processing register.
The DPA asks for documentation, not trust. Those who cannot show the former cannot rely on the latter.
// 04 / What it is
govanalytics is web analytics that fits within your frameworks, not the other way around.
Hosted in your country (jurisdiction). Compliant with your local regulations and applicable Information- and Security standards. Without cookies, without data transfer outside the EU, without hidden processors.
With documentation that your procurement, data protection, and security officers can review without a red pen.
And with an architecture in which your data stays yours; stored in your own environment; exportable at any time - all without needing us.
For the technical foundation: the warehouse-first manifesto of our core — d8a.tech.
// 05 / For whom
Two reasons to choose [gov].
For every layer of public administration, and for those who choose to hold themselves to the same standard — even without obligation.
01 — Because it's required
For those bound by public standards.
Organisations required by law, regulation, or administrative law to meet Dutch and European standards.
- 01Municipalities
- 02Ministries
- 03Provinces
- 04Water authorities
- 05Implementing organisations
- 06Public bodies and agencies
02 — Because it's right
For those who hold themselves to the same standard.
Organisations that take themselves seriously where the law leaves room. Often regulated, sometimes not, always deliberate.
- 01Banks and insurers (DORA)
- 02Healthcare institutions (NEN 7510)
- 03Grid operators and utilities (NIS2)
- 04Universities and SURF members
- 05NGOs and family offices
- 06Any organisation with a principle
// 06 / The invitation
And for everyone who chooses to hold themselves to the same standard
even without the law requiring it.
Whether you are a municipality meeting a council resolution, a bank building towards DORA, or an organisation that simply believes this is the right way: you can start measuring under the same standard today. The same platform. The same documentation. The same architecture.