Effective date: 14 August 2026
LexiCricket (“LexiCricket”, “we”, “us”) provides AI-assisted cricket rules lookup through the LexiCricket website chat, the LexiCricket iOS app, and the LexiCricket Android app (together, the “Service”). This policy explains what information the Service collects, why, who we share it with, and the choices you have.
You do not need an account to use the chat. To answer your question, we need to know which cricket association’s rules to answer from, and the question itself. When you send a message, your question text and the selected association are sent to our backend to generate an answer (see “The AI backend” below). Your country/city/association selection is remembered on your own device (browser local storage on the website; on-device storage on iOS/Android) so you don’t have to re-select it next time — it is not tied to an account or any other identifier, and we do not maintain a server-side history of your conversations.
We use Google Analytics (GA4) on the website to understand whether the chat is being used at all — page views, which association you selected, whether a question received an answer, and roughly how long that took. We never send Google Analytics your question text, the answer text, your email address, or any other free text you type — only the selected association and coarse, non-identifying signals such as whether the answer included citations and a bucketed response time (for example, “2–5 seconds” rather than an exact figure). Google Analytics sets a cookie to recognise repeat visits. We haven’t added a cookie consent banner because we don’t use advertising or cross-site tracking, but you can block Google Analytics with a browser extension or ad blocker without affecting chat functionality.
On the website only, when you first open the chat, your browser may ask permission to share your device’s location so we can pre-fill the country and city for you. If you allow it, your coordinates are sent directly from your browser to BigDataCloud, a third-party reverse-geocoding service, to resolve them to a country and city name — that lookup never passes through LexiCricket’s own servers, and only the resulting country/city names (not your coordinates) are used to pre-fill the selector. You can decline the browser’s permission prompt and pick your location manually instead. The iOS and Android apps use a coarser, GPS-independent signal (your device’s time zone) for the same purpose, and don’t call BigDataCloud.
Cricket association staff who manage rules content sign in to a separate admin console with an email address and password. We store your email address, an encrypted password, and an account role, and use a session cookie to keep you signed in. This applies only to association administrators — people using the consumer chat never create an account.
When an administrator uploads a cricket association’s rules (as a PDF or similar document), we store descriptive details (title, filename, document type, version) in our database, and the document’s content is uploaded to Google’s Gemini File Search service so it can be used to ground chat answers. This content is association-provided rules material, not personal information about you.
The iOS and Android apps use RevenueCat to manage subscriptions purchased through the Apple App Store or Google Play. RevenueCat identifies your device using its own anonymous, device-generated identifier — we do not send RevenueCat your name, email, or any other identifying information.
When you ask a question, your question text and the selected association are sent to Google’s Gemini API, which generates an answer grounded in that association’s uploaded rules documents. We do not attach your name, email, device identifier, or any other personal information to that request. This use of Google’s Gemini API is governed by Google’s own API terms for the product tier we use; we do not separately use your questions to train any model ourselves.
We use Google Analytics (GA4) on the website only, to measure page views and basic product usage (see “Product analytics” above) — never your question or answer text. We do not use analytics, advertising, crash-reporting, or attribution SDKs in the iOS or Android apps, and we do not sell personal information.
| Provider | Purpose | What they receive |
|---|---|---|
| Google (Gemini API) | Generates chat answers; stores uploaded rules documents for retrieval | Question text, selected association’s rules documents — no personal identifiers |
| Google Analytics (website only) | Measures website usage | Page views, selected association ID, whether an answer had citations, bucketed response time — no question or answer text, no personal identifiers |
| BigDataCloud | Reverse-geocodes device coordinates (website only, with permission) | Latitude/longitude, called directly from your browser |
| Supabase | Database, authentication, and backend functions | Administrator account data, association/document metadata |
| Cloudflare | Website hosting | Standard web request data needed to serve the site |
| RevenueCat | Subscription/entitlement management (iOS/Android) | Anonymous device identifier, purchase/restore events |
| Apple App Store / Google Play | Processes in-app purchases | Handled entirely by Apple/Google — LexiCricket never receives your payment details |
All subscription payments are made through the Apple App Store or Google Play billing systems and processed by Apple or Google. LexiCricket does not collect or store your card number or other payment details.
We keep administrator account data and association rules content for as long as the account or association relationship is active, and delete it when it’s no longer needed or when deletion is requested (see “Your rights” below). Your chat questions are used to generate a response and are not stored by us in a server-side chat history. Your location/association selection stays on your own device until you clear it or uninstall the app.
Administrator passwords are stored encrypted, never in plain text. Traffic between your device and our services is encrypted in transit (HTTPS/TLS). No method of storage or transmission is perfectly secure, but we take reasonable steps appropriate to the information involved.
Depending on where you live, you may have rights to access, correct, or delete your personal information, or to object to or restrict certain processing. Since the consumer chat doesn’t collect an account or identifier tied to you, most of these rights apply to administrator account data. To exercise any of these rights, or with any privacy question, contact us using the details in “Contact us” below.
The consumer chat does not require an account and does not knowingly collect your name, contact details, or other identifying information, regardless of your age. If you believe a child has provided us with personal information some other way, contact us and we will address it.
Our service providers (including Google, Supabase, and Cloudflare) may process or store information in countries other than your own. Where this happens, we rely on those providers’ own safeguards for cross-border data handling.
We may update this policy from time to time. If we make material changes, we’ll update the effective date above.
If you have questions about this policy or want to exercise your privacy rights, contact us at privacy@lexicricket.com.
LexiCricket is not affiliated with any cricket association. Answers are drawn from publicly available rules and playing conditions, provided to help educate umpires and players.