Clear privacy rules for PH accounts
On a quiet login night, the checks stay simple: sign-in, support, payment review, and account control only.
We keep the data needed for those steps, avoid stored card details on our side, and use local review when a request needs it.
Review focus
Short checks. Clear purpose. For PH users, any extra verification stays tied to the request in front of you.
Typical first reply target from support during listed hours.
Payment options can be reviewed in pesos-friendly flows.
Card details are not kept on our side after processing.
We review the minimum data required for each request.
What we review
Account data used for sign-in, support, and tier checks.
Session logs
Device logs help keep sessions stable and spot misuse.
Payment checks
Only the details needed to confirm a request are reviewed.
Local handling
PH requests may pass through local review steps when needed.
Data and purpose
| Item | Why it is used | How long we keep it |
|---|---|---|
| Account data | Sign-in, support, and access checks | Only while the account is active or required by review |
| Device logs | Session stability and misuse review | Short operational window |
| Payment checks | Confirming deposits, withdrawals, or related inquiries | As long as needed for the request |
Common questions
Do you store card details?
No. Card details are not stored on our side after processing.
Why would extra verification appear?
Some PH requests need a short local review to confirm account activity or payment checks.
What data is the minimum?
Only the data needed for sign-in, support, review, or payment handling is used.
Contact path
For privacy questions tied to PH accounts, use the same account channel you signed in with. That keeps the review clean and traceable.