Clear privacy rules for mobile play.
We keep data scope narrow: login checks, device access, and payment review only, with transparent RTP notes and simple support on Philippine mobile use.
Quick privacy points
Only request-based checks for sign-in and device review.
No stored payment info after review ends.
Transparent RTP data stays visible where games are listed.
Support answers stay short and easy to scan on phones.
Data use at a glance
Account setup, access checks, and support tickets only.
Membership levels can affect gift handling and withdrawal routing.
Average response target from the support desk.
Popular payment routes reviewed per request.
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
| Area | What is used | Why it matters |
|---|---|---|
| Loyalty | Tier level, gift handling, withdrawal routing | Keeps member benefits matched to account status |
| Support | Login time, device type, request details | Speeds up replies without broad data access |
| Odds info | Public RTP notes and game listing data | Helps users check game info before they play |
FAQ
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.