Reference

slot138 Privacy Policy For Your Account

Our Privacy Policy explains how slot138 handles the details connected with your account, including phone verification, device access and wallet activity through DANA, OVO, GoPay or QRIS.

Account recordsWallet activityDevice accessYour privacy choices
slot138 slot138 Privacy Policy For Your Account
PRIVACY CONTACTS

Get Help With A Policy Request

A direct contact path helps when you want to ask about your personal data, correct an account record or understand a wallet reference. Use the support route connected to your account and include your registered phone number, request type and any relevant receipt detail. We use those details to locate the right record without asking you to send a password.

Team online

Account data

Ask us to confirm the account details linked to your registered phone number. We may request a verification step before discussing records, so another person cannot obtain details through a simple message.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, share the transaction reference rather than wallet credentials. Our support route can check which account record the reference belongs to.

Access concerns

If a sign-in or device check affects your privacy request, contact support from the account path and explain what changed. We can review the request after confirming your registered account details.

HANDLING YOUR DATA

How slot138 Manages Privacy Details

We handle privacy as an account process rather than a broad promise. The records connected with your phone verification, wallet status and device session are used for defined account tasks, and our…

Account collection

We collect details you enter during the account path, such as your phone number and verification response. Information created by sign-in, lobby access or payment status may be linked to the same account record.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a payment status to your account. Bank transfer and virtual account records are handled for reconciliation, not as permission to view your banking password.

Cookies and sessions

Cookies can keep a necessary sign-in session active and remember security settings on your browser. You can manage browser cookie controls, though removing essential cookies may interrupt the account path.

Device security

We may record device or browser signals to identify unusual access, protect your session and investigate account changes. These signals support security checks; they do not replace the phone verification step.

Retention periods

We retain account, support and payment-reference records only for the period needed for account operations, security checks, dispute handling or legal duties. Retention can vary by record type and local requirements.

Change requests

To request correction, access or removal where available, contact us through the account support route with your registered phone number. We verify the request first and explain any limit that applies.

Privacy Policy Questions About slot138

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account records, device signals, cookies, local wallets and contact steps, so you can decide what to share and how to request a change. Access remains where local law permits.

It explains what account, device, cookie, support and payment-reference data we handle, why we use it, how retention works and how you can request access or correction through the account support route.

No. We use payment references and status details to match activity with your account. You should never send a wallet password, one-time code or banking credential when asking about a transaction.

Device and browser signals help us identify unusual sign-ins and protect your account session. They can support a phone verification check, but they are not used as a substitute for confirming your registered account.

Contact us through the support path connected to your account, provide your registered phone number and describe the correction. We verify ownership before changing records and explain any legal or operational restriction.

Retention depends on the record and the reason it is needed, such as account access, security, payment reconciliation, dispute handling or legal duties. We remove or restrict records when the applicable period ends.

Yes. Ask through the account support route and we can explain the cookies connected with necessary sessions and security settings. Browser controls can limit cookies, but essential account functions may then stop working.

Yes. Account access and the handling of certain requests depend on local law. We apply this Privacy Policy where local law permits and will explain the relevant limit when we verify your request.