Reference

unoslot Privacy Policy For Indonesia Accounts

Your account details, wallet records and device access deserve clear treatment, so our Privacy Policy explains what unoslot collects and why.

Clear collection purposesWallet record contextAccount access choicesIndonesia policy wording
unoslot unoslot Privacy Policy For Indonesia Accounts
CONTACT PATHS

Where Privacy Questions Meet Account Help

A clear contact route helps when your Privacy Policy question involves a login, wallet reference or account record. Use the support path shown inside your account area and include the phone number linked to your account, the relevant date and the payment reference when available. We can then separate a data request from a cashier-status question without asking you to repeat unrelated details.

Team online

Account data request

Ask us to explain the personal data connected with your account. Include your linked phone number and the account step that prompted the question, so we can check identity before discussing records.

Wallet record query

For DANA, OVO, GoPay or QRIS records, send the payment reference and approximate time through the account support route. We use those details to locate the matching wallet entry without exposing another account's data.

Privacy contact route

If you want a correction, access copy or deletion request, state the exact change in your message. We may ask for phone verification before responding because account privacy depends on confirming who is making the request.

DATA HANDLING

What Happens To Your Account Data

We keep this policy practical by linking each data category to an account action you can recognise.

Collection at account opening

We receive the details you enter during account creation, including contact information needed for phone verification. If a field is required for account access, our support route can explain its purpose under this Privacy Policy.

Cookies and browser choices

Cookies can remember sign-in preferences and help connect a browser session to your account. Clearing cookies may require another login or phone verification, but it does not automatically erase wallet records held for policy purposes.

Payment references

A QRIS scan, DANA transfer or bank reference can remain linked to the account record needed for status checks. We use the reference to investigate a receipt question, not to display your wallet details to another account.

Account security signals

We record sign-in and device activity to identify unusual access and protect the account path. Moving between mobile and desktop may create separate events, while phone verification helps confirm access before account details are discussed.

Retention and deletion

We retain account and payment records for as long as needed for security, support and duties that depend on local law. A deletion request can be sent through support, and we will explain which records can or cannot be removed.

Changes to your records

You can ask us to correct inaccurate contact or account details through the support path. Mention the field that needs changing and complete any identity check requested before we alter information connected with DANA, OVO, GoPay or QRIS activity.

Privacy Policy Questions From Indonesia Accounts

These Privacy Policy answers focus on the records you are most likely to notice while opening an account, signing in or checking a wallet reference. They also explain how to ask for changes when your account uses a mobile browser, desktop session or local payment rail. If a situation is not covered, send the details through the account support path.

It covers account details, phone verification, login and device events, cookies, support messages and payment references. It also explains why we use those records for access checks, security, wallet-status questions and retention where local law permits.

We can store transaction references, status, amount and time linked to your account when you use DANA, OVO, GoPay or QRIS. These records help us match a receipt or status question, while wallet credentials remain outside the account record we handle.

Phone verification helps confirm that the person requesting account details or a data change is connected to the account. We may require that step before discussing records, correcting contact details or responding to an access request.

Yes, send an access request through the account support route and identify the linked phone number. We will verify the request, explain which records are available and note any payment or security records that must remain under retention rules.

Tell support which account field is inaccurate and provide the corrected detail. We may ask you to complete phone verification before changing it, especially when the request affects login access or records linked to DANA, QRIS or bank transfer.

You can clear cookies through your browser settings on mobile or desktop. After clearing them, you may need to sign in again and complete phone verification. Cookie removal does not automatically erase account, payment or security records retained for policy reasons.

Retention depends on the purpose of the record, including account security, wallet-status support and duties that depend on local law. You can ask support about a specific record, and we will explain whether it can be deleted or must remain.