1. What cookies and local storage do
Cookies are small records that a website can ask your browser to retain and, in many cases, send back with later requests. Local storage is another browser mechanism: it retains values for a site but does not automatically attach them to ordinary page requests. Similar privacy rules may apply to both, so this policy covers browser storage as well as traditional cookies.
The supplied cricketindialbs.com files do not set HTTP cookies. They use localStorage solely to remember the choice made through the cookie banner. That record stays in your browser and is not sent to an analytics endpoint by the site’s script.
2. Storage inventory
The table distinguishes what is actually used from categories offered in the preference controls. “Not set” means no storage item or corresponding service is included in this edition. There are no hidden marketing categories, third-party fonts, remote maps or externally hosted article images.
| Category | Item / provider | Purpose and duration |
|---|---|---|
| Essential | cic_cookie_consent_v1First-party localStorage | Remembers category choices, version and timestamp. Valid for 180 days; removed or replaced when expiry is checked on a later visit. |
| Analytics | Not set No provider | No audience measurement, session replay or visitor identifier. No duration applies. |
| Functional | Not set No provider | No optional saved display settings or embedded-service preferences. No duration applies. |
3. What each banner button means
Accept All records both optional categories as allowed. Reject Non-Essential records both as disabled. Preferences opens separate analytics and functional controls, followed by a save button. Essential preference storage remains enabled so your decision can be remembered. All three routes leave the articles available.
Optional categories are currently inactive. Accepting them does not install a service, transmit your message or authorise unrelated future processing. If a deployed operator introduces analytics or another material purpose, it must update the inventory, identify the provider and obtain any fresh consent required before activating that technology.
4. Change or withdraw a choice
Use “Cookie preferences” in any page footer to reopen the controls. Clear an optional checkbox and save, or choose Reject Non-Essential. Your new decision replaces the old local record. Choices are specific to the current browser and site origin, so a different device, browser profile or subdomain may ask again.
The script requests a fresh choice after 180 days or a policy-version change. If storage is blocked, the choice can only be honoured for the current page session and the banner may return on another page. A visible message explains when saving fails. Rejecting optional categories does not reduce access to editorial content.
5. Browser opt-out instructions
In Chrome, open Settings, Privacy and security, then Site settings or the controls for stored site data; search for this domain and delete its data. In Edge, use Settings and search for “cookies” or “site data,” then view and remove data for this domain. Labels can vary between releases.
In Firefox, open Settings, Privacy & Security, Cookies and Site Data, then Manage Data. In Safari on macOS, open Settings, Privacy, then Manage Website Data. On iPhone or iPad, use the Safari settings and its website-data controls; recent iOS versions place Safari under Apps. Removing all site data can sign you out of other services, so use domain-specific removal where possible.
Private browsing commonly clears storage when the private session ends. Blocking all storage may cause repeated consent prompts. Global Privacy Control and Do Not Track signals do not activate tracking here; there is no sale, sharing or analytics activity in the supplied files to opt out of.
6. Questions and deployment changes
For privacy questions, use [email protected] and read the privacy policy. The publisher details and contact identities are illustrative until verified by a real operator. Hosting infrastructure could add technologies not present in these static files; the operator must audit the deployed site and update this policy accordingly. Following an external link takes you to a separate service with its own cookie practices.