Reference

Privacy Policy For Your dubai138 Account

Our Privacy Policy explains how dubai138 handles the details you provide when opening an account, confirming your phone, or checking a wallet record.

Account dataWallet recordsCookie choicesContact requests
dubai138 Privacy Policy For Your dubai138 Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact route helps when you want to ask what data we hold or why an account record appears.

Policy request Use the support route beside your account area for a Privacy Policy question. Tell us whether you need access, correction, deletion or an explanation of a data use, and include the phone-linked account identifier for matching.
Wallet record If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the visible receipt or status reference through account support. Remove unrelated wallet details first; we only need enough information to locate the account record.
Account check Before we disclose personal account data, we may ask you to complete the phone verification step used for account access. This check helps us avoid sending login, device or payment-related details to the wrong person.
DATA PRACTICES

What You Gain From Clear Data Handling

We keep this Privacy Policy practical by linking each data use to an account task. Your login, phone confirmation and device signals help us protect access; payment references help us trace DANA…

Account security

Phone verification is part of the account access path. We use the linked phone and sign-in signals to check whether a request matches your account before discussing personal details or changing account data.

Payment matching

For DANA, OVO, GoPay and QRIS, we retain the reference needed to connect a wallet event with your account request. Bank transfer and virtual account records follow the same narrow matching purpose.

Cookie control

Cookies can keep a session active and remember selected settings on your browser. You can clear them through your browser controls, though doing so may require another login before account pages open.

Device signals

We may record device type, browser details and sign-in time to identify unusual access. On mobile, these signals help us distinguish a normal return to the account from a changed access pattern.

Retention choices

We keep information only while an account, support, security or legal need calls for it. Ask through support which category applies to your record and whether a deletion or restriction request can proceed.

Policy changes

When this Privacy Policy changes, we place the updated wording on this page and may show an account notice. Check the page before opening a new account or sending a fresh wallet-status request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions you are most likely to search before opening access. We explain the records tied to phone verification, wallet references, cookies, devices and support requests in plain terms. If your situation is different, use the account support path and tell us exactly which data or policy passage you want checked. Where local law permits, we will assess the request against the account record and the reason that record is retained.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It also explains how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account records connected with your account activity.

We use your phone number to support account opening and the verification step before account access. It helps us match a policy request to the right account and reduces the chance that login or wallet-related details are disclosed to another person.

Yes. The Privacy Policy covers payment references that connect DANA, OVO, GoPay or QRIS activity with your account. We may also retain bank transfer or virtual account references so support can check a stated status without requesting unrelated wallet content.

Use the support route beside your account and state that you want an access request under the Privacy Policy. Include your account identifier and complete any phone verification we request. We will assess the request where local law permits and explain any necessary limitation.

Yes. Send a correction request through account support and identify the specific field that is inaccurate, such as a phone-linked account detail. We may verify your account first, then update the record where local law permits and where the change can be confirmed.

Cookies can keep your browser session available and remember selected settings. They do not give us access to unrelated files on your device. You can clear or restrict cookies in browser settings, but you may need to complete account login again.

Retention depends on the account, support, security or legal reason for keeping a record. Payment references, phone-verification details and support messages may remain while that reason applies. Ask through support for the category and retention basis connected with your record.