Reference

Privacy Policy For Your ollo2 slot Account

ollo2 slot Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice accessPolicy requests
ollo2 slot Privacy Policy For Your ollo2 slot Account
REQUEST HELP

Get A Clear Privacy Policy Contact Route

A clear support route helps you ask about Privacy Policy without sending sensitive wallet credentials. Sign in first when you can, choose the account or cashier-related path, and include the email or phone linked to your account plus a short description of your request. We use that context to locate the correct record and avoid asking you to repeat the same details.

Team online

Account access

If you cannot sign in, use the account support route and provide your registered contact detail. We can explain which identity record is needed for a Privacy Policy request without asking for your DANA, OVO or GoPay password.

Receipt questions

For a wallet receipt or QRIS status question, attach only the transaction reference and date shown by your payment service. We use those details to locate the account record and explain what Privacy Policy allows us to confirm.

Change requests

To request a correction or deletion review, name the specific account detail involved and send the request through the account support path. We may ask for a verification step before changing records connected with your access.

DATA HANDLING

What We Keep Secure For Your Account

Privacy Policy works alongside the account steps you already use: phone verification before access, a sign-in session on your device and a separate payment reference for each cashier event.

Identity details

We may store the name, phone number, email address and verification result you provide during account access. These details help us distinguish your account from another record and respond accurately when you ask about Privacy Policy.

Device signals

A phone or desktop session can create technical records such as browser type, approximate access time and security events. We use these signals to protect sign-in activity, not to request your device password or read unrelated files.

Cookie choices

Cookies can keep a session active and remember selected settings. You can manage cookie controls in your browser, although removing some cookies may require you to sign in again before reaching the lobby.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear through transaction references or bank details. We use those references to match status and receipts, while wallet passwords remain with the payment service.

Retention timing

We keep account, security and payment-reference records only while needed for service operation, dispute handling, fraud checks or legal duties. After that period, we remove or anonymise them according to the applicable retention need.

Your contact right

You can ask what personal details we hold, request a correction, question a processing purpose or ask about deletion. Send the request through account support with enough detail for us to verify the correct record.

Privacy Policy Answers For ollo2 slot

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access. We keep the route practical: check your registered contact detail, use the support path inside your account and share transaction references rather than passwords. If a question involves eligibility or access, the answer depends on local law.

The Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask about, correct or delete information connected with your account.

These wallet names appear because a payment can create a reference, status or receipt connected with your account. We use that limited payment context to match a cashier event. We do not need your wallet password, PIN or unrelated wallet activity for a Privacy Policy request.

Sign in where possible, open the account support route and ask for the personal data connected with your account. Include your registered phone number or email so we can verify the record. We may request an additional identity step before releasing account-related details.

Yes, you can ask us to correct an inaccurate name, phone number, email address or verification detail. Use account support, identify the field that needs changing and provide the updated value. We check the request before applying a change that affects account access.

We keep records for the period needed to operate the account, investigate security events, resolve payment disputes or meet legal duties. When the relevant need ends, we remove or anonymise the record. The actual period can differ by record type and applicable local law.

A new phone can create a fresh device signal and may trigger an account verification step. That record helps us compare sign-in activity and protect your session. Cookies may also be reset, so you might need to sign in again before opening the lobby.

Send the deletion request through the account support path and name the records you want us to assess. We verify the account first, then explain what can be removed and what must remain for security, dispute handling or legal duties where local law permits.