Reference

138vegas Privacy Policy For Your Account

Our Privacy Policy explains how 138vegas handles the account details connected with DANA, OVO, GoPay and QRIS, so you can open an account with a clearer view of…

Account dataWallet recordsCookie choicesSecurity requests
138vegas 138vegas Privacy Policy For Your Account
PRIVATE HELP PATH

Where To Ask About Your Data

A clear support route helps you handle a Privacy Policy request without exposing extra account details.

Account request Use the support path beside your account area for a Privacy Policy request.
Wallet query For a DANA, OVO, GoPay or QRIS record, provide the payment date and receipt…
Login concern If a device or phone verification issue blocks your privacy request, explain the sign-in…
DEVICE DATA CONTROL

What We Do With Account Data

We keep the Privacy Policy practical by linking each data use to an account action you recognise: phone verification, wallet matching, sign-in protection or a request made through…

Collection

We collect details you submit during account creation, such as your phone number, plus sign-in, device and transaction records needed…

Cookies

Cookies can keep a session active, remember a language or device preference and help us understand page use.

Account security

Phone verification and device checks help protect account access.

Retention

We retain account, security and payment records only for the period needed for the stated purpose, dispute handling, legal duties…

Your request

You can ask us to access or correct personal data linked to your account, and you can ask how a…

Policy contact

Send Privacy Policy questions through the signed-in support route, with a short description of the record involved.

Privacy Policy Questions For 138vegas

These answers cover the Privacy Policy questions you are most likely to have before opening an account or checking a wallet record. They explain what to prepare, how account verification works and where local law affects a request.

The 138vegas Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references and support requests. It explains why we use each category, how long records may remain and how you can ask for access or correction.

We do not ask you to send a DANA or QRIS PIN through support. We may handle a payment reference, amount or status needed to match a transaction, but your wallet PIN and password should remain private and never appear in a message.

Sign in and use the account support path to request access to personal data. State the account phone number and the record you want checked. We may confirm account control before responding, and the request remains subject to applicable local requirements.

Yes. Send a correction request through the signed-in support path and identify the inaccurate field, such as a phone detail or account profile entry. We may ask for phone verification before changing it, so another person cannot alter your account.

On a phone or tablet, cookies may retain sign-in settings, language choices and essential session data. Your browser lets you clear or restrict them. If essential cookies are blocked, the account or phone-verification step may need to be repeated.

Retention depends on the type of record and its purpose. A DANA, OVO, GoPay or QRIS reference may remain for account security, reconciliation, dispute handling or legal duties. You can ask us to explain a record, although some retention may still apply.

Yes. Account eligibility and some data requests depend on local law. Where local law permits, you can ask for access, correction or deletion assessment through support. We will explain any verification step or record-retention reason that affects your request.