Private and compliant, by design.
In the default cookieless mode there is no personal data to leak, because none is collected, and no consent banner to maintain. Turn on cookie mode per site when you need cross-session identity, and then you do need consent. Encrypted in transit either way.
Safe by default.
No personal data by default
Cookieless out of the box: a salted hash that rotates daily, no cookie, no fingerprint. Cookie mode is a per-site opt-in.
Encrypted in transit
The tracker, ingest and dashboard are served over HTTPS only.
Runs on Cloudflare
Processed at the edge and stored in Cloudflare D1 and R2.
Workspace roles
Owners, admins and members, so people get the access their job needs.
Replays mask inputs
Form inputs are masked at capture, before a recording leaves the browser.
Backups and retention
Site settings are backed up nightly and analytics weekly. Data past your plan's window is pruned.
How it works
Where your data lives.
- 1
Collected
A salted signal that rotates daily, or a first-party cookie if you turn cookie mode on.
- 2
Processed
At the edge, with bots filtered and visits deduplicated.
- 3
Stored
In Cloudflare D1 and R2, kept only as long as your plan's retention.
- 4
Yours
Exportable on request, and deleted with the site or account that owns it.
Compared
Consent, mode by mode.
Cookie mode (opt-in, per site)
- A first-party cookie recognises returning visitors
- Needs consent under GDPR and PECR
- Disclose it in your own privacy notice
Cookieless mode (the default)
- No cookie, no fingerprint, no cross-site identifier
- No consent banner needed as installed
- Visitor hashes reset every day
Reporting a vulnerability.
Email hi@mrkr.app with Security in the subject line, and include the steps to reproduce. We read every report, reply to each one, and fix confirmed issues as a priority. Please give us a reasonable window to ship a fix before you disclose publicly.
Start with one line of HTML.Your first visitors show up within a minute.