Reference

Open goku55 Privacy Policy for Clear Account Control

goku55 Privacy Policy tells you what we collect when you open an account, how we use phone verification, and how wallet records from DANA, OVO, GoPay or QRIS…

Account dataCookie choicesWallet recordsContact requests
goku55 Open goku55 Privacy Policy for Clear Account Control
REQUEST HELP

Contact Us About Your Privacy Policy Request

A direct support path helps when you want to ask about a Privacy Policy matter rather than a lobby question.

Account support Use the support route inside your signed-in account for a Privacy Policy request. Including your registered phone detail helps us locate the correct account record before we respond.
Payment record check If your request concerns DANA, OVO, GoPay or QRIS data, attach the payment receipt reference without sharing a wallet password. We use those details to locate the relevant transaction record.
Access concern When login or phone verification blocks your request, tell us which step stopped and the device path you used. We can separate an account access issue from a personal-data request.
DATA PRACTICE

Check How goku55 Handles Account Data

We handle Privacy Policy requests through account records, device events and payment references rather than treating every message as a new profile.

Account details

We may store your name, contact detail, verification result and sign-in history to maintain the account path. We use these records to confirm that a data request comes from the account holder.

Device activity

The sign-in device and browser path may create technical records such as time, session and security events. These details help us investigate access problems without requesting your wallet password.

Cookie controls

Cookies can keep a session active and remember selected page settings. You can manage cookie permissions through your browser, although restricting them may interrupt sign-in or policy access.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain receipt references, status and matching details. We do not need your wallet password to check a record.

Retention process

We keep personal records for the period needed for account operation, payment reconciliation, dispute handling or legal duties. When a retention reason ends, records can be removed or separated from active use.

Change requests

You may ask us to access, correct or delete personal details where applicable. Send the request from your account support route, and we may verify your phone before taking action.

Find Privacy Policy Answers Before Opening Your Account

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. They explain what happens around phone verification, cookies, wallet records and contact requests, so you can decide what to share before using goku55 where local law permits.

The goku55 Privacy Policy covers account details, phone verification, sign-in events, device data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm account ownership before access or before handling a Privacy Policy request. It also helps separate your account records from another person’s request when contact details overlap.

Yes. The Privacy Policy explains that we may handle DANA and QRIS receipt references, payment status and matching details when needed to reconcile an account action. We do not request your wallet password.

Cookies can preserve your signed-in session and selected page settings. You can change browser permissions, but blocking necessary cookies may interrupt account access or require you to sign in again.

You can contact us through the account support route to request access or correction where applicable. Include your registered phone detail, and we may complete verification before sharing or changing records.

We retain payment references and related account records for operational reconciliation, disputes or legal duties described in the Privacy Policy. After the relevant need ends, records may be removed or separated from active use.

Use the signed-in account support route and describe the Privacy Policy issue clearly. If login or verification fails, include the device step that stopped you so we can route the request correctly.