Cookie Policy
This Cookie Policy explains how towerrushplay.xyz may use cookies, local storage, pixels and similar technologies when you browse the Website. It describes the difference between necessary and optional storage, why certain technologies are used and how you can control them, and it should be read with our Privacy Policy and Terms & Conditions. towerrushplay.xyz is an independent information website; our first-party cookies are not intended to contain casino passwords, UPI PINs, card CVVs or banking credentials.
What Cookies Are
A cookie is a small data file that a website or service can place in a browser, commonly containing an identifier, preference, expiry time or session value. A cookie is not normally a software program and cannot run independently like an application, but identifiers stored in cookies can be combined with other data to recognise a browser, which is why optional tracking requires clear disclosure and, where applicable, consent. A first-party cookie is set under towerrushplay.xyz, while a third-party cookie is associated with an external provider whose technology appears on the Website. Session cookies normally expire when the browser session ends, while persistent cookies remain until their configured expiry or manual deletion.
Cookie Categories
| Category | Main purpose | Typical consent position |
|---|---|---|
| Strictly necessary | Security, consent records and core functions | Active because required for the requested service |
| Functional | Language, display and user preferences | Optional where not essential |
| Analytics | Aggregate traffic and performance measurement | Activated after applicable consent |
| Affiliate | Referral attribution | Activated after applicable consent where lawful |
| Advertising | Personalised or campaign advertising | Optional and not required for core content |
A cookie's category should be determined by what it actually does. Calling a marketing identifier essential does not make it necessary.
Strictly Necessary Cookies
These support functions requested by the user or required to operate the Website safely, such as remembering whether you accepted or rejected optional categories, protecting a contact form, applying security and rate-limiting controls, and maintaining temporary session consistency. They should not be used to build an advertising profile and should store only the data reasonably required. Blocking all first-party storage may prevent the Website from remembering your consent decision, so the banner could appear again.
Analytics Cookies
Analytics cookies can help measure how visitors use the Website, such as pages viewed, approximate session duration, referral source, browser category and page-performance events, in order to identify broken links and content that needs improvement. Analytics should not be described as anonymous unless the active configuration supports that claim, and no analytics provider is named as active unless it is genuinely deployed. Optional analytics scripts should remain blocked until consent where consent is required.
Affiliate and Advertising Cookies
Affiliate cookies can help attribute an eligible action to the page or link that generated a referral, using a click ID, campaign ID, timestamp, referring page, destination and conversion status. They should not give towerrushplay.xyz access to your UPI PIN, bank password or casino password. Affiliate tracking does not make a third-party service lawful in India and may be restricted where online-gaming advertising is prohibited. Advertising cookies are not required to read the Website's core information and, if introduced, should not load merely because a user accepted necessary cookies.
Managing Your Preferences
The cookie consent banner should explain the main categories in plain language and provide meaningful choices rather than treating silence as acceptance. It should offer Accept all, Reject non-essential and Manage preferences, with the rejection option no harder to use than acceptance. You can also inspect, block and delete cookies through browser settings in Chrome, Firefox, Edge and Safari, though blocking every cookie may prevent the Website from remembering language, consent or security state. Rejecting optional cookies should not prevent access to the Website's ordinary Tower Rush articles.
Live Cookie Inventory and Updates
A Cookie Policy should be supported by an inventory of the technologies actually detected on the live Website, listing each cookie's name, provider, purpose, category, duration, first or third-party status and consent position. We do not invent cookie names in this document; the exact list must match a current technical scan, and an unknown cookie should not be assigned to the essential category without investigation. The inventory should be rescanned after changes to the theme, plugins, analytics, advertising, affiliate code or embedded content. This Policy may be updated when the Website adds or removes providers or responds to legal developments, and the last-reviewed date will change after a revision.
