Reference

h5 lobby Privacy Policy For Your Account

h5 lobby Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataDevice choicesWallet recordsCookie controls
h5 lobby h5 lobby Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps when you want to understand a record rather than guess what it means.

Privacy request Ask through account support when you want a copy of personal data linked to…
Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date…
Account correction Your account support request can ask us to correct a name, phone detail or…
HOW WE HANDLE DATA

Practical Controls For Account Privacy

Our privacy process follows the account actions you can recognise: phone verification before access, device checks during sign-in, cookie choices in your browser and payment references matched to a transaction.

Account security

Phone verification helps connect account access to the contact detail you supplied. We also review sign-in and device signals for unusual activity. If a login looks unfamiliar, contact support from the account path and avoid sharing passwords, PINs or one-time codes.

Cookie choices

Cookies can remember a session, preserve language or help us understand which privacy page was opened. Your browser controls whether optional cookies remain. Blocking them may require another sign-in, while essential session cookies support the account path you request.

Payment references

We keep transaction references needed to connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. These references help with receipt checks and disputes; they do not require us to store your wallet PIN.

Device signals

When you move from a mobile browser to desktop, we may record technical signals such as browser type, operating system and session time. These details help protect sign-in and diagnose access issues without giving us control of your device.

Retention period

We retain account, support and transaction records only for as long as needed for the stated service purpose, dispute handling or a legal duty. To ask whether a record remains, contact support with the account detail and date concerned.

Requesting changes

You can ask for access, correction or clarification through the site support route. We may verify your phone or account identifier first, then explain any limit that applies where local law permits before changing or removing a record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions you may search before opening access. We keep the wording tied to real actions, including phone verification, wallet references, browser cookies and support requests. If your question is not listed, use the privacy support path with the smallest amount of detail needed to locate your account.

The h5 lobby Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, retention approach and ways to request access or correction.

We use phone verification to connect account access with the contact detail you supplied and to help detect unusual sign-in activity. The verification result may be retained for account protection and dispute handling. We will not ask you to send a private one-time code through support.

Yes. The Privacy Policy covers the transaction references and status details needed to match DANA or QRIS activity with your account. We may use those records for receipt checks, account support and disputes, while wallet PINs and private wallet credentials should remain with you.

Send a request through the account support route and state that you want access to your personal data. Include your account identifier and a useful date range, but omit passwords, PINs and one-time codes. We may confirm your verified phone before explaining what can be provided.

You can ask support to correct an account name, phone detail or contact address when the change is allowed. We may request phone verification or another account check before editing the record. If a legal or transaction reason prevents a change, we will explain that reason.

Essential cookies can keep a requested session active, while optional cookies may support preferences or page measurement. Your browser can block or remove optional cookies. Clearing session data may sign you out and require phone verification again when you return to account access.

Access, data requests and retention duties can vary by jurisdiction, so eligibility depends on local law. Where local law permits, we will process an access or correction request and explain any restriction that applies to your account or transaction record.