Replace Google Analytics without legal risk.
GA4 is the most widely used analytics platform in the world. For Dutch public sector organisations, that popularity does not match the legal reality.
Why GA4 is a problem for public sector organisations.
01.
GA4 sends visitor data to servers in the US. Under default settings, personal data is processed, even in the "EU region".
Wrong location02.
A marketing claim is not a legal basis. A valid legal basis is found in a DPIA your DPO can sign, not in a checkbox inside a cookie settings panel.
No legal basis03.
If you need consent to measure your own services, you are measuring in the wrong way. Consent management is not an architectural solution.
Cookie banner is a symptom04.
GA4 was designed for advertising performance and e-commerce. The compliance overhead for public sector use was added on, not designed in.
Wrong toolHow Govanalytics solves it.
How it worksGDPR-compliant by architecture. No IP storage, no personal data, no cookies. The legal basis is built into the architecture, not the configuration.
Hosted in the Netherlands. All data stays on Dutch servers within the EU. No American parent company, no Schrems II risk. Compliant with the Dutch BIO.
Complete processing documentation. DPIA template, data processing agreement and records of processing activities are available. Documentation your DPO and procurement team can assess directly.
Your existing tagging keeps working. Govanalytics supports the GA4 Measurement Protocol and Matomo. Your GTM container, custom events and UTM parameters carry over: you are not starting from scratch.
Migration in a few days to a week. Both systems run in parallel: you compare reports and only switch off GA4 when the data matches.
How the migration works.
Implementation in detailAdd Govanalytics alongside your current solution. Via the same GTM account or via direct script installation, alongside GA4, Matomo, Piwik PRO or any other existing tool. Both systems run simultaneously.
Run in parallel. Compare data for 2 to 4 weeks. You see both systems side by side and decide yourself when to switch.
Switch off your current solution. Once Govanalytics data is stable and matches what you expect, switch off the current tag. Migration of historical data is available on request. Get in touch
Update your DPIA and records of processing activities. Document the change in your processing register and finalise with an updated DPIA.
What is Govanalytics, and how is it different?
Govanalytics is a GDPR-compliant web analytics platform for Dutch government organisations. Unlike Google Analytics, no personal data is processed, no cookie banner is required, and all data is stored in the Netherlands. The built-in AI interface lets you query your own analytics data directly, without involving an analyst.
We're not a government body. Is it still for us?
Govanalytics is primarily designed for government organisations, but housing associations, healthcare providers, educational institutions and other organisations operating under strict privacy legislation also use the platform. If your organisation has a Data Protection Officer or faces GDPR compliance requirements, Govanalytics is a logical choice. Get in touch to discuss whether it fits your situation.
Who owns our data, also after the contract ends?
You always and at all times remain the owner of your own data. After the contract ends you receive a full data export in a standard format. Govanalytics has no claim on your data, does not share it with third parties and never sells it.
Where is our data stored, and who can access it?
All data is stored on servers in the Netherlands, at UpCloud in Amsterdam — an ISO 27001-certified hosting partner. Storage falls entirely under Dutch and European law. No data is transferred to the United States or other third countries. Only you and users you have authorised have access to your data.
What about the cookie law?
For a commercial company, Google Analytics 4 is risky but manageable. You can weigh the legal exposure, put up a cookie banner, and carry on.
For public organisations, that logic does not hold. Government websites are not optional: citizens cannot choose not to visit the municipal website when they need a permit. That makes the legal basis for data processing harder to justify, including under the current enforcement practice of the Dutch Data Protection Authority.
Every public organisation also has a Data Protection Officer who will ask for a DPIA during an audit. Writing a watertight DPIA for Google Analytics 4 is close to impossible: the data flows are partly on Google's servers and therefore difficult to describe exhaustively.
Cookie MeasurementHow do we stay GDPR-compliant, even after a misconfiguration?
Govanalytics is cookieless by design: even with a misconfiguration, no personal data is processed. No opt-in is required and no cookie banner is needed for your analytics. Privacy is the default, not the exception. This also makes the platform straightforward to justify to your Data Protection Officer or in a review by the Dutch Data Protection Authority.