Data Collection Practices

None of this is sold, rented, or otherwise handed to third parties for their own purposes. Aggregated, anonymised traffic patterns tell us that a guide is being read by visitors from India on mobile devices and abandoned halfway — which is a signal to rewrite the guide, and nothing more personal than that.

Data We Do Not Collect

The shortest and most important section of this policy. This site does not collect, request, or store:

• Passwords or login credentials for any service
• OTP codes or verification messages
• Payment details of any kind — card numbers, UPI handles, bank or wallet information
• Identity documents, their numbers, or their photographs
• Fairplay account data — we have no connection to the platform and no visibility into it

There is no registration here, no profile, no account, and therefore no honeypot of sensitive records to breach. If any page or message appearing to come from this site ever asks for items on this list, treat it as fraudulent — it is not ours. The protection of your personal information starts with a simple architectural choice: data that is never collected can never leak.

User Rights & Data Deletion

What little data exists remains under your control, and exercising that control does not require legal vocabulary or persistence. Through the contacts form you can:

• Request deletion of any correspondence or personal data you have submitted
• Ask what information, if any, is associated with your messages
• Request that access to your data be restricted while a question is resolved
• Withdraw any previously given consent without explaining why

Requests are confirmed once completed, and deletion means deletion — not archiving under a different label. The same boundary as everywhere on this site applies: data is never transferred to third parties, and a deletion request does not survive as a marketing record somewhere. For most visitors, the practical reality is even simpler: if you never used the contacts form, the only traces of your visits are anonymous statistics that identify nobody.

Cookies & Preferences Management

Cookies on this site are convenience tools rather than surveillance instruments. They remember the language you chose, the theme you prefer, and similar interface settings, so the site looks the same on your next visit without asking again. Managing them happens in your browser, not here, and every mainstream browser offers the full set of controls:

• View which cookies a site has set, and inspect their contents
• Delete cookies for one site or for everything
• Block cookies entirely, or only third-party ones
• Set cookies to expire automatically when the browser closes

What changes if you refuse cookies: nothing essential. Every article, guide, and page on this site remains fully readable with cookies disabled — refusal never locks content. What you lose is convenience: the language setting resets, the theme returns to default, and any saved preference asks to be chosen again on each visit. That trade-off belongs entirely to you, and the site works honestly on either side of it.

Third-Party Services

Running even a simple site involves a small supporting cast, and honesty requires naming the categories. We use third-party services of two kinds: analytics tools that turn raw visits into the aggregated statistics described above, and protective services that filter bots, scrapers, and abusive traffic before it reaches the pages. These services process technical data — requests, browser signatures, traffic patterns — under their own privacy policies, which govern their side of the processing.

Two boundaries keep this arrangement clean:

If a reader wants to opt out of analytics at the individual level, standard browser tools — tracker blocking, private browsing modes, the cookie controls above — apply here exactly as they do across the web, and the site remains fully functional under all of them.

Security Measures

Security on this site follows the same philosophy as data collection: keep the attack surface small, then protect what remains. The measures in place are concrete. All traffic runs over HTTPS, encrypting the connection between your browser and the site, so pages and form submissions travel sealed rather than readable in transit. Access to anything non-public — form submissions, site administration — is restricted to the minimum number of people who genuinely need it, behind their own authentication. Stored correspondence is kept encrypted, retained only as long as a request requires, and deleted afterwards or on demand.

And then the honest sentence that every truthful privacy policy owes its readers: complete security does not exist, here or anywhere, and we do not guarantee it. What we guarantee instead is the discipline around it — minimal collection so there is little to lose, encryption in transit and at rest, restricted access, prompt deletion, and a standing commitment to tell readers plainly if anything ever goes wrong with their data. Combined with the architectural fact that this site holds no passwords, no payment details, and no documents, the realistic risk to a visitor remains as low as web publishing allows. Questions about any practice described here are welcome through the contacts page, and answers will be specific rather than reassuring noise.