Reference

Open sensa138 Privacy Policy for your account

sensa138 Privacy Policy explains what we collect when you create an account, check DANA or QRIS status, and open the lobby on a phone.

Account dataWallet recordsDevice choicesPolicy requests

Explore Our Lobby Read FAQ

Check DANA and QRIS data use

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

Our Privacy Policy sets out how we collect, use, store and disclose details linked to your sensa138 account. This can include your phone number, verification result, login records, device details, cookie choices, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or

1
a virtual account. We use these records to confirm account access, match wallet status, investigate a receipt and respond to a policy request. If you open Andar Bahar or Crash Games, we may retain session and activity records needed for account history and security checks. Where
2
local law permits, you can ask us to explain, correct or remove eligible data. Some records may remain when required for a dispute, security review or legal duty. This policy applies to our Indonesia-facing service, and access depends on local law.

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

CONTACT PATH

Contact us about policy requests

A clear contact path helps you ask about the Privacy Policy without searching through the lobby.

Account contact Send a policy question through account support and include your registered phone number. We can explain how verification data connects to access, subject to checks needed to protect your account.

Wallet query If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the receipt details through the support path. We use the reference to trace status without asking for your wallet password.

Device request Tell us whether you used Android, iPhone or desktop when a cookie or login record looks unfamiliar. This device path helps us investigate the event and explain the related Privacy Policy entry.

CONTROL DETAILS

Browse how we handle device data

We keep the Privacy Policy practical by separating account identity, payment references, device signals and support correspondence.

Data handling

We use phone, account and session details to verify access, maintain account records and answer support requests. Payment references from QRIS or bank transfer help us match a transaction without storing your wallet password.

Cookie choices

Cookies and similar device files can remember sign-in context and help us understand technical errors. You can adjust browser settings, although removing them may require another phone verification step before access.

Account security

Phone verification, login records and device signals help us identify unusual access. If your route from mobile login to the lobby looks unfamiliar, contact support so we can check the account event.

Retention periods

We retain records only for the operational, dispute or legal period that applies to them. Wallet references, support messages and account history may therefore have different storage periods.

Change requests

You can request correction, access or removal of eligible account data through support. State the requested change clearly and provide enough account detail for us to confirm your identity.

Policy contact

Questions about this Privacy Policy can follow the same account support route. We will explain the relevant data category, request step and any local-law condition affecting the response.

Find Privacy Policy answers for access

These Privacy Policy answers cover the questions we hear before an account is opened, from phone verification and payment references to cookies and deletion requests. Read them alongside the full policy, then contact us with the account detail needed to check your case.

It covers account details, phone verification, login and device records, cookie choices, support messages, payment references and requests to access, correct or remove eligible data.

We use your phone number to create and verify account access, connect support requests to the correct account and investigate unusual login events. Access depends on local law.

Yes. The policy explains how we use DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account details, to match wallet status or receipts.

You can contact account support with your registered phone number and request access to eligible records. We may first confirm your identity before preparing the response.

Send the correction request through the account support path, name the field that appears wrong and describe the change. We will check the account record before updating eligible details.

Cookies can retain sign-in context and help diagnose device issues. Browser settings let you adjust them, but removing cookies may lead to another verification step during account access.

You may request removal of eligible data through support. Some account, payment or security records can remain when a dispute, legal duty or access-protection need requires retention.

Open sensa138 Privacy Policy for your account

Contact us about policy requests

Browse how we handle device data

Data handling

Cookie choices

Account security

Retention periods

Change requests

Policy contact

Find Privacy Policy answers for access

01 What does the sensa138 Privacy Policy cover?

02 Why does sensa138 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I request a copy of my account data?

05 How do I ask sensa138 to correct my data?

06 How does the Privacy Policy treat cookies?

07 Can I request deletion of my sensa138 data?

Related Pages