Editorial policy
This policy governs how content on 8day.gg is written, reviewed, corrected, and updated. It exists so that readers can evaluate our work against a documented standard, so that our editorial team has a written reference when questions arise, and so that operators seeking coverage understand what we will and will not do. The policy is reviewed twice a year and updated as needed to reflect changes in market conditions or in our own practice.
How our content is written, reviewed, corrected, and updated.
Independence from operators
No operator has editorial control over any page on 8day.gg. This means specifically that no operator has the ability to review copy before publication, request changes to ranking positions, request removal from a ranking, or request changes to test result figures. Operators can submit factual corrections through the same channel available to any reader, and factual corrections are handled through the standard corrections process described further down this page.
The editorial team does not have access to affiliate commission data at the operator level. This information is held by the commercial team and is deliberately kept out of the editorial workflow to prevent commission signals from affecting testing results or ranking decisions. When commercial and editorial functions are structurally separated in this way, editorial decisions cannot be gamed by commission rate adjustments, and we consider this separation to be the single most important structural safeguard on the site.
No individual on the editorial team owns equity in, has a consulting relationship with, or has family relationships to leadership at any operator we cover. Where any of these relationships exists (they currently do not), the affected editor recuses themselves from testing or writing about the operator in question, and the article is written and reviewed by other members of the team.
Two-editor review
Every page on 8day.gg passes through at least two of the three core editors before publication. The author writes the piece and completes the operator tests described within it. The fact-checker independently verifies the licence claim against the regulator's register, sanity-checks the numeric figures against the raw test data, and confirms that compliance and payments assertions match our internal reference documents.
When author and fact-checker disagree on a substantive point, the third core editor is brought in to arbitrate. The arbitration decision is documented in our internal editorial log, which is reviewed quarterly to identify patterns that might indicate a need for methodology updates.
Where all three core editors disagree on how an operator should be scored on a pillar, the operator does not receive a ranking placement until the disagreement is resolved by additional testing. This has happened three times in the past year and has typically been resolved by a second withdrawal test or a re-verification of licence status.
Native-language coverage
Pages for non-English markets are written by contributors who write natively in the target language, not translated from English by machine or by a non-native translator. This applies to European Portuguese for Portugal, Danish for Denmark, Dutch for the Netherlands, Swedish for Sweden, French for France, and Thai for Thailand. The core editors read enough of each language to sanity-check translations against raw source data, but the finished text in each non-English market is the work of a native-language writer working with our team's operational testing data.
Machine translation is used only for internal reference, never for published copy. Machine-translated copy is readable but does not carry the natural cadence that native readers recognise as trustworthy, and the difference is materially larger in Thai and Danish than it is in French or Portuguese.
Where a native-language contributor is unavailable, we delay publication rather than publish translated copy. This slows our publication cadence in some markets but preserves the trust signal that native-language coverage produces.
Sourcing and citations
Numeric claims on 8day.gg fall into three categories, each with a documented sourcing standard.
Test results (withdrawal times, deposit times, support response times, bonus completion times) come from our own testing and are supported by internal raw data. The published figure is the median of at least three baseline measurements. Where an individual result is unusually high or low relative to the baseline, we note this in the text rather than smoothing it out.
Regulatory facts (licence numbers, licence dates, regulator names, jurisdiction rules) come from the regulator's own register or published documentation. Where a regulator changes a rule or reissues a licence, we update the affected page within one publication cycle. Aisha Halima maintains the internal reference on regulatory facts and reviews it monthly.
Third-party facts (game RTP, provider studio information, industry statistics) come from the provider or publisher directly wherever possible. Where a claim rests on third-party reporting, we identify the source in the text so that readers can evaluate it independently. We do not attribute claims to sources we have not personally verified.
Corrections
Corrections to factual errors are handled within three business days of receipt. The correction is made on the affected page, dated in a changelog entry at the bottom of the page, and if the error affected a ranking position, the ranking is recalculated. A correction never silently overwrites a prior statement without a changelog entry.
Corrections can be submitted through our contact page or by direct email to any of the three core editors. Corrections received from operators are treated with the same weight as corrections received from readers, and the same evidence standard applies to both.
Where a factual dispute cannot be resolved by documentation (for example, a disagreement about whether a withdrawal was processed within an operator's advertised time frame), we retest at the earliest opportunity and publish the retest result regardless of whether it supports the original or the corrected version. This has happened twice in the past year and in both cases the retest supported the original figure.
Content standards
Content on 8day.gg follows a house style designed for clarity and honesty rather than for search engine optimisation or affiliate conversion optimisation. Key elements of the style include the following.
First-person plural voice for editorial statements ("we tested", "our measurements") to make the collective source of the claim visible to the reader. First-person singular is used only in author-attributed opinion pieces, which are rare on the site.
Direct, specific language is preferred over marketing-derived vocabulary. We do not use "delve", "unleash", "seamless", "ever-evolving", "moreover", "furthermore", "landscape", "navigate the", "in today's", "elevate your", or "in the world of" in our published copy. These phrases carry no specific information and their appearance in a text is typically a signal that the text was written to fill space rather than to inform.
Em-dashes are not used. Sentences that would otherwise be broken by em-dashes are broken by commas, colons, or full stops. This is a house style choice made for consistency across markets, not a claim that em-dashes are grammatically wrong in general.
Numeric figures include units and context. A withdrawal time is expressed with the payment method, the deposit country, and the sample size ("USDT on Tron, median of three baseline measurements, tested from a French bank account"). Numbers without units or context are not published.
Section length is calibrated to content, not to word count targets. A section that fully explains its subject in three paragraphs stays at three paragraphs. Sections are not padded to reach a target length.
Advertising and sponsored content
8day.gg does not accept sponsored content, advertorials, guest posts, or ghost-written material. All published copy is written by our editorial team or by contributors under the same editorial standards.
We do participate in affiliate programmes with the operators we recommend on ranking pages. Affiliate participation means that when a reader clicks a tracking link from 8day.gg to an operator's site and subsequently registers or deposits, the operator pays us a commission. This model is described in detail on our affiliate disclosure page. Affiliate participation is disclosed inline on every page that carries affiliate links.
Display advertising is not currently sold on 8day.gg. Should this change in the future, display advertising will be clearly labelled as such and will not be permitted to visually resemble editorial content.
Author conduct
Members of the editorial team do not accept gifts, hospitality, junkets, or other benefits from operators. Attendance at industry conferences (ICE London, SBC Summit, iGB Live) is paid for by 8day.gg from our operating budget, not by conference sponsors. Where an operator invites a member of the editorial team to test a new product, the invitation is accepted or declined based on editorial interest, and the resulting coverage is written to the same standard as unsolicited coverage.
Personal gambling by members of the editorial team is not restricted, but is disclosed at aggregate level in our annual transparency report. No member of the editorial team holds a high-roller account, VIP status, or preferential relationship with any operator we cover.
More about how we work

