Reference

Privacy Policy for Your ids3888 Account

Our ids3888 Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening access.

Account dataWallet referencesDevice controlsYour privacy requests
ids3888 Privacy Policy for Your ids3888 Account
PRIVACY HELP ROUTE

Where to Ask About Your Data

A clear contact path helps you question a record without repeating your account story. Use the support route connected to your ids3888 account when you need a copy, correction or explanation of personal data. Include the phone number or account identifier you use to sign in, but do not send a wallet PIN or password. Our team can then locate the relevant account, device or payment reference and explain the next privacy step.

Team online

Account privacy request

Send your request through the account support path beside the cashier area. Tell us whether you want access, correction or removal of a detail, and identify the phone number linked to your account without sharing your password.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, include the transaction date, amount shown in your account and the rail used. We use those details to find the matching record while keeping your wallet credentials out of the request.

Login and device concern

If a sign-in alert or unfamiliar device appears, contact us through the same support route and describe the device path, such as mobile browser or desktop browser. We can check session records and guide an account security change.

DATA HANDLING PRACTICE

What We Keep And Why

We separate information needed for account access from records used to trace a wallet or security event.

Account details

We use your sign-in identifier, phone verification result and selected account details to create and protect access. A clear account step helps us match a privacy request to you before releasing or changing personal data.

Payment references

We store the reference needed to connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account action with your account. We do not need your wallet PIN to investigate a payment record or status question.

Device signals

Browser type, device indicators, sign-in time and session events help us spot unusual access. These signals can be checked when your mobile path shows an unfamiliar login, without treating ordinary device use as a problem.

Cookies and sessions

Cookies and session storage help keep your sign-in state, language choice and security checks working. You can manage browser cookie settings, although turning them off may require another account verification step.

Activity records

We may retain account events linked to titles such as Live Blackjack Diamond or Fishing War Quick Arena when they are needed for security, account support or transaction tracing. We do not use those titles to infer unrelated personal traits.

Changes and retention

You can ask what we hold, request a correction or question the reason for retention through support. We assess the request against account security and legal needs, then explain which data can be changed and which record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, wallet and device questions you may have before using ids3888. We keep the process practical: identify the account, describe the record and use the support path connected with your sign-in. If a request concerns access or eligibility, it depends on local law and is handled where local law permits.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request access or correction.

Phone verification helps us connect a privacy request or security alert to the correct account. It can also help identify an unusual sign-in before account access is restored. We use the verification result for account protection, not as a reason to collect unrelated details.

Yes. The policy includes the payment reference, status and timing needed to match a DANA or QRIS action with your account. It can also cover OVO, GoPay, bank transfer and virtual account references. We do not ask for your wallet PIN in a privacy request.

Use the account support path and state that you want a copy of your personal data. Include the phone number or account identifier used for sign-in, plus enough detail to locate the request. We may ask for an account check before releasing personal records.

You can ask us to correct an inaccurate account detail through support. Describe the field that needs changing and provide the updated value without sending a password or wallet PIN. We check the request against account security before applying the change.

Retention depends on the type of record and the reason it exists. Security events, account checks and payment references may need to remain for transaction tracing or legal duties. Ask support about a specific record, and we will explain the applicable retention reason.

A new phone or browser can create a new session record, including device indicators and sign-in time. We use that information to check unusual access. If the device is yours, complete the requested account step; if not, contact support so we can secure the account.