Does Matomo or Plausible let a site skip the cookie banner?
If you are deciding whether to keep a consent banner, the short answer is that Plausible's design uses no cookies, and its own documentation says that means no cookie banner is required. Matomo is different: it can qualify for a consent exemption under the CNIL's rules in France, but only when the configuration stays inside the listed purposes. Those purposes are performance measurement, anonymous statistics and no marketing measurement. Matomo's own ePrivacy FAQ says that enabling User ID, heatmaps or session recordings removes the exemption, so a single plugin toggle can put a site back under consent requirements.
Matomo's FAQ also names Italy, the Netherlands and Spain as authorities that exempt certain privacy-focused analytics when criteria are met, and suggests following the CNIL configuration there. That guidance is a starting point, not a ruling. Each authority's rules, the way your site uses cookies or local storage, and whether any other tag on the page sets identifiers all affect the answer. Plausible's cookieless claim covers its own script and settings, so confirm that no other scripts on the site set cookies before dropping the banner.
Before you decide, confirm three things with your privacy counsel or data protection officer: which authorities apply to your visitors, which Matomo settings and plugins are enabled in your instance, and whether your self-hosted deployment changes any transfer or processor analysis. Self-hosting keeps analytics data in your own infrastructure, but it does not replace a legal review of the consent position. Document the configuration you chose, because the exemption depends on it staying that way.
How each platform handles consent, data and self-hosting
This table compares Matomo On-Premise and Plausible Community Edition on cookie use, consent exemption, the features that remove an exemption, self-hosted duties, Cloud data location and security fix cadence. Read each row as a question to answer for your own site, since exemption depends on how the tracker is configured and on the rules of your national authority.
| Question | Matomo On-Premise | Plausible Community Edition |
|---|---|---|
| Does the default setup use cookies? | Matomo sets cookies by default, so a banner is usually needed unless the consent-exempt configuration is applied and verified. | Plausible is designed to use no cookies, so the vendor states no cookie banner is required for its analytics. |
| Consent exemption criteria | CNIL may exempt a tracker limited to performance measurement, anonymous statistics only, and no marketing measurement. Confirm the exact setup with your authority. | Exemption is not a configuration step because no consent is needed for cookieless analytics. Confirm the position under your own authority's rules. |
| Features that remove an exemption | Adding User ID, heatmaps or session recordings removes the CNIL exemption, so these must stay off if you rely on it. | Marketing funnels, user journeys and ecommerce revenue goals are missing from Community Edition, so the feature set is narrower by design. |
| Authorities named in Matomo's guidance | France, Italy, the Netherlands and Spain. Matomo suggests following the CNIL configuration for Italy, the Netherlands and Spain. | Plausible's supplied materials do not name authorities. Ask your counsel or data protection officer to confirm local treatment. |
| Self-hosted responsibilities | The operator runs the database, web server, upgrades, backups, consent settings and the evidence of configuration. | The operator manages installation, upgrades, capacity, uptime, backups and security, so Docker, ClickHouse and PostgreSQL also need an owner. |
| Data location for Cloud versions | Matomo Cloud data is stored in Frankfurt, Germany. Self-hosted data stays wherever your infrastructure sits. | Plausible describes its service as made and hosted in the EU. Self-hosted data stays in your chosen infrastructure. |
| Security fix cadence | Upgrade timing is set by your team. Confirm the patch process and release notes against your own change control. | Community Edition gets security fixes only when the operator applies a release, and it ships twice per year. Plausible Cloud ships updates multiple times per week. |
| Transfer exposure for Cloud use | Using a hosted service moves the data processing decision to a provider. Assess third-country access under Chapter V before choosing Cloud. | Same assessment applies. Self-hosting keeps the data under your control, but the analytics script still needs a documented lawful basis. |
How Matomo qualifies for a consent exemption
Matomo can run without a consent banner only if the install stays inside the narrow scope that French and some other EU authorities accept. France's CNIL recognizes certain audience measurement trackers as exempt from consent when they are limited to purposes such as performance measurement, collect only anonymous statistics and exclude marketing measurement. Matomo's own ePrivacy FAQ names France, Italy, the Netherlands and Spain as authorities that exempt certain privacy-focused analytics when their criteria are met, and it suggests following the CNIL configuration for Italy, the Netherlands and Spain. Treat that suggestion as a starting point for your legal review, not as a determination by those regulators. Confirm with counsel whether each country where you have visitors accepts the CNIL configuration, and record the decision, the settings used and the date you last checked the rules.
Two features remove the exemption entirely: User ID and the heatmap and session recording tools. Matomo's FAQ states that adding User ID, heatmaps or session recordings takes the tracker outside the exemption, so a team that turns on any of them must plan for a consent mechanism on those pages. The Heatmap and Session Recording plugin is a paid premium plugin sold per number of users under the InnoCraft EULA rather than under the GPL, and it comes with a 30-day free trial according to its marketplace listing. Because that plugin is the most common reason an otherwise compliant install loses its exemption, make the decision on it a formal change: a named owner, a privacy review and a written sign-off before anyone installs it on a production site.
Plan the settings review as a control, not a one-time setup. On a self-hosted Matomo, the exemption depends on the tracking code, the consent-related settings and any plugin enabled on the site, so each change should be checked against the CNIL criteria before release. Ask whether any tag manager, custom dimension or ecommerce tracking sends identifiers that would count as User ID, and confirm with your privacy team how Matomo's tracking settings should be configured for each jurisdiction in scope. Keeping a dated record of this review also helps when a regulator or auditor asks how the exemption was justified.
What changes the consent result in practice
A site can start with a configuration that needs no banner and still lose that position after a single setting or data source changes. The cards below cover the switches, imports and jurisdictions that move a Matomo or Plausible install from consent-exempt to consent-required, and what to confirm before relying on either.
Enabled features remove the exemption
Matomo's ePrivacy FAQ says that adding User ID, heatmaps or session recordings removes the CNIL exemption for audience measurement. Heatmaps and session recordings are also a separate paid plugin under the InnoCraft EULA. Before launch, list every feature and plugin enabled on the site, and treat any user-level identifier as a trigger for a consent review.
Marketing use of the data
The CNIL exemption covers measurement limited to performance and excludes marketing measurement. If analytics data feeds ad targeting, retargeting audiences or campaign attribution shared with ad platforms, the purpose falls outside the exemption. Confirm with your DPO which downstream tools receive exported reports or event data, because an export can change the purpose even when the tracker itself stays unchanged.
Google Analytics historical import
Matomo's Google Analytics Importer and Plausible's GA4 import both bring historical data into a new install. Matomo's importer only brings aggregated reports, while Plausible imports daily aggregates up to the first native visit and supports up to 5 GA properties per site. Imported history is not created by the tracker, so confirm what the import contains, where it was processed, and whether the legal basis for the original GA collection still covers its use.
Plausible Google integration settings
Plausible's Community Edition Google integration uses GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET to enable Search Console keyword data and GA4 historical import. Enabling it adds a data flow from Google into your install. Check the environment file before go-live, confirm which sites are connected in the Imports and Exports settings, and record the Google account that owns the credentials.
Which authority applies to visitors
Matomo's FAQ names France, Italy, the Netherlands and Spain as authorities that exempt certain privacy-focused analytics when criteria are met, and suggests following the CNIL configuration for Italy, the Netherlands and Spain. Your position depends on where visitors are, not where the server sits. Confirm with local counsel whether each target country accepts the CNIL-based setup, and apply the strictest rule to visitors from any country you have not checked.
Community Edition or Cloud operation
Plausible Community Edition receives security fixes only when the operator applies a release, while Plausible Cloud ships updates multiple times per week. Your team also owns hosting location, backups and access to the data. Confirm who runs the install, how quickly patches reach production, and whether a Cloud or self-hosted deployment is the one covered by your records of processing.
What self-hosting changes for GDPR transfers and control
Self-hosting moves the transfer question onto your own infrastructure. When you run Matomo or Plausible Community Edition in your own cloud account or data center, the personal data sits where you put it, and the Chapter V question becomes a question about where the server physically runs and who can reach it remotely. The EDPB's Guidelines 05/2021 (version 2.0) are explicit that remote access from a third country counts as a transfer even when someone only views data on a screen for support or administration, and that storage in a cloud outside the EEA does too. Map every administrator, vendor engineer and backup location to a country before you assume a self-hosted install stays inside the EEA. Your implementation partner's remote support sessions and any offsite backup target belong in that map.
Hosted options change the picture without removing it. Matomo Cloud stores data in Frankfurt, Germany, and Plausible says its service is made and hosted in the EU. Those facts answer where data rests, not who can reach it. Ask each vendor, in writing, which legal entity operates the service, where its support staff work, whether any sub-processor sits outside the EEA, and how it handles access requests. A non-EU operator, a non-EU sub-processor or support access from a third country can each create a transfer even when the data center is in Europe.
Some third-country laws deserve an exposure assessment, not a conclusion about either vendor. The US CLOUD Act (18 U.S.C. 2713) can reach data in a provider's possession, custody or control wherever it is stored, and GDPR Article 48 limits recognition of foreign disclosure orders to those based on an international agreement in force. Under EDPB Recommendations 01/2020, if a provider must access data in the clear and the destination's authority powers exceed what is necessary and proportionate, no effective technical supplementary measure may exist. Document the question, ask each vendor whether it has received such requests and how it responds, and record your decision with your data protection officer. Self-hosting shifts much of this control to you, but it does not remove the need to document it.
How to confirm the consent setup in your own environment
This sequence helps you check whether your Matomo or Plausible configuration matches the consent position you intend to take, with a written record of each check. It produces evidence for your own review and for counsel, not a legal conclusion about your compliance.
Inventory every tracked data point
List each data point your analytics setup collects: page URLs, referrers, device and browser fields, IP handling, custom dimensions, goals, ecommerce fields, User IDs, and any heatmap or session recording tools loaded on the same pages. Assign an owner, typically the web or analytics lead, who signs off the list. The output is a single inventory sheet that names every field and where it is configured, so later checks have a fixed baseline.
Check each data point against the CNIL criteria
Compare the inventory with the CNIL conditions summarized in Matomo's ePrivacy FAQ: the tool must be limited to performance measurement, collect only anonymous statistics, and exclude marketing measurement. Mark each item as within, outside, or unclear. The privacy or compliance lead performs this review and records the reasoning next to each line. Items marked unclear go to counsel before any configuration change.
Disable User ID, heatmaps and session recordings if an exemption is wanted
If you intend to rely on a consent exemption for Matomo, the same FAQ says User ID, heatmaps and session recordings remove that exemption. Turn off User ID tracking in the site settings, remove heatmap and session recording scripts from every template, and confirm no tag manager still loads them. The admin who owns the tag container confirms this in writing, and a crawl of key pages in a staging copy shows no related requests. For Plausible, confirm that no equivalent identifiers or add-on scripts are injected.
Confirm no marketing measurement is configured
Review goals, campaign parameters, advertising integrations, remarketing tags and any connected ad platform or conversion pixel. The CNIL criteria exclude marketing measurement, so any advertising tag on the same pages can change the analysis even when the analytics tool itself is configured narrowly. The marketing owner and the analytics owner review the list together and record the decision for each tag. A removed or confirmed-absent tag list is the output.
Verify the Google Analytics import contents
If you import historical data, check exactly what the importer brings in. Matomo's importer brings aggregated report data only, and Plausible's importer brings daily aggregates and can include Search Console keyword data when the Google integration is configured. Confirm that imported reports contain no fields outside your inventory and that no user-level data enters the new tool. The analytics owner documents the import settings and the date range so the record shows what was brought across.
Verify server location and admin access paths
Record where the database, application and backups physically run, and which accounts, support vendors or remote connections can view data. The EDPB guidelines treat remote access from a third country, even display-only support access, as a transfer, so list every such path. The infrastructure owner produces a diagram and an access register, and confirms that backup copies sit in the same approved locations. Ask any hosting or support provider to confirm their access model in writing.
Get the configuration signed off
Send the inventory, the CNIL comparison, the tag review, the import record and the access register to counsel or to the data protection authority guidance that applies to your organization. Ask them to confirm whether the configuration fits the exemption, or whether a consent banner is still needed. Record their decision, the version of the configuration reviewed, and the date. Re-run this sequence after any change to tracking, tags, hosting or the analytics version, because the sign-off covers only the setup reviewed.
Questions buyers ask before hiring help with consent and GDPR
Does Plausible need a cookie banner?
Plausible's own homepage describes its service as using no cookies, so that no cookie banner is required. That claim is the vendor's description, so confirm it against your own configuration and the current version you run. The banner question is still a legal one: whether a banner is needed depends on what else your site sets, such as embedded video, chat widgets, advertising pixels or consent-gated tags. Those components are outside the analytics script and need their own review. Ask your counsel to map every third-party element on the pages in scope before you drop the banner.
Does Matomo need a cookie banner under CNIL rules?
It can avoid one, but only in a specific configuration. Matomo's ePrivacy FAQ says France's CNIL recognizes some audience measurement trackers as exempt from consent when they are limited to purposes such as performance measurement, collect only anonymous statistics and exclude marketing measurement. The same FAQ names Italy, the Netherlands and Spain as authorities that exempt certain privacy-focused analytics when their criteria are met, and suggests following the CNIL configuration for those countries. Each authority's criteria still need to be read against your own setup, and the exemption is a matter for your legal team to confirm.
What turns off the consent exemption in Matomo?
Adding features that go beyond anonymous performance measurement removes the exemption. Matomo's ePrivacy FAQ names User ID, heatmaps and session recordings as examples. Heatmap and Session Recording is a paid premium plugin sold under the InnoCraft EULA, so enabling it is both a licensing decision and a consent decision. Other settings to review include custom dimensions that capture identifiers, cross-site tracking and any marketing or advertising use of the data. Once the exemption is lost, the banner, consent records and cookie configuration become your obligation again, and the work to restore them is a separate scope item.
Does self-hosting change the GDPR position for analytics?
Self-hosting keeps the data in your own infrastructure, which narrows the transfer questions, but it does not remove your GDPR duties. Your organization stays the controller for analytics data whether it runs Matomo or Plausible on-premises or in a cloud account. Hosting location still matters: under the EDPB Guidelines 05/2021, remote access from a third country, even only displaying data on a screen for support, counts as a transfer, and so does storage in a cloud outside the EEA. Confirm where support staff and any managed provider access the servers from, and document that in your records of processing.
How much effort do configuration and legal review take, and who pays for each part?
Effort splits into technical configuration and legal review, and each is paid by a different party. Technical work covers installing the platform, setting the consent-exempt configuration, disabling features that remove the exemption, testing tag behavior and documenting the settings. Legal review covers reading the rules of each authority that applies to your audience and confirming the position against your processing records. Your internal counsel or privacy office usually owns the legal review, while an implementation partner such as DeployOpen can be scoped to the technical work and the evidence. Neither part is priced here. Ask for each as a separate line in a written scope, with the assumptions behind any time estimate.
Can our team configure consent and GDPR settings without outside help?
Yes, if you have a team that can read the vendor settings and a privacy owner who can sign off the legal position. Plausible Community Edition and Matomo On-Premise both document their analytics settings, and the configuration itself is not complex. The harder parts are keeping the configuration unchanged over time, since a later plugin or tag can silently remove an exemption, and running upgrades without losing settings. Plausible's self-hosted documentation says Community Edition operators manage installation, upgrades, backups and security themselves, and security fixes arrive only when you apply a release. Decide who owns each of those duties before you start.
What should a written scope for consent and GDPR work include?
A written scope should name the platform and edition, the sites and pages in scope, the consent position you want for each authority, and the features that must stay off. Ask for a list of every configuration change, the evidence produced (screenshots, settings exports, test results), and what the legal review covers versus what it leaves to your counsel. Require a statement of who makes the final legal determination, and that no output is an audit report or certification. Ask how changes after go-live are handled, including upgrades and new plugins. Most engagements are fixed-scope, so these items should be written before work starts.
When consent should decide the choice
Consent should decide the choice only when the site needs basic traffic metrics and nothing else. If the goal is pageviews, referrers and top pages, and the team will not add marketing measurement, heatmaps or session recordings, both platforms can run without a cookie banner for that purpose. Matomo's exemption depends on configuration. Its ePrivacy FAQ says the CNIL recognizes some audience measurement trackers as exempt when they are limited to performance measurement, collect only anonymous statistics and exclude marketing measurement. Plausible's position is simpler: its homepage says it uses no cookies, so no cookie banner is required. Your legal team still has to confirm the reading for each jurisdiction where you operate.
The decision changes once marketing or behavioral features enter the plan. Matomo's FAQ states that adding User ID, heatmaps or session recordings removes the CNIL exemption, so a site that later enables the Heatmap and Session Recording plugin must treat itself as needing consent again. Plausible's Community Edition has no heatmaps or session recording to add, but it also lacks marketing funnels and user journeys, so a team that needs those will look elsewhere regardless of consent. Check each feature against the consent rules before you turn it on, and record that check as part of your change process.
Before you commit, confirm three things with your privacy counsel and your own configuration: which EU authority applies to your visitors, whether your Matomo settings match the exemption criteria that authority publishes, and whether any tag, plugin or import in your stack sets cookies or stores identifiers that the exemption does not cover. Matomo's ePrivacy FAQ names France, Italy, the Netherlands and Spain and suggests following the CNIL configuration for the last three, which is a starting point, not a legal opinion. Self-hosting does not change the cookie analysis by itself, but it does put you in control of the settings, so the configuration review is yours to own.
How DeployOpen works on this
DeployOpen plans, implements, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Matomo or Plausible decision, that means mapping your consent position, data flows and hosting location before any tag goes live, then delivering a configuration and evidence pack your privacy and legal teams can review.
How we scope
- Confirm which EU authorities your audience sits under and which tracking purposes you actually need.
- Record in writing whether you intend consent-exempt Matomo settings or a cookieless Plausible deployment.
- Agree a fixed scope listing deliverables, timelines and the legal review you will own, before work starts.
How we build
- Configure Matomo or Plausible settings to match the chosen position, such as disabling User ID and heatmaps where they remove the exemption.
- Map data flows, hosting location and any third-country access paths your processor and cloud provider expose.
- Test tag behavior on live pages to confirm no non-essential identifiers or cookies are set under the chosen design.
How we hand over
- Document the configuration, data flow map and consent decision so an auditor or regulator can trace each setting.
- Provide an operator runbook covering upgrades, backups, access control and who approves any later feature change.
- Walk your team through the record of processing inputs and the questions to put to your legal counsel.
How we support
- Ongoing support, upgrades and periodic re-testing of tracking behavior are available as a retainer.
- Re-review the configuration when Matomo or Plausible releases change defaults, plugins or data handling.
- Confirm with your legal team any change in regulator guidance, since DeployOpen prepares evidence but does not issue certifications.
Sources and further reading
- Matomo FAQ: ePrivacy Directive national implementations and website analytics ↗
- Plausible: Self-hosted web analytics (Community Edition) ↗
- Regulation (EU) 2016/679 (GDPR), EUR-Lex ↗
- EDPB Guidelines 05/2021 on the interplay between Article 3 and Chapter V of the GDPR (version 2.0) ↗
- EDPB Recommendations 01/2020 on measures that supplement transfer tools (version 2.0) ↗
- Commission Implementing Decision (EU) 2023/1795 on the EU-US Data Privacy Framework, EUR-Lex ↗

