fantasye is editorial. The desk does not accept wagers.
This page describes the editorial position the desk takes on viewing access, age boundaries and the boundary between editorial coverage and wagering activity. The desk's editorial role is to publish evidence-first journalism on esports tournaments, matches, teams, players, games and patch context. The desk is not a wagering service.
The desk does not publish picks, odds or wagering guidance
The desk's editorial output covers tournaments, matches, teams, players, games and patch context. The desk does not publish picks, odds, prop estimates, payout estimates or wagering guidance. The desk treats wagering-guidance content as outside its editorial scope; readers who want such content should consult a dedicated wagering-analysis publication.
The desk's commercial disclosure at /disclosure/ names the operator relationship the desk has, which is limited to the disclosed first-party route. The disclosed first-party route is an editorial comparison entry, not a wagering recommendation.
What the desk will not publish
The desk will not publish: betting-shop odds as primary content, payout-calculator outputs, wager-tracking summaries, prop-bet recommendations, or links to wagering-pitch emails. The desk will treat any of the above as outside editorial scope and decline to publish.
Where the editorial boundary sits
The editorial boundary is the line between covering esports competition (which the desk does) and helping a reader place a wager (which the desk does not). The desk sits on the cover-side of the line. The desk's published content covers who is playing, what the format is, what the patch changed and how the desk interprets the change.
The desk's editorial boundary does not change based on the operator the disclosed first-party route leads to. Whether the route leads to a free product page or a paid product page, the desk's editorial output stays on the cover-side of the line. The desk does not publish wagering guidance in exchange for the disclosed first-party route fee or any other commercial consideration.
Age and uncertainty boundaries, by region
Where regional regulation requires viewers to be of legal age, the relevant page on this site lists the age boundary and the uncertainty about cross-region access. The desk does not publish wagering content aimed at any specific region. The desk's editorial output is intended for an adult readership; the desk does not market to minors.
NA
Viewers in NA jurisdictions where wagering is regulated should review their regional regulation before following the disclosed first-party route. The desk does not publish wagering guidance for any NA jurisdiction.
EU + UK + IE
Viewers in EU jurisdictions should review their regional regulation before following the disclosed first-party route. Several EU jurisdictions require viewers to be of legal age and to use regional operators only. The desk does not publish wagering guidance for any EU jurisdiction.
APAC
Viewers in APAC jurisdictions should review their regional regulation before following the disclosed first-party route. Several APAC jurisdictions restrict or prohibit wagering on esports. The desk does not publish wagering guidance for any APAC jurisdiction.
Where to find help if your viewing or wagering activity is causing harm
If a reader believes their viewing or wagering activity is causing harm, the desk recommends contacting a regional helpline before continuing. The desk does not publish a list of regional helplines on the public site because the desk cannot verify helpline numbers across regions; readers should consult their regional public-health service for the relevant contact.
What the desk will do on a reader inquiry
If a reader emails [email protected] with a viewing-related concern, the desk will reply with one acknowledgement and one redirect to the relevant regional service. The desk does not provide crisis support or wagering-counselling services.
Compare the product route, with editorial context
Read before you click
The disclosed first-party route is a third-party product page operated by gogotofly.com. The desk does not edit or approve the operator's product page; readers should review the operator's terms before following the link.
Editorial disclosure
fantasye does not accept wagers. The disclosed first-party route is a product comparison entry only.
Reading the editorial boundary between covering and wagering
The first habit is to keep the boundary explicit. The desk's editorial boundary is the line between covering esports competition (which the desk does) and helping a reader place a wager (which the desk does not). The desk sits on the cover-side of the line. The boundary is named on /responsible-play/ and reinforced by the corrections register the desk maintains. A reader who follows the boundary for two minutes ends up able to audit the desk's editorial scope.
The second habit is to decline what the desk will not publish. The desk will not publish picks, odds, prop estimates, payout estimates or wagering guidance. The desk will not publish wagering-guidance content for any region, including regions the desk does not name. The desk treats wagering-guidance content as outside its editorial scope; readers who want such content should consult a dedicated wagering-analysis publication.
The third habit is to keep the regional-context section plain language. The desk describes the regional context in plain language, naming the regions the desk covers and the age boundaries the relevant regulation publishes. The desk does not publish a list of regional helpline numbers on the public site because the desk cannot verify helpline numbers across regions; readers should consult their regional public-health service.
Where the desk diverges from coverage that mirrors trade-press reads is on the boundary-discipline policy. Trade press will sometimes publish wagering-pitch content that does not name the source of the pitch. The desk does not. The desk names what the desk publishes and what the desk declines; the discipline is sometimes slower to operate; it is always more honest to read.
The desk also treats the editorial boundary as a working document. Rows move up the boundary-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The boundary is rebuilt from publisher and operator pages only. A row the desk kept for "tracking purposes" is a row the reader cannot verify, so the desk removes rather than retains. This is sometimes the slower choice; it is always the more honest choice.
Editorial cycle: weekday-morning source-scan, weekday-afternoon narrative-edit, weekly patch workshop. Verification timestamps on the dispatch stream.
How the desk reads this
The responsible-play page is built around three sections: editorial position, regional context and help. Each section is short by design: a reader who follows the page for five minutes can re-read the page's section language under two minutes. The page does not expand the sections into a long-form document unless a reader asks for the expansion.
Where the page covers the editorial boundary. The boundary is the line between covering esports competition (which the desk does) and helping a reader place a wager (which the desk does not). The page names the boundary and the editorial scope on either side. The page is reviewed at the end of each calendar month against the corrections register the desk maintains.
Where the page covers the regional context. The regional context is described in plain language, naming the regions the desk covers and the age boundaries the relevant regulation publishes. The desk does not publish a list of regional helpline numbers on the public site because the desk cannot verify helpline numbers across regions; readers should consult their regional public-health service.
Where the page covers the help section. The help section describes where to find help if a reader believes their viewing or wagering activity is causing harm. The desk does not provide crisis support or wagering-counselling services; the desk replies to a reader inquiry with one acknowledgement and one redirect to the relevant regional service.
What the page is not. The page is not a wagering-guidance document, not a crisis support document, not a regional helpline directory. The page is a working description of the desk's editorial boundary, regional context and help section. Where the desk publishes a wagering-guidance document, the document is on a separate page; the responsible-play page is the editorial boundary.
How the cycle reads in practice
A worked example of the editorial boundary in practice. The desk reads a Tier-1 source change and considers whether to publish the change as a dispatch line. The desk publishes the dispatch line because the change is editorial content (a tournament-stage update). The desk does not extrapolate a wagering-guidance read from the dispatch line; the editorial boundary is the cover-side of the line.
Where the page covers a worked regional-context example. The desk publishes a viewing-matrix update that adds a new region row. The row lists the operator's tier of access; the desk does not extrapolate a wagering-guidance read for any region. The regional-context section is named on the page; the help section is named on the page; the page does not expand into a wagering-guidance document.
Where the page covers a worked help-section example. The desk replies to a reader inquiry within 24 hours on weekdays. The reply cites the help section of the responsible-play page and the relevant regional public-health service. The desk does not provide crisis support or wagering-counselling services; the desk's reply is short by design.
Where the page covers a worked editorial-ethics policy. The page references the editorial-ethics page in the disclosure section. The editorial-ethics page describes what the desk does and does not accept: no payment in exchange for editorial coverage, no payment in exchange for editorial silence, no gifts or hospitality from operators or publishers.
Where the page covers what the desk will do if a reader files an inquiry about a wagering-pitch email. The desk replies within 24 hours on weekdays with a one-line acknowledgement and a redirect to the editorial-ethics page. The desk declines the wagering-pitch email; the desk does not engage with the operator beyond the one-line acknowledgement.