Reference

sembahslot Privacy Policy for Your Account Data

sembahslot Privacy Policy explains what we collect when you create an account, verify your phone, use DANA or QRIS, and browse from a mobile device in Surabaya or…

Account dataWallet recordsCookie choicesSecurity steps
sembahslot sembahslot Privacy Policy for Your Account Data
CONTACT PATHS

Get Privacy Help Through Your Account

A privacy question should not require you to repeat your account story.

Access requests Ask us to confirm whether we hold account data connected with your registered phone…
Correction requests If your phone, email or profile detail is inaccurate, contact support from the account…
Payment references For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and status…
HANDLING YOUR RECORDS

Your Data Path From Login to Retention

We treat privacy as an account process rather than a footer link. The policy explains why a phone check is requested, how cookies support sign-in and preference storage, and when transaction or…

Phone verification

Before account access is completed, we use the registered phone step to reduce mistaken identity. We record the verification result and related time, not your private wallet password.

Cookie controls

Essential cookies help maintain a signed-in session and remember required settings. Browser controls can remove optional cookies, although clearing essential data may require another login.

Device signals

A mobile browser or desktop session may create security signals such as device type, login time and network details. These signals help us investigate unfamiliar access to your account.

Payment matching

A wallet reference, QRIS receipt or bank transfer detail can connect a cashier event with your account. We use the smallest practical set of payment data for reconciliation.

Retention decisions

We keep records only as long as needed for the stated account, security, payment or legal purpose. When a record is no longer needed, our process removes or de-identifies it.

Policy requests

You can ask what data we hold, why it is used, or whether a correction is possible. Contact us through the signed-in support path and complete ownership checks when requested.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy questions cover the account actions you are most likely to take: opening access, verifying a phone, using a local wallet, browsing on mobile and contacting support. We keep each answer tied to the records our team can actually locate and explain. If your situation involves local eligibility, access depends on local law.

It covers account details, phone verification, login and device signals, cookie use, payment references, support messages, retention and requests to access or correct your personal data.

Phone verification helps connect account access with the correct owner and supports security checks. We retain the verification result and related timing, while your DANA or OVO password remains private.

Yes. The Privacy Policy explains how we use DANA, OVO, GoPay and QRIS references, status, amount and timing to match cashier activity, receipts and account questions.

You can contact us through the signed-in support path and request access to data linked with your account. We may verify your phone or email before responding to protect the record.

Send a correction request from your account support route, name the inaccurate phone, email or profile field, and complete any ownership check. We assess the requested change before updating records.

Essential cookies help keep your mobile session active and save required settings. Browser controls can remove optional cookies, but clearing essential cookies may sign you out and require another login.

Retention depends on the reason for collection, including account security, payment reconciliation and legal duties. When a record is no longer needed, we remove or de-identify it where permitted.