Reference

sl999 Privacy Policy for Your Account

Clear control over your account data starts with knowing what we collect, why we use it and how you can ask for changes.

Account dataWallet recordsCookie choicesMobile access
sl999 sl999 Privacy Policy for Your Account
PRIVACY CONTACTS

Get Help With Account Data

A direct contact path helps when your privacy request is connected to login, a wallet reference or a device session.

Account support chat Use the support chat linked from your signed-in account to ask about collected data, phone verification records or a privacy request. We will ask for enough detail to locate your account.
Wallet record help If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the relevant date and reference through the account support route. Do not share your wallet PIN or password.
Access issue route When a mobile browser session or login check blocks your request, tell us the device path and account email or phone detail. We can separate access troubleshooting from the privacy request.
DATA HANDLING

What We Do With Your Privacy Choices

We keep this Privacy Policy practical by linking each data use to an account action you recognise.

Collected account details

We may collect your name, contact detail, phone verification result, login activity and support messages. These records help us provide account access and respond when you ask about your personal data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can identify a transaction or status. We do not need your wallet PIN to match that record with your account.

Cookies and devices

Cookies and device signals may remember a session, reduce repeated login checks or flag unusual access. You can manage browser cookie settings, though disabling them may affect account access.

Account security

Phone verification before account access helps connect a request to the correct account. Keep your password and wallet credentials private, and contact support if a session looks unfamiliar.

Retention approach

We retain account, support and transaction records for as long as needed for the stated service, security, dispute and legal purposes. Retention can vary when local law requires a different period.

Changing your details

Ask through the signed-in support route if your contact detail, device record or account data needs correction. We may verify ownership before changing or disclosing private information.

Privacy Policy Answers for sl999

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. They also explain what to prepare when you contact us about data, cookies or a device session in Indonesia.

It covers account registration, phone verification, login and device signals, cookies, support messages, payment references and requests to access, correct or remove personal data where local law permits.

No. The Privacy Policy describes payment references used to match DANA, OVO, GoPay or QRIS activity with your account. Your wallet PIN and password should never be sent through support.

Phone verification helps connect account access and privacy requests to the correct person. It can also help us investigate an unfamiliar login without asking you to reveal a wallet credential.

Cookies can keep a mobile or desktop session recognised and support security checks. You can adjust browser settings, but disabling required cookies may prevent normal sign-in or privacy-request access.

Yes, contact us through the signed-in support route and state that you want an account-data copy. We may verify ownership first, then handle the request according to local law.

Send a correction request through account support, identifying the field that is wrong and the correct detail. For safety, we may ask for phone or account verification before making changes.

It explains our data handling for Indonesian account access, including wallet references and mobile sessions. Service availability and eligibility depends on local law, so check the applicable rule before opening access.