Contact

Five ways to reach the editorial desk, and what the desk replies to

The headshot desk reads every inbound. This page documents the five reasons a reader writes in, the public email alias for each, and what the desk does if an inbound falls outside the desk's scope. The desk does not run a phone line, does not run a chat, and does not sell a service.

Read customer care Open the desk

Inbox aliases

Five public aliases, five kinds of inquiry

Alias	Use for	What the desk does
[email protected]	Desk inquiry	Reply with the relevant surface, within a working day
[email protected]	Brief correction	Verify on a canonical source, publish a stand-alone correction
[email protected]	Security report	Route to the security contact, publish a public note on the newsroom
[email protected]	Organizer, team or reporter partnership	Read in the order they arrive, reply when there is a fit
[email protected]	Press inquiry	Reply with the same editorial standard, with a verification trail if requested

The aliases are listed for the reader's reference. The desk does not promise an instant reply. The desk promises a reply.

Out of scope

What the desk does not reply to

Wallet inquiries

The desk does not host a wallet. The desk does not reply to wallet inquiries and asks readers to contact the relevant operator directly.

KYC and payout

The desk does not run KYC. The desk does not process payouts. The desk asks readers to contact the relevant operator directly.

Individual counseling

The desk does not provide individual counseling on play behaviour. The public support channels are listed on the responsible play page.

Response window

How fast the desk replies

The desk aims to reply to desk inquiries within one working day. Correction inquiries and security reports are replied to within one working day as well. Partnership inquiries are read in the order they arrive and are replied to when there is a fit. Press inquiries are replied to with the same editorial standard as any other reader.

The desk does not promise an instant reply. The desk does not run a 24/7 support line. The desk is a small editorial newsroom, and the reply window reflects the size of the team. The desk asks readers to be patient and to use the public aliases above for any time-sensitive inquiry.

Press

How a press inquiry is handled

The desk reads press inquiries in the order they arrive. The desk replies with the same editorial standard as to any other reader, with a verification trail if requested. The desk does not offer exclusives, does not offer embargoed access, and does not offer a paid placement. The desk's editorial role is to publish reads, not to sell access.

For press inquiries that ask for a comment on a specific brief, the desk's standard practice is to point the press to the brief itself, the canonical source, and the desk's editorial standard. The desk does not authorise a quote that is not on the record. The desk does not authorise a paraphrase that changes the meaning of a published brief.

For press inquiries that ask for a desk background conversation, the desk's standard practice is to reply with a written summary of the conversation. The summary is published on the desk's notes if the press inquiry results in a published article. The summary is the desk's editorial record of the conversation, and the desk does not alter the record after the fact.

Partnership

How a partnership note is read

The desk reads partnership notes from organizers, teams, and credible reporters in the order they arrive. The desk's standard practice is to reply when there is a fit. The desk does not accept partnership notes from third-party surfaces, from affiliate networks, or from operators that hide the canonical source. The desk's editorial role is to publish reads; the partnership must respect the editorial role.

For partnership notes that ask for cross-promotion, the desk's standard practice is to decline. The desk does not cross-promote a third-party surface. The desk does not embed a third-party widget on a desk. The desk does not run a sponsored section. The desk's editorial surface is the central URL, and the surface is not for sale.

Response time

What the desk's response time looks like in practice

The desk's published response time is one working day for desk inquiries, one working day for corrections, and one working day for security reports. The desk's actual response time is typically four hours for desk inquiries, two hours for corrections, and one hour for security reports. The desk publishes the published response time so that the reader knows the worst case; the desk tracks the actual response time so that the standards contact can hold the desk to the standard.

For partnership inquiries, the desk's response time is two working days. The partnership inquiries are read in the order they arrive, and the desk replies when there is a fit. The desk's standard practice is to publish a partnership note on the contact page so that the reader knows the response time before sending the inbound.

For press inquiries, the desk's response time is four working hours. The press inquiries are read in the order they arrive, and the desk replies with the verification trail if requested. The desk's standard practice is to publish a press note on the contact page so that the reader knows the response time before sending the inbound.

What the desk reads

Five specific kinds of inbounds the desk treats as a priority

The first priority inbound is a security report that identifies a credible phishing surface. The desk's standard practice is to reply within one hour and to publish a public note on the newsroom within the same day. The desk treats the public note as a stand-alone correction that respects the reader who reported the issue.

The second priority inbound is a correction that identifies a real error in a published brief. The desk's standard practice is to verify the correction against a canonical source, to reply within one hour, and to publish a stand-alone correction within the same day. The desk treats the correction as a fix and the brief as a public record.

The third priority inbound is a desk inquiry from a reader who is at risk of a play-related harm. The desk's standard practice is to reply within one hour and to surface the public support channels listed on the responsible play page. The desk's role is to surface the channels; the reader's role is to use the channels.

The fourth priority inbound is a desk inquiry from a reader who has identified a third-party surface that violates the editorial standard. The desk's standard practice is to reply within one hour and to publish a public note on the newsroom within the same day. The desk treats the public note as a stand-alone correction that respects the reader who reported the issue.

The fifth priority inbound is a desk inquiry from a reader who has identified a jurisdictional concern. The desk's standard practice is to reply within four hours and to surface the jurisdictional directory on the is-legal page. The desk's role is to surface the directory; the reader's role is to verify the local rule.

What the desk does not do

Five things the desk explicitly does not do, in the contact surface

The desk does not provide individual counseling on play behaviour. The desk's editorial role is to surface the public support channels listed on the responsible play page. The desk does not provide a private counseling service, does not endorse a private counselor, and does not sell a service.

The desk does not process wallet, KYC, or payout. The desk does not host a wallet, does not run KYC, and does not process payouts. The desk asks the reader to contact the relevant operator directly for any wallet, KYC, or payout inquiry.

The desk does not authorise a quote that is not on the record. The desk does not authorise a paraphrase that changes the meaning of a published brief. The desk does not offer exclusives, embargoes, or paid placements. The desk's editorial surface is the central URL, and the surface is not for sale.

The desk does not reply to anonymous tips that cannot be verified against a canonical source. The desk's standard practice is to verify every inbound against a canonical source before publishing a correction. An anonymous tip that cannot be verified is held to the standard; the desk does not publish the tip as a brief.

The desk does not reply to inbounds that are not in the contact page's published languages. The desk's standard practice is to publish in English only. Inbounds in other languages are routed to the partner desks in the relevant language; the desk's role is to surface the partner desks, not to translate the inbounds.