Reference

pgkuda Privacy Policy for Indonesia

Our Privacy Policy explains how we collect, use and protect the details connected with your pgkuda account, including phone verification, device activity and wallet records.

Account clarityWallet recordsCookie choicesData requests
pgkuda pgkuda Privacy Policy for Indonesia
CONTACT THE DESK

Where To Ask About Privacy

Questions about our Privacy Policy should reach us through the support route connected with your pgkuda account. Include the phone number on the account, the topic of your request and any relevant wallet reference, but do not send a password or full payment credential. We can then match your request to the correct account record and explain the next step without asking you to repeat unnecessary details.

Team online

Account support

Use the account support route when you need to ask what personal details are held for your login, phone verification or account status. We may ask you to confirm account details before discussing the record, so the request stays with the person who controls the account.

Wallet questions

For a privacy question linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, provide the relevant reference and date through support. We use that narrow context to locate the record without requesting your wallet PIN or complete banking credentials.

Data change request

Ask support to correct a phone number, explain a stored record or discuss deletion where the law allows it. We verify the account before making a change and may retain a limited record of the request to show how the Privacy Policy was applied.

SIX DATA CHECKS

What We Do With Your Details

A clear Privacy Policy should tell you what happens beyond the account form. We separate account details from the operational signals needed to keep a sign-in, wallet status or payment reference understandable.

Account records

We hold details such as your phone number, verification state and account settings to create and maintain your access. If you ask about these records, we first confirm the account connection before sharing or changing anything linked to your identity.

Device signals

A mobile browser or desktop session can produce device and sign-in signals, including session timing and security events. We use them to identify unusual access and help restore the correct account path; they are not a reason to request your private device password.

Cookie controls

Cookies and similar storage can keep a signed-in path working, remember selected settings and help us understand technical errors. Your browser provides controls for clearing or restricting them, although some account functions may not work as intended after those changes.

Wallet references

A DANA, OVO, GoPay or QRIS reference can appear beside an account transaction record. Bank transfer and virtual account references may also be retained for reconciliation. We do not need your wallet PIN or complete banking password to investigate a status question.

Retention period

We keep records only for as long as needed for the purpose described in this policy, account support, security checks or a legal requirement. When a record no longer has a valid purpose, our handling process considers removal or de-identification.

Account protection

Phone verification and sign-in checks help protect the account connected with your data. Keep your credentials private and contact support if access changes unexpectedly. We may ask for a limited confirmation before discussing a request, correcting details or changing account access.

Privacy Policy Answers For Your Account

These answers address the Privacy Policy questions we expect you to ask before opening or using a pgkuda account. They cover account data, device activity, cookies, wallet references and requests for access or correction. If your situation is not covered, use the account support route and include only the details needed to identify the issue.

The pgkuda Privacy Policy covers details linked with your account, including phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains why we use those records, how long we retain them and how you can ask about eligible changes.

We use your phone number to create and protect the account, complete the stated verification step and help match a support request to the correct account. Keep the number current so an access question can be checked without exposing account details to another person.

Yes. The Privacy Policy covers account-linked references for DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. These references help us trace a payment status without asking for your wallet PIN, banking password or full payment credential.

Contact us through the account support route and state whether you want access to a record or correction of a detail. Include your account phone number and the relevant topic. We verify control of the account before discussing the request or changing stored data.

We use cookies and related browser storage to keep account sessions working, remember selected settings and help identify technical errors. You can clear or restrict them through your browser. Some account paths may then require another sign-in or may not work correctly.

We retain account, support and wallet-reference records for the period needed for the stated purpose, security checks, account assistance or a legal requirement. When continued retention is not needed, our process considers removal or de-identification, subject to applicable law.

You can send a deletion request through account support, and we will assess which records can be removed where local law permits. Some records may need to remain for security, transaction tracing or legal reasons. We explain the outcome and any reason for continued retention.