Reference

Privacy Policy for Your gbo500 Account

gbo500 Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can ask about your records before opening an account.

Policy accessAccount dataWallet recordsCookie choices

Explore Our Lobby Read FAQ

Privacy Policy: DANA and QRIS Records

gbo500 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide when creating an account, completing phone verification, contacting support, and checking wallet activity. This can include your name, phone number, login identifiers, device signals, browser settings, support messages, and transaction references. When you use DANA, OVO, GoPay, QRIS, bank

1
transfer, or a virtual account, we may receive status and reference data needed to match a payment request without storing unnecessary wallet credentials. We use these records for account access, fraud checks, payment reconciliation, technical support, and legal duties where local law permits. We do not
2
use payment references to create unrelated advertising profiles. Retention depends on the record type, account status, security needs, and applicable local law. If access or eligibility is discussed, it depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY CONTACT

Contact gbo500 About Privacy Requests

A direct support path helps you ask what data is linked to your account, why a verification step appeared, or how to correct an outdated phone number.

Account data request Use the logged-in support chat to ask for a copy, correction, or explanation of personal data connected with your gbo500 account. We first check account ownership through the phone verification details already on file.

Wallet reference check If a DANA, OVO, GoPay, or QRIS record looks unfamiliar, send its transaction reference through the protected support path. We compare the reference with account activity and explain the status without requesting your wallet password.

Login privacy help When a phone change or device sign-in blocks account access, contact support from the account page or available sign-in route. We use verification questions and account history to protect your records before making a change.

DATA CONTROLS

Six Privacy Steps Behind Account Access

Privacy decisions are built into the account flow rather than left to a separate promise.

Data collection

We collect details you enter during account creation, such as your phone number and login information, plus technical signals from the browser or device used to open the lobby. We use these details for account operation, verification, support, and security checks.

Cookie choices

Cookies and similar browser storage can keep your session, remember selected settings, and help us identify technical faults. You can manage browser permissions on your phone or desktop, although blocking required cookies may interrupt login or the policy request path.

Account security

Phone verification is required before account access and may appear again after an unusual device change. We do not ask for your password or DANA, OVO, GoPay, or QRIS wallet PIN through support messages, and you should never share those credentials.

Record retention

We retain account, payment reference, and support records only for the period needed for account service, dispute handling, security review, and legal duties. A closed account may still have limited records kept when local law or an unresolved transaction requires it.

Correction requests

You can ask us to correct an inaccurate name, phone number, or account detail through the protected support route. Include the affected field and a short reason; we may request phone verification before changing information that controls sign-in or wallet matching.

Policy questions

For a Privacy Policy question, contact us through the support chat linked to your account and describe the record or process involved. We will explain the relevant handling step, any identity check, and whether the request is limited by local law.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the searches we hear before an Indonesian account is opened or a wallet record is checked. We explain the practical route for data access, corrections, cookies, device signals, and payment references without separating privacy from the account steps that create those records. Where a request affects eligibility or access, the outcome depends on local law.

The gbo500 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references. It explains how we use those records for login, security, reconciliation, support, and legal duties when you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Open the support chat connected with your account and ask for a copy or explanation of your personal data. Include the phone number linked to the account through that protected route. We may confirm ownership before responding, and the available response depends on local law and the record requested.

We do not ask you to send a DANA, OVO, GoPay, or QRIS wallet PIN through support. Our payment handling uses status and transaction references to match an account request. Never place a wallet PIN, password, or full security credential in a chat message or form.

Device and browser signals help keep a mobile session working, identify repeated sign-in attempts, and investigate technical faults. They can include browser type, operating details, and session markers. We use them alongside phone verification; they do not replace your password or prove identity on their own.

Send a correction request through the protected support chat and name the field that is wrong, such as a phone number or account name. We may ask for phone verification before changing sign-in or wallet-matching data. We handle the request according to the Privacy Policy and local law.

Retention varies by record type. Account details, payment references, and support messages may remain while the account is active or while a dispute, security check, reconciliation task, or legal duty is open. After closure, limited records can remain where local law requires continued retention.

You can manage cookies through your phone or desktop browser settings. Required cookies may be needed to keep a login session, remember a setting, or route a support request, so blocking them can interrupt access. Cookie handling remains covered by this Privacy Policy and depends on local law.

Privacy Policy for Your gbo500 Account

Contact gbo500 About Privacy Requests

Six Privacy Steps Behind Account Access

Data collection

Cookie choices

Account security

Record retention

Correction requests

Policy questions

Privacy Policy Questions Before Account Access

01 What does the gbo500 Privacy Policy cover?

02 How can I request my data from gbo500?

03 Does gbo500 store my DANA or QRIS wallet PIN?

04 Why does gbo500 use device information on mobile?

05 How do I change incorrect account details under the Privacy Policy?

06 How long does gbo500 keep payment and support records?

07 Can I disable cookies without affecting account privacy?

Related Pages