Reference

Open g1002 Privacy Policy Before Account Access

g1002 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the lobby and cashier.

Account detailsWallet referencesDevice choicesPrivacy requests
Explore Our Lobby Read FAQ
g1002 Open g1002 Privacy Policy Before Account Access
CONTACT THE TEAM

Ask About Privacy From The Cashier Path

A clear contact route matters when you want to know why a record exists or how a request is being handled. Start with the support route shown beside account and cashier help, then include your registered phone number and the subject of your Privacy Policy question. Do not send a wallet PIN or full payment password. We can use a DANA, OVO, GoPay, QRIS, bank-transfer or virtual-account reference to locate a status without exposing unnecessary payment credentials.

Team online

Privacy question

Send a question about the Privacy Policy through the account support route. Include the email or phone linked to your account, the relevant date and the data point you want clarified. We use those details to find the correct record and keep the reply tied to your account.

Data change request

Ask us to correct an account detail when your phone, email or identification record has changed. We may ask you to complete the same phone-verification step used for account access before making an update, so a request cannot be applied to the wrong g1002 account.

Payment record help

For a wallet or bank record question, provide the transaction reference, payment rail and approximate time. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references help us trace the cashier event while avoiding a request for your PIN or full banking credentials.

HANDLING DETAILS

Explore The Privacy Controls Behind Your Account

The practical part of our Privacy Policy is the way account, device and payment records are separated and checked.

Account security

Phone verification is part of the account path before access is completed. Session and device signals can help us identify an unusual login or repeated access attempt. Keep your password and wallet PIN private; support will not need either one to explain a Privacy Policy matter.

Cookies and sessions

Cookies and related browser storage may keep a sign-in step available, remember a device setting or help restore the correct lobby session. You can review browser controls on your phone or desktop, although turning them off may interrupt account access or require another verification step.

Payment references

The cashier can create a reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use that reference to match status and receipt records. It is different from a wallet password, card secret or banking login, which you should never place in a support message.

Retention checks

We keep different records for different operational reasons. Account and security data may be needed to protect access, while payment records can be needed to reconcile a receipt or resolve a dispute. When a retention period ends, handling follows the account and legal requirements that apply to the request.

Your requests

You can ask for access to personal data connected with your account, request a correction, or ask a question about deletion and retention. We first confirm that the request comes from the account holder, then explain any limit that depends on local law or an unresolved payment record.

Policy contact

Use the support channel available from your signed-in account and state that your message concerns the Privacy Policy. Include a reachable contact and the relevant account step. We use the details you provide to respond, and we avoid collecting extra identity or wallet material when it is not needed.

Browse Answers About g1002 Privacy Policy

These Privacy Policy answers cover the account actions you are most likely to question before opening access. They explain the relationship between phone verification, wallet records, cookies, support messages and retention without turning a payment reference into a request for private banking credentials. Read the relevant answer, then contact us from the signed-in support route when your situation needs an account-specific response.

The g1002 Privacy Policy covers information connected with account creation, phone verification, sign-in sessions, device settings, support messages and payment references. It explains why we use those records, how we protect account access, how retention works and how you can ask about, correct or access data where local law permits.

For DANA, OVO, GoPay or QRIS, we may keep a payment reference, amount, time, status and account connection needed to reconcile the cashier record. We do not need your wallet PIN to answer a status question. Bank transfer and virtual account records follow the same reference-based approach.

Yes. The Privacy Policy provides a route to ask what personal data is connected with your account. Contact support from the signed-in account, identify the relevant phone or email and describe the request. We verify account ownership first and explain any restriction that depends on local law.

Send a correction request through the account support route and name the field that needs changing. We may repeat phone verification before applying an update, because changing contact details affects future access. A support reply can explain which account record was changed and when the request was completed.

It does. Cookies or related browser storage can keep a session connected, retain a device preference or reduce repeated sign-in steps on mobile. Your browser settings control some of this storage. Disabling it may remove a saved session and require phone verification again before the lobby opens.

Retention depends on the type of record and why it is needed. Payment references can support reconciliation or a dispute, while security records can help investigate account access. The Privacy Policy explains the applicable handling, and support can clarify a request after confirming the account and the record involved.

Use the support path available from your account and write Privacy Policy in the message subject or opening line. Include your registered contact and, for a payment question, the reference and rail such as QRIS or bank transfer. Never include a wallet PIN, password or banking login.

Related Pages

g1002 Indonesia Account information Live Dragon Tiger Prestige About Us Access guide