Mobile privacy rules, readable in 30 seconds
Built for Philippine mobile users. We only check login, device, and payment verification. Payment details are not kept after review — a lighter process.
Policy snapshot
- Check types: login, device, payment
- Payment details not stored after review
- Clear labels for visible games and access data
Common user needs
What the policy covers
Login access
Only the information needed for access is requested. After one review, minimal data is retained.
Device access
Phone and browser signals are used for the current session check only — not for other purposes.
Payment review
Only transaction context is kept. No card or wallet data is stored. Verification ends the process.
Game notes
Listed games retain RTP data for easy comparison, clear on mobile screens.
How data is handled
Login confirmation
Basic account info confirms access, suited for mobile login and short sessions.
Device check
Only phone and browser signals needed for the current request. Page load stays light.
Payment close
After review the flow ends. No payment data is stored, reducing repeat entry.
Support snapshot
Short replies help mobile users finish each step faster — fewer page switches, less waiting.
Mobile-first flow
Faster login
Key actions fit on one screen for phone layouts.
Less data
Reduced extra content keeps browsing smooth on low data.
Clearer labels
Access data, game data, and review data are marked separately.
Continuous
Short sessions still allow users to follow the full path.
Common questions
Do you keep payment information?
No. Review is limited to the current check. Payment data is not retained.
Why is the policy so short?
Mobile users need fast reading. The wording is direct so it works well on small screens.
How are requests handled?
Each request is handled case by case. Only data needed for access or review is used.