Privacy at Datamano
Datamano measures how people use a website for the company that runs it. This page describes, as precisely as we can, what the Datamano tracker collects on those websites, where it is stored, for how long, and who processes it.
No cookies, and nothing stored without consent by default
The tracker never sets cookies. By default it stores nothing in the visitor's browser: a visit is recognised for one day only, from a fingerprint computed on our servers (a hash of the IP address and browser signature with a daily salt that is destroyed after two days).
A visitor is recognised across visits, through an identifier kept in the browser's local storage for up to 13 months, only when the visitor has consented (through the site's consent banner, Google Consent Mode or IAB TCF purpose 1), or for visitors located in the United States when the site keeps the default “Automatic by country” setting. A site can choose “Strict everywhere”: then no visitor is recognised across visits without consent. A refusal is remembered for 6 months.
The tracker stops when a browser sends Do Not Track or Global Privacy Control, unless the site owner turned this off.
What the tracker collects
- Pages viewed: the address (without its fragment; email addresses, tokens and sensitive query values are replaced by “redacted”), the title, the referrer, campaign tags and ad click identifiers, the screen width, and whether the page was shown, hidden or preloaded when it started loading.
- Interactions: clicks (position, element and up to 80 characters of its text), scrolling, time spent in form fields. For a link to another site, or a click that is repeated, unanswered or slow to answer, the address of the link is kept, cleaned like a page address: an email or phone link (
mailto:,tel:) keeps only its kind, never the address or the number. The value typed in a field is never collected; password, email and phone fields are ignored entirely. Copying and text selection are counted by length only. - Page quality: JavaScript errors and loading performance (web vitals).
- Page structure: titles, headings, buttons and form labels of the pages, to name the areas visitors interact with.
- Device: browser, operating system and device type, derived from the browser signature, which is not stored.
- Identified visitors: when a site calls
identify(), the identifier it passes is hashed before storage; other attributes are discarded unless the site explicitly enables them. - Console and network logs: only if the site turns them on; request and response bodies are never collected.
Session replays
A replay reconstructs a visit from the page's structure, not a video. Every form field is masked, and email addresses, phone numbers, card numbers, bank account numbers (IBAN) and tokens are masked in the browser, before anything is sent: in the text displayed on the page, and in the element attributes that carry text (image descriptions, tooltips, accessibility labels, data- attributes, the values of options, buttons and checkboxes). Email and phone links (mailto:, tel:) keep only their kind, never the address or the number, and an email address inside any other link is masked. Names and postal addresses shown as plain text are not detected automatically: sites mark such areas with the data-dm-mask attribute (or data-private) to mask them.
A visit is kept as a replay when it shows a strong signal (repeated clicks, form errors and similar) or in a 3% sample. Nothing is recorded before the visitor consents, wherever the visitor is (through the site's consent banner, Google Consent Mode or IAB TCF purpose 1, or the site's own consent call): the replay starts at that moment, and each replay keeps a record of that consent (how it was given and when). When a visitor declines consent, recording stops and anything not yet sent is discarded; a browser that sends Do Not Track or Global Privacy Control is not recorded.
IP addresses
IP addresses are never stored in clear. At collection time the address is used to look up the country, region, city and network in our own geolocation database, kept in Paris: the address is never sent to a third party, and no lookup is made when the browser sends Do Not Track or Global Privacy Control. It is also used to limit abusive traffic for one minute, then stored only as a truncated salted hash.
How long data is kept
| Data | Kept for |
|---|---|
| Page views, events, visits and visitor aggregates (analytics storage) | 12 to 13 months: data is deleted one whole month at a time, once the last day of that month is a year old |
| Session replays | 30 days at most from the start of the recording (shorter on some plans) |
| Page screenshots | 90 days; screenshots of A/B test variants are kept as long as the test |
| Network of a visit (ASN) | 13 months |
| Console and network logs (only if the site turned them on) | 30 days |
| Visits in the operational database | 4 days; country, device and entry page are cleared after 24 hours |
| Visitor records in the operational database | 12 months after the last visit; 2 days for visitors recognised for one day only |
| Hashed IP addresses used to limit abusive traffic | 2 hours |
| Chat Analyst conversations | 180 days after their last message (or earlier if the user deletes them); in a longer conversation, the detailed analysis results of answers older than 180 days are cleared |
Who processes data
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, accounts, server functions (including the collection endpoint) and file storage | Database in Paris, France (AWS eu-west-3); functions run at the edge location nearest the caller |
| ClickHouse Cloud | Analytics storage: page views, events, visits and session replays | Ireland (AWS eu-west-1) |
| Netlify | Hosting of the Datamano app and of the tracker script | Functions in Ireland (Dublin); static files served from a global CDN |
| Google (Gemini API) | AI analysis in the Chat Analyst: questions, results of the analyses run for them, voice dictation, replay summaries, page screenshots | Google's global endpoint |
| DeepSeek | AI analysis in the Chat Analyst (choice and use of analysis tools, review of answers) and in the event composer | DeepSeek's API |
| Stripe | Billing: email address and account identifiers of paying customers; cards and billing addresses stay with Stripe | Stripe |
Erasure, deletion and export
- Erasing a visitor: the owner or an administrator of a site can erase everything recorded about one visitor (analytics, replays and the copies kept in Chat Analyst answers) from the replay player.
- Deleting an account: deleting a Datamano account cancels its subscription and deletes its sites (those it alone owns), their analytics, replays and files. Stripe keeps its own billing records.
- Export: site owners can export their events and page views (CSV, up to 365 days).
Who answers your requests
- You visited a website that uses Datamano: the company that runs that website decides what is measured and answers requests about your data (access, erasure, objection). Contact it directly: it can erase everything recorded about you in Datamano, as described above.
- You have a Datamano account: you can export your sites' data and delete your account, with everything attached to it, from your account settings.