Mouseflow vs Offen Fair Web Analytics

Compare Mouseflow and Offen Fair Web Analytics on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Hotjar

Mouseflow

Denmark· Web Analytics

Needs review

Shortlist when you need session replay, heatmaps, friction scoring, and journey/funnel analysis from a Danish SaaS with public DPA and pin-able EU (Belgium) or US (Iowa) Google Cloud residency. Skip when you only need cookieless pageview analytics, must avoid US-group cloud or US affiliate processing, or require self-host—consider etracker, Friendly Analytics, or a self-hosted stack instead.

Session replayHeatmaps + friction scoresEU or US residencyDPA availableDenmark HQISO 27001 DC (claimed)

View listing Visit Website

Offen Fair Web Analytics

Germany· Web Analytics

Needs review

Shortlist when you want self-hosted, Apache-2.0 analytics that only measures after opt-in, encrypts events in the browser, and lets visitors open their own data in the Auditorium. Skip when you need cookieless full-coverage metrics, session replay/heatmaps, or zero-ops managed EU hosting—consider Plausible, Pirsch, or Friendly Analytics instead.

Opt-in onlyBrowser E2E encryptionSelf-hostedApache-2.0Visitor data accessBerlin-based project

View listing Visit Website

Highlighted rows differ between the two products.

Mouseflow vs Offen Fair Web Analytics: Snapshot
Feature	Mouseflow	Offen Fair Web Analytics
Country of origin	Denmark	Germany
Category	Web Analytics	Web Analytics
Open source	No	Yes
Self-hosted	No	Yes
Headquarters	Denmark	Germany
Legal entity	Mouseflow ApS, Flæsketorvet 68, 1711 Copenhagen V, Denmark; affiliate Mouseflow, Inc., Austin, Texas	Public legal notice lists Frederik Ring, Berlin (offen.software); product authors Frederik Ring and Hendrik Niefeld—no separate GmbH name verified on imprint
Governing law	Denmark (DPA); courts of Copenhagen for DPA disputes	Germany (indicative from Berlin imprint)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Low
Hosting / residency	Google Cloud EMEA Limited storage/hosting in Belgium (EU) and Iowa (USA); region by signup geography (EU customers → EU; Americas/Oceania → US). Affiliates Mouseflow ApS (DK) and Mouseflow, Inc. (TX) process Customer Data for support/implementation; DoiT Multi-Cloud Sverige (SE) for multi-cloud consulting.	Product is operator self-hosted (your VPS/cloud/on-prem). No Offen multi-tenant analytics SaaS or vendor subprocessor list for visitor events. Related marketing site (offen.software) names Hetzner Online GmbH (Germany) as host—not the analytics data path. Optional community deploys include Heroku (operator choice).
Summary	Denmark-headquartered behavior analytics SaaS: session replay, heatmaps, friction detection, journey analytics, and AI insights for CRO and UX teams, with EU or US Google Cloud residency and a public DPA.	Open-source, self-hosted web analytics with opt-in consent, browser-side end-to-end encryption, and a shared Auditorium so visitors can see and control their own usage data.
Tags	analytics gdpr session-replay heatmaps friction saas enterprise ai cro	analytics gdpr open-source privacy self-hosted opt-in e2e-encryption

At a glance: Mouseflow vs Offen Fair Web Analytics
At a glance	Mouseflow	Offen Fair Web Analytics
HQ	Copenhagen, Denmark	Not listed
Legal entity	Mouseflow ApS (+ Mouseflow, Inc. US affiliate)	Not listed
Category	Behavior analytics / session replay SaaS	Not listed
Hosting	Google Cloud Belgium (EU) or Iowa (US)	Not listed
Self-host / OSS	No / No	Not listed
Commercial model	Session-volume SaaS; free tier; unlimited users	Not listed
HQ / authors	Not listed	Berlin, Germany (Frederik Ring & Hendrik Niefeld)
License	Not listed	Apache-2.0 (code/docs); logo CC-BY-NC-ND-4.0
Delivery	Not listed	Self-host only (binary, Docker, community deploys)
Consent model	Not listed	Opt-in only; first-party cookies
Default retention	Not listed	6 months (configurable shorter)
Funding note	Not listed	NLnet NGI support (project-stated)

Key capabilities: Mouseflow vs Offen Fair Web Analytics
Key capabilities	Mouseflow	Offen Fair Web Analytics
Session replay	Yes	Not listed
Heatmaps + friction scores	Yes	Not listed
EU or US residency	Yes	Not listed
DPA available	Yes	Not listed
Denmark HQ	Yes	Not listed
ISO 27001 DC (claimed)	Yes	Not listed
Opt-in only	Not listed	Yes
Browser E2E encryption	Not listed	Yes
Self-hosted	Not listed	Yes
Apache-2.0	Not listed	Yes
Visitor data access	Not listed	Yes
Berlin-based project	Not listed	Yes

Mouseflow

Full-session replay without sampling
Records complete visitor journeys—clicks, scrolls, navigations, device context—for later playback, starring, tagging, and sharing. Mouseflow markets 100% recording (no sampling) so rare bugs and checkout failures are not lost to traffic samples; filter by source, device, page, or friction events before reviewing.
Heatmaps with segment and period comparison
Click, scroll, movement, and attention heatmaps overlay page layouts so teams see ignored CTAs and fold issues. Compare devices, campaigns, or time ranges side by side to measure redesign impact without running a separate heatmap product.
Friction Detection and Mina AI prioritization
Automated scores surface rage clicks, dead clicks, hesitations, form abandons, and JavaScript errors, with links into the underlying replays. Mina AI answers natural-language questions about sessions and heatmaps so analysts spend less time manual-filtering queues.
Journey maps, funnels, forms, and surveys
Multi-page Journey Analytics, conversion funnels, field-level form analytics, and on-site feedback surveys sit in one workspace so drop-off diagnosis does not require four vendors. Useful for CRO and ecommerce teams closing the loop from path → leak → fix.
EU or US data residency on Google Cloud
Public subprocessors list Google Cloud EMEA Limited with Belgium (EU) and Iowa (USA) storage. Signup geography determines default region (EU customers → EU; Americas/Oceania → US). Confirm contracted region and subprocessor annex before treating residency as guaranteed.
Privacy controls, DPA, and Visual Privacy Tool
Vendor defaults include IP masking, keystroke exclusion for EU visitors, and field/element masking; customers must still audit HTML for PII. A public B2B DPA is available for electronic signature, with SCCs/DPF language for international transfers.

Offen Fair Web Analytics

Opt-in only collection with first-party cookies
No analytics events are recorded until the visitor actively consents. Cookies are first-party and the tracker is meant to run on a same-site subdomain so third-party cookie restrictions and cross-site tracking models do not apply. Visitors who never opt in leave no usage trail—expect lower absolute volumes than cookieless tools that measure by default.
Browser-side end-to-end encryption of usage events
Clients encrypt usage data before it leaves the browser; the server stores ciphertext and cannot decrypt events alone. Only the visitor (via their cookie) and the matching operator account can open that visitor's data in the Auditorium. Practical impact: a compromised database or overly broad ops access does not yield plaintext browsing histories the way a typical self-hosted analytics DB would.
Auditorium for both operators and visitors
Operators see aggregates across pages where the installation is active (unique users/sessions, top pages, filters). Each opted-in visitor can open the same style of UI for their own data only, with plain-language metric explanations, and can delete data or fully opt out later. This is the fair design point: measurement is not a one-way glass.
Essential metrics without IP or User-Agent capture
Dashboards cover real-time activity, page views, unique users and sessions, bounce rate, returning users, top pages, referrers, UTM campaign/source, landing and exit pages, weekly retention, and load time. Location is country-level from timezone mapping; mobile share uses orientation capability—not IP geolocation or UA parsing. No heatmaps, session replay, or warehouse-grade product analytics.
Lightweight self-host: binary, Docker, SQLite or SQL
Production installs use a single binary (Linux/Windows/macOS) or the offen/offen image; docs also cover Heroku, Uberspace, and YunoHost. Default store is SQLite; MySQL and Postgres are supported. AutoTLS can request Let's Encrypt certificates. Config is environment variables or offen.env. You own uptime, backups, SMTP for password reset, and the subdomain layout.
Multi-site accounts, teams, and short retention
One installation can cover multiple websites with shared team access. Default retention is six months with automatic deletion; operators can shorten retention (e.g. 12 weeks, 30 days, 7 days) knowing shorter values purge older events on startup. Consent banner appearance is customizable; UI locales include EN, DE, FR, ES, PT, and VI.

Assurance & compliance: Mouseflow vs Offen Fair Web Analytics
Assurance & compliance	Mouseflow	Offen Fair Web Analytics
Independent security / no-logs audit	Partial Vendor claims third-party penetration/vulnerability tests and offers a Security Kit; no public independent no-logs audit report found for download without request.	Not found No public third-party audit PDF found; coordinated disclosure via SECURITY.md email only.
ISO 27001	Vendor claimed Vendor states data centers maintain ISO 27001; request Security Kit for certificate scope—not independently re-verified against a public registry in this draft.	Not found No public ISO 27001 certification claim found on official site or docs.
SOC 2 / SOC 3	Partial Privacy page mentions SOC 2 Type II-certified infrastructure; compliance/About emphasize SOC 1 Type II for data centers; FAQ prefers SOC 1 as internal standard. Confirm report type/scope via Security Kit.	Not found No public SOC 2/3 report found.
GDPR / EU data protection	Vendor claimed Danish entity; public GDPR page, DPA, IP masking, EU residency option, SCCs/DPF transfer language. Customer remains responsible for consent and PII exclusion from HTML.	Vendor claimed EU authors; opt-in, data minimization (no IP/UA), visitor access/erasure, short default retention, Datensparsamkeit framing. Self-host means operator remains controller—confirm your legal basis and notice.
US CLOUD Act exposure (indicative)	Partial Danish entity, no known US parent; session data on Google Cloud (Belgium/Iowa) and US affiliate Mouseflow, Inc. may process Customer Data. EU residency does not eliminate US-group cloud risk. Indicative only—not legal advice.	Partial EuropeanStack assessment: no known US parent; product not delivered as US-hosted vendor SaaS. Operator-chosen infrastructure (including optional Heroku/US cloud) can still create CLOUD Act paths for stored ciphertext/metadata. Not legal advice.
Data processing agreement (B2B)	Vendor claimed Public DPA at mouseflow.com/legal/data-processing-agreement/ with electronic signature; SCCs and DPF language included.	Not applicable No multi-tenant vendor analytics processing relationship documented; operator self-hosts and is typically controller. Custom development/support via offen.software is separate from a standard SaaS DPA.
EU AI Act	Not applicable Behavior analytics SaaS with optional AI assistants (Mina, MCP); not positioned as a high-risk AI system product for this checklist.	Not applicable Web analytics metrics product; not an AI system product.
PCI DSS (data center)	Vendor claimed Vendor states data centers maintain PCI DSS compliance; not a substitute for customer PCI scope on payment pages—mask card fields.	Not listed

Considerations & known limitations: Mouseflow vs Offen Fair Web Analytics
Considerations & known limitations	Mouseflow	Offen Fair Web Analytics
Google Cloud (US-group) hosts session data	Medium Even EU-region (Belgium) storage uses Google Cloud EMEA Limited. Material for DPIAs that treat any US-group cloud as in scope for CLOUD Act/transfer analysis.	Not listed
US affiliate processes Customer Data	Medium Mouseflow, Inc. (Texas) is listed for consulting, support, maintenance, implementation, and development on Customer Data—not only a marketing office.	Not listed
Session replay can capture unexpected PII	Medium Defaults mask IPs/keystrokes/sensitive fields, but customers must audit DOM/HTML, forms, and custom variables; incidental PII is a shared-responsibility risk in this category.	Not listed
ISO/SOC claims are data-center scoped	Low Public materials emphasize infrastructure certifications; SOC 1 vs SOC 2 wording differs across pages—verify current reports rather than assuming org-wide SOC 2.	Not listed
SaaS-only (no self-host)	Low Closed multi-tenant SaaS only; no official on-prem path if residency or operator control requirements demand it.	Not listed
Opt-in undercounts absolute traffic	Not listed	High Visitors who never consent generate no events. Growth and content KPIs will not match cookieless tools or GA-style default measurement—treat as design, not a misconfiguration.
You own uptime, backups, and secrets	Not listed	Medium No managed Offen cloud. Operators must run HTTPS/subdomain layout, set OFFEN_SECRET for stable sessions, configure SMTP for resets, and back up SQLite/SQL—plus avoid reverse proxies that log IPs if minimization is a goal.
E2E crypto is vendor-claimed architecture	Not listed	Medium Browser-side encryption and server inability to decrypt are core claims from project docs/README, not independently audited in public materials found. Security-sensitive orgs should review source or commission assessment.
Hosting choice reintroduces cloud jurisdiction	Not listed	Medium Self-host on US-group cloud or Heroku means CLOUD Act/subprocessor analysis shifts to your host even though Offen itself is Berlin-based OSS without a vendor SaaS region map.
No public ISO/SOC or audit pack	Not listed	Low Procurement checklists that require vendor ISO 27001/SOC 2 will stall; evidence is open source and design docs, not cert registry entries.
Essential metrics only	Not listed	Medium No heatmaps, session replay, advanced funnels, or product-analytics warehouse features. Wrong tool if the shortlist criterion is UX research depth rather than fair traffic statistics.

Fit

Mouseflow

Best fit when

CRO, UX, and ecommerce teams that need full session recordings linked to heatmaps and funnels
Mid-market orgs wanting public session-volume packaging and unlimited seats rather than per-seat DX platforms
EU buyers who can accept Google Cloud hosting if Customer Data is pinned to the Belgium region
Teams that want vendor friction scoring and Mina AI triage instead of manual replay queues only
Procurement that requires a signable DPA, SCCs/DPF language, and a published subprocessor list

Poor fit when

Sites that only need cookieless aggregate web analytics without DOM session replay
Hard sovereignty mandates that forbid US-group cloud (Google Cloud) or any US legal entity in the support path
Buyers requiring open-source or official self-hosted deployment
Enterprises standardized on Contentsquare/FullStory-class platforms who need deep custom DX integrations already covered there

Consider instead when

When: You need cookieless traffic analytics without session replay depth
Consider: etracker or Friendly Analytics
Different category focus: measurement and privacy defaults vs high-fidelity replay
When: You want free heatmaps/replays and accept Microsoft as processor
Consider: Microsoft Clarity
Lower cost of entry; different privacy and commercial model
When: You need enterprise digital-experience analytics with heavy customization
Consider: Contentsquare or FullStory
Higher implementation and procurement weight
When: You need Swiss/EU product hosts with no Google Cloud visitor path
Consider: Friendly Analytics or fusedeck
Confirm each peer’s subprocessor list independently

Offen Fair Web Analytics

Best fit when

Public-sector, media, NGO, or mission-driven sites that need visitor-visible transparency and strict opt-in
EU teams that must keep analytics off third-party trackers and can run a small always-on instance
Operators who want first-party subdomain cookies, CSP-aware embedding, and no IP/User-Agent collection
Organisations evaluating fair-processing design over maximum measurement coverage
Teams comfortable with SQLite or SQL self-host ops (binary or Docker) and publishing their own privacy notice

Poor fit when

Product or growth teams that require near-complete traffic measurement without consent friction
Needs for heatmaps, session replay, funnels, or ad-ecosystem attribution comparable to Hotjar/Mixpanel/GA
Buyers seeking a vendor-managed multi-tenant analytics cloud with SLAs and a signed vendor DPA as processor
Large enterprises that require public ISO 27001/SOC 2 or third-party security audit packs before shortlist

Consider instead when

When: You want privacy-oriented analytics with managed EU hosting and lower consent friction
Consider: Plausible Analytics or Pirsch Analytics
Typically optimised for simpler cookieless or low-friction models and hosted plans; less radical visitor Auditorium design than Offen.
When: You need EU hosted privacy analytics with operator support and less self-host burden
Consider: Friendly Analytics
European catalog peer oriented to hosted privacy analytics; compare consent model and feature depth to Offen’s opt-in + E2E approach.
When: You need deep product analytics, funnels, or session UX tooling rather than fair traffic metrics
Consider: Hotjar, Mixpanel, or a full GA4 stack (with legal review)
Different category: richer product/UX analytics, different jurisdiction and subprocessor profile.

Open questions for due diligence

Mouseflow

Will the order form / DPA annex hard-pin EU (Belgium) residency for our account, including backups and AI features?
Which categories of Customer Data does Mouseflow, Inc. (Texas) access in day-to-day support?
Can the current ISO 27001 / SOC report package be validated (scope, dates, legal entity) via the Security Kit?
Are AI (Mina) and MCP features processed only in the same residency region as session storage?
What is the published retention default per plan and the process/SLA for deletion after offboarding?

Offen Fair Web Analytics

Will your traffic and KPI model tolerate opt-in-only measurement after a pilot on a non-critical property?
Where will you host the instance (EU on-prem/VPS vs US-group cloud), and who holds OFFEN_SECRET and DB backups?
Do procurement rules require third-party audits or ISO/SOC that Offen does not publish?
Do you need a signed vendor DPA as processor, or is controller-only self-host acceptable to counsel?
Is subdomain + CSP (script-src/frame-src + unsafe-inline styles for the banner) feasible on your main site?