What this policy covers
This privacy policy describes how sportazain.com (the editorial site) collects, uses, retains and shares data. The policy covers the editorial site's content, the RSS feed, the contact channel and the editorial desk's internal workflow. The policy does not cover the platform's data practices; the platform's own privacy policy governs the platform's own data practices and is the authoritative source for those.
The editorial site is operated as a single-desk publication. The site does not run advertising, does not collect reader data beyond what the RSS feed and the contact channel require, and does not share reader data with third parties except as described below.
What data the editorial site collects
The editorial site collects only the data needed to operate the site and to respond to reader messages. The site collects: the IP address of every visitor, for the purpose of serving the site and detecting abuse; the user-agent string, for the same purpose; the URL of every page request, for the same purpose; the RSS subscription count, for the purpose of measuring the audience of the editorial coverage. The site does not collect: names, email addresses, phone numbers, payment information, biometric data, or any other personal identifier beyond the IP address.
Reader messages sent through the contact channel are stored in the desk's email inbox. The desk uses the email address only to respond to the message; the desk does not add the email address to any marketing list.
How the editorial site uses the data
The editorial site uses the IP address, user-agent and URL of every request to serve the site, detect abuse, and measure the audience. The site uses the RSS subscription count to measure the audience of the editorial coverage. The site uses the contact-channel email address to respond to reader messages.
The site does not use the data for advertising, retargeting, or third-party tracking. The site does not embed third-party analytics scripts; the site uses the server access log as its analytics source.
What data the editorial site retains
The editorial site retains the server access log for 30 days. The site retains reader messages for 30 days after the response is sent, then deletes them. The site retains the RSS subscription count as an aggregate number; the site does not retain the IP addresses of individual subscribers.
Adult readers who want their data deleted can contact the desk at the address on /contact/. The desk processes valid deletion requests within 30 days. The desk does not charge for deletion requests.
Reader rights
Adult readers have the following rights under the Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000. The right to access the data the site holds about them; the right to correct inaccurate data; the right to request deletion of the data; the right to withdraw consent for any data processing the reader previously consented to; the right to grievance redressal.
To exercise any of these rights, contact the desk at the address on /contact/. The desk responds within 30 days; the desk does not charge for responding to rights requests.
Grievance officer
The editorial desk's grievance officer is the editor on duty, reachable at the address on /contact/. The grievance officer responds to reader grievances within 30 days. If a reader's grievance is not resolved within 30 days, the reader can escalate to the relevant data-protection authority.
Cookies and similar technologies
The editorial site uses cookies only for the purpose of serving the site. The site does not use cookies for advertising, retargeting, or third-party tracking. The site's cookies expire at the end of the browser session.
Children's privacy
The editorial site is intended for adult readers (18+) of legal age in their jurisdiction. The site does not knowingly collect data from minors. If a minor has submitted data to the site through the contact channel, the desk will delete the data on request from the minor's parent or guardian.
Cross-border data transfers
The editorial site's hosting provider stores server access logs in data centres located in India. The site's email provider stores reader messages in data centres located in India. The site's payment processor stores affiliate commission records in data centres located in India and in the processor's home jurisdiction. The site does not transfer reader data to any other jurisdiction.
Changes to this policy
The editorial desk publishes a changelog of material changes to this policy. Material changes are flagged at the top of this page with a date stamp and a short description of the change. Adult readers who disagree with a change can contact the desk; the desk will respond within 30 days.
Frequently asked privacy questions
How do I request my data?
Send a request to the address on /contact/ with your name and the email address you used to contact the desk. The desk responds within 30 days with the data the desk holds about you.
How do I delete my data?
Send a request to the address on /contact/ with your name and the email address you used to contact the desk. The desk deletes the data within 30 days of receiving the request.
Does the desk share my email address with third parties?
No. The desk uses the email address only to respond to your message. The desk does not add the email address to any marketing list and does not share it with third parties.
Does the desk use cookies for tracking?
No. The desk uses cookies only for the purpose of serving the site. The desk does not use cookies for advertising, retargeting or third-party tracking.
What happens to my data after the desk responds?
The desk deletes the message within 30 days of sending the response. The desk retains the response for internal editorial tracking; the retention window is 12 months.
Can the desk provide my data to a law-enforcement authority?
Yes, when required by valid legal process. The desk treats law-enforcement requests as a serious matter and reviews each request against the desk's legal obligations. The desk publishes a transparency report of law-enforcement requests at the end of each year.
How the desk handles data subject access requests
The desk processes data subject access requests within 30 days of receiving a valid request. The desk verifies the requester's identity before disclosing data; the desk uses the email address on file to verify the request. The desk does not disclose data to anyone other than the verified requester.
The desk does not charge for data subject access requests. The desk does not refuse a request without a legal basis. Adult readers who believe their request has been refused without a legal basis can escalate to the relevant data-protection authority.
How the desk handles data portability requests
The desk provides the data it holds about a reader in a machine-readable format (CSV or JSON) within 30 days of receiving a valid data portability request. The desk includes all data the desk holds about the reader, including the contact-channel correspondence and the RSS subscription count if the reader is identifiable.
The desk does not include data the desk does not hold. The desk is a single-desk publication with limited data; the data portability response typically contains the contact-channel correspondence and a brief metadata record.
How the desk handles breach notifications
The desk notifies affected readers within 72 hours of becoming aware of a personal data breach that is likely to result in a risk to the reader's rights. The notification includes a description of the breach, the categories of data affected, the likely consequences, and the measures the desk has taken or proposes to take.
The desk has not had a personal data breach as of Issue 01 (August 2026). The desk publishes a transparency report of personal data breaches at the end of each year if any have occurred.
How the desk handles children's data
The desk does not knowingly collect data from minors. If a parent or guardian believes a minor has submitted data to the desk through the contact channel, the parent or guardian can contact the desk at the address on /contact/ to request deletion. The desk deletes the data within 30 days of receiving a valid request.
How the desk handles automated decision-making
The desk does not use automated decision-making for any purpose that affects the reader. The desk does not profile readers; the desk does not make automated decisions about reader messages; the desk does not use machine learning to filter or categorise reader messages. All reader messages are reviewed by a human member of the editorial team.