Privacy

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

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):

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:

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.

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:

Your game settings, best scores, achievements and missions stay in your own browser.

Following teams and sharing scores

🔔 Notifications (only if you turn them on)

Ask CricLiveChat, read-aloud and translation

Local storage on your device

We use your browser's local storage to remember things that stay on your device:

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:

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:

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

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

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:

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.