Mobile privacy rules, written for quick reading
Data checks stay narrow: login access, device review, and payment verification only, with clear notes for phone users in the Philippines.
What the policy covers
We keep processing limited, use SSL-protected checks, and avoid storing payment details after review.
Built for mobile sign-in flows, short sessions, and low-data browsing.
What users usually need
Quick sign-in
Only the details needed to confirm access are requested.
Payment review
The check ends after verification, with no stored payment info.
Game notes
RTP data stays visible on listed games for easier comparison.
Support scan
Short replies help mobile users move through each step faster.
Policy at a glance
Request types checked: login, device, payment.
Stored payment details after review.
Mobile-first flow for lighter loading.
Clear notes on visible game and access data.
How data is handled
| Check | What is used | Result |
|---|---|---|
| Login access | Basic account details for sign-in confirmation | Reviewed once, then kept minimal |
| Device access | Phone and browser signals for request-based checks | Used only for the current session |
| Payment review | Transaction context without storing card or wallet data | Closed after verification |
Common questions
Do you keep payment information?
No. The review is limited to the check itself, and payment details are not retained.
Why is the policy short?
Mobile users need fast reading, so the wording stays direct and easy to scan on small screens.
How are requests processed?
Each request is handled case by case, with only the data needed for access or review.
Need a faster mobile flow?
Open the registration page, check the policy details, and continue with a clear request path.