Reference

juara189slot Privacy Policy for Your Account

Your account record, wallet selection and device session are covered by the juara189slot Privacy Policy, so you can see what we collect and why before opening an account.

Account clarityWallet contextDevice safeguardsPolicy access
juara189slot juara189slot Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Near Account Access

A clear support route matters when a privacy request and an account check meet. We ask you to use the signed-in support path first, because it helps us connect your request with the right account record without asking you to post personal details publicly. If you are in Jakarta or elsewhere in Indonesia, the same account-based route applies where local law permits.

Team online

Account support

Open the support path from your signed-in account when you want to ask what personal details we hold or why a phone verification record is needed.

Wallet reference

Include the relevant DANA, OVO, GoPay or QRIS reference when your request concerns payment data, so we can locate the record without requesting your full wallet credentials.

Correction request

Tell us which account field needs changing and provide enough account context for matching. We may ask for an account step before making a privacy-related correction.

DATA HANDLING

What You Can Check and Change

We keep this policy area practical: account records support access checks, device signals help identify a familiar session, and payment references help reconcile a request.

Collected account data

We may hold your account identifier, phone verification result, sign-in record and selected wallet route.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account details may appear as transaction references.

Cookies and sessions

Cookies and similar session data can remember sign-in state, language choices and device continuity.

Account security

A new device or unusual sign-in can trigger an account check before access continues.

Retention choices

We retain account and transaction records only as needed for the stated account, security and legal purposes.

Your request route

You may ask for access, correction, deletion or clarification through account support.

Answers About Your Privacy Policy

These Privacy Policy answers focus on the questions you may have before creating or using an account. We cover phone checks, device sessions, cookies, local wallets and request handling, so the policy is easier to apply to your own account. If your situation is different, use the signed-in support path and mention the specific record.

It covers account details, phone verification, device sessions, cookies, payment references and requests to access or change records. It also explains why we use each category and when local rules affect a request.

These wallet names can appear in account and transaction references. We use the selected rail to match status or receipt details, while your wallet password and private wallet credentials should remain outside our support requests.

We may retain the result and related account reference so we can confirm account control during access checks. Ask support about the specific record, its purpose and its retention period where local law permits.

Cookies can keep a session active and remember selected settings on your browser. You can clear or restrict them in browser controls, but doing so may lead to another sign-in or phone verification step.

Yes. Use the signed-in support path, identify the field that is wrong and explain the requested correction. We may verify account control before changing it, and the route depends on local law.

Send a deletion request through account support with the affected account details. We assess which records can be removed and which must remain for security or legal purposes where local law permits.

Use the account support path and describe the sign-in issue without sending a wallet password. We may ask for a phone or account check before discussing personal data linked to the record.