Data Collection Principles
Two principles govern everything below. First, minimalism: if a piece of information is not needed to serve pages or to defend the site against abuse, it is not collected. Second, separation: this site’s data practices have nothing to do with any gaming platform a reader may use — what a platform collects is governed by that platform’s own policy, not this one.
| Principle | What it means in practice |
| Minimal collection | Only technical signals required for operation and security |
| No personal profiles | No names, no accounts, no identity data gathered |
| No payment data | The site processes no payments, so none exists here |
| Separation | Third-party platforms’ practices are their own |
Types of Collected Data
The technical signals the site works with are the ordinary ones any web resource sees:
- IP address — as part of standard server traffic handling and abuse protection
- Browser type and version — to serve pages that render correctly
- Device settings — screen and language signals that shape how content displays
- On-page behavior — aggregate signals such as which pages are visited and for how long
- Anti-abuse signals — patterns used to detect bots, scraping and attack traffic
These signals describe traffic, not people. They are used to keep the site fast, readable and defended — and they are the full extent of what flows in. Retention follows the same minimal logic: technical logs are kept only as long as operation and security require, after which they age out of the systems that held them rather than accumulating into an archive.
Personal Information Not Collected
The clearest part of this policy is the list of absences. The site does not collect:
- Personal identity data — names, addresses, dates of birth or government identifiers
- Passwords of any kind, for this site or any other
- Confirmation or verification codes, including anything sent by a gaming platform
- Identity-verification documents or their contents
- Payment details — card numbers, wallet addresses, banking information
No page on this site has a legitimate reason to request any item on that list. If something presenting itself as this site ever asks for one, it is not this site — it is an imitation, and the request itself is the proof.
Cookies Usage
The site uses cookies for the unglamorous purposes cookies were built for: keeping navigation smooth and remembering reader preferences between visits.
| Cookie purpose | What it does |
| Navigation | Keeps moving between pages fast and consistent |
| Preferences | Remembers display settings a reader has chosen |
| Security | Supports the anti-abuse signals described above |
Control sits with the reader. Every mainstream browser allows cookies to be viewed, restricted or deleted through its settings, and the site remains readable with cookies limited — some conveniences, such as remembered preferences, simply reset. Readers who prefer to browse with minimal state can do so; the materials do not hide behind cookie consent walls, because reference content has no reason to. Blocking cookies entirely in the browser also works — pages still load, and nothing essential to reading the guides depends on stored state.
Data Processing by Providers
Running a website involves infrastructure, and infrastructure involves contractors. The technical information described above may be processed by service providers strictly for two purposes: hosting — keeping the site online and serving its pages — and security — filtering attacks and abusive traffic before they reach the resource.
The boundaries of that arrangement are firm:
- Providers process technical signals only, within the categories listed in this policy
- Processing serves hosting and security — no other purpose rides along
- No transfer of data to third parties for marketing, profiling or resale takes place
- Providers act on the site’s instructions, not on independent uses of the traffic they see
In plain terms: the data that keeps the site running stays inside the machinery that runs the site. It is not a product, and nobody buys or rents it.
User Rights
A reference site holds little, but readers still hold rights over what it does handle. A reader may contact the editorial team to:
- Ask what categories of technical information the site has handled in connection with their visits
- Request clarification of anything in this policy that reads ambiguously
- Request deletion of technical data tied to them, where the site’s technical model supports isolating it
- Object to a processing practice they believe falls outside this policy
One honest caveat belongs here: because the site does not build personal profiles, technical signals are often not attributable to a specific person at all — an IP address in a server log is not a name. Where a request concerns data the site can isolate, it will be acted on; where the technical model makes isolation impossible, the response will say so plainly rather than promise what cannot be done. Requests go through the contact page, are read by the editorial team, and receive an answer that reflects what the infrastructure actually allows — the same standard of accuracy the rest of the site is held to.
This policy may be updated when the site’s technical setup or procedures change, and the current version on this page is always the version in force. Readers in India should also remember the separation principle from the top of this page when moving outward: any gaming platform reached through a link has its own collection practices, its own cookies and its own policy — and those, not this document, govern what happens there.