Privacy Policy

CHASE288 no longer collects behavioural analytics through Amplitude. The Amplitude software is not loaded, no new analytics identifier is created and no gameplay, session or visitor events are sent, whatever choice you made in the past. We therefore no longer ask for analytics consent.

Before this change, visitors who accepted optional analytics (our lawful basis was consent) had gameplay events, mode progression, time spent, navigation and returning visits measured through Amplitude. That historical information remains stored with Amplitude and is subject to the deletion process and retention limitations described below.

If your browser previously accepted analytics, open Privacy settings, also linked at the bottom of every page, and choose Delete past analytics. This clears the analytics identifier stored in that browser and attempts to submit a request for Amplitude to delete the analytics previously collected from it. Amplitude processes deletion requests on a schedule, usually within about 30 days, so deletion is not immediate. Privacy settings shows whether deletion has been queued on our server, requested from Amplitude, confirmed, or unable to proceed. A retry message does not mean a request has been accepted. If submission fails, you can retry where offered or email hello@chase288.io for deletion help. Browsers that rejected or withdrew consent earlier continue any deletion already requested.

Historical analytics were processed, and remain stored, in Amplitude’s EU data centre.

When analytics were active, Amplitude’s servers received the visitor’s IP address as part of the network connection. CHASE288 told Amplitude not to record it: our checks of stored test events found no IP address and no city, region or country.

When a visitor accepted analytics, their browser first saved a random deletion code, then our server issued a random anonymous identifier paired with it; the identifier was stored in your browser’s local storage so we can recognise returning visitors. Our server keeps only a scrambled (hashed) copy of the code. Automatic deletion requires the matching code. If registration is interrupted, the saved code is used to recover the same identifier; a lost code cannot safely be reissued solely from the identifier. Some browsers that accepted analytics before this change may not hold a usable code; automatic deletion is unavailable for them, but you can email us. No new analytics identifiers or deletion codes are created now. After a deletion request, a limited identifier/code reference and request status remain in browser storage to support deletion and retries, not tracking. Each browser or device has its own separate identifier, so a deletion request in one browser does not affect data from another, and clearing your browser storage removes the code needed for automatic deletion. You can still email hello@chase288.io in those cases.

Session Replay, automatic click and page tracking (autocapture) and similar features were always disabled.

CHASE288 previously used PostHog (EU-hosted) for analytics. It no longer sends data to PostHog. Analytics collected by PostHog before the switch remain stored there. To request their erasure, email hello@chase288.io.

We do not use analytics for behavioural advertising.

Separately from Amplitude, our hosting platform, Lovable, provides basic traffic statistics for the published website: visits, page views, visit duration, referring sites, device type (desktop, mobile or tablet) and approximate country (inferred from your browser’s time zone). These figures are aggregated, are not linked to the Amplitude identifier and do not build visitor profiles. They are part of operating the website and are separate from Amplitude.

To protect the website from abuse, such as automated sign-ups or excessive requests, our server briefly keeps request counters linked to a pseudonymised connection identifier. This is a one-way scrambled value made from your IP address and a secret key; the IP address itself is not stored. These counters are deleted within two days.

Challenge a Friend lets you set a target and send a link to someone else to chase it. You do not need an account, and we do not ask for your name, email address or a password.

Our lawful basis for operating anonymous matches, storing results, validating gameplay, preventing abuse and the limited referral measurement described below is legitimate interests: running the feature you choose to use and understanding, in aggregate, whether challenges lead to new challenges. You have the right to object to this processing by emailing hello@chase288.io.

To run each challenge, we store the following in our database (Supabase, provided through our hosting platform, Lovable): a random challenge identifier, the assigned stadium, the match code, the creation date, the target, the batting selections made, the scorecards dealt, the scores, balls used, the match outcome and related timestamps.

Your browser keeps randomly generated access credentials so you can resume a match and view its result. Our server stores these credentials only in scrambled (hashed) form. If you clear your browser storage or use a different browser or device, you may lose access to a challenge.

This browser may also keep a personal challenge list and a cumulative wins, losses and draws record. Only verified completed matches count, once per challenge. The cumulative record and the challenge identifiers used to prevent duplicate counting may remain for months or years, beyond individual match expiry, unless browser storage is cleared. They are not synchronised across browsers or devices. Removing a challenge from Your Challenges only hides it in this browser: it does not cancel the match, erase its server record, remove its access credential or change your cumulative record. This is separate from making a privacy erasure request.

Before expiry, anyone with a challenge link can see its target, stadium, match code, creation date and whether it is awaiting an opponent, in progress or completed. Completed challenges also show final scores, the opponent’s balls used and outcome. Link previews may show the target, stadium, match code, creation date and completed scores/outcome. Individual batting selections and access credentials are not shown publicly.

You choose whether to share challenge links or results, using your own messaging or sharing apps. CHASE288 does not access your contacts or send messages on your behalf.

Challenge records expire 30 days after creation. After that time, CHASE288 no longer returns challenge details or results through the link or generates challenge-specific link-preview metadata, even if the record has not yet been deleted. Records are deleted by our scheduled daily cleanup at 03:30 UTC; a failed cleanup can delay physical deletion but does not restore public access. Messaging services may retain previews or copies already shared in their own caches after expiry or deletion; CHASE288 cannot remove those copies. Expired references held in your browser are removed the next time you visit CHASE288, so some may remain in your browser for a while after the server record has expired.

While a setter bats, a temporary server draft stores a hashed access credential and the dealt scorecards. It expires after one day; successful submissions remove it, and expired unsuccessful or abandoned drafts are deleted by daily cleanup or when a new innings starts. Browser drafts use that expiry. A finished innings awaiting submission is kept locally for up to 30 days from the submission attempt, allowing recovery if the server created a challenge but its response was lost. Successful or definitively invalid submissions and a new setter innings clear the pending copy. Valid in-progress games are not removed by expired-draft cleanup. Older browser entries without expiry stamps receive a bounded recovery window on the next visit: one day for a setter draft and 30 days for a pending submission or opponent reference; a successful challenge lookup replaces an opponent reference’s expiry with the server expiry.

Referral measurement: when someone who has accepted a challenge then creates their own, and their browser still holds that challenge’s access credential, the new challenge records which challenge it came from (its parent) and how many steps it is from the first challenge (its generation). The parent challenge also records whether it led to a new one. These links are stored in the challenge records and are deleted with them after 30 days. They use no account, cookie or permanent player identifier, and no tracking across other websites.

We use them to keep private weekly totals of challenges created, accepted and completed, challenges that led to new ones, and the generations reached, so we can measure how the game spreads (its “viral reproduction”). These weekly totals contain no challenge links, credentials, scores or batting selections, are visible only to us, and are kept after individual challenges are deleted; we have not set a fixed deletion period for them. When very few people play in a week, a small count could in principle help someone who already knows who played to work out that a particular challenge occurred.

Emails sent to hello@chase288.io are forwarded using ImprovMX and received through Gmail. When you write to us we may receive your name, email address and message.

We use correspondence to respond to enquiries, investigate bugs, consider feedback and handle privacy requests. Genuinely anonymised summaries of feedback may be used to help improve the game and draft responses.

We do not automatically add correspondents to marketing lists, and we do not sell personal information.

Friend-challenge records, including their referral links, expire 30 days after creation; temporary setter drafts expire after one day. Private weekly growth totals are kept beyond individual challenges without a fixed deletion period. Scheduled daily cleanup and browser-reference retention are described in Section 4.

No new Amplitude data is collected. We aim to keep historical Amplitude analytics data for no longer than 12 months. Automatic deletion after a set period is not currently available on our Amplitude plan, so this is a target rather than an enforced setting, and data may be kept longer until we can delete it. A deletion request asks for earlier deletion for that browser, as described above. Records of deletion requests (an anonymous identifier, the hashed code and the request status) are removed about 30 days after the deletion is completed or closed. Unused deletion codes are removed after about 13 months. Security request counters are deleted within two days.

Ordinary correspondence is kept for up to 12 months, unless an ongoing matter or legal obligation justifies keeping it longer. Spam may be deleted sooner.

Under UK data protection law you may have rights to access, correct or delete personal data we hold about you, or to object to its use. To make a request, including erasure of analytics data that automatic deletion cannot cover, or to ask a question, email hello@chase288.io.

If you are unhappy with how your data is handled, you can also complain to the Information Commissioner’s Office (ICO) at ico.org.uk.

CHASE288 is accessible to players of all ages. We do not ask for a date of birth, name, email address or an account to play, and we do not use data for advertising or sell it. No behavioural analytics are collected, referral measurement uses no permanent identifier, challenge results are shown only to people with the link, and Challenge a Friend does not access contacts or send messages. These safeguards apply to everyone; we have not completed a formal assessment against the ICO Children’s Code and do not claim conformance with it. If you are a parent or guardian with a concern, email hello@chase288.io.

If this policy changes, we will update this page and its Last Updated date.