Alpha Privacy

These policies cover the current CheckX Alpha. Proposed Hunts are not confirmed events.

Privacy notice updated 13 September 2026: Captain-only first-name visibility and Founding Xplorer validation.

1. Scope

This notice describes the current CheckX Alpha: email sign-in, Xplorer demand validation, Founding Xplorer enrollment, X Captain proposals, commitments, invitations, referrals and Captain Briefs. It also covers the founding-access form. The concept demo does not operate a live Hunt.

2. Information we collect

For sign-in, we collect your first name, email, confirmation that you are 18 or older, acknowledgment of the policies and related timestamps. We store verification challenges and hashed codes, session identifiers in hashed form, expiry times and attempt counts. Email verification establishes access to an inbox; it is not an identity or age-document check.

For demand validation, we may collect the CheckX use case you voluntarily select, such as a night out, birthday, date, city exploration, team outing, dedicated Hunt or Something Else. If you choose Something Else, we may also collect the optional short response you provide. We may record whether and when your account became a Founding Xplorer, whether the source was direct or a Founding Xplorer referral, and the related validation and referral identifiers. These records may be associated with your CheckX/Xplorer account when you are authenticated. They are first-party or pseudonymous records where applicable, not anonymous data.

For proposals, we store your Captain name, proposal title, Private or Public mode, occasion, city or area, suggested timing, age description, commitment target, location types and description. We also store commitments, invitation and inviter associations, status changes and the location notes and other content you enter in a Captain Brief.

The founding-access form stores your name, email, city, selected role and organization when supplied. Do not put private information about other people or sensitive personal information into free-text fields.

3. How information is used

We use validation preferences and Founding Xplorer status to understand which CheckX experiences people want, improve the Alpha, offer appropriate early-access or feedback opportunities, and recognize Founding Xplorers. Founding referral attribution helps us understand how people discover the Alpha and whether interested Xplorers bring others. It does not create a Hunt invitation, Crew commitment, reward or public ranking.

We use other account and product information to authenticate you, restore your account and Xs, prevent duplicate commitments, maintain Hunt invitation attribution, calculate crew progress, save Briefs and evaluate proposals. We record first-party operational events such as validation, signup, proposal, invitation and commitment activity to understand whether these flows work and to investigate misuse. These events can be linked to account, validation, proposal, invitation, referral and visitor identifiers, but event rows do not contain raw email addresses.

The app uses daily hashes derived from a network address or visitor identifier, request counters and expiry times to limit abuse. The app does not store raw IP addresses in these rate-limit records; hosting providers may process network addresses and technical request logs when delivering and securing the service.

4. Cookies and browser data

Cookies keep you signed in, bind verification to the browser that requested it, protect against abuse and associate operational activity with a visitor. Read the Cookies & Technology Notice for the current cookie inventory, browser-storage details and first-party measurement explanation. Signing out invalidates the current session. Clearing cookies may sign you out but does not delete your account or commitments.

The current Alpha does not request live GPS tracking, payment details or identity documents. Demo locations and rewards are illustrative.

5. Visibility and service providers

Founding Xplorer status may be shown to the account holder, but CheckX does not publish sequential signup numbers, a Founding Xplorer directory, email addresses or referral totals. A Founding share link identifies its referring account to CheckX without exposing that person’s email or private Hunt information.

People with a valid Hunt invitation can see the proposal’s shared details, Captain name and crew count. Both Private and Public proposals currently require an invitation or an existing Captain/member relationship; there is no public proposal directory. Treat invitation links as shareable access. The current participant view does not expose other members’ email addresses or the Captain Brief. After you acknowledge this updated notice, your first name is visible only to the Captain of each X you commit to, including existing commitments. Your email stays private from Captains and other participants. Earlier acknowledgments alone do not enable first-name visibility. There is no public participant directory. CheckX can access stored information to operate and review the Alpha.

Resend processes recipient email addresses and sign-in messages to deliver authentication email. Sites hosting and Cloudflare infrastructure process site requests and stored application data. These providers may process data in locations outside your country. The current application does not sell account data or implement advertising-audience sharing. It does not send proposal or Brief content in sign-in emails.

6. Retention and your choices

Codes stop working after ten minutes and sessions expire after 30 days. Expired authentication and rate-limit records are cleaned up in limited batches during later activity, so expiration does not mean immediate deletion. Account, validation preference, Founding status, referral, proposal, commitment and operational records currently remain stored for Alpha operation; there is not yet an automatic account-deletion or fixed product-record retention schedule.

You can stop using the Alpha and sign out. Contact CheckX at support@checkx.ai to request access, correction or deletion, or to report a privacy concern. Requests require manual review and may require verification of account ownership. There is no self-service deletion tool in this Alpha. Do not send a password or sign-in code with a request.

7. Minors and updates