Reference

sl99 Privacy Policy for Your Account

Clear control over your account, wallet and device data is the purpose of the sl99 Privacy Policy.

Account dataWallet recordsCookie choicesContact requests
sl99 sl99 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Policy Help From Your Account

A clear contact path helps when you need a copy of your data, a correction, or an explanation of a wallet record.

Account access Use the support route shown after sign-in for a Privacy Policy request.
Wallet records For a DANA, OVO, GoPay or QRIS query, include the account reference and transaction…
Data changes Ask us to correct account data through the listed contact route.
HANDLING PRACTICES

How We Apply the Privacy Policy

We apply this policy to practical account events rather than collecting data without a purpose.

Data collected

We may collect registration fields, phone verification results, login timestamps, device details, support messages and transaction references linked to DANA, OVO, GoPay, QRIS or bank transfer activity.

Cookie settings

Cookies can support sign-in continuity, security checks and page preferences. Your browser controls provide a way to limit optional cookies, while required account cookies may remain active.

Account security

We use phone verification and account activity checks to reduce mistaken access. Never send us your password, full wallet PIN or one-time verification code through a support message.

Retention period

We retain account, security and transaction records only for the period needed for account operation, dispute handling, legal duties and record integrity, then remove or separate them.

Sharing boundaries

We share data only where needed to operate account services, process a selected wallet route, protect access, answer a support request or meet a lawful requirement.

Requesting changes

You can ask for access, correction or deletion through the account contact path. We verify the request first and explain any record that must remain under local rules.

Privacy Policy Questions for sl99 Accounts

These Privacy Policy answers focus on the account steps you are most likely to question before opening an account or contacting support. We keep the request path practical, including what to provide when a DANA, QRIS or device record needs checking.

It covers account registration, phone verification, sign-in events, device signals, cookie use, support messages and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account to the correct person, reduce mistaken access and confirm requests to change account data. We record the verification result rather than asking you to share a code in support.

Yes. The Privacy Policy covers references created when you select DANA or QRIS, including account matching, transaction status and support checks. Do not send a wallet PIN or full security credential.

You can request access through the contact route shown on the site or inside your account. Include your registered phone number and request scope; we verify ownership before releasing account-related data.

Send a correction request through the account support path and identify the field that is wrong. We may confirm your phone ownership, then update eligible records or explain why a record must remain.

Retention depends on the purpose of each record, including security, dispute handling, account operation and legal duties. When the applicable period ends, we remove, aggregate or separate the record where practical.

Use the public contact route displayed on the site and provide your registered phone number without sending a password or one-time code. We can use verification questions to locate the correct account request.