Privacy and consent
Web Analytics is coming soon
Web Analytics is cookieless by default: it stores nothing on visitors' devices and keeps no IP addresses. This page lists exactly what that means, so you can describe it accurately in your own privacy notice.
What is never stored
- IP addresses. The IP is used in memory for the visitor hash, the country and region lookup, excluded-IP checks and rate limiting, then discarded. It is not written to any database, log or metric.
- Full user agents. Only the browser and its version, the operating system and its version, and the device class are kept.
- Query strings. Only
utm_source,utm_medium,utm_campaign,utm_content,utm_term,refandsourceare read; the rest of the query string is dropped before storage. - Cookies or device storage in cookieless mode. The script writes nothing to cookies or local storage, except a visitor's own opt-out choice when they make one.
Cookieless mode
Each visitor is identified by a keyed hash of the site, their IP address and their user agent. The key is a random salt that changes every UTC day and is deleted once the visits that began under it have ended, at most a day and 30 minutes after it was created. After that, a stored visitor id cannot be linked back to an IP address and user agent, even by Hubfly space.
What this means for your reports:
- The same person counts as a new visitor each day. Visitor totals over several days are the sum of daily unique visitors.
- There are no returning-visitor, retention or cross-day journey reports, and
identifyis ignored.
Because nothing is stored on the device and no personal data is kept, a consent banner is not needed for this mode under the GDPR and ePrivacy rules as commonly interpreted.
You remain responsible
Persistent mode
Choose Persistent ID under Visitor identity in the site's Settings → Privacy when you need returning visitors, retention or identify.
- The script keeps a random first-party id in local storage (
hfa_id) and sends it with each batch. Hubfly space stores a keyed hash of it, with a random key per site, never the raw id. hubfly('identify', userId)stores the user id you pass as given, so you can find that user's visits. Do not send email addresses or other direct identifiers you are not allowed to process.- This mode stores data on the device, so visitors in the EU need to give consent. Turn on Wait for consent: the script stays cookieless until your consent tool calls
hubfly('consent', true), andhubfly('consent', false)deletes the stored id.
Visitor and site controls
- Do Not Track. With Respect Do Not Track on, the script sends nothing from browsers that send
DNT: 1orSec-GPC: 1. - Opt-out. Offer a link or button that calls
hubfly('opt_out'); that browser then sends nothing to the site untilhubfly('opt_in'). - Exclusions. Visits that match Exclude pages or Exclude IP addresses in the site's Settings → Tracking are filtered before anything is stored.
Retention and deletion
- Raw events are deleted after the site's retention: 30 days by default, adjustable from 30 to 365 days.
- Daily summaries, which power long-range trend charts, are deleted after 730 days.
- Deleting a site deletes its database immediately.
- Raw events are not backed up. Settings and daily summaries are backed up nightly, and those backups follow the same deletions within 30 days.
Where data is kept
A site's data stays in the region of its project, and its events are sent only to that region's HubProxy. No third party receives raw events. Country and region lookups use the DB-IP Lite databases, licensed CC BY 4.0: IP geolocation by DB-IP.