Reference

Privacy Policy For Your okgas Account

Our Privacy Policy explains how okgas handles the details you provide when opening an account, checking wallet status or entering the lobby.

Account detailsWallet checksCookie choicesAccess requests
okgas Privacy Policy For Your okgas Account
CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact route matters when you want to ask about your Privacy Policy rights or a wallet record. We keep privacy questions close to the account and cashier paths, so you can provide the relevant phone number, transaction reference or device context without describing your full activity. Send only the details needed for the request; our team can explain the next step and may ask for an account check before discussing personal records.

Team online

Account support path

Open the support route from your signed-in account and choose a privacy question. Include your registered phone number only when requested, so we can match the request without asking you to repeat unrelated account details.

Cashier status check

For DANA, OVO, GoPay or QRIS records, share the visible transaction reference and status rather than a wallet password. We use that reference to locate the payment event and explain what the Privacy Policy allows us to retain.

Access request

Ask us to locate, correct or clarify personal data through the available account contact route. We may confirm your phone verification first, then describe the request stage and any detail needed to complete it.

HOW WE HANDLE IT

See How Your Account Records Stay Clear

The Privacy Policy is practical: it explains the records created when you sign in, verify a phone, move through the cashier or open a game area such as Live Dealer Lobby.

Data we collect

We may receive your account name, phone verification state, sign-in events, device type and records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. The policy explains the purpose attached to each category.

Cookie choices

Cookies and similar device storage can remember sign-in state, protect account sessions and show whether a page has already loaded. You can review browser controls on your phone or desktop, although limiting necessary cookies may affect account access.

Account security

Phone verification helps us check that an account request is connected to the right person. We also use sign-in and device signals to identify unusual access, and we will not ask you to provide a wallet password through support.

Retention periods

We keep personal and transaction records only for the period needed for the purpose described in the Privacy Policy, account administration or a required dispute check. When a record is no longer needed, our handling follows the stated retention process.

Correction requests

If your account detail is inaccurate, contact us through the signed-in support path and describe the field that needs attention. We may request phone verification before making a correction, which helps prevent another person changing your record.

Who to contact

Use the account support route for questions about collection, cookies, payment references, retention or access requests. Giving your registered phone number and the relevant reference helps us answer the Privacy Policy question without exposing unrelated records.

Answers About okgas Privacy Policy

These Privacy Policy answers address the searches we hear most often before account access. Each answer stays focused on your data, the account step involved and the contact route available when you need clarification.

It covers account details, phone verification, sign-in activity, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains why we use those records, how long they may remain and how to ask about them.

Yes. The Privacy Policy explains that we may retain a wallet route, transaction reference, amount and status needed to match an account event. We do not need your DANA, OVO or GoPay password, and you should not send that password through support.

Open the signed-in account support path and ask for a personal data access request. Include the registered phone number only through the requested field. We may complete phone verification before discussing records, helping ensure the response goes to the account holder.

You can request a correction through the account support route by naming the inaccurate field and supplying the current detail. We may check your phone verification first. The Privacy Policy explains how we assess the request and confirm when the record has been updated.

Cookies can preserve a sign-in state, protect an account session and record basic page activity needed for access. You can adjust browser settings on your Android phone, iPhone or desktop. Blocking necessary cookies may prevent some account or lobby pages from loading.

Retention depends on the purpose described in the Privacy Policy, including account administration, payment matching and dispute checks. DANA, QRIS, bank transfer and virtual account references may remain for that stated period. Contact support if you need the retention reason for a specific record.

Access and eligibility depends on local law, and the service is available only where local law permits. The Privacy Policy describes handling for account activity connected with the service. If your location or access status is unclear, contact us through the account support path.