Skip to content
Documentation menu: Privacy and data protection

Privacy and data protection

Privacy features and data protection controls for your analytics

Privacy mode

Hide personally identifiable information during presentations and screen sharing

Data protection

The script sets two first-party cookies and does not store IP addresses with events. It is designed to help you meet your GDPR and CCPA obligations. Consent requirements depend on your jurisdiction.

First-party data

The script runs on your domain and sets only first-party cookies and localStorage entries. It sets no third-party cookies.

Privacy mode

Control how customer information is displayed on your dashboard and protect sensitive data during presentations or screen sharing.

When to use privacy mode

Presenting analytics to stakeholders

Recording training or demo videos

Taking screenshots for documentation

Working in public spaces

How privacy mode works

When privacy mode is enabled, the system will mask sensitive customer data:

Customer names

Replaced with placeholder dots (••••••••)

Email addresses

Masked format (••••••••@••••.com)

Customer initials

Replaced with generic user icon

Analytics data

Revenue, sources, and metrics remain visible

Enabling privacy mode

Two ways to turn privacy mode on
1

Dashboard header

Click the privacy icon in the dashboard header for quick access. This toggle is available on all dashboard pages.

Privacy toggle button
2

Settings page

Open Settings in the dashboard sidebar. The Privacy card there has the same switch, Hide customer identifiable information, with an explanation of what it masks.

Settings, Privacy card

Privacy persistence

Your privacy settings are saved to your browser's local storage and will persist between sessions until you change them. Each device or browser will have its own privacy setting.

Data protection

What the script stores, what we keep, and what stays your decision

Cookies and browser storage

The tracking script sets two first-party cookies on your domain and uses localStorage for attribution data. The cookies belong to the exact host unless you add the optional data-cookie-domain attribute, which shares them across your subdomains:

  • • thebizness_visitor_id: persistent visitor ID, 365 days
  • • thebizness_session_id: session ID, expires one hour after the last tracked activity
  • • thebizness_utm and thebizness_referrer_data in localStorage: UTM and referrer data, used for attribution for up to 30 days. The entry stays in the visitor's browser until it is replaced or cleared
  • • With data-cookie-domain, the script briefly sets and removes a test cookie, thebizness_cookie_domain_probe, to check that the browser accepts cookies for that domain
  • • No third-party cookies are set

The durations above are upper limits. Safari (macOS and iOS) and Brave cap cookies written by JavaScript at about 7 days, and Safari also clears localStorage after 7 days without a visit.

Whether you must show a cookie banner or obtain consent before the script runs depends on your jurisdiction. That decision is yours.

Personal data and consent

The script stores data that can identify or relate to a visitor:

  • • IP addresses are not stored with events. They are used only as a rate-limit key: held in server memory for about one minute for the per-minute limits, and as a keyed hash that expires within a day for the daily allowance of events reported from a browser
  • • Visitor and session IDs are persistent identifiers
  • • Customer names and emails can be hidden with privacy mode
  • • Send customer emails from your server, never from the browser
  • • You are responsible for consent where your jurisdiction requires it

What we keep, and for how long

  • • Raw pageviews, custom events and conversion events are deleted automatically after 25 months
  • • Revenue records are kept while your account exists. Each conversion you send is also stored as a revenue record
  • • Stripe keys, webhook secrets and ingest secrets are encrypted at rest
  • • Deleting a website or your account deletes its data, including recorded revenue, and removes the Stripe webhook endpoint (best effort)
  • • Disconnecting Stripe removes the webhook endpoint (best effort) and deletes the saved key, signing secret and account ID. Revenue already recorded is kept

Your obligations as a website owner

theBizness.ai is designed to help you meet your obligations under laws such as the GDPR and the CCPA, but it cannot meet them for you. You decide whether you need consent or another legal basis before the script runs, and you describe the data collected in your own privacy policy.

Our privacy policy lists the providers that process data for us and the exact cookies and browser storage we use.

Ready to get started?

Start tracking your marketing performance. Privacy mode is built into your dashboard.

Card required. Charged when your 7-day trial ends unless you cancel first. One trial per customer.