Reference

paduka500 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, use DANA or QRIS, and contact support.

Account dataCookie choicesWallet recordsYour requests
Explore Our Lobby Read FAQ
paduka500.xyz page image
CONTACT YOUR WAY

Who To Contact About Your Data

A clear contact route matters when a privacy request is time-sensitive. Start from the support chat linked in your account area, describe the account step involved, and include only the details needed to locate the record. We can then separate a login question from a wallet-status question without asking you to send a password or full wallet credentials.

Team online

Support chat

Use the on-site support chat for a copy request, correction request or question about how your account details are used. We may ask for your registered phone number to locate the account.

Wallet records

If your privacy question concerns DANA, OVO, GoPay or QRIS, mention the payment rail and transaction reference. Do not send a wallet PIN, password or one-time security code.

Account route

For sign-in, phone verification or cookie concerns, open the account support path from the same device you normally use. This helps us check the relevant session without exposing unrelated records.

YOUR DATA CONTROLS

Account Security And Cookie Choices

We treat privacy as an account process rather than a paragraph hidden away. The controls below describe how we handle records created by sign-in, payment status, device use and support contact.

Data we collect

We may hold your name or account label, registered phone number, verification result, device signals, session events and payment references. These details help connect your account activity without storing your wallet password.

Cookie settings

Cookies can keep your sign-in session and selected page settings available while you move between the lobby and account area. Your browser controls let you block or remove them, though some account steps may need them.

Account security

Phone verification, session checks and unusual-login signals help protect access. Keep your password and one-time codes private, and contact support if a device reaches your account without your permission.

Payment matching

For DANA, QRIS, bank transfer and virtual account activity, we use references and status details to reconcile your request. The payment provider remains responsible for credentials held inside its own wallet or banking service.

Retention periods

We keep records for account operation, security checks, dispute handling and legal duties, then remove or restrict them when they are no longer needed. The exact period can depend on local law and the record type.

Requests and corrections

You can ask us to access, correct or delete eligible account data through support chat. We verify ownership before making a change, so another person cannot alter your phone, wallet status or sign-in record.

Privacy Policy Questions For Your Account

These answers address the searches we hear around paduka500 Privacy Policy, from phone verification to payment references and device cookies. Read them before opening an account, then use the support route if your request concerns a particular record or sign-in event. Account availability remains where local law permits.

It covers account details, phone verification, device and session signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm that you control the registered account before access or account changes. It also supports security checks when a new device or unusual sign-in event appears.

No. We use payment references and status details to match a request, but your DANA, OVO, GoPay or QRIS credentials stay with the relevant payment service.

Open the support chat from your account area and ask for a data copy. Include your registered phone number and the record type you need, while leaving out passwords and one-time codes.

Yes, you can request a correction through support chat. We first verify account ownership, then assess the requested change against security needs, payment records and retention duties that apply where local law permits.

The period depends on the record and the reason it was created, such as account security, payment reconciliation or a dispute. We remove or restrict records when operational and legal needs end.

Use your browser settings to block, delete or limit cookies. Essential session cookies may be needed for sign-in and phone verification, while preference cookies can usually be adjusted separately.

Related Pages

paduka500 Indonesia About Us Access guide Mahjong Ways Dota 2