Privacy policy.

What we collect

Reading this site does not require an account, and we do not ask for personal information to show you a page. Our hosting provider records standard server logs, which typically include an IP address, a timestamp, the page requested and a user-agent string. These are used to keep the site running and to detect abuse.

If you write to the desk, we hold your message and your address for as long as needed to deal with it and to keep a record of any correction that resulted.

What we do not do

• We do not operate accounts, wallets or balances, so we hold no financial data.
• We do not collect KYC documents. Any verification happens on an operator's own platform.
• We do not sell or rent reader data.
• We do not publish reader correspondence without permission.

Outbound links

This site carries one commercial outbound link, marked with rel="sponsored nofollow noopener noreferrer". Following it takes you to a third party operating under its own privacy policy and terms, over which we have no control. Anything you enter there is governed by that operator's policy, not this one. We recommend reading it before registering.

Requests and children

To ask what we hold about you, or to have correspondence deleted, write to the desk through the contact page. Include enough detail to identify the correspondence.

This site is intended for adults. Its subject matter is real-money skill gaming, which is restricted to players aged 18 and over. We do not knowingly collect information from anyone under 18.

Lawful basis for processing

The publisher processes the limited personal data described in this policy on the lawful basis of legitimate interest, where the interest is the operation of an editorial publication and the maintenance of its security. Where the publisher processes personal data on the basis of consent (for example, where a reader has volunteered information in a message), the consent can be withdrawn at any time by writing to the desk through the contact page. Withdrawal of consent does not affect the lawfulness of processing carried out before the withdrawal.

The publisher does not rely on consent as the lawful basis for any processing that is strictly necessary for the operation of the site, including the server logs described above and the security measures applied to those logs.

How long we hold what you send us

A message you send the desk is held for as long as is necessary to respond to it, to keep a record of any correction that resulted from it, and to defend any claim that may later arise from the content of the message. Routine correspondence is reviewed after twenty-four months and either deleted or anonymised into a statistical record of the kind of question the desk received. A reader can request earlier deletion at any time.

Server logs are retained for thirty days and then deleted automatically. Logs that are part of an active security investigation are retained for the duration of the investigation and then deleted.

Cookies and similar technology

This site does not set any first-party analytics or advertising cookies. The site does set a single session cookie, used by the server to maintain the session between page loads during a single visit; the cookie expires when the browser is closed. The site does not use any third-party analytics service, any third-party advertising network, any third-party tag manager, or any third-party embedded content that would set its own cookies.

A reader who chooses to block the session cookie in their browser settings will find that the site continues to work; pages do not require the cookie to render or to be readable.

International transfers

The publisher's hosting is in India and the data the publisher holds is processed in India. Where a reader writes to the desk from outside India, the act of sending the message constitutes an instruction to transfer the content of the message to India for processing. The publisher does not transfer personal data to any other jurisdiction.

Your rights as a reader

You have the right to ask what personal data the publisher holds about you, to ask for inaccurate data to be corrected, to ask for data to be deleted, to ask for the processing of your data to be restricted, and to ask for a copy of the data you provided in a portable format. To exercise any of these rights, write to the desk through the contact page with enough detail to identify the correspondence. The publisher responds to a rights request within thirty days; if the request is complex, the publisher will write to the reader within thirty days to explain the extension.

You also have the right to complain to the relevant data protection authority if you believe the publisher has not handled your personal data lawfully. The publisher would prefer to resolve the complaint directly, and the contact page is the route for that conversation.

Changes to this policy

The publisher may revise this privacy policy from time to time. The current version is always published at this URL, with an updated date at the top of the page. Material changes are flagged in the body of the page for at least thirty days after the change takes effect. Where a change affects personal data already held, the publisher will, where practicable, notify affected readers directly.

How to reach the desk about privacy

Questions about this privacy policy, or requests to exercise the rights described above, should be sent through the contact page. The publisher's named contact for privacy matters is the editor on duty; the contact page lists the current named editor and the response window for privacy queries, which is thirty days from receipt.

Data minimisation in practice

The publisher applies a data-minimisation rule to every form, log and message store on the site. The rule is: collect the smallest set of data that is necessary for the purpose, keep it for the shortest time that is reasonable, and delete it without prompting when the time is up. Where a form asks for information that the publisher does not strictly need, the field is marked optional; a reader who leaves the field blank will not be refused service for doing so.

The server log retention period described above is the publisher's current minimum that balances operational security against the privacy of the reader. The publisher reviews the period annually and reduces it where the security case for retaining a longer log has weakened.

Security measures applied to the data we hold

The publisher applies the security measures that a small editorial site can reasonably apply: TLS on every page, HTTP-only cookies, no third-party scripts on the critical path, no third-party analytics, restricted access to the message store on the production server, and an off-site backup that is itself encrypted and access-controlled. The publisher does not claim that any of these measures is sufficient against a determined attacker; the publisher claims only that they are the measures that the desk itself relies on, and that a security review of the site would not find a measure the desk has quietly declined to apply.

A reader who has a specific concern about the security of a message they have sent the desk should write to the desk through the contact page; the desk will explain the controls in place for the message in question and, where appropriate, will agree a retention that is shorter than the publisher's default.

Children and the age limit

This site is intended for adult readers and its subject matter is real-money skill gaming, which is restricted to players aged 18 and over in every Indian state. The publisher does not knowingly collect personal information from anyone under 18. Where the publisher learns that information has been received from a reader under 18, the publisher will delete the information within thirty days and will not use it for any purpose.

A parent or guardian who believes a child has sent the desk information should write to the contact page with enough detail to identify the message; the desk will confirm deletion within seven days of receipt of the request.

Where this site hands off to a third party

The publisher hands off to a third party only when a reader clicks the single commercial outbound link, marked with rel="sponsored nofollow noopener noreferrer". From the moment the reader lands on the third party's page, the third party's own privacy policy and terms apply. The publisher is not the controller of any data the third party collects, and the publisher does not see, store or have access to the data the third party collects. A reader who wants to understand what the third party is doing with their data must read the third party's own policy, on the third party's own site.

The publisher selects the third party on editorial grounds and reviews the selection periodically. Where the publisher becomes aware that a third party has materially changed its data-handling practice in a way that affects a reader, the publisher will note the change in the body of any page that links to the third party.