Reference

slot168 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a slot168 account, connect DANA or QRIS, and move from login to the lobby.

Account recordsWallet checksCookie choicesSecure sessions
slot168 slot168 Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Policy Help Near Account Support

A clear contact path matters when a Privacy Policy question affects your login or wallet status. Send our support team the email or phone number attached to your account, explain the request in plain English, and include a payment reference only when it is relevant. We use those details to locate the correct record without asking you to send a password or full wallet credentials.

Team online

Account requests

Ask us to correct your name, phone number or email through account support. We may request a matching account detail before changing records, which helps prevent an unauthorised request.

Wallet questions

For DANA, OVO, GoPay or QRIS status questions, provide the transaction reference and approximate time. We check the account record and payment status without asking for your wallet password.

Policy contact

Use the support contact path for access, cookie or retention questions. Describe the Privacy Policy request clearly, and we will explain any identity check or legal reason affecting the response.

HOW WE HANDLE DATA

Privacy Choices Across Your Devices

Our handling process follows the account journey rather than collecting unrelated details. A phone sign-in, desktop session, QRIS payment reference and support conversation can each create separate records, so we connect them…

Account data

We collect details you provide during account opening, including contact details used for phone verification. We use them to identify your account, send service replies and match a request to the right record.

Device signals

Your phone or desktop may share browser, device and login signals. We use these signals to detect unusual access, protect sessions and investigate a wallet status question without reading unrelated device content.

Cookies

Cookies can keep a session active, remember selected settings and help us understand which policy page was opened. You can manage cookies through your browser, although some account functions may then need another login.

Account security

Phone verification and sign-in checks help us separate your account from an unapproved request. Never send a password or wallet PIN in support messages; we use account details and references instead.

Retention

We keep account, payment reference and support records only as long as operational, security or legal needs require. When a record is no longer needed, we remove it or make it unable to identify you.

Your request

You can ask for a copy, correction or deletion of personal data through support. Tell us the account email or phone number, and we may verify ownership before making a change.

Privacy Policy Answers for slot168

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. We keep the wording practical: what we collect, why a device signal appears, how payment references are used and where to send a request. If your situation is not listed, contact support with the account detail needed to locate your record.

It covers data collected during account opening, phone verification, login, support contact and wallet activity. It also explains cookies, device signals, retention, security checks and how to request access or corrections.

We use your phone number to support account identification and phone verification before account access. It can also help us match a support request to your record, but you should never send a wallet PIN.

Yes. We may keep payment references, status results and timing connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity so we can check an account request.

Contact support using the account email or phone number linked to your profile. State whether you want access or a correction, describe the record, and complete any ownership check we request.

Cookies may maintain your sign-in session, remember settings and show which policy page was opened. Your browser controls cookie removal, though clearing them may require you to sign in again.

You can submit a deletion request through support. We assess the request against account security, payment records and legal retention needs; some records may need to remain for those reasons.

Send the question through our account support path and include the relevant account detail. Eligibility and access depend on local law, so we explain the applicable process rather than assuming the same result everywhere.