Privacy Policy

When you explicitly choose English or Dutch, a preference cookie remembers that choice across cricketx.net and benelux.cricketx.net for up to one year. If you sign in, the explicit preference is also stored privately on your account. Changing language does not change prices, shipping availability or referral terms.

When regional context capture is enabled, country-only IP lookup inside Firebase using a bundled database or verified payment billing evidence can establish a regional introduction. Short-lived first-party context receipts last up to seven days; a recognized account or purchasing organization can retain its introduction for later purchases. Visitor IP addresses are not sent to an external geolocation API. We keep the country, evidence reference and audit history rather than the raw IP address as that durable introduction. Language choice and visiting a regional page do not prove financial eligibility. Contact CricketX to request review or correction.

A direct or external arrival on benelux.cricketx.net can also establish a partner introduction using a server-issued receipt. Following an internal CricketX link, choosing Dutch or simply opening a regional page does not establish that referral.

A Benelux enquiry is shared with the configured Benelux recipient and CricketX. We keep the submitted contact details, message, reference and separate delivery states for up to 180 days to answer and track the enquiry. If the partner address is not configured, the page directs you to CricketX instead of claiming that a partner message was delivered. Enquiry data and regional financial records are private; partner earning summaries do not expose customer identities.

We only collect what we need to run the product. Nothing is sold to third parties.

• Account data. Your email address and a hashed password when you create a CricketX account. We use Firebase Authentication for this.
• Subscription state. Your current plan, billing cycle and renewal date, stored in Firebase Firestore. We never store your card details on our servers — Stripe handles every payment directly.
• Gameplay data. Inside the VR app, CricketX stores local training stats on your headset so you can review past sessions. Only summary data is ever synced to your account.
• Order data. If you buy a smart bat, we store your shipping address and order history so we can deliver the bat and handle any returns.
• Technical data. Standard web server logs (IP address, browser, timestamps) and app crash reports. Used to keep the site and app running.
• Mode purchases. If you buy a CricketX mode, bundle or pass, we store which modes your account owns, the purchase, amount, any referral code and your non-refundable acknowledgement, so the modes unlock in CricketX and we can handle payment questions. The coaches who created the modes see sales dates, products and their share, never your name, email or payment details.
• Creator records. If you are a coach or creator who earns from CricketX modes, we keep your creator schedule, acceptance record, earnings, adjustments and payment history in your Partner account, and handle receiving-bank details as described in the bank details notice.
• Affiliate records. If you participate in the affiliate program, we keep your agreed offer, acceptance record, commissions, adjustments and payment history. Receiving-bank details are encrypted and used for affiliate payments. Read the Affiliate Bank Details Privacy Notice before submitting them or authorizing an administrator to enter them.

Every use of your data falls into one of these buckets:

• Running the CricketX VR app and this website (authentication, subscription gating, order processing).
• Responding when you email support.
• Sending you service emails about your account — receipts, renewal reminders, subscription changes.
• Improving the product — anonymised usage metrics help us work out which features get used and which do not.
• Meeting our legal obligations (tax records, fraud prevention).

We do not sell your data. The cookies section explains the website analytics and advertising-attribution services. The regional section explains when an enquiry is shared with Benelux and CricketX.

CricketX uses a small set of vetted processors to run the service:

• Google Firebase — authentication, database, hosting, cloud functions. Data is stored inside Google's infrastructure under their security and privacy terms.
• Stripe — payment processing and recurring billing. Card data is handled directly by Stripe and never touches our servers.
• Meta (Quest Store) — if you buy the base game on the Meta Quest Store, Meta handles that purchase under Meta's own privacy terms.
• Shipping partners — when you order a smart bat, your shipping address is shared with the courier handling delivery and nothing more.
• Affiliate payment administrators and providers — receiving-bank instructions are shared with the authorized administrators named in the affiliate bank notice through our mail service, and with the bank or transfer provider needed to pay you. These details are not shared with other affiliates or buyers.
• Website analytics and advertising attribution — Google Analytics, Google Tag Manager and the Meta Pixel can receive usage and browser information as described in the cookies section.
• Benelux enquiries — when partner contact delivery is configured, your submitted contact details and message are shared with that Benelux recipient and CricketX, as described in the regional section.

We update this page when the services used to process account, purchase, analytics or enquiry data change.

You have the right to:

• See what personal data we hold about you.
• Correct anything that is wrong.
• Delete your account and the personal data attached to it.
• Export a copy of your account data.
• Cancel your subscription at any time — you keep access until the end of the paid period.
• Unsubscribe from any marketing email. Service emails (receipts, renewal warnings) cannot be unsubscribed while your account is active.

Email CricketX@xrevstudio.com and we will handle the request within a reasonable timeframe — typically under 30 days.

This site uses a small number of first-party cookies and browser local-storage entries:

• Authentication session. Keeps you logged in across pages. Cleared on logout.
• Smart bat cart. Your current cart is stored in browser local storage only. No cart data is sent to our servers or synced across devices.
• Preference state. Things like the Pricing page's monthly / yearly toggle are remembered locally.
• Affiliate referrals. When you follow an affiliate link, we store an expiring referral identifier in your browser to apply eligible offers and attribute purchases. The referral window is normally 45 days. To decide whether an affiliate offer applies to a subscription, we check whether your account or email had a subscription running, or a subscription payment in the previous 120 days, when you first used that affiliate’s link or code. You can remove the saved referral link at checkout. Entering a code takes priority over a saved link.

This website also loads Google Analytics, Google Tag Manager and the Meta Pixel for usage measurement and advertising attribution. These services can use their own identifiers, cookies and network requests. Browser privacy controls may restrict them.