Cookies & Browser Storage

Current website practice

Mopshy uses first-party browser storage for lead attribution, session linkage, authentication, and your analytics preference. Google Analytics 4 is an optional production integration and is not loaded by the application unless a GA4 Measurement ID is configured and you select “Allow analytics” in the site preference notice.

Necessary first-party storage

We use browser local storage to remember first-touch and most recent non-direct acquisition information. The stored record can include UTM campaign values, common ad click IDs, the first landing-page path, an external referrer with query parameters removed, and the time of the first visit. This allows a later form submission to carry useful first-party attribution even after you navigate to another page on mopshy.com.

We also store your analytics choice in local storage so the site does not repeatedly ask for the same preference. Choosing “Only necessary” prevents the Mopshy application from loading the optional GA4 integration.

Session storage

After a lead form is submitted, the site may keep the resulting lead identifier in session storage. This lets a later click on a Mopshy booking link be associated with the same inquiry. Session storage is scoped to the browser session rather than used as a cross-site profile.

Optional Google Analytics 4

If GA4 is configured and you allow analytics, Google Analytics may use first-party cookies or related browser identifiers to provide aggregate usage and conversion measurement. Mopshy’s implementation tracks page views and business-conversion events such as successful inquiry submissions and booking-link clicks. We do not require optional analytics to submit a form or use the public site.

Bot protection

Mopshy can use Cloudflare Turnstile on public lead forms to distinguish legitimate visitors from automated abuse. When enabled, Turnstile runs a browser challenge and the server validates its short-lived token before accepting the inquiry. Turnstile is a security control rather than an advertising tracker.

Authentication storage

If you use a Mopshy sign-in or connected-tool authorization flow, Supabase authentication may store session information in the browser as required to keep you signed in. Those account flows are separate from ordinary marketing-site browsing.

Your choices

Browsers provide controls to clear cookies, local storage, and session storage. Clearing Mopshy's local storage resets the first-party attribution record and the saved analytics preference on that device. Clearing authentication storage can sign you out of account-based features.

Contact

privacy [at] mopshy.com