Data Not Collected
The categories that worry people most are the categories this site is built not to touch:
- Passwords β for the platform, for email, for anything at all
- OTP codes, in text or in screenshots
- Payment requisites: card numbers, UPI identifiers, bank or wallet details
- Documents and document photographs
- Any data from inside Fairplay accounts, to which this site has no access whatsoever
The protection is architectural rather than promised. With no registration, no user accounts, no payments, and no gaming functions, the site has no field, form, or database where such data could even arrive. What cannot be collected cannot be breached, sold, or subpoenaed β absence is the strongest encryption there is. The corollary protects readers directly: any page or message presenting itself as this site and requesting an item from the list above is counterfeit by definition, and deserves closure, not compliance.
User Rights & Deletion
The little data that does exist stays under the reader’s control, exercised through one message to the contacts form:
| Right | How to use it | What happens |
| Deletion | Request removal of your correspondence and data | Erased and confirmed β removed, not archived |
| Access | Ask what is associated with your messages | A specific answer, not a form letter |
| Restriction | Ask that your data be frozen during a dispute | Untouched until the matter closes |
| Consent withdrawal | Revoke any processing permission, no reason needed | Processing stops |
No request requires legal phrasing, identity documents, or persistence β the message is the procedure. And the boundary that simplifies everything repeats here: data never leaves for third parties, so a deletion here is a deletion everywhere it exists. Readers who never use the form hold the simplest position of all: their visits leave only anonymous statistics, and statistics contain nothing to delete.
Cookie & Preferences Management
Cookies on this site remember choices β the language you set, the theme you prefer, similar interface comforts β so a return visit resumes rather than restarts. The management console is your browser, where the standard controls apply: inspect what any site has stored, delete selectively or entirely, block for one site or all sites, or auto-expire everything at window close.
The functional consequences are modest and worth stating exactly:
| Your setting | Effect on this site |
| Cookies allowed | Preferences persist between visits |
| Cookies cleared | Settings reset once, then persist again |
| Cookies blocked | Every visit starts from defaults β nothing else changes |
| Third-party cookies blocked | No visible effect on reading |
That is the full extent of the damage: no article, guide, or table becomes unavailable, because refusal of cookies never gates content here. The choice is purely a convenience trade, it belongs to the reader alone, and the site functions honestly under any setting.
Third-Party Services
Two categories of external services participate in running this site, and naming them is part of the policy rather than a footnote to it. Analytics services convert raw visits into the aggregate statistics described above β counting, timing, pathing, anonymously. Anti-bot and protective services stand in front of the pages, filtering automated scrapers and abusive traffic away from the reading experience. Both categories process technical data β requests, browser signatures, traffic patterns β and that processing is governed by the respective services’ own privacy policies on their side of the line.
On this site’s side of the line, two constraints hold without exception: external services never receive the contents of messages sent through the contacts form, and nothing in the chain connects to advertising β no ad networks, no data brokers, no marketing integrations exist anywhere in the stack. Readers preferring to opt out individually can do so with ordinary browser tooling β tracker blocking, private windows, the cookie controls above β and every page continues to work.
Security Measures

Protection here is layered and finite, in that order. The layers:
- HTTPS on all traffic β pages and submissions travel encrypted end to end.
- Encryption at rest for stored correspondence.
- Access restriction β non-public areas reachable only by the minimal .maintaining set, each person behind separate authentication.
- Retention discipline β correspondence kept only while needed, deleted after or on demand.
The finite part is stated rather than hidden: complete security of data is not guaranteed, by this site or by any other, and policies claiming otherwise are advertising. What is guaranteed is the posture that makes incidents both unlikely and small β minimal collection, so little exists to lose; encryption in transit and at rest; narrow access; fast deletion; and a commitment, should anything ever go wrong, to tell affected readers directly and specifically what happened and what it touched. Stacked on the architectural facts β no passwords here, no payment data, no documents β the realistic exposure of visiting this site sits at the floor of what web publishing allows.
Transparency in Analytics
Analytics deserves its own daylight, because “we analyse traffic” can hide anything. Here is what the analysis actually sees and does. It sees flows: how many readers arrive, which guides they open, where attention holds and where it drops, which paths connect pages. It does not see persons: no names, no identities, no cross-site shadows, no individual histories assembled into profiles. The output is editorial instruction β a guide abandoned at step four gets its step four rewritten; a page nobody finds gets relinked; a section read repeatedly gets expanded. Readers can observe the loop themselves: content changes on this site trace back to aggregate reading patterns, and to nothing more personal. Analysis that optimises content is the entire program; analysis that follows people is not run here, and the advertising integrations that would want it do not exist in the stack.
User Consent & Control
The legal frame, stated last because it depends on everything above: using this site constitutes agreement with this privacy policy β the standard arrangement for resources without accounts, where consent cannot be collected by checkbox. But consent here is neither blanket nor one-way, and the controls stay in the reader’s hands throughout:
- Cookies are configurable or refusable at any moment, through the browser, with content unaffected
- Submitted data is deletable on request, with confirmation
- Any processing consent is withdrawable without justification
- Analytics participation is escapable through standard browser privacy tools
Continued use under those controls means continued agreement; ending use, or exercising any control, adjusts the agreement instantly and without penalty. A policy is healthy when the reader holds the levers and the site holds the obligations β that distribution is the design here, and questions about any part of it reach the team through the contacts form, where answers come back specific.

