Reference

Privacy Policy For Your idchas88 Account

Our Privacy Policy explains what idchas88 collects when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS at the cashier.

Account dataWallet recordsCookie choicesPolicy requests
idchas88 Privacy Policy For Your idchas88 Account
CONTACT THE DESK

Get Privacy Help Beside Account Support

A clear support route matters when your account record or wallet status needs attention. From the account help area, tell us which email or phone detail is involved, what step you completed, and whether the issue concerns DANA, OVO, GoPay, QRIS or a bank transfer. We use those details to locate the right record without asking you to send a password. Your request can also cover a correction, access question or removal request where local law permits.

Team online

Account help path

Open the account help path and identify the profile detail connected to your Privacy Policy request. We can use your account step, phone verification status and sign-in context to locate the relevant record without requesting your password.

Cashier status check

If a wallet record looks incorrect, include the payment rail and reference shown in your cashier history. DANA, OVO, GoPay, QRIS, bank transfer and virtual account details help us separate a payment question from a wider account-data request.

Policy request route

For access, correction or deletion questions, send the request through our support route with the account email or verified phone detail. We may ask for a matching account step before changing personal data, where local law permits.

HANDLING YOUR RECORD

Inside idchas88 Data And Cookie Controls

We keep the Privacy Policy practical by tying each data use to a recognisable account action. A phone verification event supports sign-in control, a QRIS reference supports cashier reconciliation, and a device…

Account creation

When you open an account, we collect the details needed to create and maintain your profile. Phone verification before account access helps connect the sign-in event with your account and gives us a specific point to check if access stalls.

Device signals

A mobile browser or desktop session may provide browser, operating system, language and sign-in time details. These signals help us identify an unusual access pattern and investigate why the lobby or account area behaves differently on your device.

Cookie choices

Essential cookies can keep account navigation and policy access working during a session. You can review cookie controls in your browser settings; changing optional cookies may affect remembered preferences, but it does not change the account records required for a cashier request.

Payment records

Cashier records can include a rail name, reference, amount status and account connection. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries let us trace a status question without treating the payment reference as your account password.

Retention process

We keep personal data only for the period needed to operate the account, resolve a payment or support matter, and meet applicable obligations. Where local law permits, you can ask which records remain, why they remain, and whether removal or anonymisation is available.

Change requests

If your name, phone detail or other account data is inaccurate, contact us through the policy support route. We may compare the request with your verified account step before making a change, helping prevent an unknown person from altering your profile.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often from people deciding whether to open an account. They explain what happens around phone verification, device access, local wallet records, cookies, retention and requests for a copy or correction. If your situation is not covered, use the account support route and include the specific step or payment reference involved.

It covers account details, phone verification, device signals, cookies, support messages and cashier records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access, correction and removal requests where local law permits.

Phone verification helps us connect account access with the person completing the account step and gives support a specific record to check. It can also help us investigate an unfamiliar sign-in without asking you to place your password in a message.

Yes. The policy covers payment references and status information connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help us match a cashier event with the correct account and answer a status request.

A session may provide browser type, operating system, language, device signals and sign-in time. We use this information to support account access, examine unusual sessions and understand a mobile or desktop issue; it does not give us your device password or private files.

You can contact us through the policy support route and state whether you want access, correction or another data request. Include the account email or verified phone detail. We may confirm the matching account step before responding, and availability depends on local law.

Retention depends on the account purpose, payment reconciliation, support history and applicable legal needs. We remove or anonymise records when the relevant period ends under our process. You can ask which category remains and the reason for keeping it where local law permits.

Open your browser cookie controls and adjust optional preferences there, then contact account support if you need clarification about a specific cookie. Essential cookies may remain necessary for sign-in and policy access, while changing optional settings can affect remembered choices.