DESK
What the desk collects, why and for how long
iplfantasyteam.com is an editorial site. The desk collects the minimum data needed to publish the site, to respond to reader messages and to keep the desk's pages reachable. The desk does not collect identity documents, payment information or contest entries because the desk does not run a fantasy platform. The privacy notice below describes the data the desk actually collects, the data the desk declines to collect, and the choices a reader has about the data the desk holds.
The notice is written in plain language. Where the desk uses a technical term (such as "server log" or "first-party cookie") the term is explained where it first appears. A reader who is not a privacy specialist is the reader this notice is written for; the desk would rather the notice be readable than impressive.
Data the desk collects automatically
Like most websites, the desk's server records each request in a log. The log includes the URL requested, the date and time of the request, the response status, the size of the response and the IP address of the requester. The desk uses the log to detect abuse, to diagnose outages and to understand which pages are being read. The desk does not sell or rent the log; the desk retains the log for a defined period and then deletes it.
The desk's pages also use a small set of first-party cookies and local storage entries. The cookies are used to remember a reader's preferences (such as a dismissed banner) and to support the menu and theme behaviour on the page. The cookies are first-party — set by the desk's own domain — and are not used to track the reader across other sites. A reader who clears cookies will not lose access to desk pages.
Data the desk collects when a reader sends a message
When a reader sends a correction, a source note or a methodology question through the contact page, the desk receives the reader's name (where provided), the reader's email address and the message itself. The desk uses the message to respond; the desk does not use the message for marketing, does not add the reader's email to a newsletter list and does not sell the message to a third party. The desk retains the message for a defined period and then deletes it.
Where a reader asks the desk to keep the message confidential, the desk keeps it confidential. Where the desk publishes a correction that originated in a message, the desk credits the reader only where the reader has asked to be credited. The desk's standing position is that a correction message is a private communication; the desk's editorial copy is the only thing the desk publishes.
Data the desk does not collect
The desk does not collect identity documents, payment information, contest entries, wallet balances, withdrawal details or KYC records. The desk does not collect passwords, OTPs or any other credential the reader uses on a fantasy platform. The desk's contact form is designed to refuse attachments the desk does not want to hold; the desk does not store identity documents even when they are offered.
The desk also does not collect precise location data. The desk's server log includes an IP address, which is a coarse network identifier, not a precise location. The desk does not ask for the reader's address, postal code or GPS coordinates. A reader who wants to share location context in a message is welcome to do so; the desk will treat the location context as part of the message and will delete it when the message is deleted.
Why the desk collects what it collects
The desk collects the log data to keep the site running and to detect abuse. The desk collects the message data to respond to reader messages. The desk collects the cookie data to remember reader preferences. The desk does not collect any data for advertising, profiling or commercial targeting. Where a future feature seems to need additional data, the desk will publish an updated privacy notice before the feature goes live; the desk will not silently extend the data it collects.
The "why" matters because it limits what the desk can do with the data. A log entry that the desk holds for abuse detection cannot be used to build a marketing profile; a correction message that the desk holds for response cannot be sold to a third party. The desk's commitments follow from the stated purpose. A reader who reads the "why" can hold the desk to the commitments without needing a legal opinion.
| Data | Purpose | Retention and use |
|---|---|---|
| Server log | Detect abuse, diagnose outages, understand which pages are read. | Retained for a defined period and then deleted. Not sold or rented. |
| First-party cookies | Remember reader preferences; support menu and theme behaviour. | Cleared by the reader at any time. Not used to track across other sites. |
| Contact-page message | Respond to corrections, source notes and methodology questions. | Kept confidential; credited only on request. Not added to marketing lists. |
| Newsletter signup (where offered) | Send desk updates the reader has asked for. | The reader can unsubscribe at any time using the link in any email. |
| Identity documents | Not collected. | The desk declines to accept identity documents even when offered. |
Cookies and the desk's own pages
The desk's pages use a small set of first-party cookies and local storage entries. The cookies are not advertising cookies; they are functional cookies that remember reader preferences and support the menu, the theme and any dismissed banner on the page. The cookies do not follow the reader across other sites. A reader who clears cookies will not lose access to desk pages; the cookies are a convenience, not a gate.
Where the desk embeds a third-party asset (such as a font file from a font provider), the third party may set its own cookies. The desk's pages are designed to use first-party assets where possible; where a third-party asset is used, the desk tries to use a provider that respects reader privacy. A reader who wants to know more about a specific third party's cookies can read that third party's own privacy notice.
How long the desk keeps data
Server logs are retained for a defined period — typically a few months — and then deleted. Contact-page messages are retained for as long as the desk needs them to respond and for a reasonable period after that for reference; once the reference period ends, the messages are deleted. Cookies are cleared when the reader clears them or when the cookies expire. The desk's retention choices are described in plain language here; the desk does not keep data longer than the period described.
Where the desk is asked to delete a specific piece of data sooner than the period described, the desk usually complies. The request is best sent through the contact page; the desk responds within the response time described on the contact page. The desk's commitment is that the data is held for the purpose described and for no longer; a request to delete is consistent with that commitment.
Sharing data with third parties
The desk does not sell reader data. The desk does not rent reader data. The desk does not share reader messages with third parties except where the reader has asked the desk to share them or where the desk is required by law. The desk's hosting provider has access to the data the desk stores, but the provider is bound by a data-processing agreement and does not use the data for its own purposes.
Where a reader follows a link from a desk page to a third-party site, the third party may collect the reader's data under its own privacy notice. The desk is not responsible for the third party's data practices. The desk tries to link only to pages that are themselves appropriate for an editorial reader; the desk does not link to pages the desk would not be comfortable recommending.
Reader rights and how to use them
A reader who wants to ask about the data the desk holds can use the contact page. The desk responds within the response time described on the contact page. The desk can confirm whether it holds data about the reader, can describe the data and can delete the data on request. The desk's commitments in this notice are the desk's commitments regardless of where the reader is based; the desk applies the same standards to every reader.
A reader who has a complaint about how the desk handles data can also escalate to the relevant data-protection authority. In India, the relevant authority depends on the nature of the complaint; the desk's contact page can help a reader find the right authority where the desk can do so. The desk treats every reader equally and treats every complaint as an opportunity to improve the desk's practice.
Reader questions
Does the desk collect identity documents?
Does the desk use advertising cookies?
How long are server logs retained?
Can I ask the desk to delete my message?
Does the desk sell reader data?
Where can I read the desk's hosting-provider policy?
Continue with care
Read the privacy notice together with the disclaimer and the terms. The three pages describe what the desk holds, what the desk publishes and what the desk does not represent; the three pages together are the reader's reference for using the desk.