Cookies & Tracking
Effective
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 (email link, Google, Discord, Twitch, Apple or a passkey). Stores a signed JWT identifying your account. Removed on sign-out. While you sign in, NextAuth also sets short-lived security cookies: a CSRF token, the page to return to afterwards, and, for a provider or passkey sign-in, the values that protect that step.
- Adding a sign-in method — a first-party cookie (
sensipets.sign-in-link) set when you add Google, Discord, Twitch, or Apple as a sign-in method from Settings, so that sign-in is added to your account. It lasts 10 minutes. - Linking Discord — a first-party cookie (
sensipets_discord_oauth_state) that protects the round trip to Discord when you link it from Settings. It lasts 10 minutes. - Support request access — when you contact support without signing in and open the link we email you, a first-party cookie (
sensipets_support_<request number>) lets this browser read and reply to that request for 90 days. - Last sign-in method — a first-party cookie (
sp_last_sign_in) naming the way this browser last signed in, such asgoogle, so the sign-in page can show it first. It names a method, not your account, and lasts a year. - Passkey offer — a first-party cookie (
sp_passkey_offer) set after you sign in with an email link, so the game can offer once to add a passkey. It holds no account details and is cleared when the offer shows, or after 10 minutes. - Consent record — a small
localStorageentry (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.
Sign-up offers and referrals
These first-party cookies carry an offer or a referral into sign-up, so they are set whatever you choose on the banner. Each is signed so it cannot be altered, and each is cleared when you finish setting up your account, or after 30 days.
- Referral (
sp_ref) — set when you open another player's referral link. It holds that player's account number so the referral can be credited when you join. - Welcome offer (
sp_offer) — set when you arrive on one of our campaign pages that comes with a welcome week. It names the offer and the page, and nothing about you.
Storage on this device
Besides cookies, the game keeps some data in your browser's localStorage and sessionStorage so it works smoothly. It stays on your device and is not used for advertising.
- Cached game data — copies of things the game loads often, such as avatars, preferences, and the world map, kept for up to a day under keys starting
sp.rq.. You can clear them from Settings → Account, under Local cache. - Display and game settings — such as your theme (
sp-theme), book reader settings, minigame difficulty, and local best scores. - Drafts and reminders — such as an unsent Brightworks commission (
brightworks.commission-draft.v2), banners you dismissed, and hints you have already seen. - Account setup progress — your place in setting up a new account, kept in
sessionStoragefor that tab only.
Analytics
What product analytics does before you make a choice on the banner depends on where you are. In the United States, Canada (outside Quebec), Australia, and New Zealand, it runs in a storage-free mode — we count page views and clicks without writing an analytics identifier to your device, and anonymous visits are not linked across full page loads. Everywhere else, including the UK, the EU, and Quebec, when we can't tell where you are, or when your browser sends a Global Privacy Control signal, nothing is captured in your browser until you click Accept. If you sign in, product events can be linked to your account ID; your email address and name are added only after you accept. Clicking Accept enables the storage below, so we can recognise a returning visitor. Clicking Decline switches product analytics off in your browser — no browser PostHog events are sent.
- 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
localStorageand a matching cookie. Automatic click and form capture and session recording are disabled. We send defined product events, page views and departures, performance measurements, and error reports. - Email visits — once you have accepted analytics, arriving from one of our emails stores which email brought you in
sessionStorage(sensipets.email-attribution), for that tab only.
Server-side records of account and transaction outcomes, operational measurements, and errors are separate from browser tracking. They do not use analytics storage on your device and are not controlled by the browser analytics choice.
Advertising measurement
We run ads on Google (including YouTube), Meta (Facebook and Instagram), Reddit, and TikTok, and we need to know which of them actually bring people to the game. They measure leads, completed registrations, and purchases; we do not use them to show you ads inside Sensipets. When they run depends on where you are:
- United States, Canada (outside Quebec), Australia, New Zealand — advertising measurement is on until you click Decline on the cookie banner or under Your Privacy Choices in the footer. That opts you out of the sale or sharing of your personal information for advertising. We also treat a Global Privacy Control (GPC) signal from your browser as that opt-out.
- Everywhere else, including the UK, EU and Quebec — advertising tags stay off until you click Accept.
- Players under 16 — once your account tells us you are under 16, advertising measurement stays off everywhere, even if you click Accept.
- We tell these apart by the country your connection comes from, stored in a short-lived first-party cookie
sp_consent_region. When we can’t tell, tags stay off until you accept.
- Google Ads, Meta pixel, Reddit pixel, TikTok pixel — each may set its own cookies to connect an ad click to a later sign-up or purchase. Each tag receives page views and lead, completed-registration, first-pet, and purchase events; Meta may set
_fbpand_fbc, and TikTok may set_ttp. Declining, or not choosing outside the regions above, prevents every browser advertising tag from loading. - Server-side conversion measurement — when advertising measurement is on for you (by the rules above), we send completed-registration, first-pet, 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, a GPC signal, or not choosing outside the regions above 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 cookiessp_attrandsp_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 follows the same advertising rules above.
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.
When we switch on a bot check for sign-in, the sign-in page loads Cloudflare Turnstile. It runs from Cloudflare's servers and receives your IP address and browser details to tell people from automated sign-ups. The Privacy Policy lists the other companies that help run Sensipets.
Changing your mind
Click Your Privacy Choices 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, and it stops server-side conversion reporting for anything you do afterwards. A purchase is reported according to the choice in effect when its checkout began. Until you choose, a Global Privacy Control signal from your browser works like Decline.
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.

