The desk reads every message. Use this page to send a correction, a source submission or general feedback. For account-level or money-related issues, use the operator’s verified customer-care route instead.
What to send
Page URL
The URL of the page you are writing about.
Issue or suggestion
A short paragraph with dates, facts and the change you are proposing.
Source
Where applicable, a public source for the change.
Your name & contact
Optional. Anonymous submissions are read but harder to verify.
Response time
Verified corrections are published in the open correction log within 7 days. General feedback is read but not always replied to. Money-related or account-level issues must go to the operator’s verified customer-care route; the desk cannot resolve them.
What the desk cannot help with
Account recovery
For account recovery, password resets or withdrawal issues, contact the operator’s verified customer-care route (see Customer Care).
Bonus disputes
For bonus disputes, contact the operator first; the desk does not mediate individual account issues.
Predictions for specific matches
The desk publishes the frame, not predictions for specific matches. A prediction for a specific match is your decision, not the desk’s.
What helps the desk the most
A correction with a public source is the single most useful message we receive. A short paragraph with the page URL, the paragraph you are correcting, and the source you are citing lets us verify and publish within 7 days. Anonymous tips are read but harder to act on without a source.
The response window
Verified corrections are published in the open correction log within 7 days. General feedback is read but not always replied to. Money-related or account-level issues must go to the operator’s verified customer-care route; the desk cannot resolve them.
How we prioritise messages
The desk prioritises in this order: (1) verified corrections with a public source, (2) questions that affect the standing research on the site, (3) general feedback. Anonymous tips are read but harder to act on without a public source.
How we triage messages
Every message the desk receives is triaged within 48 hours. Verified corrections with a public source go straight to the editing queue. General feedback is logged for the next editorial pass on the relevant page. Account-level or money-related issues are redirected to the operator’s verified customer-care route; the desk cannot resolve them and will not pretend otherwise.
Where the desk publishes
All desk publications live on this site. We do not have a Telegram channel, a Twitter account, a Substack, a podcast or a YouTube channel. If you find an account claiming to be the desk on a platform we do not publish on, it is not us; please report it via the contact form so we can record it in the editorial standards.
Response time, made public
The desk commits to publishing verified corrections in the open correction log within 7 days. General feedback is read within 48 hours but is not always replied to. Money-related or account-level issues are redirected to the operator’s verified customer-care route; the desk cannot resolve them and will not pretend otherwise.
If the desk has not responded to a verified correction within 7 days, that is a breach of the editorial standard; please flag it. If the desk has not read a general feedback message within 48 hours, that is a queue issue; please flag it.
Submit a tip
The desk accepts tips from readers. A tip is a short message pointing us to a public source we have not yet used. Useful tips: a new operator page with updated KYC rules, a state-government publication on fantasy-cricket regulation, a broadcaster match note we should be citing, an operator’s own correction of a previous public statement. Anonymous tips are read but harder to act on without a public source.
Submit a source
If you have a public source that supports a claim we have not yet cited, send it via the contact form. Include the URL, the date of the publication, and the specific claim you are citing. Verified sources are added to the relevant guide with attribution. The desk does not pay for sources, but we cite them when we use them.
Press and partnerships
The desk does not currently accept paid partnerships, sponsored content or guest posts. Press inquiries are read but not always replied to. If you would like to discuss a citation or a translation of a guide, contact the desk; we usually reply within 7 days.
If the desk does not reply, what does that mean
If the desk does not reply within 7 days to a verified correction, that is a breach of the editorial standard. The desk commits to publishing verified corrections in the open correction log within 7 days; a missing correction is logged in the next editorial pass. If the desk does not reply within 48 hours to general feedback, the message is in the queue and will be read within the next editorial pass.
Languages the desk can read
The desk reads English fluently. Hindi and Tamil messages are read with the help of translation tools; reply quality is best-effort. Marathi, Bengali, Telugu, Kannada and Malayalam messages are accepted and translated for editorial purposes but replies may be in English.
A direct line to the editor
For sensitive editorial issues (a suspected error in a published guide, a question about the editorial standards, a request to anonymise a citation), the desk can be contacted directly. Use the contact form with the subject “Editorial”; the editor reads the message within 48 hours and replies within 7 days.
What the desk will not do on contact
The desk will not provide legal advice, financial advice or medical advice via the contact form. We will not mediate disputes between readers and operators; the verified customer-care route is the right channel for that. We will not accept paid content or sponsored messages; affiliate links on the site are disclosed in the footer. We will not share your contact-form messages with third parties.
A final note
Every message is read; not every message gets a reply. The desk commits to publishing verified corrections in the open correction log within 7 days. For everything else, the message is logged and read in the next editorial pass. If your message is urgent (a security issue, a published error, an operator misrepresentation), flag it in the subject line and the desk prioritises it.
Questions readers ask
Do you reply to every message?
We read every message and reply to verified corrections. General feedback is read but not always replied to.
Can I send an anonymous tip?
Yes — anonymous tips are read but harder to verify and may not be acted on without a public source.
How do I escalate a money issue?
First, contact the operator’s verified customer-care route. If still unresolved, the National Consumer Helpline (1915) and the INGRAM portal are the relevant channels.
Response windows the desk can and cannot commit to
The desk does not commit to a 24-hour, 48-hour or 7-day response window. The honest answer is that the desk reads every contact message, that the desk replies to every verified correction within 7 days, that the desk does not always reply to feedback messages, and that the desk does not run a live-chat or 24/7 support route. The contact page is a one-way inbox the desk reads on business days; the desk does not staff an out-of-hours queue.
If the contact is a security report (a phishing page that impersonates the desk, a leaked credential, a data-handling concern), the desk escalates within one business day, but the desk does not commit to a fixed investigation SLA. The Customer Care page carries the operator’s verified escalation routes for account-level concerns; the desk does not handle account-level concerns on the reader’s behalf.
Reader follow-up
The contact inbox is also the desk’s only reader-facing channel. The desk does not run a live-chat, a phone line, a Telegram channel or a WhatsApp number. The contact page is a one-way inbox the desk reads on business days. If a reader needs an account-level escalation, the verified customer-care route on the Customer Care page is the right escalation; the desk does not handle account-level concerns on a reader’s behalf. If a reader needs a security report, the contact page is the right route; security reports are escalated within one business day.
Does the desk run live chat?
No. The contact page is a one-way inbox the desk reads on business days.
Will the desk reply to feedback?
The desk reads every contact message. The desk replies to verified corrections within 7 days; the desk does not always reply to feedback messages.
How do I send a security report?
Use the contact page. Security reports are escalated within one business day, but no fixed investigation SLA is committed.
Can the desk act as an intermediary with the operator?
No. The desk does not contact the operator on a reader’s behalf and does not have reader-account access. The operator’s customer-care route is the right escalation.
Open the editorial app entry
Verify the current offer in your own account, then play only what you can afford to lose.