Privacy notice.

The site uses a small number of cookies and a small number of local storage entries. The cookies and local storage entries are used for the mobile drawer state (whether the reader has the menu open or closed), the editorial index rail position (which section the reader was last viewing), and the editorial comment thread preferences (whether the reader wants long-form threads expanded by default). The cookies and local storage entries are not used for advertising, are not linked to a reader profile, and are not shared with third-party platforms.

The site does not use a third-party analytics cookie. The site uses a small server-side analytics tool that records anonymous pageview counts and referrer sources without setting a cookie on the reader's device. The site's analytics tool is configured to honour the reader's "Do Not Track" browser setting; readers who have Do Not Track enabled are not recorded in the site's analytics output.

The site does not use third-party advertising cookies. The site does not use Facebook Pixel, Google Ads conversion tracking, or any equivalent. The site does not embed third-party iframes that would set a cookie on the reader's device. The site's editorial position is that a reader's reading history on the site is the reader's, and the desk does not share the reader's reading history with third-party platforms.

The desk's process for a data-subject request is to handle the request by correspondence wherever possible. The desk prefers to handle requests by correspondence because the desk's editorial publication is small, the desk's data footprint is small, and the desk's readership is small enough that a single correspondence can resolve the request without the desk having to invoke a formal process. Readers who want to send a data-subject request should write to the contact page with the subject line "Data-subject request" so the letter is routed to the managing editor.

The desk's typical response to a data-subject request is to acknowledge receipt within one working day, to confirm the request within five working days, and to resolve the request within thirty days of the acknowledgement. The desk's experience is that the vast majority of requests are resolved within a single round of correspondence; the desk has not had to invoke a formal process in the publication's history.

The desk's policy on retention of personal data is unchanged: the desk retains the minimum personal data needed to operate the publication, retains correspondence for twelve months from the last meaningful exchange, and deletes data on request. The desk's policy on server logs is unchanged: the logs are retained for a rolling 30 days and are not linked to a reader profile. The desk's policy on third-party-subprocessor disclosure is unchanged: the desk publishes a list of subprocessors at the bottom of this page and updates the list whenever a subprocessor is added or removed.

The desk's policy on changes to this privacy notice is unchanged across issues: any material change is announced at the top of this page with a date stamp and a one-paragraph summary of what changed and why. A non-material change (a typo fix, a link update, a wording clarification) is made without an announcement and is reflected in the version history at the bottom of this page. The desk does not retroactively apply a new privacy term to a reader who registered under an earlier version; the version the reader registered under is the version that governs the reader's relationship with the site.

The desk's policy on data retention is unchanged: the desk retains the minimum personal data needed to operate the publication, retains correspondence for twelve months from the last meaningful exchange, and deletes data on request. The desk's policy on data deletion is unchanged: the desk deletes data on request within thirty days of the request, and the desk's experience is that the vast majority of requests are resolved within a single round of correspondence.

The desk's policy on subprocessors is unchanged: the desk publishes a list of subprocessors at the bottom of this page and updates the list whenever a subprocessor is added or removed. The current list of subprocessors is: a hosting provider for the editorial site, a CDN provider for the editorial site's static assets, and an email provider for the desk's editorial correspondence. The desk does not currently use any other subprocessors.

The desk's policy on children is unchanged: the publication is intended for adult readers and is not directed at children under the age of 18. The desk does not knowingly collect personal data from children. If a parent or guardian believes that a child has submitted personal data to the desk, the desk responds promptly to a request to delete the data, and the desk's typical response time is within one working day.

The desk's policy on international readers is unchanged: the publication is written primarily for readers in India, and the legal references in the publication are Indian-state-level references. Readers outside India are welcome to read for general information but should consult their local rules before considering any paid rummy activity. The desk does not currently publish a separate international edition; the desk's editorial position is that the publication's editorial line is Indian and is meant for Indian readers first.

The desk's policy on regulatory cooperation is unchanged: the desk cooperates with requests from Indian regulators, courts, and law-enforcement agencies to the extent required by Indian law. The desk's experience is that the volume of such requests is low; the desk responds to each request within the desk's standard turnaround. The desk's policy on secret warrants and gag orders is unchanged: the desk does not voluntarily comply with a gag order, and the desk will challenge a gag order in court if the desk's editorial position is that the gag order is incompatible with the publication's commitment to reader transparency.