Reference

Open slo100 Privacy Policy Clearly

slo100 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account detailsWallet recordsCookie choicesAccess requests
slo100 Open slo100 Privacy Policy Clearly
REQUEST HELP

Check Privacy Policy Support Paths

If a Privacy Policy question affects your account, we keep the request tied to the account details you already used rather than asking you to send unrelated documents.

Account access When you cannot open your account, tell us the phone or contact detail linked to it and state that your request concerns the Privacy Policy. We use an account check before discussing personal records, so another person cannot casually obtain your sign-in details.
Wallet record For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the payment reference and date rather than sending a full wallet password. We can compare the reference with the cashier record and explain what data was stored for that transaction.
Data request To ask for access, correction or removal where available, describe the exact record and the account step involved. We may request phone verification before processing the request, then explain any limits that depend on local law or an unresolved account matter.
HANDLING DETAILS

Browse How We Handle Your Data

The Privacy Policy is practical: it connects each data type with an account purpose and a way to contact us.

Account collection

During the account path, we collect the details needed to create access and complete phone verification. When you browse casino rooms, football, badminton or basketball areas, technical records may show the device and session needed to keep the account path working.

Payment records

A wallet entry can contain a method, amount reference, status and time. DANA and QRIS records are not the same as bank records from BCA, BRI, Mandiri or BNI, so we keep the reference needed to match a cashier event without treating it as your wallet password.

Cookies

Cookies can remember a session choice, support account continuity and help us see whether a page works on mobile. You can adjust cookie controls in your browser. Removing some cookies may require you to repeat the login or phone-verification step.

Account protection

We use account checks around sign-in, phone verification and sensitive data requests. If a wallet status stalls, we ask for a payment reference instead of a secret credential. These steps help us distinguish your request from an attempt to access another account.

Record retention

We keep personal and transaction records for the period needed to provide account support, resolve disputes, protect the service or meet applicable legal duties. The period can differ by record type, and access depends on local law when a retention duty still applies.

Changes and contact

You can ask us to correct a contact detail, explain a stored record or consider deletion where available. State the account step, device path or payment reference involved. We may verify your identity, record the request and explain the outcome through the support path.

Find Privacy Policy Answers

These Privacy Policy questions focus on the account and payment situations you are most likely to search for before opening access. Each answer describes the practical path we use, while legal rights and eligibility remain dependent on local law.

The slo100 Privacy Policy covers account details, phone verification, device and session records, cookie use, payment references and support requests. It also explains why we use those records, how we protect access, how long certain records may remain and how you can request access or correction.

Yes. The Privacy Policy covers the payment reference, method, status and time connected with a DANA or QRIS cashier event. It does not replace the separate privacy terms of your wallet provider. We do not need your wallet password to check a payment reference.

We use phone verification data to create and protect your account, confirm an access request and reduce the chance that another person discusses your private records. If you request a correction or account-data change, we may repeat the verification step before responding.

You can contact us with a clear request for the personal data connected with your account. Include the account contact detail and the record you want located. We may verify your identity, and the response or available action depends on local law and any required retention duty.

Use the support path and identify the incorrect field, such as a contact detail, phone-verification record or payment reference. Do not send a password. We will check the account, confirm what can be changed and explain any reason a correction cannot be completed.

The Privacy Policy allows records to remain for the time needed for account operation, payment matching, security, dispute handling or legal duties. Retention differs by record type. Where local law permits, we remove or reduce records when the operational reason has ended.

Cookies can help keep a mobile browser session and remember selected settings, so removing them may send you back through login or phone verification. Your browser controls cookie choices. The Privacy Policy explains this use, and access depends on local law.