Set up your bannerConfigure Your ToolsSession Recording and Heatmaps

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Lower riskCookies 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 areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk (default)
1Processing purposesOperator decisionImprove the serviceImprove the service
2CookiesWebsite/tracking settings (disable cookies)DisabledEnabled (first-party, ≤ 90 days)
3Masking and exclusionVisual Privacy Tool (exclude, mask, whitelist)Mask all text containing personal data; exclude sensitive pagesDefault masking
4Do Not TrackAccount privacy settings (automatic for EU/EEA accounts)OnOn
5Data locationAccount regionEUEU
6LoadingConsenter script blockingAfter consentAfter consent
7RetentionPlan-dependent; per DPAShortest availablePlan 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 fieldConfiguration A — Lower riskConfiguration B — Medium risk (default)
Processing purposesImprove the serviceImprove the service
Tracking methodFirst party tracking (single session)First party tracking (cross-session)
IdentifierIP addressDevice identifiers, IP address
Data categoriesBrowsing and interaction data, Device characteristics, IP addressBrowsing and interaction data, Device characteristics, Device identifiers, IP address
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer plan / DPACookies ≤ 90 days; data per plan / DPA
Processing locationEU; US if US sub-processorsEU; 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

On this page