Reference

Privacy Policy for Your pg kuda Account

pg kuda Privacy Policy explains how we handle the account details, phone verification, wallet records and device data connected with your use of our lobby.

Account clarityWallet recordsDevice controlsPolicy requests
pg kuda Privacy Policy for Your pg kuda Account
ASK ABOUT PRIVACY

Get Help With A Privacy Request

A clear support route matters when a phone check, wallet reference or login event looks unfamiliar. Use our account support path to ask about the Privacy Policy, identify the account record involved and explain what you want changed. We may ask you to confirm account ownership before discussing private details. This keeps a request tied to the right account, whether you are checking a QRIS receipt from a mobile browser or a bank transfer record from desktop.

Team online

Account access

Use the account help path when you cannot recognise a login, phone verification event or device marker. We will ask for account details needed to locate the record, while avoiding disclosure before ownership is confirmed.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment reference and approximate date. This lets us trace the relevant record without requesting your full wallet credentials.

Privacy changes

Send a request when you want to access, correct or question personal data held under this Privacy Policy. We may reply with an account check before applying a change or explaining a retention reason.

DATA HANDLING

What The Privacy Policy Covers

We handle privacy requests through the same account controls that protect your lobby access. A phone verification step helps us distinguish you from someone attempting to use your account, while session and…

Account details

We use the details you provide during account creation and phone verification to identify your account, respond to requests and protect account access. Please keep those details current so a privacy request can be matched correctly.

Payment references

A DANA, OVO, GoPay or QRIS reference can connect a receipt with the correct account. Bank transfer and virtual account records serve the same reconciliation purpose; we do not need your wallet password to check status.

Cookies and sessions

Cookies may keep a signed-in session available and remember basic browser conditions. Your device path can differ between mobile and desktop, so clearing cookies may require another account check before access continues.

Security signals

Login time, device markers and failed account steps can help us spot activity that does not match your usual pattern. We use these signals for account protection and support investigation, not as a substitute for your confirmation.

Retention approach

We keep personal data only while it supports account operation, payment matching, disputes or legal duties. When a record is no longer needed for those purposes, we remove it or separate it from direct account identification where practical.

Your request rights

You can ask which personal data we hold, request an accurate correction, question a processing purpose or ask about deletion. Some records may remain when payment reconciliation, dispute handling or local law requires continued retention.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the records you are most likely to ask about before opening or using a pg kuda account. They cover identity checks, local wallet references, browser behaviour, account access and requests for changes. Where eligibility or access is discussed, it depends on local law.

It covers account details, phone verification, login and device signals, cookies, payment references, support requests and retention. The Privacy Policy also explains how you can ask for access, correction or deletion, subject to payment duties, dispute handling and local law.

Phone verification helps us confirm account ownership before access or a privacy request is handled. It can also help us investigate an unfamiliar login. We use the verification result for account protection and do not treat it as permission to collect unrelated phone data.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay and QRIS. We may use those records to match a receipt or investigate a payment question, while you should never send a wallet password or private security code.

We may receive browser type, device markers, session activity and basic login timing when you use a mobile or desktop browser. These details help keep sessions working and investigate unusual access. Clearing cookies can trigger another account check before your session continues.

Use our privacy support path and state whether you want access, correction, purpose clarification or deletion. Include the account contact details needed to locate your record. We may verify ownership first, then explain the result and any record that must remain.

We retain payment references only while needed for account operation, reconciliation, disputes or applicable legal duties. That can include bank transfer and virtual account records as well as wallet receipts. You can ask support why a particular record remains available.

Yes. Send the request through our support path with your account contact and the specific record involved, such as a QRIS receipt or login event. Access or eligibility depends on local law, and we will explain any limit that affects the request.