Mouseflow
How to configure Mouseflow at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for Mouseflow and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. The Mouseflow tracking script (session recordings, heatmaps, funnels, forms) on a website. Mouseflow ApS is a Danish company.
What the service does in this scope. Mouseflow states that it uses only first-party statistics cookies with a lifetime of no more than 90 days, no third-party cookies and no cross-site tracking. Customers can delay data collection until consent or "disable cookies entirely and still capture sessions, heatmaps, and funnels". EU customer data is stored in the EU; international transfers rely on SCCs and the EU–US Data Privacy Framework. Content can be excluded or masked with the Visual Privacy Tool.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Cookies disabled; content masked; loaded after consent. |
| Configuration B — Medium risk (default) | First-party cookies (≤ 90 days); default masking; loaded after consent. |
No configuration without prior consent. Even with cookies disabled, Mouseflow records sessions and transmits interaction data. Mouseflow documents integration with consent tools but does not document a consent-free configuration, so both configurations load after consent.
Step 1 — Configure Mouseflow
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Cookies | Website/tracking settings (disable cookies) | Disabled | Enabled (first-party, ≤ 90 days) |
| 3 | Masking and exclusion | Visual Privacy Tool (exclude, mask, whitelist) | Mask all text containing personal data; exclude sensitive pages | Default masking |
| 4 | Do Not Track | Account privacy settings (automatic for EU/EEA accounts) | On | On |
| 5 | Data location | Account region | EU | EU |
| 6 | Loading | Consenter script blocking | After consent | After consent |
| 7 | Retention | Plan-dependent; per DPA | Shortest available | Plan default |
Step 2 — Map the configuration in the Consenter Manager
Processing location. EU storage for EU customers. Check Mouseflow's sub-processor list; where US sub-processors are used, list the United States as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) |
| Identifier | IP address | Device identifiers, IP address |
| Data categories | Browsing and interaction data, Device characteristics, IP address | Browsing and interaction data, Device characteristics, Device identifiers, IP address |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per plan / DPA | Cookies ≤ 90 days; data per plan / DPA |
| Processing location | EU; US if US sub-processors | EU; US if US sub-processors |
Privacy-policy follow-up
- Mouseflow as processor; recordings and heatmaps; cookies (B) or cookieless (A); masking; EU storage; transfer mechanisms.
Verification checklist
- No Mouseflow requests before consent.
- A: no
mf_*cookies set. - Recordings reviewed for unmasked personal data.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on