Reference

Read the 8g8g Privacy Policy

The 8g8g Privacy Policy explains what we collect when you create an account, verify your phone, browse on mobile, or check DANA and QRIS status.

Account dataWallet recordsCookie choicesRequest access

Explore Our Lobby Read FAQ

Check DANA Data Before Account Access

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

Our Privacy Policy covers the details needed to create and protect your account, including your phone number, verification status, login records, device signals and selected wallet route. When you choose DANA, OVO, GoPay or QRIS, we may record the payment reference, amount, status and time so

1
we can match a receipt to your account without storing a wallet password. Browser cookies can remember session settings, while security logs help us investigate unusual sign-ins. We retain records only for operational, dispute, security or legal needs, then remove or anonymise them when they are
2
no longer needed. Access to 8g8g and any related account service depends on local law. If you need a copy, correction or deletion request, contact us through the policy support route and include the account phone number used for verification.

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

PRIVACY HELP ROUTE

Ask About Your Account Data

A clear request helps us locate the right record without exposing another account. Use the support path connected to your account area for privacy questions, and tell us whether your request concerns phone verification, a QRIS receipt, a device session or a wallet status entry. We may ask you to confirm account details before discussing personal data. Where local law permits, we will explain the next step for access, correction or removal.

Team online

Access request

Ask us which account records we hold by providing the phone number linked to your verified account. We will use that detail to separate your request from another account.

Wallet query

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather than a wallet password. This lets us check status while keeping sensitive sign-in details private.

Correction request

If your name, phone record or device entry needs correction, describe the specific field and account step involved. We may verify the request before changing stored details.

DATA HANDLING DETAILS

Browse Privacy Controls On Mobile

Privacy choices should remain understandable whether you open the account page on a phone or desktop.

Account creation

We collect the account details you submit and the phone verification result before access is enabled. This creates an account record tied to your own login path, not to a shared device.

Device signals

We may record browser type, device identifiers, session time and security events. These signals help us detect unusual access without reading private files, contacts or unrelated activity on your device.

Cookie settings

Cookies can keep a session active, remember language or preserve a page choice. You can manage browser cookie controls, although disabling necessary cookies may interrupt account access or policy requests.

Wallet references

A DANA, OVO, GoPay or QRIS transaction may be linked to an account reference, status and timestamp. We do not need your wallet password to match that payment record.

Security checks

Phone verification and session checks help us respond when login behaviour changes. Never send a password or one-time code in a privacy request; we only need enough detail to verify ownership.

Retention requests

We keep records for account operation, payment matching, security review, disputes or legal duties. You can ask what remains stored, why it remains stored and whether correction or removal is available.

Find Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before account access. Each response stays focused on your data, your wallet references and the steps needed to contact us. Account eligibility and access depend on local law, and a request may require phone verification before we disclose or change personal records.

It covers account details, phone verification, device and session signals, cookies, payment references and retention. It also explains how to ask for access, correction or removal where local law permits.

No. Our Privacy Policy describes payment references, status, amount and time for DANA or QRIS matching. We do not need your wallet password, and you should never send it to support.

Phone verification connects the account to the contact detail you submitted and helps protect access when a device or session changes. We may use the result when handling a data request.

Yes, you can contact us through the account privacy route and identify the verified phone number. We may confirm ownership first, then explain which records can be provided.

State the exact field that is wrong, such as a phone detail or account name, and explain the requested correction. We may ask for verification before updating the record.

We retain them while needed for account operation, receipt matching, security, disputes or legal duties. After that, records are removed or anonymised when practical and permitted.

You can submit a deletion request through the privacy support route. We will assess it under applicable requirements because some security, payment or legal records may need to remain.

Read the 8g8g Privacy Policy

Ask About Your Account Data

Access request

Wallet query

Correction request

Browse Privacy Controls On Mobile

Account creation

Device signals

Cookie settings

Wallet references

Security checks

Retention requests

Find Privacy Policy Answers

01 What does the 8g8g Privacy Policy cover?

02 Does 8g8g store my DANA or QRIS password?

03 Why does 8g8g need phone verification?

04 Can I request a copy of my 8g8g account data?

05 How do I correct personal data in the Privacy Policy record?

06 How long does 8g8g keep device and payment records?

07 Can I ask for deletion under the Privacy Policy?

Related Pages