Reference

Privacy Policy for gerbang asia Accounts

gerbang asia Privacy Policy explains how we collect, use and protect details connected with your account, mobile access and wallet activity.

DATA PURPOSESACCOUNT ACCESSWALLET CONTEXTLOCAL LAW
Explore Our Lobby Read FAQ
gerbang asia Privacy Policy for gerbang asia Accounts
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you ask about the personal data connected with your gerbang asia account. Send a request through our account support route when you need a copy, correction, deletion assessment or explanation of a payment reference. Include the phone number or account detail used for access, but do not send a wallet PIN or password.

Team online

Account support

Use the support route attached to your account when a privacy question concerns phone verification, login records or device access. We may ask you to confirm account details before discussing personal data, so a request reaches the correct account holder.

Wallet questions

For DANA, OVO, GoPay or QRIS references, tell us the payment rail, date and transaction reference shown in your account. We use those details to locate the record without asking you to share a wallet PIN or full authentication secret.

Access concerns

If your privacy request follows a login or device problem, mention whether you used a mobile browser or desktop browser and what happened before access stopped. We can separate a security check from a request to amend your personal data.

DATA PRACTICE

How We Handle Your Account Data

We apply the Privacy Policy during ordinary account activity, not only when you contact us.

Account records

We use your account details and phone verification result to recognise the account you are asking about and to protect access. A successful sign-in does not give support permission to disclose another person’s records, even when a payment reference looks similar.

Payment references

We retain the transaction reference, amount status and selected rail needed to reconcile a wallet or bank route. DANA, OVO, GoPay, QRIS and virtual account records help us answer a status question without storing your wallet PIN or online banking password.

Browser cookies

Cookies and similar browser markers can keep a session connected, remember a language or help us detect unusual sign-in behaviour. On mobile, clearing browser cookies may remove saved access and require phone verification again before you reach the account area.

Security controls

We use sign-in records, device signals and verification steps to identify unusual access. If a login from a new browser needs checking, we may pause account discussion until you confirm the account detail through the support route.

Retention period

We keep records only for the period needed to operate the account, resolve a payment question, protect against misuse or meet a legal obligation. When a record is no longer needed for those purposes, our handling process moves it toward deletion or secure restriction.

Changes and contact

You can ask us to correct an inaccurate phone detail, explain a data use or assess a deletion request through account support. State the requested change clearly; we may retain a request record so we can show how the Privacy Policy question was handled.

Privacy Policy Answers Before Access

These Privacy Policy answers address the account and payment questions most likely to arise before you open access. They also explain what you can ask from us, what verification may be needed and how browser behaviour affects your records. Where service eligibility is relevant, access depends on local law.

It covers data linked to your account, phone verification, browser access, support messages and payment references. That can include a DANA, OVO, GoPay, QRIS or bank-transfer reference, along with security records used to protect your account where local law permits.

Our Privacy Policy does not require us to store your DANA or QRIS PIN. We use transaction references and status details to match a payment question. Never send a wallet PIN, banking password or one-time authentication code through support.

Phone verification helps us connect an access request with the correct account and reduce unauthorised disclosure. We may ask you to confirm the phone detail already associated with your account before discussing records, changing data or assessing a deletion request.

Yes. Send a clear correction request through account support and identify the inaccurate detail, such as a phone number or account profile field. We may verify your identity first, then update the record or explain why a legal or security reason prevents the change.

Cookies can keep a browser session connected and help us recognise unusual access. Clearing them on your mobile browser may remove saved access and trigger phone verification again. Cookie handling does not reveal your wallet PIN to us.

We retain payment references for the period needed to reconcile a transaction, answer a status question, protect the account or meet a legal duty. The period can differ by record type; when the purpose ends, we delete or restrict the record through our handling process.

Use the account support route and state whether you want access, correction, deletion assessment or an explanation. Include your account phone detail and relevant payment reference, but not a password or PIN. We may request verification before responding to protect your data.

Related Pages

gerbang asia Indonesia Fair Play Policy Access guide gerbang asia Casino Account information