Reference

Privacy Policy for unoslot Accounts

Your unoslot account details, wallet records and device signals are handled under one clear Privacy Policy, so you can understand what supports login and payment checks.

Account clarityWallet recordsDevice controlPrivacy requests
unoslot Privacy Policy for unoslot Accounts
PRIVACY HELP ROUTES

Where To Ask About Your Data

A clear contact route matters when a Privacy Policy question concerns your own account rather than a general request. Start from the support path connected to your unoslot account and include the phone detail used at registration, the subject of your request and any relevant wallet reference. We use those details to locate the correct record without asking you to send a password or security code. If you are in Jakarta or elsewhere in Indonesia, keep the request focused on data access, correction, deletion or wallet-status records.

Team online

Account data request

Ask which account details we hold by using the privacy contact route shown after login. Include your registered phone detail and the specific record you want checked; never include your password, one-time code or full wallet credentials in a request.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, provide the transaction reference and date through our support path. We can check the status attached to your account while keeping your wallet PIN and banking login outside the request.

Correction or removal

If a Privacy Policy request asks us to correct or remove data, tell us which field or record is involved and why. We may verify account ownership through the phone detail on file before changing anything linked to your login.

DATA HANDLING DETAILS

What We Do With Account Records

The practical side of our Privacy Policy is tied to the account steps you can see: phone verification before account access, sign-in activity, wallet status and the device…

Account details

We use the details entered during account creation, including your phone contact, to identify your account and complete the clear…

Wallet references

Payment records can contain a rail name such as QRIS or bank transfer, a reference, amount status and account connection.

Browser cookies

Cookies and related browser storage can keep a session active, remember a selected setting and help identify unusual sign-in behaviour.

Device signals

We may record device type, browser details, language setting, network indicators and sign-in time for security and troubleshooting.

Retention approach

We keep account, support and transaction references for as long as needed for service operation, security checks or legal duties.

Your request path

You can ask for a copy, correction, restriction or eligible removal of personal data through the privacy contact route.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening an account. They cover the records linked to login, local payment references, cookies, device access and requests made through support. If your situation is specific, use the privacy contact route shown within your account and describe the record you want us to check.

The unoslot Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains retention, security handling and how you can request a change.

We may collect the details you enter for an account, your registered phone contact, verification status, login events and device or browser signals. If you use a wallet rail, we may also retain a transaction reference and status. We do not ask for your wallet PIN.

A DANA or QRIS transaction can create a reference, status and account connection that help us match your payment question. The same approach can apply to OVO, GoPay, bank transfer and virtual account records. Your wallet credentials remain with the relevant payment service, not in our support request.

Yes. Use the privacy contact route available after account access and name the data you want copied or corrected. Include your registered phone detail so we can verify ownership. We may retain some records when security, service operation or legal duties require it.

Cookies can keep your session settings and help detect unusual sign-in patterns, while device and browser signals support security checks and troubleshooting. Mobile browser access may produce different signals from desktop access. You can clear cookies in device settings, but another account check may follow.

We retain account, support and payment references only for operational, security or legal needs that apply to the record. When that need ends, we remove, anonymise or restrict the data through our retention process. Ask through the Privacy Policy contact route for a record-specific explanation.

No. This Privacy Policy explains data handling; it does not change access or eligibility requirements. Account access depends on local law, and payment or account features are available where local law permits. If you need clarification about your data, contact us through the account privacy route.