Privacy Policy
Last updated: 14 November 2026
CricLiveChat is an independent, fan-made cricket scoreboard. We built it to need as little of your data as possible: there are no user accounts, we never ask for your personal details, and the few things the site remembers about you stay on your own phone or computer.
The short version: no accounts, no names, emails or phone numbers. No ads or advertising cookies today (if we add Google ads later, see Advertising). Chat and prediction data are deleted automatically after each match; a cricket-game challenge link after 7 days. We never sell your data.
What we do NOT collect
- No accounts, sign-ups, names, emails, phone numbers, or passwords.
- No advertising or tracking cookies today, and we don't track you across other websites (see Advertising for what would change if we add ads).
- We never sell, rent or share your personal data.
What we do process
A random device code
When you first open CricLiveChat, your browser makes up a random code of letters and numbers and keeps it in its own storage (criclive_vid). It is sent with the site's own requests so that a laptop and a phone on the same Wi-Fi count as two people: for poll votes, spam limits, prediction scores and reports, and for counting visitors (the "online now" number, daily visitors, viewers per match, and once a day which way you use CricLiveChat: website, home-screen app or our Android/iPhone app, together with a country, to see roughly where visitors come from: the country Cloudflare (see below) attaches to each request, or else your device's time zone turned into a country (for example Asia/Kolkata → India). We keep only daily totals per kind and per country, never which device said what, and we don't look up or keep your IP address for counting. It says nothing about you, isn't linked to your name or any account, and is never shared with anyone. Clearing your browser's storage for this site creates a new one.
What we count — totals only
To see what people enjoy and how the site is found, we count these. Each is a number per day (an India day, midnight to midnight IST) — never a list of who did what, never your IP address, and never linked to your device code once the day's count is worked out (the "already counted today" check lives in our server's memory and is gone by the next day):
- Visitors: how many different devices opened the site that day, which way (website, home-screen app or our apps), the country as described above, the site language you read in, and whether the device visited on an earlier day. That last one comes from your browser's own once-a-day note (see Local storage): it already holds the date of your last visit, so nothing new is stored.
- How a visit arrived: one word from a fixed list — a link shared from our ↗ Share button, WhatsApp, Google, Bing, another search engine, Facebook, Instagram, X, Telegram, YouTube, Reddit, another website, our app, or typed/bookmarked. We never keep or send the address you came from. Links made by our Share button end in
?via=share; the page removes it from the address bar as soon as it opens. - How long a visit lasts: one of four bands (under 1 minute, 1–5, 5–20, more than 20 minutes), sent once when you first leave the page.
- Busiest hours: the highest "online now" number in each hour of the day.
- What gets used: page views, and how often each page, match tab and feature is tapped (for example "Scorecard tab +1"), plus how many different devices opened each match.
Search engines and link-preview robots are left out of the counts. In Europe and the UK none of this is counted unless you say yes (below).
Visitor counting: your choice
In Europe and the UK, we don't count your visit unless you say yes. If your device's clock is set to a European time zone, we ask once: Allow visitor counting or Don't count my visit. Until you choose, and if you say no, we don't create the device code just for counting. We make it only when you use something that needs it (a vote, a post, a prediction or a report), and even then your visit is left out of every count. A small cookie, clc_nc=1, holds no id, just "don't count", so our server knows on page loads too. The site works the same whichever you choose. Anyone, anywhere can change this any time: ☰ menu → Privacy choices. We count only how many people chose each answer (daily totals, no id). The time zone is a guess, not your location, so if we ask you when the law doesn't require it, nothing is lost. The very first page you open is answered before the choice exists: like any website, our server sees that request and may add one to that day's page-view count — a number only, with nothing stored on your device.
A display name you choose
To chat, you pick a display name (for example, "Guest-4560"). It's stored in your own browser and shown next to your messages so others can follow the conversation. You can change it any time, and it isn't linked to your real identity.
Chat messages, discussion & poll votes
Messages you post, discussion topics and replies, and poll votes you cast are sent to our server so they can be shown to other people watching the same match. They are deleted automatically once the match is over:
- Match chat, discussion topics and replies, poll votes and prediction scores — all deleted 12 hours after the match finishes;
- Global chat — only the most recent 100 messages are kept at all; older ones are removed as new ones arrive;
- Private group chats — cleared shortly after the match they were created for ends;
- The Pavilion (our fan community page) — each post, with its replies, reactions and poll votes, is deleted 7 days after it was posted, together with any photo in it.
We keep no long-term archive of any of it, and none of it is backed up off the server.
Friends groups are monitored by our admin
A friends group is private between its members — other visitors can't see it. But for everyone's safety, the CricLiveChat admin can read every message (and photo) posted in every friends group, and may remove messages, mute a person or close a group that breaks our terms. Before you create or join a group we show you this notice, and you must accept it; if you don't accept, you can't create, join, read or post in that group. Your acceptance is remembered only on your device (criclive_grpok2, the codes of the last 20 groups you accepted) — nothing extra is stored on our server. Group messages are still deleted automatically, as described above.
Automatic check of group messages. Right after a message is posted in a friends group it is checked in two ways. Our own filter, which runs on our server and sends nothing anywhere, looks for selling or promotion (for example "buy", "DM me", "earn money"), clearly off-topic subjects in a message that says nothing about cricket, and the same message repeated several times. OpenAI's free safety service receives the message text alone to check it for harmful content (abuse, threats, hate, sexual content); we never send your name, device code, IP address or which group it is, and very short messages, emoji, stickers and photos are not sent. Neither check hides or blocks a message: if one flags it, the message and its flag are shown to our admin, who decides whether to remove it. A flag is deleted after 7 days, or sooner when the group is deleted, and is never in our backups. OpenAI does not use API data to train its models; it may keep it for up to 30 days to detect abuse of its service (OpenAI's privacy policy).
Photos in chat and Discussion
You can add a photo to a match's chat or Discussion, to global chat, or to a friends group. Before it leaves your device, your phone or browser shrinks it and saves a fresh copy, which removes the hidden details photos carry, such as where it was taken (GPS) and the camera model; our server removes them again in case they slipped through. Every photo is then checked by an automatic image-safety service (OpenAI's moderation service) before anyone else can see it — only the photo is sent, never your name, device code or IP address. A photo that fails the check is not posted and not kept; if the check can't run, the photo is refused. Photos are stored on our own server only (never in backups) and are deleted: 6 hours after the match finishes for match chat and Discussion (sooner than the messages themselves), and 6 hours after it was posted in global chat and in a friends group (sooner if the group closes first). A photo in a Pavilion post or reply is deleted with that post, 7 days after the post was made. Only post photos you took or have the right to share.
Keeping chat safe
An automatic filter blocks betting, abusive and personal-information messages. Messages it stops are kept for at most 7 days so a moderator can review them, and are never backed up. Links can't be shared in any chat: a message containing a link is refused and not kept. A post that waits for a moderator (for example one with contact details) is deleted if it isn't approved within 7 days. If a moderator mutes a chat user, we keep the mute (the device code and the chat name used) until the mute ends, so that it survives a server restart. Mutes are the one chat-safety record that is also in our backup (so a mute survives a server replacement); each is removed when it ends.
Reporting and blocking
Every message and discussion post from someone else has a ⋯ button.
- Block hides everything a person posts — on your device only. Your block list is kept in your own browser; nobody, including us, is told whom you blocked.
- Report sends us a copy of that message, the reason you picked, and the device codes of the author and of each person who reported it, so we can review it and count each reporter once. Reports stay on our server only (never backed up). Every report is deleted 30 days after the last time it was reported — whether or not a moderator has acted on it.
- To make blocking possible without revealing anyone, each message carries an anonymous author tag — a scrambled code made from the device code with a secret only our server holds. The same person always gets the same tag, but it can't be turned back into the device code or linked to a person.
Your IP address (transiently)
Like any website, our server sees your IP address while it answers your request. We use it only, in memory, to prevent spam and abuse (rate-limiting). We do not write it to our access logs, use it to identify you, or build a profile of you. If a request fails with a technical error, the server's error log may briefly record the address involved; those logs are deleted automatically after 14 days.
Anonymous, aggregate usage numbers
We keep basic, non-identifying counts — such as how many pages are viewed and how many people are online — to understand how the site is used. These are aggregate figures only and contain no personal identifiers.
Prediction and quiz scores
If you play the next-ball prediction game or the match quiz, we keep a small score record — how many calls you got right, how many you made, and your current streak — against your device code, together with the display name you chose. It is scored on our server so a leaderboard can't simply be typed in by a browser. If you are in a friends group, the other members see your next-ball score next to the name you post under in that group — worked out from the same record, nothing extra is kept. These scores are kept per match only, are not linked to any real identity, are deleted 12 hours after that match finishes, and are never copied to backup storage.
The cricket game (CricLive Cricket, /play)
The game is our own and uses no real data: every player, team and chase in it is made up. It needs no name and no account. What it sends to us:
- Usage counts — when the game opens, a game starts or finishes, its mode, whether you won and how long it lasted. We add these to daily totals only; to count how many different people played today we use your device code in memory for that day — it is never written down.
- Challenge a friend — only if you tap it: the chase number, the difficulty, the random number that sets the deliveries and your score. It is kept under a random link code for 7 days, then deleted, and is never copied to backup storage.
- Play a friend live — our server passes the two phones' game moves (the delivery, the shot, the running) between them and keeps nothing on disk: the room exists in memory only and closes 30 minutes after the last move. There is no chat and no name in a room.
Your game settings, best scores, achievements and missions stay in your own browser.
Following teams and sharing scores
- Follow your team and favourite matches are saved only in your own browser. They are not sent to us, with one exception that you choose: if you turn on notifications for My matches, the matches you starred and the names of the teams you follow are sent with your notification sign-up, so we know which alerts to send (see Notifications). They are kept with that sign-up only — not with your device code — and deleted with it.
- Share builds the score picture on your own device and hands it to your phone's share menu (WhatsApp, Telegram and so on). We don't see who you share with or what you send; whatever app you choose handles it under its own privacy policy.
🔔 Notifications (only if you turn them on)
- Off by default. Nobody is asked on arrival. Only when you tap 🔔 (☰ menu → Notifications, or 🔔 on a match), ⏰ Remind me on an upcoming match, or Yes on our one-time question does your browser load Google's Firebase messaging code and ask whether CricLiveChat may send notifications. If you never tap it, nothing of Firebase is loaded and Google receives nothing from us about you.
- One question, once: after you have watched a live match for about a minute, or when you come back on another day, we may show a small card once — "Get a ping for wickets & results?" with Yes and No thanks. Following a team may show it once too ("Get alerts when your team plays?"). Only Yes leads to your browser's own question. It is never shown again on that device, whatever you answer; that it was shown is remembered only on your device (
criclive_pingask,criclive_folask, andcriclive_vday= the date of your first visit), never sent to us. - ⏰ Match reminders: Remind me on an upcoming match sends you one notification about 15 minutes before its listed start. Our server keeps the same sign-up as below plus the code of that match — nothing else (no name, email, device code or time zone). The match code is deleted the moment the reminder is sent (or when the match is called off, or you tap Remind me again to cancel). If reminders are all you asked for, your whole sign-up is deleted from our server once the last one has been sent. Where notifications can't work (an iPhone browser tab, our iPhone app, or a browser without them) the button offers 📅 Add to calendar instead, which downloads a calendar file and sends us nothing.
- What you choose: all live matches, My matches (the matches you starred ★ and the teams you follow), or one match; and which events — wickets, fifties and hundreds, innings breaks, results, start of play. We only ever send match alerts: never betting, odds or ads.
- What our server keeps: the notification token your browser or app gets from Firebase Cloud Messaging (Google), your choice of level, the match codes and team names it covers, the event types, the codes of matches you asked to be reminded about (until each reminder is sent), a random stop key and the last day your device checked in. No name, no email, no device code, no IP address. It is kept on our server only — never in our backups.
- Who else: to deliver an alert we send Firebase Cloud Messaging (Google) the token and the alert text (for example "India v Australia — 🎯 WICKET…"). Google passes it to your browser's or phone's push service (for example Google, Apple or Mozilla). Firebase privacy information.
- On your device: your choice and the token (
criclive_push), and Firebase's own records in your browser's storage (firebase-messaging-database,firebase-installations-database). - Deleted: the moment you choose Off (the token is removed from our server and your browser's subscription is cancelled), when you tap Stop alerts on a notification, when Google tells us the token no longer works, after 60 days without your device checking in, or if our moderators erase all sign-ups. iPhone notifications have no buttons, so on iPhone use ☰ → Notifications → Off.
- Where it works: Chrome, Edge, Firefox and Samsung Internet on computers and Android, our Android app, and on iPhone/iPad (iOS 16.4 or later) only from CricLiveChat added to the Home Screen. You can also block notifications for this site at any time in your browser or phone settings.
Ask CricLiveChat, read-aloud and translation
- Ask CricLiveChat (the 🤖 chatbot) answers on your device from the scores and schedule the site already has. Your conversation is kept only in your browser and deletes itself after 5 minutes. To answer about a particular player, points table or series it asks our server for that player's or table's data — the question itself is not stored.
- Read aloud (🔊) uses your phone's or computer's own voice. Some browsers (for example Chrome on desktop) may use an online voice from Google to speak the score text; no personal information is involved.
- Translate to English on a chat message sends only that message's text to MyMemory (Translated srl), which returns the translation. Your name and device code are not sent.
- Error reports: if the page crashes, it sends us the technical error message, the build number, whether it's a phone or a computer, and which page was open — at most 3 per visit, nothing about you — so we can fix it.
Local storage on your device
We use your browser's local storage to remember things that stay on your device:
- your chosen chat name, and that you've accepted the disclaimer;
- the teams you follow and the matches you've favourited;
- only if you turned notifications on: your notification choice, match reminders and token (
criclive_push) and Firebase's own records, see Notifications; - whether we have already asked you once about notifications (
criclive_pingask,criclive_folask) and the date of your first visit (criclive_vday), so the question is never on your first visit and never repeated; - cached team and player names, the latest news headlines (
criclive_news, replaced each visit) and the career records of players you opened (criclive_plc, the last 40, at most a week old), so pages load faster; - display settings — light/dark mode, which tab and page you last used, and which sections you've opened or closed;
- your own copy of the scorecard as it builds during a match, your quiz answers and Fan Battle picks (with the score each live question was asked at, so its options don’t change under you), your own prediction tallies (which is all your badges are worked out from), and which chat and discussion messages you've already seen (so unread counts are correct);
- your device code, language choice, read-aloud setting, your block list and the messages you reported (so they stay hidden for you);
- the cricket game's settings (sound, voice, difficulty, keys), best scores, achievements and whether you have seen its tutorial;
- your Ask CricLiveChat conversation (deleted after 5 minutes), and how many different days you've visited, so the "Add to Home Screen" tip appears only once you're a returning visitor and never again after you close it;
- the friends group you joined (its code and name) and the codes of the groups whose monitoring notice you accepted (
criclive_grpok2; an oldercriclive_grpokmay remain from before the AI check was added and is no longer used), a once-a-day note that your daily usage count was sent, with its date (criclive_hello; the date is how we know a device has visited before — see What we count), and — for this visit only (session storage) — whether you opened the site from our Android app and where you were on the page, so a refresh keeps your place for 30 minutes; - that you confirmed you are 18 or older, and the day (only if you post — see Age);
- your visitor-counting choice and the day (
criclive_count), and, if counting is off, the smallclc_nc=1cookie (no id), see Visitor counting; - for our own moderators only: the admin page's settings, and an ads test preview switch with its counters. These never exist on a visitor's device unless the test preview is switched on in that browser.
We don't read any of this remotely; you can clear it at any time through your browser settings.
Advertising
CricLiveChat shows no ads today and sets no advertising cookies. To keep the site free we may show ads in future, served by Google AdSense. When ads are switched on:
- Google and its partners may use cookies and similar technologies to show and measure ads, including ads based on your earlier visits to this and other websites.
- If you're in the EEA, the UK or Switzerland, you'll be asked for your consent first, and you can say no.
- Anyone can turn off personalised ads in Google Ad Settings, and read how Google uses data at How Google uses information from sites that use its services.
- Google's handling of that data is covered by Google's Privacy Policy. We never share chat, votes or anything else we hold with advertisers.
We'll update the "Last updated" date above on the day ads go live.
Services that help run the site
We use a small number of providers. They handle data only to deliver the service, under their own privacy policies:
- Cloudflare — the network between you and our server. Every request passes through it, so it processes your IP address to deliver the site quickly and protect it from attacks; it may set a strictly necessary security cookie to tell real visitors from bots. We read back only Cloudflare's own daily totals for the site (requests, visitors, countries, known robots) with a read-only key — numbers, never anything about one person. Cloudflare's privacy policy.
- Amazon Web Services (AWS) — hosts our server. Our backups there hold the cricket match archive, the aggregate usage numbers and the chat-moderation records described above — no chat messages, discussion or game scores.
- Our cricket data provider sends scores to our server only; it receives nothing about you.
- OpenAI — when you add a photo, it receives that photo to check it is safe (not adult, violent, hateful or harmful); when you post in a friends group, it receives the text of that message to check it for harmful content (details). Nothing else. Under OpenAI's API terms, what we send is not used to train its models. OpenAI's privacy policy.
- Google Firebase Cloud Messaging — only if you turn notifications on: your browser loads its code from Google, gets a notification token, and our server sends the alerts through it (see Notifications). Never loaded for anyone else. Firebase Analytics is not used.
- MyMemory (Translated srl) — only when you tap "Translate to English" on a chat message: it receives that message's text, nothing else. MyMemory's privacy policy.
Phone apps
The CricLiveChat apps for Android and iPhone show this same website inside the app. They ask for no contacts, location, camera or microphone. The Android app asks to show notifications only after you tap 🔔 (see Notifications); the iPhone app does not offer notifications yet — on iPhone they work from the website added to your Home Screen. Everything on this page applies to the apps exactly as to the website. On Android the app runs the site in Chrome; on iPhone it uses Apple's built-in web view.
Ads in the iPhone app. The iPhone app contains Google's ad software (Google AdMob) so that one banner can be shown above the page later. It is switched off today: while it is off, the app does not start Google's software, shows no consent message and sends Google nothing. If we switch it on, the app will first show Google's consent message where the law requires it (EEA, UK, Switzerland and some US states). iPhone will ask whether apps may track you, and Google uses the advertising identifier only if you say yes. Google may receive your IP address, device and app information and ad interactions to show and measure ads, under Google's Privacy Policy. The app asks Google for ads suitable for teens only, and gambling, betting and dating ads will be blocked in Google's settings before it is switched on. You can change your choice any time from ☰ → Ad privacy choices in the app. We'll update this page and the "Last updated" date before it is switched on. The Android app and the website show no ads today.
Our fonts and all other site files are served from our own server, so no font or analytics company sees your visit (Firebase is loaded only for people who turn notifications on). Aside from the providers above, we don't share your data with anyone, and we never sell it.
Where your data is kept, and why we use it
- Where: our server and its backups are run by Amazon Web Services in Ohio, United States. If you use CricLiveChat from India, the EEA, the UK or anywhere else, what you send us (messages, votes, your device code) is handled there. Where the law asks for it (for example under the GDPR for the EEA and UK), we rely on the safeguards in our provider's standard data-processing terms.
- Why (legal basis): to show your messages, votes and scores to other fans, because you asked us to (you posted them); to stop spam and abuse and keep the site working, including the IP address held in memory and the anonymous counts, because we have a legitimate interest in a safe, working site; to check photos, because you chose to post one. If ads that use cookies or identifiers are ever switched on, they will run only with consent where the law requires it.
- How long: as stated in each section above. Most of it is deleted automatically within hours of a match ending.
- No automated decisions with legal or similar effects are made about you. The chat filter and the photo check only decide whether a post is shown.
Age: anyone can read, posting is 18+
Anyone may read scores, news and public chat. Sending chat messages, posting in Discussion or the Pavilion, adding photos, joining friends groups and playing other people in the game are for people aged 18 or over. The first time you try one of these, we ask you to confirm that you are 18 or older. Your browser keeps only that you said yes and the day (criclive_age18). We never ask for your date of birth or ID, and the answer is not stored on our server. Our server refuses those posts from a browser that hasn't confirmed.
This is your own confirmation; it does not prove anyone's age. CricLiveChat is not directed at children. If you think someone posting is under 18, tap ⋯ → Report → May be under 18, or use the request form (choose Child safety if a child may be at risk). We act on child-safety reports within 24 hours.
Your choices and rights
- Clearing your browser's storage for this site resets your chat name, followed teams, disclaimer acceptance and preferences.
- Because chat and polls are deleted automatically, most content disappears on its own. If you'd like a specific message removed sooner, or have any other request about your data, contact us and we'll act on it.
- If you're in India, you have rights under the Digital Personal Data Protection Act, 2023; in the EEA or UK, under the GDPR. Because we hold almost nothing about you, most requests are answered by the automatic deletions above — but we'll always respond to a request.
How to make a request
Use the request form; no account is needed. You get a reference number. We acknowledge within 24 hours and aim to resolve within 15 days. The form shows this device's code (criclive_vid) and your anonymous author tag, and can attach the code so we can find what you posted. You can add codes from your other devices. Your email is optional and is used only to reply.
The limits, honestly: without accounts, a device code only shows which posts came from a device. It doesn't prove who you are, so we only act on what that code itself posted, and we never send anyone the messages we find. When we erase, we remove chat and group messages, blank your Discussion and Pavilion posts, and remove your votes, poll votes and prediction scores, held posts and the code inside reports. An active mute stays until it ends, because it is a safety record. None of these is ever in our backups, so a restore can't bring them back. Requests are kept on our server only (never in backups) and deleted 90 days after they are closed. We keep a record of each erasure (when, how much, and the request number) with the code scrambled so it can't be read back. That record is kept for 2 years.
Wherever you live, you can ask us what we hold about your device code, ask us to correct or delete it, and complain. Because we have no accounts, we may ask you for the device code (shown in your browser's storage as criclive_vid) or the message and match, so we can find it. Some places give you specific rights:
- India (DPDP Act 2023): access, correction and erasure, a grievance channel (below), and the right to name someone to act for you. If you are not satisfied with our answer, you can go to the Data Protection Board of India.
- EEA (GDPR) and UK (UK GDPR): access, correction, erasure, restriction, objection and portability. You can complain to your local data protection authority (in the UK, the ICO).
- United States (California CCPA/CPRA and other state privacy laws): we do not sell or share personal information, and we don't use it for targeted advertising today. Your browser's Global Privacy Control signal needs no extra step from you because there is nothing to opt out of. If that changes, this page will add a "Do Not Sell or Share" choice and honour the signal. You can ask to know, correct or delete, and we won't treat you differently for asking.
- Canada (PIPEDA), Australia (Privacy Act 1988), UAE and Saudi Arabia (PDPL), Pakistan, Bangladesh, Sri Lanka (PDPA 2022) and the Caribbean: you can ask for access and correction, or withdraw from anything that needs your consent, by writing to us. You can also complain to your national privacy regulator where one exists.
Changes to this policy
We may update this policy as the site evolves. When we do, we'll change the "Last updated" date above. Significant changes will be reflected on this page.
Contact & grievances
CricLiveChat is run by NagaJyothi V, Alpharetta, Georgia, USA. NagaJyothi V is also the grievance officer for this policy (including under India's DPDP Act) and can be reached at contact@criclivechat.com.
Questions, requests or complaints about privacy? Use the request form (you get a reference number) or email us at contact@criclivechat.com. We aim to reply within 7 days.
Mail sent to contact@criclivechat.com is forwarded to our inbox by Cloudflare Email Routing; Cloudflare does not keep a copy. We use your message and address only to reply.