Reference

des138 Privacy Policy for Your Account

Our des138 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, browse Auto Roulette or check wallet status.

Account dataWallet recordsDevice choicesPolicy requests
des138 des138 Privacy Policy for Your Account
POLICY HELP ROUTE

Get Privacy Policy Help Beside Support

A clear contact path matters when you want to ask about personal data, a wallet reference or an account record. Use our support chat from the account or cashier area and describe the exact request, such as correcting a phone detail or asking why a QRIS reference appears in your history. We may ask for account checks before discussing private records, so your request reaches the right account safely.

Team online

Support chat

Send a Privacy Policy question through our support chat beside the account and cashier path. Include your account contact and the subject of your request, but do not send a password, wallet PIN or complete payment credential.

Account checks

We may confirm your phone verification or another account detail before releasing personal data. This step helps us avoid sending a DANA, OVO, GoPay or QRIS record to the wrong person.

Status questions

If a bank transfer or virtual account reference is unclear, mention its date and route in the same conversation. We use those details to locate the record without asking you to repeat unrelated account activity.

ACCOUNT DATA PRACTICE

What Our Privacy Controls Cover

Privacy work is part of the account path, not a separate promise hidden away from the cashier.

Data handling

We use account and contact details to create your profile, complete phone verification and respond to a request. We use payment references to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity to the correct account.

Cookies

Cookies can support sign-in continuity, session security and your selected display settings. On a mobile browser, you can manage cookie permissions through the browser controls, although disabling some cookies may interrupt the account path.

Account security

We use sign-in records, phone verification and device signals to identify unusual access. Never share your password or verification code in support chat; we will not need those secrets to explain a Privacy Policy request.

Retention

We keep records for as long as needed for the stated account, payment, security or support purpose, then assess whether they can be removed. A request can ask us to explain why a particular record remains.

Correction requests

If your phone detail, contact information or account record is inaccurate, tell us through support chat. We may compare the request with phone verification before changing information connected with your account.

Access requests

You can ask which personal data is linked to your account and how it is used. Include the account contact and a clear request; we will confirm identity before discussing records tied to Auto Roulette or another title.

Privacy Policy Answers for des138 Accounts

These Privacy Policy answers cover the questions we hear before an account is opened or when a wallet record needs checking. We explain the practical route for requests involving phone verification, cookies, device access and payment references. If your situation is unusual, contact support chat with the smallest useful set of account details.

It covers personal data connected with your account, including contact details, phone verification, sign-in records, device signals, payment references and support messages. It also explains cookies, retention, security steps and how to ask for access or correction where local law permits.

Phone verification helps connect account access to the correct contact detail and supports security checks when you request private records. We may use the result to confirm identity before discussing activity linked with DANA, OVO, GoPay or QRIS.

Yes. The Privacy Policy covers transaction status and reference details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a payment route to your account and investigate an unclear status.

You can request access to personal data linked with your account through support chat. Give us your account contact and describe the records you want to see. We will complete an identity check before sharing private account or payment details.

Send a correction request through support chat and identify the field that is inaccurate, such as a phone or contact detail. We may compare your request with phone verification before changing the record, so the account remains connected to you.

Open your mobile browser settings, locate privacy or cookie controls and adjust permissions there. Cookies can support sign-in continuity and display choices, so disabling them may affect the session. The Privacy Policy explains their purpose without requiring an app.

Yes, access or eligibility depends on local law. Where local law permits, we handle requests for access, correction or retention details through support chat after confirming the account holder. We will explain the applicable route if a request has limits.