Reference

p200m slot Privacy Policy for Your Account

p200m slot explains how we collect, use and protect the account, device and payment details connected with your access.

Account dataWallet detailsDevice choicesPrivacy requests
p200m slot p200m slot Privacy Policy for Your Account
ASK OUR DESK

Get Help With a Privacy Request

A direct support route helps you resolve privacy questions without guessing which account screen to use. Send us the email or phone detail linked to your account, describe the request, and include a payment reference only when it is relevant. Our team can explain a stored device record, help locate the privacy contact path, or clarify why phone verification is needed before account access.

Team online

Account Wallet Help

Choose Account Wallet Help when your request concerns an account identifier, DANA status, QRIS reference or wallet record. We use the details you provide to locate the correct account, then ask for an account step that helps prevent another person from changing your data.

Login privacy route

If a login or phone verification issue blocks your request, tell us the device type and the last successful access time. We can separate an access problem from a data request and avoid asking you to send passwords, wallet PINs or full payment credentials.

Payment receipt check

For a privacy question linked to a receipt, provide the transaction reference and payment rail, such as OVO, GoPay or bank transfer. We use that narrow reference to check the account record while limiting unrelated wallet details in the support conversation.

DATA CONTROL

Privacy Choices Across Your Account

Our privacy process follows the same account path you use to reach the lobby: verify the phone, sign in, check the relevant record and contact support when a change is needed.

Account details

We use your account contact details to provide access, send account notices and match a privacy request to the right record. If a correction is needed, tell us which field is wrong and complete the account check we request before we change it.

Device signals

A mobile browser may provide device and login signals that help us recognise unusual access. These signals can include browser type, session timing and network details. They support account security and are not a request for your phone contents or wallet PIN.

Cookies

Cookies and similar browser storage can keep a session active and remember essential access settings. You can manage browser permissions through your device settings, although removing necessary cookies may require you to verify your phone again before returning to the lobby.

Payment references

For DANA, QRIS, OVO, GoPay and bank transfer activity, we normally work with transaction references and status details rather than wallet passwords. A reference lets us investigate a receipt or withdrawal check without requesting unrelated payment credentials.

Security checks

We may compare login signals, phone verification and account activity when access or a withdrawal request appears unusual. This helps us protect your record. If a check pauses access, contact support with your account contact detail instead of sending a password.

Retention requests

We keep account, security and transaction records only while they support account operation, dispute handling or applicable legal duties. You can ask what remains connected with your account, request a correction, or ask whether deletion is available for a specific record.

Answers About p200m slot Privacy Policy

These answers address the questions we expect you to ask before opening an account or sending a privacy request. They cover account access, payment references, device records, cookies, corrections and deletion. If your situation is not listed, contact us through the support route and include only the details needed to identify your account.

The p200m slot Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references and security records. It also explains retention and how to request access, correction or deletion where that request is available under applicable requirements.

We use your phone number to create and protect account access, complete the verification step and help distinguish your request from another person’s request. We do not ask for your wallet PIN. Access and eligibility depends on local law, including any local requirement affecting account use.

Yes. The Privacy Policy covers references and status linked with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a receipt or account record, while avoiding requests for your wallet password or unrelated payment credentials.

You can contact us to request a correction when an account field, contact detail or transaction reference appears wrong. Include the affected field and the account contact detail used for access. We may complete a verification step before changing the record so your account remains protected.

Send a deletion request through our support route and identify the account record you want assessed. We will check whether deletion is possible or whether a record must remain for account security, dispute handling or legal duties. We will explain the result rather than removing data without review.

Our mobile browser path may use essential cookies or browser storage to maintain a session and remember access settings. You can manage permissions in your browser settings. Removing necessary storage may sign you out or require phone verification before you access the lobby again.

Use the support path connected with your account and describe the privacy request in plain English. Add your account phone or email, plus a payment reference only when needed. Never send a password or wallet PIN. Where local law permits, we will explain the next account step.