Fair Play and Testing Policy

This Fair Play and Testing Policy explains how game fairness, technical stability, mobile performance, payment integrity, and player reporting may be handled on the platform.

The purpose of this page is to give users a clear overview of how games, app releases, security systems, and account-related features are expected to be tested before and after launch.

Fair Play Principles

The platform is designed to provide real-money gambling services under clear and testable rules. Game results should not be controlled by the player, the operator, support agents, or any manual process.

Fair play depends on several elements:

• certified game software;
• random result generation;
• transparent game rules;
• visible RTP information where provided by suppliers;
• secure account sessions;
• controlled payment processing;
• documented complaint handling.

Users should always read the rules of each game before placing real-money bets.

Random Number Generator Testing

Casino games should use Random Number Generator systems or supplier-controlled game engines to produce independent results. These systems are normally tested by approved laboratories before games become available to players.

RNG testing helps confirm that game outcomes are not predictable or manually changed during play. The same principle applies to slots, table games, instant games, and other digital casino formats where random outcomes are used.

Return to Player and Game Rules

Return to Player, also known as RTP, shows the theoretical percentage a game may return to players over a long period. RTP does not guarantee results in a single session and should not be treated as a prediction of short-term wins.

Each game should include its own rules, paytable, feature description, and bonus mechanics. Players should check this information before playing, especially when using bonus funds.

Game Provider Certification

Games available on the platform may come from third-party software providers. These providers are responsible for game design, payout settings, math models, server communication, and technical updates.

Before adding a new provider or title, the platform should check certification status, technical compatibility, game rules, payment logic, and responsible gambling requirements. Provider availability may vary by region, licence conditions, and account location.

Testing Before Release

New games, payment features, mobile updates, and account tools should be tested before public release. Testing helps identify errors that could affect login access, game loading, payment flow, bonus tracking, or account security.

Pre-release checks may include:

• game launch testing;
• payment flow testing;
• mobile layout checks;
• browser compatibility checks;
• APK installation review;
• PWA performance review;
• load testing during high traffic;
• account session and logout testing;
• bonus calculation checks;
• error message review.

If a technical issue is found, the affected feature should be corrected before wider release.

Mobile App and PWA Testing

Mobile access should be tested separately from desktop access because phones, tablets, browsers, and operating systems can behave differently. Android APK and iOS PWA formats require regular checks for installation, loading speed, account access, and gameplay stability.

Mobile testing may include:

Users should download or install mobile access only through official website sources.

Payment and Transaction Integrity

Payment systems should be tested to confirm that deposits, withdrawal requests, balance updates, and transaction histories are recorded correctly. Any failed, pending, reversed, or delayed transaction should be traceable through internal records.

Payment integrity checks may include:

• deposit confirmation;
• balance update timing;
• withdrawal request status;
• payment method ownership checks;
• duplicate transaction prevention;
• refund and reversal tracking;
• transaction history accuracy;
• KYC status connection with payouts.

Users should keep screenshots or records of important payment actions until a transaction is completed.

Bonus Calculation Checks

Bonus systems should be tested because promotions can involve wagering, expiry dates, maximum bet limits, game restrictions, and win caps. Incorrect bonus tracking can create disputes between the user and the operator.

Bonus checks may include:

• correct bonus activation;
• promo code validation;
• free spin delivery;
• wagering progress tracking;
• eligible and restricted game lists;
• maximum bet rule application;
• expiry time display;
• bonus cancellation process;
• conversion from bonus balance to cash balance.

Users should read promotion terms before activation and avoid using a bonus if any rule is unclear.

Security and Account Protection

Fair play also depends on secure account access. The platform should use technical and organisational measures to protect login sessions, payment data, verification documents, and user activity.

Security measures may include encrypted connections, session monitoring, password controls, device checks, restricted staff access, payment protection, and suspicious activity detection.

Users are responsible for keeping login details private, using strong passwords, and avoiding shared devices where account security cannot be controlled.

External Audits and Review

The platform may use external testing, technical audits, supplier reviews, and compliance checks to support fair operation. These checks can cover game performance, payment systems, app releases, security controls, and data protection.

Audit frequency and scope may depend on the operator, licence conditions, software providers, and regulatory requirements. Users should check the legal pages or support section for current information about testing partners and certification references.

Player Reporting

Users should be able to report technical issues, unusual game behaviour, payment errors, incorrect bonus tracking, or account problems through the available support channels.

A useful report should include:

• registered email address;
• game name or feature affected;
• date and time of the issue;
• device and browser used;
• transaction ID where relevant;
• screenshots or screen recordings;
• description of what happened;
• support ticket number if already created.

Clear reports help support teams investigate faster and reduce repeated questions.

Complaint Review

If a user believes a game result, payment action, or bonus calculation was handled incorrectly, the issue should be reviewed through the complaint process listed in the website terms.

The review may include checking game logs, transaction records, account history, bonus activity, device data, and communication records. If the issue cannot be resolved internally, the user may be directed to the relevant regulator, dispute body, or external complaint channel where available.

Transparency for Players

Users should have access to the information needed to understand how games and account features work. This includes game rules, paytables, promotion terms, payment conditions, privacy information, and responsible gambling tools.

Important information should be written clearly and updated when rules, features, or payment conditions change. Users should review the latest terms before depositing, activating bonuses, or installing mobile versions.

Responsible Gambling and Fairness

Fair testing does not remove the risk of gambling losses. Even certified games can produce losing sessions, and no result is guaranteed.

Users should set limits, take breaks, and avoid gambling with money needed for bills, rent, credit payments, or daily expenses. If gambling becomes stressful or difficult to control, account limits, cool-off periods, self-exclusion, and independent support services should be used.

Policy Updates

This Fair Play and Testing Policy may be updated when technical systems, provider rules, testing procedures, mobile versions, payment flows, or regulatory requirements change.

The latest version should be published on this page. Users should review this policy regularly if they want to understand how fairness, testing, and technical integrity are handled.

Last updated: June 2026