Cookies on this site today
| Cookie | Set by | Purpose | Status |
|---|---|---|---|
| Strictly necessary | This site | Would keep a session or login alive | None. The site has no session or login. |
| Analytics | Google Analytics | Would count visits and page paths | Not enabled |
| Advertising | Any ad network | Would track you across sites | None, and none planned |
| Preference | This site | Would remember a setting you chose | None. There are no settings. |
The table is the whole story for now. Every page is plain HTML served by the host, with the stylesheet inlined and a small script that handles the menu and the WhatsApp button. Neither writes a cookie.
Why a site like this doesn't need them
Cookies are for remembering. A shop remembers your basket; a forum remembers that you're logged in. This site does neither. You read a page about, say, a Lotus365 ID, and if you want one you message the desk on WhatsApp. Nothing about that step happens on this site, so there is nothing for the site to store. The online cricket ID page explains why the ID is issued in a chat rather than by a form, and that design choice is the reason this policy is so short.
If analytics is switched on later
We may at some point enable Google Analytics to see which pages people read and where they get stuck. If we do, three things happen at once: this page gains a row describing what the analytics cookie stores and for how long, the privacy policy is updated to match, and the updates page carries an entry with the date. Until you see that entry, nothing has changed.
Even then, analytics would tell us that a page was read, not who read it. We would not link it to a WhatsApp number, an email or anything the desk holds about you.
Cookies are not how copycats get you
Copycat sites don't need cookies to do harm; they need you to type a password or send money to the wrong account. Cookie-free or not, the check is always the same: compare the address and the WhatsApp number against the official channels page before you act.
Cookies set by other services
Two things on this site take you elsewhere. The WhatsApp button opens WhatsApp, on your phone or in a browser tab, and the login link the desk sends opens the exchange. Both are run by other companies under their own cookie and privacy terms, which we neither see nor control. The safety page covers how to tell a real exchange login page from a copy, which matters far more than what either page stores.
Managing cookies in your browser
You can view, block or delete cookies for any site in your browser settings, usually under privacy or site data. Doing so here has no effect on how the site works, because nothing depends on one. If you block all cookies everywhere, some exchange login pages may stop working, and that is a matter for the exchange, not us.
Cookie categories, retention and how to raise a question about this cookie policy
Cookie policies usually describe cookies by category, so that a reader can tell which ones a site could function without. This site sets none from its own code today, but the categories are worth setting out, both so you can judge any change we announce later and so you can read other sites' policies with the same vocabulary.
Strictly necessary cookies are the ones a site needs in order to work at all: keeping you logged in, remembering a form between pages, protecting against certain attacks. This site has no login, no forms and no basket, so it has no need of them. If one were ever required, for example by a security measure at the hosting layer, it would be listed here with its name and purpose.
Preference cookies remember a choice you made, such as a language or a dismissed notice. We have no such choices to remember. Analytics cookies measure how pages are used; the section above explains what would change if those were switched on and how you would be told. Advertising cookies follow you between sites to build a profile; we do not run advertising and will not add this category.
Retention for a cookie means how long it stays on your device. Session cookies vanish when the browser closes; persistent cookies have an expiry date set by whoever created them. If analytics were ever introduced, this page would state the retention period for each cookie it sets and would not describe one as lasting for as long as the account is active, since this site has no accounts; the only retention periods tied to an account are the ones in the privacy policy, and those concern the WhatsApp desk, not cookies.
The WhatsApp button on every page opens a chat in the WhatsApp app or site, which has its own cookie and privacy arrangements that we do not control. The same is true of any exchange you log in to after the desk issues an ID. The online cricket ID provider page explains that the exchange, not this site, holds your account, and the exchange's own cookie notice governs that session.
If you believe this site has set a cookie not described here, open your browser's storage inspector, note the cookie name and the domain it is set for, and email that to the address on the contact page. We will reply with where it came from, and if it came from our code, it will be removed or added to this page with its purpose and retention period.
Questions
Anything about this page goes by email; the contact page has the address. The terms of use and disclaimer sit alongside it. This cookie policy is reviewed whenever anything on the site changes how it loads.