Reference

slot21 Privacy Policy for Your Account Data

Our Privacy Policy explains what slot21 collects when you open an account, verify your phone and move between the lobby and wallet area.

Clear data purposesPhone verification contextWallet record controlsPolicy request path
slot21 slot21 Privacy Policy for Your Account Data
PRIVACY CONTACT

Get Privacy Help Beside Wallet Status

A clear contact path helps when a privacy question appears beside a login or wallet event.

Account data request Ask us to locate the account details connected with your phone verification step, login record or saved contact route. Include your account reference so we can check the correct record.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account entries, send the visible reference and date. We can check how that payment record is linked to your account.
Privacy change request Use the account contact path to ask about correction, access or deletion of eligible data. We may verify account ownership before changing information connected with your profile.
DATA PRACTICE

How slot21 Handles Account Data

Our handling process follows the account events you can recognise: registration, phone verification, mobile-browser sessions, wallet status and policy requests.

Account details

We use details such as your contact route and verification status to create, maintain and protect the account. We do not need unrelated personal details for a request to reach the lobby.

Device and session data

A mobile browser or desktop session can create technical records such as device type, browser settings, IP address and session time. These records help us identify access problems and unusual sign-ins.

Cookies

Cookies can remember session choices and help the account path work between login and the lobby. You can manage browser cookie settings, though some account functions may then need another sign-in.

Payment references

A wallet or bank record may include a method name, reference, amount and status needed to match your instruction. We use that context for account servicing, receipt checks and access protection.

Security checks

Before we reveal or change account data, we may ask for details that confirm ownership. Phone verification and account references help prevent another person from changing your contact or wallet records.

Retention requests

We retain records only for operational, security or legal needs connected with the account. Ask us about a specific record, and we will explain the available correction, access or removal path.

Privacy Policy Questions Before Account Access

These answers address the searches we hear before an account is opened or a wallet is connected. They cover the records created by login, phone verification, payment status and mobile browsing. If your situation is different, send the account reference through the privacy contact path so we can address the specific record.

It covers account details, phone verification, device and session data, cookies, payment references and privacy requests connected with your use of slot21. It also explains purposes, security steps and retention handling.

Phone verification helps confirm that the person opening or accessing an account controls the supplied contact route. We use its status for account protection and may check ownership before fulfilling a data request.

Yes. The Privacy Policy covers payment references and statuses shown in your account for DANA, OVO, GoPay, QRIS, bank transfer and virtual account instructions. We use them to match account events.

When you use a mobile browser or desktop path, technical records may include device type, browser details, IP address, session time and security signals. These help maintain sessions and investigate unusual access.

You can request correction through the account contact path. Include the affected field and account reference; we may verify ownership before changing contact details, verification status or another eligible record.

Retention depends on the record and the operational, security or legal reason for keeping it. Ask about a particular account or payment reference, and we will explain the applicable handling path.

Use the privacy contact path in your account area and describe the request plainly. Provide your account reference, not a payment password, so we can identify the relevant data without exposing extra details.