Corrections
If you spot a fact that needs correcting — a player profile, a venue number, a captain pivot note, a squad update — write to the editorial corrections inbox. Include the URL of the published note and the source for the correction. We publish a corrections entry within 7 days of receipt and credit you by name unless you ask to remain anonymous.
Sourcing and primary records
If you have a primary record we should publish — a franchise handle update, a partner operator rule change, a venue file update — share the URL and timestamp. We verify the record, name you in the public byline where appropriate, and publish.
Partnership queries
For partnership queries — content collaboration, brand-safe affiliate, data licensing — write to the desk. We do not engage in paid-tipping collaborations, in advertorial captain-pick deals, or in any partnership that compromises the editorial independence of the desk.
Editorial feedback
Editorial feedback (what works, what doesn’t, what’s missing) is welcomed at any time. We publish a quarterly “desk note” summarising the recurring feedback themes and our response.
What we do with each contact channel
Editorial corrections route to the verification reviewer; the desk publishes a corrections entry within 7 days. Sourcing records route to the cricket writer and the verification reviewer; the desk publishes the record on the relevant page with a visible date. Partnership queries route to the editor-in-chief; the desk responds within 14 days. Editorial feedback routes to the editorial desk.
What the desk will not respond to
Requests to publish guaranteed win rates. Requests to publish “best of” leaderboards or promotion lists framed as tips. Requests to delete a published item that is factually correct but inconvenient for a partner operator. Requests to publish partnership deals that compromise editorial independence.
Privacy on the contact channel
Do not send partner-operator login credentials or KYC documents over the contact channel. The desk does not need them to verify or correct an editorial item. The partner operator is the right destination for any issue that requires account-level access.
What counts as an editorial correction
Any factual change to a published item: a player name, a venue file number, a captain pivot verdict, a squad update, a partner operator rule change. Corrections are publicly listed inside /news/. Items that the desk disagrees with on framing — not fact — are addressed in the editorial quarterly note, not as corrections.
What counts as a source record
A source record is a named, dated, public document. The desk accepts source records from franchise handles, partner operator official channels, regulatory filings, public scorecards, and established publications. The desk does not accept anonymous sources; we do not publish from unnamed contributors; we do not publish from reposts or screenshots without verifying the original record.
The feedback rhythm
The desk responds to feedback through three channels: corrections (with verification reviewer), the quarterly desk note (collective themes), and editorial standards updates (procedural changes). The desk does not respond to feedback through private DMs or social handles.
Writing a good sourcing note
Include the URL or citation. Include the timestamp of the record (publication date, last modified date, or even the time of day for live records). Include a short description of what the record claims. The desk verifies the record before publication.
Writing the best possible message
Brief subject line. Clear identification of the published item (URL or item title). Specific claim for correction with source. Verification reviewer name where relevant. The desk responds within 7 days for editorial corrections, 14 days for partnership queries.
What the desk will not do with the contact channel
Sell or trade contact information. Forward user messages to partner operators without consent. Use the contact channel to recommend tipping products or financial opportunities. Publish user PII in any response.
The desk’s response policy
Editorial corrections: within seven days of receipt. Sourcing records: within seven days of receipt. Partnership queries: within fourteen days. Editorial feedback: addressed in the next quarterly desk note. The desk never responds through private DMs or social handles.
The desk’s channel list
Editorial corrections → /contact/ form. Sourcing records → same form. Partnership queries → same form, with “partnership” in the subject. Editorial feedback → same form, with “feedback” in the subject. The desk responds within 7 days for editorial corrections, 14 days for partnership queries, and addresses feedback in the quarterly desk note.
What the desk will respond to
Factual errors in published items. Source records the desk may have missed. Editorial feedback that improves the desk’s reading. Partnership queries that respect the editorial independence of the desk.
The correspondence cycle
Receipt (logged with a date) → review → acknowledgement within 7 days → resolution or correction (if applicable) → closure. The desk maintains a correspondence archive of editorial corrections received.
Writing the message
Brief subject. Clear identification of the published item (URL or item title). Specific claim for correction with source. Verification reviewer name where relevant. The desk never responds through private DMs or social handles.
The desk’s three correspondence thresholds
First threshold — editorial corrections. The desk responds within seven days. The response carries a verification date and a corrections pathway. Second threshold — sourcing records. The desk responds within seven days. The response carries a verification reviewer name. Third threshold — partnership queries. The desk responds within fourteen days. Each threshold respects the editorial independence of the desk.
The correspondence archive
The desk maintains a correspondence archive of editorial corrections received, verification reviewer assignments, and corrections pathway dates. The archive is read-only and is available to any reader who requests it through the contact pathway. The archive is part of the desk’s quality signal.
Private versus public correspondence
The desk does not respond to editorial corrections through private DMs or social handles. The contact pathway is the only editorial channel. The desk publishes public corrections inside the news feed; private replies are reserved for sensitive corrections where the reader has asked to remain anonymous.
Closing the loop on a correction
The desk closes a corrections loop with a public note inside /news/. The note carries the original item, the corrected item, the source for the correction, and the verification reviewer. The reader who submitted the correction is credited by name unless they ask to remain anonymous.
The desk’s three take policies
The desk takes all reader messages seriously. The desk reads each contact-channel message within seven days of receipt. The desk responds to editorial corrections, sourcing records, partnership queries, and editorial feedback. The desk does not respond to commercial pitches unrelated to the editorial desk.
Contact versus social handles
The desk uses the contact form as its primary editorial channel. The desk does not respond to corrections through social handles. The desk uses social handles for service announcements only — outage notices, scheduled maintenance windows, and corrections of public-facing errors.
What the desk publishes on correspondence
The desk publishes a public corrections note inside /news/. The desk credits the source by name unless requested otherwise. The desk maintains a correspondence archive of editorial corrections received, verification reviewer assignments, and corrections pathway dates.
Closing thoughts on contact
The contact channel is the editorial correction pathway. It is the sourcing pathway. It is the partnership pathway. It is the feedback pathway. The desk does not run support or financial channels; the partner operator is the source of truth for support and financial questions.
