Clear privacy rules for mobile play.
A late-night session, a quick check on GCash, and the page still reads cleanly on phone screens.
We keep data scope narrow: login checks, device access, and payment review only, with transparent RTP notes for Philippine mobile users.
Quick privacy points
Request-only checks
Only request-based checks for sign-in and device review.
No extra storage
No stored payment info after review ends.
Visible RTP notes
Transparent RTP data stays visible where games are listed.
Phone-friendly support
Support answers stay short and easy to scan on phones.
Data use at a glance
What the team handles
Account data
Used for sign-in, support, and loyalty tier checks.
Payment review
GCash, Maya, Online Banking, and GrabPay checks cover each request only.
Device signals
Basic device and access details help confirm mobile logins.
Storage limits
Extra payment details are not retained after the review is done.
Membership and support notes
| What is used | Why it matters |
|---|---|
| Tier level, gift handling, withdrawal routing | Keeps member benefits matched to account status |
| Login time, device type, request details | Speeds up replies without broad data access |
| Public RTP notes and game listing data | Helps users check game info before they play |
Payment routes
Reviewed on request.
Checked only for the current session.
Used for verification when needed.
No extra payment data is kept.
Common questions
What data do you collect on mobile?
Only what is needed for login, device access, and payment review on each request.
Do you keep payment details?
No stored payment info remains after the review is completed.
How does VIP status affect privacy handling?
Tier data may guide gift handling and withdrawal routing, but it does not widen the data scope.
Philippine users can read this policy on phone screens with less scrolling, while support and privacy checks stay tied to the request at hand.