Reference

pakde123 Privacy Policy For Your Account

Our pakde123 Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and connect DANA, OVO, GoPay or QRIS.

Account collectionWallet recordsCookie choicesRequest access
pakde123 pakde123 Privacy Policy For Your Account
PRIVACY CONTACT

Privacy Help From The Account Path

A clear contact path helps when a privacy request is more specific than a normal login question. Open the support link on the sign-in page and tell us whether you need access, correction, deletion or an explanation of wallet records. Include your account contact and the relevant date, but never send a password or full payment credential. We may ask for account verification before releasing protected details.

Team online

Access request

Ask for the account details we hold by using the privacy route linked from sign-in. We verify ownership first, then explain the available record and delivery step.

Correction request

If your phone number or account detail is wrong, identify the exact field and submit the request through support. We check the account before changing stored data.

Wallet query

For a DANA, OVO, GoPay or QRIS receipt question, provide its date and reference rather than full wallet credentials. Our support path can match the record safely.

DATA PRACTICES

Data, Cookies And Account Protection

We keep this policy practical: the details used to open an account are different from the device signals used to spot unusual sign-ins.

Data collected

We may store your contact details, phone verification result, sign-in time, device information and account actions.

Cookie use

Session cookies keep your account path working between sign-in and the lobby.

Account security

We use sign-in checks, phone verification and device signals to identify unusual access.

Retention timing

Account and wallet records remain available while needed for access, receipt checks, disputes or legal duties.

Data sharing

We disclose only the details needed for account support, payment matching, security checks or a lawful request.

Policy changes

If a material Privacy Policy change affects how we use account data, we place the updated wording on this page.

Privacy Policy Questions For pakde123

These Privacy Policy answers address the searches we hear most often before account access: what is collected, how wallet references are used, which device details matter and where to send a request. If your case concerns a specific receipt or sign-in event, include its date so we can locate the correct record.

It covers account details, phone verification, sign-in events, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Use the privacy contact route linked from the sign-in page. State that you want an access request, add your account contact and complete ownership checks before we release protected details.

Yes. The policy covers data created when you sign in on a mobile browser, move from login to the lobby or use phone verification. Device signals support access checks.

We keep limited references to match a receipt, confirm an account action and investigate a disputed wallet event. We do not need your full DANA, OVO, GoPay or QRIS password.

Yes. Identify the incorrect field through the privacy contact route, such as a phone number or contact detail. We verify account ownership before making a correction to stored data.

We retain each record only while it supports account access, receipt checks, disputes, security work or legal duties. After that purpose ends, we delete or anonymise the relevant details.

Yes. Access to pakde123 and the rights available for a particular data request depends on local law. Contact us through the account path and we will explain the applicable next step.