Reference

235slot Privacy Policy for Your Account

235slot Privacy Policy explains what we collect when you open an account, enter the lobby, or use DANA, OVO, GoPay and QRIS for a wallet action.

Clear data purposesWallet status controlsRequest-based support
235slot 235slot Privacy Policy for Your Account
HELP WITH REQUESTS

Get Privacy Policy Help Through Your Account

A clear support route helps when you want to ask about a record, correct contact details, or understand why a verification check is connected to your account. Open the account help path while signed in and include the relevant transaction reference or device detail. We use the request to locate the right record without asking you to send a wallet password or full payment credential.

Team online

Data access request

Ask us which account details, login events or payment references are linked to your profile. Include your registered phone number and a clear request so we can check identity before sharing account-related data.

Correction request

If your phone number or account detail is no longer accurate, use the support path to request a change. We may ask for a phone verification step before updating the record connected to your access.

Wallet record query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the payment reference rather than a password. We can compare the reference with the account status and explain the recorded result.

DATA CONTROL DETAILS

What Our Privacy Process Covers

We keep the Privacy Policy practical: account details support access, device signals support session checks, and payment references help us resolve wallet questions.

Account details

We may hold the phone number and account information you provide during account creation and phone verification. These details connect your sign-in activity with the correct profile and help us respond to a personal data request.

Device signals

Your browser, device type, session time and security events can be recorded when you sign in from mobile or desktop. We use these signals to spot unusual access without treating them as wallet credentials.

Cookies

Cookies can keep an active session available and help us understand whether a Privacy Policy page has been opened. You can manage cookie settings through your browser, although some account functions may then require another sign-in.

Payment references

DANA, OVO, GoPay and QRIS activity may create a reference, amount status and time record for account matching. Bank transfer and virtual account references can serve the same purpose when a wallet result needs checking.

Retention approach

We retain records for as long as their stated purpose requires, including account security, payment reconciliation, dispute handling or legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Your data request

You can ask us to access or correct personal details, and you can ask about deletion where that option applies. Send the request from your account support path; we verify your identity before changing or disclosing account data.

Privacy Policy Answers for 235slot Accounts

These Privacy Policy answers focus on the account actions that matter before access: phone verification, mobile sessions, wallet references, cookies and personal data requests. If your question concerns a particular DANA, OVO, GoPay or QRIS record, keep its reference available when contacting support. We can then explain the account status without asking for your private wallet sign-in details.

The 235slot Privacy Policy covers account details, phone verification, device and session signals, cookies, wallet references, support requests and retention. It explains why we use each category, how we protect account access, and how you can ask about or correct information linked to your profile.

Phone verification connects the sign-in request to the account owner before account access. It also helps us handle a correction or data access request safely. We use the verification step to reduce mistaken disclosure and do not ask you to provide a DANA, OVO or GoPay password.

Yes. The Privacy Policy covers the payment references and status details needed to match DANA or QRIS activity with your account. We may record a reference, time and result for reconciliation, but wallet credentials remain with the relevant payment service rather than being requested by us.

We may record device type, browser details, session time and security events connected with your sign-in. This helps us identify an unfamiliar access pattern on mobile or desktop and investigate an account question. These signals are handled for access security, not as a substitute for your identity request.

Open the signed-in account support path and state whether you want access, correction or deletion where available. Add your registered phone number and the relevant record reference. We verify identity first, then explain the next step and any reason a record must remain.

Retention depends on why the record exists. Account, payment and security details may remain while needed for account access, reconciliation, dispute handling or legal duties. When those purposes end, we follow the applicable retention process rather than keeping every record indefinitely.

Yes. Access and eligibility depend on local law. The Privacy Policy is available for you to read before creating an account, while particular account actions or data rights may vary by applicable requirements. Contact support if you need a policy answer for your account location.