Metrickle

Security, privacy and accessibility at Metrickle

What Metrickle collects, how it is protected, who can see it and how to delete it, written to match what the product does today.

How Metrickle handles your data

Facts about how the product works today. Each one is explained on the pages above.

0raw IP addresses stored with events
0cookies or local storage in cookieless mode
DNT + GPChonoured by the web script by default
Offsession replay and heatmaps until you switch them on per app
Maskedevery input in session replay, and all text by default
SHA-256hashes stored for API tokens, never the token itself

Where data is stored

Analytics data (events, the session replay index, replay recordings, feedback screenshots and heatmap page snapshots) is stored per workspace in one location, in Cloudflare D1 and R2. By default that storage has no jurisdiction restriction, so Cloudflare decides where it sits.

EU data location for Enterprise workspaces is being set up and is not live yet. Email chris@metrickle.com if you need it, and we will confirm when it is available before any of your data arrives.

Wherever analytics data is stored, account details (sign-in, workspaces, members, billing), app and survey settings, feedback text and study participants' contact details are kept in one global account database.

See where your apps break, and who they break for

Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.

Start free