For corrections
- URL of the affected piece.
- The exact sentence or number that needs review.
- A link or copy of the source that supports the correction.
- Whether you would like a footnote or a quiet edit.
Email is the fastest way to write in. Notes received on the editorial inbox are read and triaged by topic; the notes that follow explain what to include, who reviews each kind of message, and which types receive a written reply.

Reading notes sit on the inbox until the desk has time to respond properly. Editorial replies are typed, by a person, with the original message in front of them — short notes go back fast, longer notes take longer.
The inbox itself accepts everything; the practical question is which messages reach a written reply and which stay informational. The patterns here cover what typically arrives and what the desk does with it.
Notes received on [email protected] are triaged by topic. Using a subject line that names the topic (for example "Correction request — match analysis") helps the right reply land.
Notes are read on the editorial inbox. Replies go out where a reply adds information; automated acknowledgement messages and fixed reply windows are not used because they tend to create more confusion than they save.
The editorial inbox does not reply to anonymous notes, pitches for paid link placement, betting-operator affiliate enquiries, or pitches about specific match outcomes. The reasoning sits in the commercial-disclosure note.
The more specific the note, the more useful the reply. The cards below cover the kind of note readers send most often.
Email is the primary channel. For very formal correspondence, the same inbox is also the right address.
Legal notices, takedown requests, and formal partnership letters go to the same editorial inbox ([email protected]). Mark the subject line with "Formal" so the request can be prioritised.
Requests for a copy of stored data, correction, or deletion are handled through the editorial inbox. Each request is acknowledged in writing within a reasonable window; turnaround depends on the kind of request. The full data picture sits in the privacy notice.
Notes received on the editorial inbox include notes that should not have been sent. A short written rule covers what happens when a note crosses a line.
Notes that contain personal attacks, threats, discriminatory language, or that target the publication with the intent of forcing an editorial change. Each note is read on its own terms; the list above is a guide rather than an algorithm.
The note is acknowledged in writing, the issue is named, and a path forward is offered where one is available. Where the note is part of a repeated pattern from the same sender, the pattern is recorded and the reply covers only the substantive content; the abusive framing is not engaged.
Replies stop to a sender when the pattern is repeated after a written notice, when the sender refuses to engage substantively, or when continuing the exchange would consume bandwidth needed for the writing itself. The decision is logged against the sender's address and revisited if the sender returns after a longer gap.