Reference

Privacy Policy For Your goku55 Account

Your account data, wallet status and device access are handled under the goku55 Privacy Policy, so you can understand what we collect before opening an account.

Clear data purposesWallet reference checksDevice access rulesRequest path
goku55 Privacy Policy For Your goku55 Account
HELP WITH DATA

Three Ways To Ask About Privacy

A clear contact path matters when you want to check a record, correct a phone detail or ask why a device signal appears in your account…

Account privacy path Open the account support route and state whether your request concerns access records, phone…
Wallet record check For a DANA, OVO, GoPay or QRIS receipt question, attach the transaction reference shown…
Policy request Ask for a copy, correction or deletion assessment through the policy contact route linked…
DATA PRACTICES

How goku55 Handles Your Account Data

Privacy becomes practical when each data use has a clear reason. We connect account records to login, verification, payment matching and support work, then limit access to the staff or process that…

Account details

We may collect your phone number, login identifiers and verification outcome to create and protect your account. We do not ask you to place a DANA, OVO, GoPay or QRIS PIN into a goku55 support message, and you should keep those credentials private.

Device signals

Login time, browser or mobile device signals can help us detect an unusual session and connect a request to the right account. These signals are used for account security and service continuity, not as a substitute for your phone verification step.

Cookies

Cookies may retain a session setting or help the account and lobby pages load as expected. You can manage cookie controls in your browser, although changing them may affect login continuity or the way policy pages are displayed on your device.

Payment references

When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, we may keep reference details and status results needed to match the account transaction. Wallet PINs and passwords remain outside our requested support details.

Retention and security

We retain records for the period needed for account security, transaction checks, dispute handling or a legal obligation that applies where local law permits. Access controls and verification steps help limit who can view account and payment records.

Changes and contact

You can ask us to correct eligible account data, explain a processing purpose or assess deletion through the policy contact route. Include your account phone detail and request category, then avoid sending a password, PIN or full wallet secret.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we expect before you open an account or connect a local wallet. They cover the data categories, device access, payment references, correction requests and account availability that matter when you use goku55 from Indonesia. Where a request depends on local law, we explain that boundary before taking action.

The goku55 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages and payment references. It explains why we use each category, how security checks work, how long records may remain and how you can ask about correction or deletion.

No wallet PIN or password should be sent to us. For DANA, OVO, GoPay and QRIS activity, the Privacy Policy concerns transaction references and status details used to match an account request. Keep your wallet credentials inside the relevant payment service and exclude them from support messages.

We use limited device and login signals to recognise an account session, identify unusual access and maintain continuity between your phone and the lobby. The Privacy Policy describes these signals as security and service records; they do not replace the phone verification step required for account access.

Yes, you can ask us to explain the data linked to your account or correct an eligible detail such as a phone record. Use the policy contact route, name the category involved and provide enough account context to locate it without sending a password or wallet PIN.

Retention depends on the reason for keeping a record, such as account security, receipt matching, dispute handling or a legal obligation. Our Privacy Policy sets the applicable approach, and a deletion request is assessed under local law rather than treated as an automatic removal.

Cookies can keep a session setting or support the display of account and policy pages on your browser. You can manage them through browser controls. Removing selected cookies may interrupt login continuity, but it does not erase account records or replace a formal privacy request.

Account access or eligibility depends on local law. The Privacy Policy describes how data is handled where local law permits, but it does not change the rules that apply in your location. Check the account access notice and contact route before submitting personal or payment details.