Reference

slo1000 Privacy Policy For Your Account

Our Privacy Policy explains how slo1000 handles the details you provide when opening an account, confirming your phone, entering the lobby, or using DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record controlsAccount access requestsCookie choices

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

slo1000 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers data collected during account creation, phone verification, sign-in, wallet selection, support contact, and policy requests. We may use account details to confirm access, connect a payment record to the right account, detect unusual sign-in activity, and keep a reliable history of requests.

1
A DANA, OVO, GoPay or QRIS reference is handled as a transaction record, while a BCA, BRI, Mandiri or BNI bank-transfer reference may be retained for reconciliation and support. We do not ask you to send wallet passwords through account help. Access and eligibility depend on
2
local law, and this policy applies where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH DATA

Three Ways To Ask About Privacy

A clear contact route helps you act on the Privacy Policy without searching through unrelated account screens.

DATA PRACTICES

How We Handle Your Privacy Choices

We keep the Privacy Policy practical: each data action should connect to account access, security, payment reconciliation, support, or a request you make.

Account security

Phone verification is used before account access so we can connect a sign-in request to the correct profile. We may record security events such as device, browser, and sign-in time to investigate unusual access.

Wallet details

We handle DANA, OVO, GoPay and QRIS references as payment records, not as permission to enter your wallet. We do not ask for your wallet password, PIN, or one-time code through account help.

Bank references

A BCA, BRI, Mandiri or BNI transfer reference can help us match a cashier record to your account. We use the reference for reconciliation and support rather than requesting unrelated banking credentials.

Cookies and devices

Cookies can remember a session, preserve a language or region choice, and help us understand whether a sign-in page loads correctly. Your phone and desktop browser may store different session details after you sign out.

Retention periods

We retain account, security, and payment records for as long as needed for the stated purpose, account support, dispute checks, or a legal duty. A deletion request is assessed against those active record needs.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page and identify the revised date or subject where appropriate. Recheck the page before opening an account or submitting a new data request.

Privacy Policy Answers For slo1000

These Privacy Policy answers focus on the questions that matter before you open an account or connect a local wallet. They explain the data used at phone verification, how device and cookie records fit into access, and how to ask for a copy or correction. If your situation involves eligibility or access, the outcome depends on local law and the details of your account request.

It covers data from account creation, phone verification, sign-in, device sessions, wallet references, support requests, cookies, and policy changes. It also explains why we retain certain records, how we restrict internal access, and how you can request a copy or correction.

We use your phone number for account identification and the verification step required before account access. It helps us connect a sign-in request to the correct profile and investigate unusual activity without asking for your DANA, OVO, GoPay or QRIS password.

Yes. The policy covers DANA, OVO, GoPay and QRIS references connected to your account, including a payment date or status reference. These records help with reconciliation and support; they do not give us permission to access your wallet credentials.

Cookies can keep a sign-in session active, remember a language or region choice, and show whether an account page loads correctly. Your mobile browser and desktop browser can hold separate session records, so signing out on one device may not sign out the other.

You can ask account help for a copy of the personal data connected to your profile. Include the verified email or phone linked to the account, and we may request an account check before locating records or explaining the available delivery route.

Send a correction request through account help and identify the field that needs changing, such as a phone detail. We may repeat phone verification to protect the account, then assess the request against payment reconciliation, security, and legal record needs.

We keep records for the stated account, security, support, dispute, or legal purpose and remove them when those needs end, subject to applicable requirements. A deletion request is reviewed individually because some payment or security records may still be needed.

slo1000 Privacy Policy For Your Account

Three Ways To Ask About Privacy

How We Handle Your Privacy Choices

Account security

Wallet details

Bank references

Cookies and devices

Retention periods

Policy changes

Privacy Policy Answers For slo1000

01 What does the slo1000 Privacy Policy cover?

02 Why does slo1000 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How do cookies affect my slo1000 account?

05 Can I request a copy of my personal data?

06 How can I correct data held by slo1000?

07 How long does slo1000 keep account and payment data?

Related Pages