Reference

Privacy Policy for your wslot account

This page explains how wslot handles the data tied to your account, login, and payment activity.

Account dataCookie useDevice logsDANA / OVO / GoPay / QRIS
wslot Privacy Policy for your wslot account
CONTACT ROUTES

Where to send privacy requests

Privacy requests move fastest through the channel you already use. Open Account > Help on mobile, tap the chat button on desktop, or email us during our daily 08:00-24:00 WIB window, and we route it to the team that handles data questions. If you want a record check, a correction, or a close-out request, include the email tied to your account and the device you used.

Team online

Live chat

Use the chat button inside your account for data questions, record checks, or a correction request. The same thread keeps context from your login and payment references, so we can respond without starting from zero.

Email

Send the account email and the request type to [email protected]. We use that address to match your records, confirm your identity, and move the request into the privacy queue without asking for extra public details.

Help form

If you are already signed in, the help form keeps your message tied to the right account. That helps us handle closure, correction, or access requests with fewer back-and-forth steps.

HOW WE HANDLE

Data handling, cookies, and retention

We handle privacy data with the same account checks we use for wallet actions and login safety.

Data we collect

We collect the account details you type, the device and browser data your phone sends, and payment references from DANA, OVO, GoPay, and QRIS so we can verify activity and answer account questions.

Cookie use

Cookies keep you signed in, remember session state, and help us spot unusual login behavior. You can clear them in your browser, but some pages may ask for a new login after that.

Account security

We use login checks, session timeouts, and abnormal-device alerts to protect your account. If you switch from one phone to another, we may ask for a fresh verification step before showing sensitive account pages.

Retention

We keep privacy records only while we need them for service, audits, dispute handling, or legal duties. After that, we remove or archive them under our internal retention process.

Requests

You can ask for access or a correction through chat, email, or the help form. Where local law permits, we will confirm the account, state what we can change, and explain anything we cannot.

Contact detail

If your request relates to a payment trace from QRIS or a login from another device, tell us the date, method, and email tied to the account. That lets us match the right record faster.

Questions about your data rights

If you want to know what we keep, who sees it, or how to ask for a change, this section puts the basics in one place. Every answer here refers to account data, cookie use, payment traces, and support records linked to your login. If something depends on local law, we say so directly; otherwise we explain the exact account step you can take.

We may record the email or phone you use, device and browser data, login time, and payment references from DANA, OVO, GoPay, or QRIS. We use that data to verify the account and answer support requests.

Yes. Cookies keep you signed in, remember session state, and help us spot unusual login behavior. You can clear them in your browser, but some pages may ask for a new login after that.

Yes, where local law permits. Send the request through live chat or email with the account details you used, and we will confirm what we can share after we verify the account.

Yes. Tell us which detail is wrong, send the correct version, and use the same email or chat thread tied to the account so we can match the record and update it safely.

We keep records only as long as needed for account service, dispute handling, audit checks, or legal duties. After that, we remove or archive them under our internal process.

Use the chat button inside your account, email [email protected], or submit the help form. Include your login email, the request type, and any payment reference if the issue involves DANA, OVO, GoPay, or QRIS.

A new phone or browser may trigger a login check. We do that to protect the account, and we may ask you to confirm the email tied to the profile before we show the privacy record.