Reference

ransslot Privacy Policy For Your Account

Your ransslot Privacy Policy gives you a clear view of the data connected with your account, from phone verification to DANA, OVO, GoPay and QRIS records.

Clear data purposesWallet record contextMobile cookie choicesDirect account requests
ransslot ransslot Privacy Policy For Your Account
CONTACT ROUTES

Privacy Questions From The Cashier Path

A privacy request should reach the support route inside your signed-in account, especially when it concerns a wallet status or payment receipt. Include the phone number on the account, the relevant request date, and the DANA, OVO, GoPay or QRIS reference shown to you. We use those details to locate the correct record without asking you to send a full password or security code. Account access still depends on local law.

Team online

Account support

Open the support path after signing in and state whether you need a copy, correction, deletion request or explanation of account data. We may ask for phone verification before discussing private records.

Payment receipt

For a DANA, OVO, GoPay or QRIS privacy question, share the visible reference and date rather than secret wallet credentials. We compare that reference with the account record and payment status.

Security concern

If an unfamiliar sign-in or device appears, contact support through the account route and change your password. We use the reported time, device signal and phone check to trace the event.

HANDLING CONTROLS

Cookies, Phone Checks And Mobile Access

Our privacy controls follow the real steps you take: opening an account, confirming a phone number, moving between the lobby and cashier, and returning from a mobile browser.

Account details

We use your phone number and account identifiers to create the requested record, confirm ownership and connect your support request with the right account. Phone verification may be required before private details are shared.

Payment records

DANA, OVO, GoPay and QRIS references help us match a deposit or withdrawal instruction with your account. We do not need your wallet password, card secret or one-time security code for that match.

Cookies

Cookies and similar device signals help keep a mobile browser session connected to the correct account and remember security preferences. Clearing them can sign you out or require phone verification again.

Security checks

We compare sign-in activity, device signals and phone verification when an account request appears unusual. These checks protect private records and help us investigate access that you did not initiate.

Retention period

We retain account, payment and support records for the period needed to provide the requested service, resolve a dispute or meet a legal duty. When that period ends, records are removed or anonymised.

Change request

Ask through the signed-in support path to correct account data, request a copy or ask whether removal is available. Include the affected field and account phone number so we can locate it.

Privacy Policy Questions For ransslot

These answers address the privacy searches we hear most often before an account is opened. They cover the data linked to local wallets, mobile sessions, phone verification, access requests and contact steps. If your situation is not listed, use the signed-in support route with the smallest amount of necessary detail. Account eligibility depends on local law.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone number to create and identify the account, complete the account step before access, connect support requests and help confirm that a private data request comes from you.

Yes. The Privacy Policy explains that cookies and device signals help maintain a signed-in mobile browser session and security settings. Clearing them may sign you out or trigger phone verification.

We use the visible payment reference, amount and date to match a wallet request with the correct account and status. We do not ask for your wallet password or one-time code.

Yes. Use the signed-in support path and state whether you want a copy or correction. Include your account phone number and the affected detail; we may verify ownership first.

Send a removal request through account support. We check whether the data is still needed for an open payment query, dispute, security matter or legal duty before confirming what can be removed.

The page is written for Indonesia, but account access and eligibility depend on local law. We apply the policy where local law permits and can explain region-related handling through support.