How satsport handles reader data.

1. What this site collects

satsportin.com does not require an account, an email address or any personal detail to read its pages. The site does not run its own analytics, advertising network or affiliate tracking pixel. Server access logs are kept for a rolling thirty days for operational diagnostics only and are not linked to a reader profile.

The access logs record the URL requested, the HTTP status returned, the response size and a coarse user-agent string. The logs do not record a reader's IP address beyond what is needed for the request to complete. The logs are not shared with marketing partners, with analytics vendors or with any third party outside the hosting stack.

2. What this site does not collect

The site does not ask for your name, phone number, date of birth or government ID. The site does not place advertising cookies, remarketing tags or social-network pixels. The site does not sell or rent reader data because no reader data is held in the first place.

The site does not use fingerprinting techniques to identify a reader across visits. The site does not use device-graph identifiers, browser-feature hashing or any other technique that creates a stable identifier without the reader's explicit consent. The site does not load any third-party font, video, map or comment service that would generate a third-party cookie or pixel.

3. Third-party scripts

This site loads its own CSS and JavaScript only. The single outbound navigation link present on each page (a sponsored operator portal) is a normal anchor; clicking it takes you to a domain outside satsportin.com whose own privacy practice will then apply. Read that practice before creating an account or sharing documents there.

The site's own JavaScript handles the mobile menu toggle, the date on the update note and a small accessibility helper for the hamburger button. None of those scripts transmit data off the page. The scripts run entirely on the reader's device and make no network requests once the page has loaded.

4. Email and corrections

When you write to the editorial desk, the desk holds the message and any attached document only for as long as is needed to investigate the reported item. Contact messages are not added to a marketing list and are not shared with third parties. If you ask for your message to be deleted, the desk removes it within fifteen working days and confirms the deletion by reply.

The desk's mail host is operated by a third-party mail provider under a data-processing agreement that restricts use to delivering mail to and from the desk. The mail provider does not profile the desk's correspondents, does not build advertising segments from the desk's mail and does not share the desk's mail with other customers. The mail provider's own privacy terms apply to the underlying service; the desk has selected a provider whose commercial model does not depend on mining mail content.

5. Children and vulnerable readers

The site is written for adult readers who are legally able to make their own decisions about skill games. The desk does not knowingly publish content aimed at minors and removes any comment or submission that appears to come from a minor or from a reader in a vulnerable situation.

The site does not require age verification at the door because the site does not collect personal data at all. Where a reader is in a jurisdiction that requires age verification for editorial content about games, the desk points to the relevant jurisdiction's rules on the terms page and asks the reader to apply those rules themselves. The desk does not design its editorial framing to circumvent any reader's local protection.

6. Your rights under Indian law

Indian readers can write to the editorial desk to ask what information is held about them, to request a correction, or to ask for the message record to be deleted. The Information Technology Act 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011 and the Digital Personal Data Protection Act 2023 frame those rights; the desk honours them regardless of jurisdiction.

The desk treats access requests, correction requests and deletion requests the same way: each is read, verified against the desk's records, and answered within fifteen working days. Where the request cannot be honoured in full, the desk replies with the desk's reasoning and offers the closest available equivalent (for example, an updated article rather than the deletion of an archived page that other readers still reference).

7. Security

The site is served over HTTPS. The desk reviews hosting and access controls on a regular schedule. Where a security incident affects reader data, the desk notifies affected readers at the address they used to reach the desk and, where required, the relevant CERT-In reporting channel.

The desk's mail account is protected by two-factor authentication. The desk's hosting account is protected by two-factor authentication and IP-restricted administrative access. The desk does not store reader data outside the mail account and the hosting stack; there is no separate customer database because there are no customers in the commercial sense.

8. Updates to this page

This page is updated when the data practice changes. The latest version is dated at the foot of this article; older snapshots are kept on request. Where the change is material (for example, the introduction of a new third-party script), the desk summarises the change in the next news briefing so that returning readers are not surprised.

9. Cookies and similar storage

This site does not set cookies for analytics, advertising or behavioural profiling. The site's own JavaScript does not write to localStorage, sessionStorage or IndexedDB. The hosting layer may set a small number of strictly necessary cookies (for example, a load-balancer affinity cookie) that are required for the request to complete; those cookies expire when the reader closes the browser and are not used to identify the reader across visits.

Where a future change requires the desk to set a non-essential cookie, the desk will add a cookie banner to the site and update this page with the categories of cookie in use, the purpose of each category and the duration of each cookie. The desk will not set a non-essential cookie without giving readers a clear way to refuse it.

10. International readers

The site's hosting stack serves traffic from edge nodes in multiple regions. The desk does not control which edge node serves a particular request; that is decided by the content delivery network based on routing efficiency rather than on a reader profile. The desk's mail account is hosted in India; messages from international readers reach the desk through the standard internet mail path.

Where a reader's local law gives them stronger rights than the rights listed above (for example, the right to data portability under the European Union's General Data Protection Regulation or the right to opt out of sale under the California Consumer Privacy Act), the desk honours those rights even though the desk does not technically engage in the practices those rights are designed to address.

11. How long the desk holds data

Server access logs are kept for a rolling thirty days and are then overwritten. The desk does not back up access logs. Contact messages are kept for as long as is needed to investigate the reported item; once the investigation is complete and any resulting update has been published, the desk deletes the message unless the writer asks for it to be retained.

Where a contact message leads to a published correction, the desk retains the message until the next major review of the affected article. After that review, the desk deletes the message unless retention is required for accounting, legal or audit reasons; the desk would rather under-retain than over-retain.

12. Changes to hosting and infrastructure

The desk may move hosting providers or change the content delivery network as the site evolves. Where a move changes the practical data-handling on the site (for example, where logs start flowing through a new region), the desk updates this page before the change takes effect. Readers who want advance notice of a hosting change can subscribe to the news briefing, where material infrastructure changes are summarised.

The desk does not treat a hosting move as a reason to begin new data collection. The desk's collection practice is described in plain language above and is the same regardless of which provider operates the underlying servers. A move that would require a change in practice is treated as a policy change, not as an operational detail.

13. Reading this page over time

This page is intended to be readable as a single document on first read. Readers who return after a long gap should still find the desk's practice clearly stated. Where a reader wants to compare two versions, the desk keeps an archived copy of any prior version of this page and will send it on request through the contact route. The current version's date is shown at the foot of this article; readers who need to evidence a specific past version can write to the desk.