Reference

gudangcuan Privacy Policy Explained

gudangcuan keeps this Privacy Policy practical: you can see what account, device, cookie and wallet details we collect, why each detail is needed, and how to ask for…

Account recordsWallet detailsCookie choicesAccess requests
gudangcuan gudangcuan Privacy Policy Explained
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path matters when a record looks wrong or you want to understand a data decision. Use the support route linked near your account and cashier area, and include the phone number on the account plus the relevant receipt or login date. We use those details to locate the correct record without asking you to send a wallet password.

Team online

Account access

If phone verification blocks your account, tell us the device type and the approximate time of the attempt. We use that match to check access logs under this Privacy Policy.

Wallet status

For a DANA, OVO, GoPay or QRIS question, attach the payment reference with sensitive wallet credentials removed. We can compare the reference with our transaction record.

Privacy request

To request a copy, correction or deletion review, state the account phone number and the exact request. We may ask for an account check before changing personal records.

DATA HANDLING

Six Practical Privacy Controls

Our handling process follows the account actions you actually take: signing in, completing phone verification, checking a wallet reference or contacting support.

Collected account details

We may hold your phone number, verification result, account identifiers and support messages. These details connect your request to the right account and help us avoid changing another person’s record.

Device activity

Login time, browser type, operating system and security signals can be recorded when you use a mobile browser or desktop. These signals help us examine unusual access without reading private device content.

Cookie choices

Cookies can keep a session open, remember selected settings and help us understand whether a page loads correctly. You can manage cookie settings in your browser, although some account steps may then need repeating.

Account protection

Never send us your login password or wallet PIN. When a phone verification issue or QRIS receipt needs checking, we rely on account identifiers and transaction references instead of secret credentials.

Storage period

We retain account, security and transaction records only for the period needed for account service, dispute handling, fraud checks or legal duties. When a record is no longer needed, our process removes or anonymises it.

Change requests

You can ask us to correct inaccurate account details, explain a processing purpose or assess a deletion request. Send the request through support with your account phone number and a precise description.

Privacy Policy Questions Before Account Access

These answers address the Privacy Policy questions we expect before you create an account or connect a local wallet. If your case involves a specific phone verification event, QRIS receipt or device session, include that context when you contact us.

It covers account details, phone verification, login activity, device signals, cookies, support messages and payment references connected with your access. It also explains our use, storage and request processes.

Yes. We may store a DANA or QRIS transaction reference, status and related account match. We do not need your wallet PIN, password or full private wallet credentials to check a receipt.

Device type, browser and login timing help us identify unusual access and investigate a failed phone verification step. We use these signals for account protection and do not treat them as access to private device files.

You can contact support and request a copy of the personal details connected with your account. Include your account phone number so we can verify the request and locate the correct record.

Send a correction request through the account support route with the phone number on your account and the field that appears wrong. We may complete an identity check before editing the record.

We keep account, security and transaction records for the period needed for service, dispute handling, security checks or legal duties. Records no longer needed are removed or anonymised through our retention process.

You may request deletion through support, and we assess it against service, security and legal needs. Some transaction or account records may remain when a valid retention duty still applies.