Methodology

Data integrity

How we count what players and readers tell us, and the numbers we refuse to show.

5
Reports before an FXCheck status
10
Clocks before an FXClock median
0
Counters seeded or rounded up
0
IP addresses in the click log
The rule

Every number on FreeExtraChips that comes from players or readers is counted as it arrives, labelled by what it actually counts and shown with its sample. We never seed a counter, round one up or call clicks “players”. Where a sample is too small to mean anything, the page says so instead of showing a weaker number. Commercial relationships change none of these numbers or their rules.

What we count

SignalWhat it countsShown fromWhere it goes
FXCheck™ status Players’ Yes/No reports on a bonus, one per browser A status from 5 reports; Verified from 8 Bonus lists, bonus pages and casino pages, by one rule. Editor’s Picks take Verified bonuses only.
FXClock™ payout times Withdrawal clocks that players start and stop themselves, each with a grade from A to D A median from 10 stopped clocks Casino reviews and the Payout Index, always apart from the desk’s own tests. Never a rating.
Trending this week Outbound clicks to the casino in the last 7 days, known bots left out A bonus needs 30 opens site-wide, 15 within a bonus type The trending bands of the home page and the bonus lists. Popularity only: it never feeds FRank, FXShield or Editor’s Picks.
Player reviews Reviews of a casino, published after moderation The first review, with the count beside the average The casino review’s “What players say”.
Corrections Factual errors we fixed, each credited to the reader who reported it first Every entry The public corrections log.

Labels say what they count

  • Trending counts are “opens”. The click log keeps no IP address, so it cannot tell one player from another, and we do not pretend it can.
  • FXCheck™ counts reports. The Yes-rate of a bonus shows from five reports, next to the counts it comes from. The rule behind each status is on the FXCheck™ methodology.
  • FXClock™ counts clocks. Each one carries its grade: A when the stop time is locked on-chain, D when it is anonymous. Refused, unresolved and excluded clocks are counted and shown apart, never in the median. Details on the FXClock™ methodology.

Numbers we don’t show

  • No FXClock median under ten stopped clocks. The page says how many there are.
  • No FXCheck verdict under five reports. The bonus shows “Low data”.
  • No trending bonus below its floor. A bonus with too few opens stays out of the band, and with none left the band does not appear.
  • No fallback numbers. A quiet week prints nothing, never a figure nobody counted.
  • No “players claimed this bonus” counters. We cannot count that, so we don’t print it.

What the desk can and cannot touch

  • FXCheck™ reports are never edited or removed, and an operator cannot have one taken down. A note with a link, contact details or abuse is not shown, and one with an accusation waits for an editor; the report counts either way.
  • FXClock™ clocks cannot be started, stopped, re-timed or re-graded by the desk. A clock can be hidden for abuse, with a reason from a fixed list, and a hidden clock stays in the “excluded” count on the brand page.
  • A player review appears only after an editor approves it.
  • A published correction stays in the log, even if the page changes again later.

Bots and bursts

  • Clicks from known bots, recognised by their user agent, are flagged and left out of Trending.
  • FXCheck™ takes one report per browser per bonus and at most five reports in ten minutes from the same connection, kept only as a one-way hash.
  • FXClock™ allows one running clock per player per casino; stops within two minutes of the start, repeated clocks and bursts from one network add up to automatic exclusion, and a transaction id can back one clock only.
  • Player reviews pass a bot check, a hidden field that only bots fill in and a limit per address before they reach the moderation queue.

If a number looks wrong

Tell us through the contact form or at [email protected], with the page and what does not add up. A confirmed error of fact goes in the corrections log; how we handle sources and disputes is in our editorial standards, and how we earn money in the affiliate disclosure.