Reference

Privacy Policy for pakde 123

Our Privacy Policy explains how we collect, use, store, and protect the details connected with your pakde 123 account.

Account dataWallet recordsCookie choicesContact requests
pakde 123 Privacy Policy for pakde 123
CONTACT THE DESK

Privacy Policy Help For Account Questions

A clear contact path matters when you need to ask what data we hold or why a payment record appears in your account. Use the support route linked near your account and cashier area, then include the phone number connected with your account and a short description of the request. Do not send a full wallet password or one-time verification code. Our team can direct privacy questions, sign-in concerns, and receipt-status questions to the right handling path.

Team online

Policy questions

Ask how the Privacy Policy applies to your account, phone verification, device session, or contact history. Include only the details needed to locate the relevant account record, and keep passwords and one-time codes out of your message.

Wallet records

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks incorrect, send the payment date and reference shown to you. We use those details to check the record without asking you to reveal private wallet credentials.

Access concerns

When a phone verification step or unfamiliar device session raises a privacy concern, contact the account support route beside the cashier path. We can explain the next account step and help separate a genuine sign-in from a session needing review.

DATA HANDLING DETAILS

What We Do With Your Account Data

Our handling process follows the account journey rather than collecting details without a clear reason.

Account opening

When you open an account, we use the supplied account details to create your profile and begin phone verification. This lets us connect your sign-in with the correct account record before you access the lobby from a mobile browser or desktop.

Payment matching

A DANA, OVO, GoPay, or QRIS transaction can create a reference used to match your account and cashier status. Bank transfer and virtual account records serve the same operational purpose, without giving us your wallet password or banking sign-in.

Device signals

We may record limited device, browser, and session signals when you sign in. These details help us identify a session that does not fit your normal account pattern and support a safer response when access stalls.

Cookie controls

Cookies and similar storage can keep your session, language choice, and page state available as you move between account pages. You can manage browser cookie settings, although turning them off may interrupt sign-in or require you to verify the device again.

Retention periods

We retain account, payment, and support records only for the period needed to provide the service, resolve disputes, protect account access, or meet a legal obligation. When a record no longer has a valid purpose, our handling process removes or de-identifies it where appropriate.

Your requests

You may contact us to ask for access to personal data, correction of an inaccurate detail, an explanation of processing, or deletion where available. We may request account verification first so a private record is not disclosed to the wrong person.

Privacy Policy Questions Answered

These Privacy Policy answers address the account and payment questions we expect you to ask before using pakde 123. They cover access requests, wallet references, cookies, device sessions, corrections, and contact steps. If your situation is not covered, use the support route shown beside your account and cashier area, with only the minimum details needed to identify your request.

The Privacy Policy covers data linked to your account, phone verification, device sessions, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, security handling, and the ways you can request access or correction.

Phone verification connects the account to the contact detail you supplied and helps us respond to sign-in or privacy requests safely. We may use the verification status when you access the lobby from a new device, but you should never send us a one-time code in a support message.

Yes. The Privacy Policy covers payment references and cashier status connected with DANA and QRIS, as well as OVO, GoPay, bank transfer, and virtual account activity. We use those references to match an account transaction, answer receipt questions, and investigate an incorrect status.

Use the support route linked near your account and cashier area, state that you are making a personal data access request, and provide the phone number connected with your account. We may ask for an account check before releasing records so another person cannot obtain your private details.

You can request a correction when an account detail is inaccurate or out of date. Send the specific field that needs changing through the support path and explain the correct value. We may verify your account first, particularly when the request affects phone verification or payment matching.

Cookies can preserve your sign-in session, language choice, and page state between account screens. Browser controls let you remove or block them, but this may interrupt access or require another verification step. The Privacy Policy explains why these storage tools support account operation and security checks.

Send privacy, correction, deletion, or data-use questions through the support route shown with your account and cashier area. Access depends on local law, so we first verify the requester and then explain what can be supplied, changed, restricted, or retained for an operational or legal reason.