Reference

Open id cash 88 Privacy Policy Clearly

id cash 88 Privacy Policy explains how we collect, use and protect your account, device and payment details before you open an account.

Account dataCookie choicesPayment recordsPhone verification
id cash 88 Open id cash 88 Privacy Policy Clearly
REQUEST HELP

Contact Us About Your Privacy

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail. Send your privacy request through the account help route and include the phone number or account identifier connected with your access. We may ask for a verification step before discussing records, so another person cannot obtain your payment or sign-in details. We handle privacy questions separately from a stalled wallet or receipt check.

Team online

Access request

Ask us for a copy of personal details connected with your account. Include your verified phone number and the relevant account step so we can locate the correct record without exposing another account.

Correction request

Tell us which account detail needs changing and why it is inaccurate. We may confirm your identity through the existing phone verification path before making an amendment to the record.

Payment question

For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference rather than sending extra wallet details. We use that reference to check the record and limit unnecessary disclosure.

HANDLE WITH CARE

Browse id cash 88 Data Practices

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We use your submitted account details to create and maintain access, connect your verified phone and identify the correct account when you ask for a privacy change. We do not need unrelated personal details for that process.

Device signals

Your browser and device path can be recorded with sign-in time, session data and security events. These details help us recognise unusual access when you switch from a mobile login to the lobby.

Cookie controls

Cookies can retain session settings and help us understand which policy pages are opened. You can restrict cookies in your browser settings; account pages may then ask you to sign in again.

Payment records

A DANA, OVO, GoPay or QRIS transaction can leave a reference, amount status and time in our records. We use those fields to match receipts, answer disputes and check the related account request.

Account protection

Phone verification, sign-in events and selected device signals support account protection. If a request concerns private records, we may repeat an account check before sharing details or changing stored information.

Retention requests

We keep information only while it supports account administration, security, a payment question, a dispute or a legal duty. Ask us about deletion or retention through account help, and we will apply local rules.

Check Privacy Policy Answers

These Privacy Policy answers focus on the searches we expect before an account is opened. They explain the records created by phone verification, mobile access and local payment references, along with the route for asking about your personal details. If your question is not listed, use the account help path and identify the account step or payment reference involved.

It covers account details, phone verification, device and browser signals, cookies, payment references, security events and retention. It also explains how to ask for access, correction or deletion, subject to local law and the reason a record must be kept.

When you use DANA or QRIS, we receive transaction details needed to match the payment with your account and check a receipt or status question. The record can include a reference, time and status, not unrelated wallet content.

We keep the verification result and related account details needed to confirm access and protect your sign-in. A privacy request may require another identity check before we disclose, amend or remove information connected with that phone.

Yes. Send an access request through the account help route with your verified phone number or account identifier. We may confirm ownership first, then explain the personal details and relevant records we can provide where local law permits.

Use the account help route and identify the incorrect detail, such as a profile field or phone record. We may repeat phone verification before changing it, because correcting the wrong account could expose another person’s information.

We retain payment references and status records only as long as they support account administration, receipt checks, disputes, security or a legal duty. You can ask why a record remains, and we will apply the retention rules that govern your request.

Yes. Your mobile browser provides cookie controls that can restrict or remove stored session data. Some account pages may request another sign-in afterward, and essential session functions may not work as expected when cookies are blocked.