Reference

Privacy Policy For Your ids138 Account

Our Privacy Policy explains what we collect when you open an ids138 account, use the lobby, or check DANA, OVO, GoPay and QRIS status.

Account dataWallet recordsCookie choicesAccess requests
Browse Casino Lobby Read FAQ
ids138 Privacy Policy For Your ids138 Account
CONTACT PATHS

Get Privacy Policy Help Beside Account Support

A clear contact route helps you resolve a privacy question without repeating your account history. When you contact us, include the account identifier and the subject of your request, while leaving out passwords or wallet PINs. Our support path can connect a privacy query with a login issue, a payment receipt, or a status check from the cashier area. Requests remain subject to identity checks and where local law permits, we explain the next step through the available account support channel.

Team online

Account access

For a data request linked to phone verification or a stalled login, use the support route beside account help. We check the account identifier before discussing stored details, so your request reaches the right record without asking you to send a password.

Wallet records

If your Privacy Policy question concerns a DANA, OVO, GoPay or QRIS receipt, include its reference and approximate date. We use that operational detail to locate the payment record while keeping wallet PINs and full authentication secrets out of the conversation.

Privacy requests

For access, correction or deletion questions, state the action you are requesting and the phone number attached to your account. We may ask for an account check before sharing or changing personal data, and we explain any local-law restriction that applies.

DATA PRACTICES

How ids138 Handles Personal Data

Privacy work is part of the account path, from the first phone check to a later request about a wallet reference.

Phone verification

We use the phone verification step to connect account access with the person making a request. A verification result can help us distinguish an authorised correction from an attempt to obtain another account's details.

Device signals

Login time, browser details and device signals can be recorded to identify unusual access patterns. These signals support account protection and are handled as security data rather than as a public profile about you.

Cookie controls

Cookies may keep a session usable and remember selected settings across the mobile login path. You can manage cookie permissions in your browser, although restricting them may affect sign-in continuity or some policy-request steps.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records when you ask us to check a receipt. We use those references for matching and support, not for collecting wallet PINs.

Retention checks

We retain account, security and transaction-related records for the period needed for the stated purpose, account protection and applicable legal duties. A retention question can be sent through support with your account identifier for a case-specific response.

Change requests

You can ask us to correct inaccurate profile data or explain how a record is used. Include the field you want changed and the reason it is inaccurate; after identity checks, we record the request and explain the available outcome.

Privacy Policy Questions About ids138

These Privacy Policy answers address the account and payment-data questions most often raised before access. They cover the records created during phone verification, the device details connected with a login, cookie choices, wallet references and the route for requesting a copy or correction. Where a request depends on local law, we explain that limitation instead of treating every account record the same way.

The ids138 Privacy Policy covers account identifiers, phone verification results, login and device signals, cookie activity, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account details may appear when they are needed to match a receipt or check account status.

Phone verification helps connect an account request to the correct account holder and reduces the chance of unauthorised access. We may use the result when you ask for a correction, discuss a wallet receipt, or need help after a login problem.

Cookies can preserve a login session, remember selected settings and help us understand page activity. You can manage them in your browser. Blocking some cookies may interrupt account access or make a Privacy Policy request require another verification step.

Where local law permits, you can request access to personal data connected with your account. Send the request through the available support channel and include your account identifier. We verify the request first, then explain the records we can provide and any lawful restriction.

Yes, you can ask us to correct inaccurate account information covered by the Privacy Policy. Identify the field and provide the accurate replacement. We may confirm your phone verification before making a change, and we will explain if a transaction or security record cannot be altered.

Retention depends on why the record exists, account protection needs and applicable legal duties. Account, security and payment references may therefore follow different periods. You can ask support about a particular DANA, QRIS or account record and receive a case-specific explanation.

Use the account support route linked beside login or the cashier area and label your request as a Privacy Policy question. Include your account identifier, requested action and relevant date. Do not send passwords, wallet PINs or full authentication credentials in the message.

Related Pages

ids138 Indonesia fillabola Dragon Tiger ids138 Casino FAQ