Reference

Open gbo799 Privacy Policy Clearly

gbo799 Privacy Policy explains how we handle your account details, wallet records, device signals and support messages before you open the lobby.

Account clarityWallet recordsDevice choicesCookie controls
gbo799 Open gbo799 Privacy Policy Clearly
ASK ABOUT PRIVACY

Browse Support Routes for Policy Help

If a Privacy Policy question arises during account access, we want you to reach the right route without repeating the whole story.

Account questions Use our account help route for questions about phone verification, sign-in records or a…
Wallet records When a payment reference needs checking, give us the rail name, such as QRIS…
Privacy requests For a copy, correction or removal request, use the privacy contact route shown with…
CONTROL YOUR RECORDS

Switch Privacy Choices With Confidence

Privacy Policy is useful only when you can act on it, so we describe the controls behind account data rather than using broad promises.

Account data

We collect the account details needed for the account path, such as your phone number and credentials created during registration.

Wallet references

A DANA, OVO, GoPay or QRIS request can create a reference showing the rail, amount status and time of the…

Cookies and sessions

Cookies can remember a session choice and help the account path work between pages.

Device security

We may compare device and browser signals with recent sign-in activity to spot an unusual access attempt.

Retention period

We keep account, payment-reference and support records while they serve account operation, dispute handling or legal duties.

Request changes

You can ask for access, correction or deletion of eligible personal data through our privacy contact route.

Ask About gbo799 Privacy Policy

These Privacy Policy answers cover the questions that usually come up before account access: what we collect, why payment references appear, how device checks work and how to request a change. If your situation is not listed, use the privacy contact route and describe the specific account step. Access depends on local law and is available where local law permits.

It covers account details, phone verification, wallet references, device and browser signals, cookies, support messages, retention and privacy requests. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number as part of the account path and phone verification step. It helps connect sign-in activity and account requests to the correct record. If the number is no longer accurate, you can request a correction after account control is confirmed.

No. A payment request may create a reference showing the selected rail, status and time, but we do not need your DANA, OVO, GoPay or QRIS PIN to match that request. Never send a wallet PIN through account help or privacy contact routes.

We use device and browser signals to support session continuity and identify unusual sign-in activity. Those signals can prompt an account check when a new phone or desktop appears. You can also manage cookies in your browser, though a later sign-in may be required.

Use the privacy contact route connected to account help and state whether you want access, correction or deletion of eligible data. Name the category, such as support messages or wallet references, and provide the account detail needed to verify your request.

We retain account, payment-reference and support records while they support account operation, dispute handling or legal duties. After that purpose ends, we remove or restrict the record under our retention process, unless a continuing legal need requires us to keep it.

Access depends on local law and is offered where local law permits. The Privacy Policy is available before account access so you can check our data practices from Indonesia, including the handling of phone verification, wallet references and mobile browser sessions.