Reference

gopek178 Privacy Policy for Indonesian Accounts

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

Clear data purposesWallet record contextPhone verification detailsPrivacy request path
gopek178 gopek178 Privacy Policy for Indonesian Accounts
SUPPORT ROUTES

Privacy Help Beside Your Account Path

A clear contact route matters when you want to ask about your personal data, a wallet reference or a phone verification record. We keep privacy help close to the account and cashier paths, so you can explain the issue without posting sensitive details in a public message. Include your account identifier and the subject of your request, but never send a password or wallet PIN.

Team online

Account access

Open the support path beside your account area when a phone verification record looks incorrect. We can use the account identifier you provide to locate the relevant privacy record without requesting your password.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, share the payment reference and date shown on your receipt. We use those details to check the record while keeping your wallet credentials outside the request.

Privacy request

Ask us to clarify, correct or remove eligible account data through the privacy request path. We may first confirm account ownership through the phone verification step before making a change.

DATA PRACTICES

How gopek178 Handles Account Data

We separate the details needed to operate an account from the records used to investigate payment or security questions.

Account details

We use your account identifier and phone verification result to connect sign-in activity with the correct account. This helps us respond to an access question without mixing your records with another account.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account. We keep transaction evidence for reconciliation and support follow-up.

Cookies

Cookies can remember sign-in preferences, maintain account flow and help us understand whether a page is functioning. You can manage browser cookie settings, although some account steps may then need repeating.

Device security

We may record browser, device and sign-in signals to identify unusual access. On mobile, the same checks apply when you move from login to the lobby through your browser.

Retention

We retain account, payment and support records only for operational, security or legal needs described in the Privacy Policy. When a retention reason ends, the record can be deleted or separated from direct account details.

Change requests

You can ask us to correct eligible details, explain a processing purpose or address a concern through the privacy request path. We may request phone verification before changing protected account data.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the questions we expect before you open an account or connect an Indonesian wallet. Each answer points to a practical step, from checking a DANA reference to asking how cookies or retention apply to your account.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention and requests to correct or remove eligible data.

Phone verification helps connect you with the correct account and protects privacy requests. We may use the verified result when checking an access issue or changing protected account details.

Yes. The Privacy Policy includes references from DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records used to match payment status and resolve account questions.

You can send a correction request through the privacy support path. Tell us which detail is inaccurate, provide your account identifier and complete any ownership check we request.

Cookies may support sign-in flow and page operation on your mobile browser. You can adjust browser settings, but disabling them may require repeated account steps or affect certain account functions.

We keep payment references for the operational, security or legal purposes described in the Privacy Policy. When those purposes end, records may be deleted or separated from direct account details.

Use the privacy request path near the account and cashier areas. Share the subject and account identifier, but do not send a password, wallet PIN or complete payment login details.