Privacy — what data the desk collects and what the desk does not collect.
The desk's data practices: server logs for 30 days, optional correction tips until actioned, no mobile or Aadhaar or PAN collection, no third-party CRM handoff and no cross-site tracking cookies. The reader can ask for a copy or a deletion within seven working days.
Server logs, optional correction tips, and the data needed to publish the coverage.
The desk collects three categories of data. First, server logs: the IP address, the user agent and the request path, retained for 30 days for abuse detection and capacity planning. Second, optional correction tips: the email address and the tip body, retained until the desk confirms the correction has been actioned. Third, the data needed to publish the coverage (fixture schedules, team form, venue records) which is sourced from public score feeds and tournament publications and is not reader data.
The desk collects three categories of data. First, server logs: the IP address, the user agent and the request path, retained for 30 days for abuse detection and capacity planning. Second, optional correction tips: the email address and the tip body, retained until the desk confirms the correction has been actioned. Third, the data needed to publish the coverage (fixture schedules, team form, venue records) which is sourced from public score feeds and tournament publications and is not reader data.
No mobile number, no Aadhaar, no PAN, no bank details, no third-party CRM handoff.
The desk does not collect the reader's mobile number, Aadhaar number, PAN, bank details or any government identifier. The desk does not embed registration forms from any third-party operator. The desk does not pass the reader's data to any third-party CRM, marketing platform or analytics tool that ties back to the reader's identity. The desk uses first-party analytics only (page views, referrer, country) and the analytics does not include cookies tied to the reader's identity.
The desk does not collect the reader's mobile number, Aadhaar number, PAN, bank details or any government identifier. The desk does not embed registration forms from any third-party operator. The desk does not pass the reader's data to any third-party CRM, marketing platform or analytics tool that ties back to the reader's identity. The desk uses first-party analytics only (page views, referrer, country) and the analytics does not include cookies tied to the reader's identity.
First-party session cookies only, no third-party tracking cookies.
The desk sets a first-party session cookie to remember the reader's preference between page loads (the menu open or closed state, the drawer collapsed or expanded state). The cookie expires when the reader closes the browser. The desk does not set any third-party tracking cookies, advertising cookies or analytics cookies that follow the reader across sites. The desk does not use Google Analytics, Facebook Pixel or any equivalent cross-site identifier.
The desk sets a first-party session cookie to remember the reader's preference between page loads (the menu open or closed state, the drawer collapsed or expanded state). The cookie expires when the reader closes the browser. The desk does not set any third-party tracking cookies, advertising cookies or analytics cookies that follow the reader across sites. The desk does not use Google Analytics, Facebook Pixel or any equivalent cross-site identifier.
Server logs 30 days, correction tips until actioned, no permanent reader profiles.
Server logs are retained for 30 days and then deleted. Correction tips are retained until the desk confirms the correction has been actioned, then deleted within seven days of the correction being published. The desk does not build a permanent reader profile and does not retain any data that ties the reader to a specific fixture read, a specific captain pick or a specific fantasy selection. The desk does not sell reader data and does not share reader data with any third party.
Server logs are retained for 30 days and then deleted. Correction tips are retained until the desk confirms the correction has been actioned, then deleted within seven days of the correction being published. The desk does not build a permanent reader profile and does not retain any data that ties the reader to a specific fixture read, a specific captain pick or a specific fantasy selection. The desk does not sell reader data and does not share reader data with any third party.
The reader can ask for a copy, ask for a deletion, or file a correction tip.
The reader can ask for a copy of any data the desk holds about the reader (a correction-tip email address, for example) by writing to the customer-care desk. The desk responds within seven working days. The reader can ask for the data to be deleted; the desk deletes the data within seven working days of confirmation. The reader can file a correction tip via the customer-care page; the desk reads every correction tip within 48 hours and publishes the correction within seven days of confirmation.
The reader can ask for a copy of any data the desk holds about the reader (a correction-tip email address, for example) by writing to the customer-care desk. The desk responds within seven working days. The reader can ask for the data to be deleted; the desk deletes the data within seven working days of confirmation. The reader can file a correction tip via the customer-care page; the desk reads every correction tip within 48 hours and publishes the correction within seven days of confirmation.
Common questions about the desk's data practices.
Does the desk sell reader data?
No. The desk does not sell reader data and does not share reader data with any third party. The desk's business model is editorial coverage, not data brokerage.
Does the desk use third-party tracking?
No. The desk uses first-party analytics only. No Google Analytics, no Facebook Pixel, no cross-site identifier. The first-party analytics does not include cookies tied to the reader's identity.
Can the reader ask for a data deletion?
Yes. Use the customer-care page. The desk deletes the data within seven working days of confirmation. The reader can also ask for a copy of any data the desk holds; the desk responds within seven working days.
Companion legal pages.
The companion legal pages for the LeaguesX editorial desk.
Terms of use
What the desk publishes, what the desk does not do, the editorial boundary and the reader's responsibility.
Disclosure
How the desk handles affiliate references, quoted operator language and the rel="sponsored nofollow" convention on outbound links.
Responsible play
The desk's stance on age, jurisdiction, the skill-based framing and the help lines available to readers in India.
About the desk
The mission, the byline convention, the corrections register and how the desk is funded.