Reference

parlay212 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, browse Auto Roulette or use DANA and QRIS, and how we use…

Account dataWallet detailsDevice accessPolicy requests
parlay212 parlay212 Privacy Policy for Your Account
NEED A DATA PATH

Ask Us About Your Account Data

A clear support route matters when a privacy request meets a login or wallet record. Start from the support path connected to your account and tell us whether you need access, correction, deletion review or an explanation of a payment record. Include the relevant account detail, but never send a password or full wallet security code. We use the account step to direct the request safely.

Team online

Access request

Ask for the personal data linked with your account through the available support path. We may check account ownership before discussing sign-in records, device activity or wallet references.

Correction request

If your phone detail or account record needs an update, describe the exact correction. We compare the request with the account step before changing information connected to DANA, OVO or another wallet.

Payment privacy help

For a QRIS, bank transfer or virtual account question, provide the date and visible reference only. We can trace the status without asking you to disclose a password or security code.

ACCOUNT SAFEGUARDS

Browse Our Data Handling Commitments

Privacy works best when each account step has a clear reason. We separate account access, payment matching and security checks, then limit staff access to the records needed for the request.

Account details

We use the details you provide during account creation and phone verification to connect access with the correct account. Keeping those details accurate helps us handle privacy requests without exposing another account.

Device signals

Mobile and desktop access can create technical records such as browser type, session time and security events. These signals help us examine unusual sign-ins without reading unrelated content on your device.

Cookies

Cookies or similar storage may remember a session, language setting or page preference. You can adjust browser controls, although disabling some storage may affect the account path used to reach the lobby.

Wallet records

DANA, OVO, GoPay and QRIS references are used to match payment status with the right account. Bank transfer and virtual account details may remain for reconciliation, security checks and required records.

Retention period

We retain different records for different operational, security and legal reasons. When a retention period ends, records are deleted, anonymised or kept only where a valid obligation requires continued storage.

Change requests

You can ask us to access, correct or review deletion of eligible data through the account support route. We may request account verification before making a change or sharing any record.

Find Privacy Policy Answers Quickly

These Privacy Policy answers cover the searches we expect from someone deciding whether to open an account from Indonesia. They focus on account records, wallet references, device activity, cookies, requests and local access wording. If your situation is not covered, use the account support path and describe the specific record or account step involved.

The Privacy Policy covers account details, phone verification, device and session records, cookies, wallet references, support requests, retention and the way we handle access or correction requests.

Phone verification helps connect account access to the correct person and supports security checks. We may use that record when handling a data request, login concern or account detail correction.

Yes. The Privacy Policy explains how DANA, OVO, GoPay and QRIS references can match a payment status to your account, while bank transfer and virtual account records support reconciliation.

We may receive technical details such as device type, browser, session time and security events when you sign in from mobile or desktop. These records help examine unusual account access.

Use the account support path and ask for a data access request. Include enough account detail for verification, but do not send your password, wallet PIN or full security code.

You can request a correction or ask us to review deletion of eligible data through support. We verify account ownership first, and some records may need to remain for security or legal reasons.

Yes. Access and eligibility depends on local law. The Privacy Policy applies to the account and data route available in your location, including the steps shown during sign-in.