How Intsinzi records and verifies play
Fair play depends on clear rules, one-time access, accurate player details and a reliable server record. This page explains how requests, rounds and claims are handled.
One-time access codes
Every approved round requires a valid code connected to a request. A code cannot be reused after a completed play. Unused code outcomes are not displayed to players before the round.
Server-side validation
The server checks the player details, code status and selected direction before accepting a round. The visual chart displays the round to the player, while the server record remains the operational source used for verification.
Recorded results
Completed rounds may include the request reference, code, player details, selected direction, result, date and claim information. These records allow the company dashboard to review a disputed round or payment enquiry.
Winning-number verification
A valid winning result generates a winning number and claim reference. The verification form checks the claim record and displays its status. A screenshot alone does not replace the server record.
Technical interruptions
If a device loses connection after a valid position has been accepted, the server record may still complete the round. Players should keep the relevant reference and contact support rather than repeatedly submitting the same code.
Fraud and manipulation
Intsinzi may suspend a request, code or claim where there is evidence of code guessing, automated play, altered screenshots, duplicate submissions, false information, account impersonation or interference with the website. Confirmed abuse may result in permanent restriction.
Dispute review
Send the request reference, code or claim reference to support. Intsinzi may compare the player message with server logs and administrative records. Reviews are handled during operating hours, 9:00 AM–8:00 PM Burundi time.
Last updated: 22 July 2026
