Reference

Open oyoslot Privacy Policy for Your Account

Our Privacy Policy explains what oyoslot collects when you open an account, confirm your phone, access the lobby and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
oyoslot Open oyoslot Privacy Policy for Your Account
REQUEST HELP DIRECTLY

Check Privacy Policy Contact Paths

A clear contact path helps you control the personal data connected with your account. We ask you to start from the support contact displayed after login, include the phone number attached to your account, and describe whether you need access, correction or deletion. If a wallet record is involved, add the DANA, OVO, GoPay or QRIS reference without sharing a password or one-time code. We use those details to locate the right record.

Team online

Account support

Use the support contact shown inside your account for a Privacy Policy question. Include your registered phone number and request type so we can identify the correct account record.

Wallet evidence

For a DANA, OVO, GoPay or QRIS query, share the transaction reference and date only. We do not need your wallet password, card secret or one-time verification code.

Access requests

Ask for a copy, correction or removal of eligible personal data through the same support path. We may verify account ownership before changing or disclosing account details.

HOW WE HANDLE DATA

Explore How Privacy Policy Works

Privacy choices are easier when each data flow has a practical reason. We separate account access, wallet reconciliation, security checks and support handling, then limit staff access to the records needed for…

Account details

We use your phone number, verification result and login history to create access, confirm account ownership and investigate unusual sign-in activity. We do not ask for wallet passwords as part of this process.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment event with the correct account. We use status and reference data rather than private wallet credentials.

Cookies and devices

Cookies can remember a session, language setting or consent choice on your phone or desktop browser. You can clear browser storage, although doing so may require another account login.

Security controls

We use account permissions, login checks and phone verification before sensitive account access. Never send a one-time code through support, even when asking about Privacy Policy rights.

Retention approach

We keep personal data only for the period needed for account operations, transaction matching, security review or a legal requirement. When a record is no longer needed, our process addresses its removal or restriction.

Changing your data

To correct a phone number, request a data copy or ask about deletion, contact us from the account support path. We may request an account step to prevent changes by another person.

Browse Privacy Policy Answers Before Opening

These answers address the Privacy Policy searches we expect from Indonesian account holders. If your situation involves a specific wallet reference, device or account step, include that detail through the support contact displayed after login. We can then respond to the record involved rather than giving a general reply.

It covers account details, phone verification, login events, cookies, device preferences, wallet references, support requests, security checks and retention. It also explains how to request access, correction or removal.

We use your phone number to create account access, complete phone verification and help confirm ownership when you contact support. Keep it current so a correction request can be handled safely.

Yes. We may handle DANA, OVO, GoPay and QRIS status, references and timestamps to reconcile an account transaction. We do not need your wallet password or one-time code.

Use the support contact shown inside your logged-in account and request a data copy. Include your registered phone number, but do not include a wallet password or one-time verification code.

Yes. Send a correction request through the account support path and identify the detail that needs changing, such as a phone number. We may verify ownership before applying the change.

Cookies or similar browser storage can retain a session, language setting or consent choice. Clearing them may sign you out or remove a saved preference, after which you can choose again.

Some requests, retention duties and account actions depend on local law. Our Privacy Policy applies where local law permits, and support can explain the next account step for your request.