Reference

gundala189 Privacy Policy Explained

gundala189 Privacy Policy explains how we collect, use and protect the details connected with your account, including wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
gundala189 gundala189 Privacy Policy Explained
CONTACT THE DESK

Reach Us About Your Privacy Policy

A clear contact path matters when your account record does not look right. Tell us which account step caused the concern, whether it involves phone verification, a wallet status or a device session, and we can route the request to the relevant team. Include only the details needed to locate your record; never send a password or full payment credential. We handle privacy questions through our account support route.

Team online

Account request

Ask us to locate, correct or explain account data by using the support route connected with your gundala189 account. Include your registered contact detail and a short description of the requested change.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and date rather than private wallet credentials. We use those details to trace the relevant record.

Access concern

If a phone verification or device session appears unfamiliar, contact us through account support and describe the device path. We can direct the privacy request while protecting the account from unnecessary disclosure.

DATA HANDLING

Explore How We Handle Account Details

We keep this policy practical by connecting each data purpose with an account action. Phone verification helps us confirm the person requesting access, while device signals help us identify unusual sessions.

Account details

We may handle the contact and verification details you submit when opening an account. We use them to provide account access, respond to your requests and connect a privacy enquiry with the correct record.

Cookie controls

Cookies can remember selected site settings and help us understand whether a page session is working. Your browser provides controls for restricting or removing cookies, although some account steps may then need repeating.

Device signals

A phone, tablet or desktop session can create technical signals such as browser and device details. We use these signals to protect account access and investigate a session you do not recognise.

Payment matching

When you use QRIS, DANA, OVO, GoPay, bank transfer or a virtual account, transaction references may be stored with account records. This helps us check receipt and status questions without requesting your wallet password.

Retention steps

We keep records for the period needed for the stated account, transaction, security or dispute purpose, then assess whether continued storage is required. The applicable period can depend on the record and local legal duties.

Your requests

You can ask what personal data we hold, request a correction, question a use or seek deletion where applicable. We may ask for account verification before changing or releasing details.

Browse Privacy Policy Answers

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the wording tied to real steps, including phone verification, device sessions, cookie controls and payment receipt checks, while access remains subject to local law.

It covers account details, phone verification, device and browser signals, cookies, payment references, support requests and retention. It also explains how to request access, correction or deletion where applicable.

We use phone verification to connect an access request with the correct account and help identify unusual attempts. The Privacy Policy explains this purpose and the checks we may make before responding.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, without asking you to disclose a wallet password.

Use the account support route and state that you are making a data access request. Provide your registered contact detail and enough context to locate the account; we may verify your identity first.

Yes. Contact account support with the incorrect field and the replacement detail. We may request verification before making a change, and the Privacy Policy explains how correction requests are handled.

Cookies can remember settings and support a working session, while some technical cookies help us identify account or device issues. Your browser controls let you restrict or remove them, subject to site functionality.

The policy describes our handling of data for the account path, including access from Indonesia. Eligibility depends on local law, so you should confirm that the service is available to you before proceeding.