What the tracking tag collects and what it doesn’t
| Collected | Not collected |
|---|---|
| The URL (path) and title of the pages viewed | Cookies and localStorage (never written) |
The referrer (where the visitor came from) and UTM parameters (only an allowlist such as utm_source) | Any other query strings (not sent, since they could contain personal information) |
| Device type (desktop / mobile / tablet) and a screen-width bucket | Storing the IP address or user agent (they’re used only as hash inputs and never stored) |
| Country and region (determined from the IP, which is then discarded) | The contents of input forms, such as names and email addresses |
| Ecommerce events (product view, add to cart, checkout start, purchase), plus the order number and amount for purchases | The buyer’s name, address, or contact details |
How visitors are identified
The visitor identifier is a hash of “a salt that changes daily + site ID + IP + user agent”.
- The IP and user agent are never stored. They’re discarded after being used as hash inputs.
- The salt changes every day, so the same person gets a different ID the next day. Individuals can’t be tracked across days.
- The site ID is part of the input, so visits aren’t linked across different sites.
This is why it’s designed to be installed without a consent banner. That said, the legal assessment depends on where your site operates and what your business does, so consult a specialist if needed.
What we receive in order data
The WooCommerce plugin and Shopify app send the order number, order date and time, currency, line items (product ID, name, SKU, quantity, revenue), tax, shipping, total paid, the order’s source, and the plugin version and site URL. The buyer’s name, address, email address, and phone number are not sent.
Where data is stored and for how long
- Servers are in a data center in Singapore (Render).
- Raw per-visit events are deleted after 90 days; only daily aggregates are kept.
- Order data is kept until you delete the site or your account.
- When you delete a site or your account, all data tied to that site or account is deleted. All that remains are aggregate values that can’t identify you or your sites.
Statistical use to improve the service
The results of improvement card follow-ups (the card type and the ratios when flagged and at the verdict) are used in statistics in a form that can’t identify the site or any individual. This is to replace the recovery-rate assumption with a measured value. See Article 11 of the Privacy Policy for details.
No tracking on local environments
On development environments such as localhost and *.local, the tracking tag does nothing. This keeps production numbers clean when you clone your production site.
Related pages
- Privacy-first — the design philosophy
- Privacy Policy — the legal document
- Terms of Service