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.

Workspaces on Pro and up can keep their analytics data in the European Union instead, in D1 and R2 storage created with Cloudflare’s EU jurisdiction. We set this before the workspace’s first data arrives; data already stored is not moved automatically. Email chris@metrickle.com to set it up.

Some data stays in one global account database wherever analytics data is stored: account details (sign-in, workspaces, members, billing), app and survey settings, and, for now, feedback message text, study participants' contact details and the evidence in cases.

See which release is costing you conversions, and who it broke for

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

Start free