Privacy and consent

Shuttlebase tracks visitors anonymously and stops tracking entirely when a visitor has not consented. This page covers what the snippet collects, what it deliberately avoids, and how consent works.

Anonymous identity

The snippet generates a random UUID in the visitor’s browser and uses it as the only visitor identifier. Shuttlebase does not collect customer PII. It never collects names, email addresses, physical addresses, phone numbers, or payment details, because the system does not need them. There is nothing in the ID itself that connects to a real person.

URL redaction

Page URLs can leak personal data through query parameters. Before sending any URL, the snippet redacts:

• Query parameters named email, password, token, auth, pass, or pwd
• Any query parameter value that matches an email address pattern

Redacted values are replaced with [REDACTED]. If a URL fails to parse, the snippet drops it entirely rather than risk sending something sensitive.

No IP address from the browser

The browser never sends an IP address in any event. Shuttlebase resolves coarse geolocation (country, region, city, postal code, timezone) server-side from CDN request headers.

Consent is all-or-nothing

Tracking is a single switch. Without consent the snippet:

• Sends no events
• Writes no user ID
• Persists no experiment assignments

Deployed winning changes still render visually. A visitor who declines tracking still sees your improved site, but they never enter running experiments and generate no data. This matches the behavior when browser storage is blocked, described in Cookies and storage.

Consent platform integrations

The snippet reads consent from your consent management platform (CMP). Supported integrations:

• Shopify Customer Privacy
• IAB TCF v2.2, including GPP and USP signals for CCPA
• OneTrust
• Osano
• A custom checker your site provides through window.msaiConsentChecker

Only your account’s CMP module is bundled into your snippet, so unused integrations add no weight. The snippet gives the CMP 3 seconds to answer before falling back.

If you run a cookie consent banner, Shuttlebase helps you map its cookies into your existing disclosure list during onboarding, so your opt-in and opt-out flows keep working unchanged.

Fallback modes

When the CMP does not answer, or when an account has no CMP, one of three configured modes applies:

• Always track. Tracking runs without asking.
• Opt-out. Tracking runs until the visitor declines. This matches CCPA-style regulation.
• Opt-in. Tracking stays off until the visitor accepts. This matches GDPR-style regulation.

Global Privacy Control

The snippet honors the Global Privacy Control (GPC) browser signal on every account. A visitor with GPC enabled is treated as having declined, regardless of your CMP or fallback mode configuration.

Your data stays yours

Shuttlebase does not share your data with other clients. The platform builds its model of how your visitors behave inside your account only, and your experiments are unique to your brand.