Home · Privacy
Privacy desk

Privacy — what we collect, what we don't

A short privacy policy: what data we collect, what we don't, how to clear cookies, and how to reach the editor with privacy inquiries.

A magnifying glass over a privacy policy document.
Data we collect

Anonymous, aggregate page-view data only

We collect three things: the page URL you visit, the country you visit from (geolocated from your IP), and an aggregated timestamp (no per-minute resolution). That's it. We do not record your IP address beyond what your browser sends. We do not set third-party cookies. We do not load tracking pixels from social-media platforms or analytics vendors.

Cookies

First-party analytics, clearable at any time

First-party cookies

We use first-party analytics cookies that are non-personalised. The cookies are set with SameSite=Strict and are scoped to the iplfantasypicks.com domain only. Clearing them from your browser removes any link between visits.

No third-party cookies

We do not load advertising-network scripts, social-media tracking pixels, or third-party analytics scripts. The page only loads its own first-party assets and Google Fonts for typography.

Browser controls

Your browser controls everything. Clear cookies from your browser settings, use private / incognito mode, or use a tracker-blocking browser. All three work the same way for our analytics.

Data retention

We retain analytics data for 26 months as required by some jurisdictions. After the retention window the data is deleted from our analytics provider. The retention is logged in the privacy policy.

Editorial questions

Editorial questions about privacy

If you have a privacy question — about a specific data point, about cookies, about a third-party script that you noticed, about a request to delete your data — send it to the editorial contact channel on the Contact page. We answer within 48 hours during business days.

Frequently asked

Questions our readers ask

Anonymous, aggregate page-view data only — typically the URL, the country of origin, and an aggregated timestamp. We do not collect personal identifiers.

We use first-party analytics cookies that are non-personalised. Clear them from your browser at any time and our analytics will no longer link your visits to a session.

No. We don't sell reading data; we don't share it with third parties; we don't run affiliate schemes. The privacy policy is short because we collect very little.

Reading support

How this page relates to the rest of the desk

The desk's coverage is interconnected

Every page on this site connects to the editorial graph — captain matrices link to predictions, predictions link to fantasy tips, fantasy tips link to player profiles, player profiles link to team desks, team desks link to venue reads. Reading the desk's coverage weekly keeps your calibration of the framework current.

This page is one node in the graph. When the inputs on this page change, the related coverage is updated. The change log is published in the editor's monthly note; readers can see the run of changes across the desk.

What to read next

From this page, the most useful next reads are: (1) the predictions hub for today's captain matrix; (2) the fantasy-tips hub for the decision framework; (3) the team desks for the squad-level reads; (4) the verification pages for safety guidance on third-party products.

Each of those is one click away from this page — the link is in the page footer, in the navigation bar, or in the related-coverage section of this page. Bookmark the desk-level landing pages for fast access; bookmark the article-level pages for deep reads.

Editor note

How an editor works this page

1

Inputs

The editor reads every input before the page publishes. Inputs include public sources, the desk's previous reads, and any source-tip submissions. The editor labels every input as confirmed, reported, or projected.

2

Verification

The editor runs the verification ladder on every claim. Confirmed (verified, on the record), reported (single-source, on the record), projected (analyst inference), editorial lean (weighted view across inputs).

3

Read

The editor writes the desk's read with a confidence tag (high, moderate, cautious, no call). The confidence tag is published at the top of the read; readers can size their own calls against the tag.

4

Audit

The editor signs off on the captain matrix and the audit ladder. The audit ladder feeds the desk confidence score; the score is published quarterly with its limitations named.

Limitations

What this desk cannot do

Outcome certainty

The desk cannot guarantee fantasy outcomes. Fantasy is uncertain by nature; the desk's reads are probabilities, not certainties. We label every read with a confidence tag and never use certainty language.

Source limitation

The desk is limited to public sources. We don't have access to private net sessions, undisclosed injuries, or unreleased squad information. When the inputs are not public, the read is held.

Editorial bias

The desk writes with humans and carries implicit biases. We minimise bias by anchoring to named inputs and a named verification ladder. We publish the editor's monthly note so readers can see the bias and the track record.

Time lag

A read at 09:00 IST may be obsolete by 17:00 IST. The desk updates the captain matrix as soon as the inputs change. Freshness of any single page is bounded by the freshness of the inputs it depends on.

Reading cadence

How often to read this page

A

Daily readers

If you build fantasy teams daily, this page is in your morning reading. The captain matrix updates throughout the day; reading it before locking your team is the highest-leverage single action you can take.

B

Weekly readers

If you build fantasy teams weekly, this page anchors your week. The desk publishes weekly recaps that summarise the reads from the previous seven days. The recap is the cheapest way to catch up if you missed the week.

C

Tournament readers

If you read for tournament-level context, this page is one node in the editorial graph. The desk's quarterly audit aggregates the reads across the whole season; the publication is on the desk dashboard.

D

Casual readers

If you read occasionally, this page is the entry point to the desk. Bookmark the homepage or the predictions hub; come back when there's a specific question. The desk's coverage is free to read at any time.

Editorial commitment

What this page commits to the reader

Confirmation

Every claim on this page is labelled confirmed, reported or projected. We do not publish composite statements without naming the data window; we do not publish any framing that implies certainty without verification.

Correction

If this page is wrong, the correction is published at the top with a dated note. The note explains what changed, when, and why. Corrections are not deletable.

Verification

Every input on this page is cross-checked against at least one independent source where possible. Single-source stories are tagged reported; we do not publish anonymous tips.

Editor

An editor reads this page before publication. The editor signs off on the captain matrix, the audit ladder, and the verification tags. The editor's note is published monthly.

Where to read more

Five follow-on reads from this page

Team reads

Every IPL franchise has a dedicated desk with squad-shape, role-question, captaincy and venue reads. The team desks are the deepest single resource on the desk — start there when you want to read about a specific franchise.

Player profiles

Player profiles break form into six phase windows — powerplay, middle, death, matchup, second innings and venue. The captain matrix on each profile is updated after every match and feeds the captain pool on the next fixture.

Verification

The verification pages cover app, download, login, bonus, referral, withdrawal and responsible play. They exist to help readers verify any third-party product they consider using — and to walk away from any product that does not verify.

Predictions

The predictions hub is where pre-toss frames, post-toss updates, captain matrices and post-match audits are published for every fixture. The hub is the most-read section of the desk.

Editor's note

The monthly editor's note aggregates corrections, source patterns, audit deltas and the desk confidence score for the previous month. Reading the note keeps your calibration of the desk current across the season.

Play now