Privacy

How tracking works

Betterdata is currently in free beta user testing. This page explains how its website analytics tracker handles visitor data.

The default tracker stores a random anonymous visitor ID in your browser’s localStorage. It does not set an analytics cookie or use fingerprinting. Persistent browser storage may require consent depending on the website and jurisdiction.

Privacy modes

Owners can also choose first-party cookie identification. This stores a random visitor ID on the current hostname for up to one year, using SameSite=Lax and Secure on HTTPS. The generated cookie-mode snippet requires the website to grant consent before tracking starts. Revoking consent deletes this ID cookie.

Website owners can choose memory-only identification: the ID then lasts only for the current page lifetime. Reloading can count as another visitor. With data-consent="required", tracking waits until the website calls betterdata.consent(true). All modes honor Do Not Track and Global Privacy Control. A browser can call betterdata.optOut() to keep tracking off on that origin until betterdata.optIn() is called.

Read the identity and consent guide for the setup steps and attribution trade-offs.

Data collected

Page paths, browser-provided referrer origins and paths (without query strings or fragments), source/campaign fields, event names, browser/device categories and approximate edge-derived location. Raw IP addresses and full URL query strings are not stored by the tracker. Custom event properties are supplied by the website owner, who must avoid personal or sensitive data.

Account data

When you sign in, we store your provider account ID, display name, avatar and verified email address to operate your account. We record when you accept our Terms and acknowledge this Privacy Policy. The service owner can see account details and connected website names for support, plus aggregate service health counts and per-website visitor totals (all time and the last 30 days), in a private admin view for service operations and support. This view does not include individual visitor identities, browsing journeys, or payment details.

Identified journeys

When you sign in to Betterdata, we link recorded anonymous activity to your account when tracking is enabled. Website owners can also use a server integration to link their authenticated customers to earlier visits, using a stable user ID and optional name and email. Verified payments may include plan, amount, currency and status. These profiles are restricted to authorized private analytics access; public shared reports do not include customer profiles or their identifiers. Signing out resets the Betterdata browser visitor ID. We do not infer identity from matching email addresses.

Google Search Console

If you connect Search Console, we store an encrypted Google authorization credential and aggregate search queries, pages, countries, devices, search appearance and performance metrics for the property you select. We use read-only access to provide your search reports and clearly labeled revenue estimates. Search queries are not linked to individual visitors. Authorized website team members can view these reports. Disconnecting deletes this website’s stored credential and imported search data; you may also revoke the application grant through your Google account. Read the connection and reporting guide.

Deletion

Website owners can delete their website and associated analytics in website settings. Anonymous IDs do not establish a person’s identity, and missing referrers remain unknown.