Skip to main content
Back to home

Cookies & Tracking

Effective 2026-09-15

This page lists the cookies and similar storage Sensipets uses, why, and how you can change your mind. For the broader policy on personal data, see the Privacy Policy.

Essential

These are required to operate the Service and are not subject to consent. They contain no marketing or behavioural data.

  • Authentication session — set by NextAuth when you sign in (magic link or Google). Stores a signed JWT identifying your account. Removed on sign-out.
  • Consent record — a small localStorage entry (sp.cookieConsent) and matching first-party cookie (sp_cookie_consent) remembering your choice. The cookie lets server-side conversion reporting honor the same decision.
  • Age requirement — a first-party cookie (sp_age_gate) set on a browser where someone entered a date of birth below our minimum age. For 30 days it stops that browser from creating a new account; existing accounts can still sign in. It holds no personal data.

Analytics

Before you make a choice on the banner, product analytics runs in a storage-free mode — we count page views and clicks, but nothing is written to your device and nothing follows you between visits. Clicking Accept enables the cookie below, so we can recognise a returning visitor. Clicking Decline switches product analytics off entirely — no PostHog events are sent at all.

  • PostHog — product analytics and error tracking. We use it to understand which features are used, diagnose bugs, and measure releases. Once you accept, PostHog stores a distinct-id in localStorage and a matching cookie. Autocapture and session recording are both disabled — only named events from the typed catalogue are sent.

Advertising measurement

We run ads on Google, Meta (Facebook and Instagram), and Reddit, and we need to know which of them actually bring people to the game. Browser tags stay off until you click Accept on the cookie banner. They measure leads, completed registrations, and purchases; we do not use them to show you ads inside Sensipets.

  • Google Ads, Meta pixel, Reddit pixel — each may set its own cookies to connect an ad click to a later sign-up or purchase. The Meta pixel receives page-view, lead, completed-registration, and purchase events and may set _fbp and _fbc. Declining or not choosing prevents every browser advertising tag from loading.
  • Server-side conversion measurement — after you accept advertising measurement, we send completed-registration and provider-confirmed purchase events from our server. They can include a hashed account or email identifier, the ad click identifier you arrived with, purchase value and product, and request context such as IP address and user agent. This does not send server-side page views or browsing activity. Declining, not choosing, or having a stale policy decision prevents this reporting.
  • Click identifiers — when you arrive from an ad, the campaign details in that link (including identifiers such as Google's gclid) are stored in a first-party cookies sp_attr and sp_attr_last, each for up to 90 days. They record your first visit and latest campaign or external referral, including campaign IDs, landing page and variant, referring site, and arrival time. They do not contain an account identifier. We save this context when signup begins so it can follow a magic link opened in another browser, and retain the signup snapshot with your account. Account-creation analytics can include this campaign context. Sending click identifiers to advertising platforms still requires accepted advertising measurement.

Third parties

Payment providers (Stripe, PayPal) are loaded only when you reach a checkout page, and set their own cookies on their hosted pages — not on Sensipets domains. Image and asset delivery via our CDN does not set cookies.

Changing your mind

Click Cookie Preferences in the footer at any time to re-open the banner. Declining will immediately disable analytics and clear the PostHog identifier on your device. It also revokes browser advertising-tag consent, so no later browser page-view or conversion events are sent. Server-side conversion reporting also requires the accepted preference captured with that registration or checkout.

Updates

When we materially change the cookies we use, we bump the version on this page and re-prompt everyone on their next visit. Current version: 2026-09-15.