Transparency report

Editorial firewall

FairLedger is published by FairLedger Insights Ltd., a UK private limited company. Our editorial team has no equity in any covered operator, and no operator has the ability to commission, edit or veto a review. The commercial team negotiates affiliate commissions and bonus codes after a casino is approved by editorial - not before.

Ranking algorithm

The Independent Score on every review is a weighted average of five inputs:

• 30% withdrawal speed (median, last 90 days)
• 25% licence and dispute history
• 20% game library and Original audit results
• 15% bonus value (after wagering)
• 10% support quality (live tested every quarter)

Affiliate commission rates are not in the formula.

Affiliate disclosure

Most outbound links to operators are affiliate links. When you sign up via FairLedger, the casino pays us a percentage of their gross gaming revenue from your account. We pass between 50% and 100% of that revenue back to you as wager-share rewards, paid every Sunday at 23:59 UTC in BTC, USDT or USDC.

See the affiliate disclaimer for the full text.

Corrections policy

If you spot an error in a deposit volume figure, a withdrawal speed number or a bonus term, email data@fairledger.io with a counter-example transaction or screenshot. We reconcile within 48 hours and stamp the correction with the date and editor who reviewed it.

Live data sources

The deposit-volume widgets across the site cross-reference our own on-chain index against the public industry-volume figures published by fairgambling.com . We fetch their public homepage server-side via a Cloudflare Pages edge proxy, parse the headline figures out of the rendered HTML and cache the result at the edge for 60 seconds. The proxy is open and documented at /api/fairgambling/stats.

If the live cross-reference is unreachable, the dashboard falls back to our cached on-chain totals and the indicator turns orange. Live data never overrides our published numbers - it only annotates them.

Authentication & accounts

Sign-in is implemented as a Cloudflare Pages Function backed by Workers KV. Passwords are hashed with PBKDF2-SHA256 (100,000 iterations - the Cloudflare Workers runtime maximum - with a 16-byte random salt and a 32-byte server pepper) before storage. Sessions are HttpOnly Secure SameSite=Lax cookies with a 30-day TTL. We never store plaintext passwords and we never email them.