Technology notice updated 13 September 2026.
CheckX uses a small number of cookies and related technologies to secure the service, sign you in, remember your session, protect against abuse and understand how the Alpha is working. CheckX currently does not use advertising cookies, advertising pixels or third-party behavioral analytics.
1. Cookies used by the current Alpha
__Host-cx_flow
CheckX · First-party · Up to 10 minutes
Securely connects an emailed CheckX sign-in code with the browser that requested it. It supports passwordless authentication and sign-in security.
__Host-cx_session
CheckX · First-party · Up to 30 days
Keeps an authenticated Xplorer signed in for Your Xs, Captain functions, commitments, referrals and Captain Briefs. Logging out or invalidating the session can end it sooner.
cx_visit
CheckX · First-party · Up to 30 days
An opaque visitor identifier used for abuse and rate controls, operational reliability and first-party product measurement. It may help CheckX understand whether Start an X was visited, proposal creation started or an invitation was opened. It does not contain your email address, is not used for advertising or cross-site behavioral tracking, and may be associated with CheckX operational events.
__cf_bm
Cloudflare · Security infrastructure · Around 30 minutes of inactivity
Supports Cloudflare bot-management protection against automated abuse. Its duration and operation are subject to Cloudflare configuration. CheckX does not use it for advertising or behavioral marketing.
CheckX authentication and visitor cookies are Secure and HTTP-only in production, use SameSite=Lax and apply across checkx.ai. HTTP-only means page scripts cannot read their contents. Cloudflare controls its infrastructure cookie and related provider-side processing.
2. Browser storage
At the time of this notice, the CheckX application does not use localStorage, sessionStorage, IndexedDB, application Cache Storage or service-worker storage for application identity or tracking. Browsers may still cache ordinary site files such as images, fonts, styles and scripts.
3. Invitation and referral links
A CheckX invitation or referral link may contain a Hunt identifier and a private invitation or referral token. The link can remain in ordinary browser history, bookmarks or copied messages. Treat a private invitation as a shareable access link and send it only to intended recipients.
4. First-party operational measurement
CheckX records first-party operational and product events to operate the Alpha and understand whether its core flows work. These may cover Start an X visits, creation starts, invitation opens, signup activity, proposals, generated invitations, commitments, Crew Ready and Captain Brief activity.
No advertising network receives these events. Event records do not contain raw sign-in codes or raw email addresses. They may use pseudonymous visitor, account, Hunt, invitation or commitment identifiers and should not be treated as anonymous. Current operational records do not have a fixed automatic deletion schedule.
5. Network and security processing
Network addresses may be processed to deliver and secure CheckX. The audited application derives a daily hash for certain rate controls instead of storing raw IP addresses in CheckX application tables. Infrastructure providers such as Cloudflare may process network information under their own service practices and retention arrangements.
6. Passwordless email
CheckX sends the recipient email address and authentication message to Resend from the server for delivery. Under the current implementation, Resend does not run a tracking SDK or pixel on checkx.ai and does not set CheckX browser cookies.
7. Advertising and future changes
No advertising or cross-site behavioral tracking is currently used. CheckX does not currently use advertising pixels or third-party behavioral analytics such as Google Analytics, Meta Pixel or TikTok Pixel.
If CheckX later introduces technology that requires additional notice, choices, consent or opt-out rights, it will update its disclosures and controls as appropriate. This page describes the current Alpha rather than making a permanent promise about future technology.
8. Questions and choices
Clearing CheckX cookies may sign you out or interrupt passwordless verification. It does not delete your account, proposals or commitments. Read the Alpha Privacy Notice for more about stored information, retention and requests. Contact support@checkx.ai with a privacy question; never send a sign-in code.