Privacy rules built for clear checks
Data use stays narrow: login, device access, and payment review only, with RTP notes shown on listed games and support replies tracked.
At a glance
Average response target for support checks.
Local payment methods kept easy to find.
Core data points handled in review flow.
Shown on listed games, where available.
What we collect
Quick sign-in
Only the details needed to confirm access are requested.
Payment review
The check ends after deposit or withdrawal handling.
Game notes
RTP data stays visible on listed titles, so users can compare before play.
Support logs
Replies are tracked to keep follow-up clear during account checks.
Payment methods used in the Philippines
GCash
Common for fast local deposits.
Maya
Used for account funding and review.
Online Banking
Helpful for larger transfers and records.
GrabPay
Kept visible for mobile-first users.
Handling rules
| Area | What is checked | Shown to users |
|---|---|---|
| Login | Access details for account confirmation | Only the required fields |
| Device | Basic device access for risk review | Short notice in the flow |
| Payments | Deposit or withdrawal request review | Method and status updates |
| Games | RTP notes on listed titles | Visible where available |
Steps that keep the process short
Sign in
Use the account details needed for access.
Review payment
Deposit or withdrawal checks are handled next.
Read game notes
RTP data stays visible on listed games before play.
FAQ
Do you collect extra profile data?
No. The policy stays limited to login, device access, and payment review needs.
Are RTP notes shown for every game?
They are visible on listed titles where the game page includes that data.
How fast do support replies come in?
The target is around 30 seconds for short checks, depending on queue volume.