Reference

Privacy Policy for Indonesia Wallet Records

Your account details, wallet receipts, device checks and cookie choices are covered here before you open an account with us.

DANA record handlingOVO privacy checksGoPay receipt recordsQRIS wallet logs
istanacash Privacy Policy for Indonesia Wallet Records
CONTACT ROUTES

istanacash Privacy Contact Paths

Fast privacy help matters when you need a correction before a withdrawal check or want to see which device is attached to your account. We handle privacy requests through logged channels so both you and our team can trace the request. Have your username, registered mobile number and recent wallet method ready before you contact us.

Team online

Live Chat Privacy Desk

Chat is open 09:00-23:00 WIB from the account menu. Tell us your registered mobile number and the privacy request type; we verify the session before discussing wallet, cookie or device records.

Email Data Requests

Send requests to [email protected] using the email on your account. Add your username, last DANA, OVO, GoPay or QRIS method used, and the change or access request you want us to check.

Account Security Path

From mobile web, go to Account > Security > Privacy Request after sign-in. That path lets us link your request to the active device, reducing the chance that another person asks for your records.

DATA HANDLING

How We Handle Your Data

Good privacy practice is practical: collect what the account needs, protect it during use, and remove it when it no longer has a valid purpose.

Account Creation Records

When you join, we collect your mobile number, username, password data and account settings. We use those records to create the account, recover access, confirm changes and connect privacy requests to the correct profile.

Payment Reference Handling

DANA, OVO, GoPay and QRIS records are stored as payment references, not full wallet access. We keep timestamps, method names and receipt signals so account checks and withdrawal reviews match the right person.

Device Security Signals

We may log browser type, IP range, sign-in time and device changes. Those signals help us detect unusual access, protect your balance records and confirm whether a privacy request came from your own session.

Cookie Choices

Cookies keep sign-in sessions stable, remember basic language and help us measure page errors. You can clear cookies in your browser; after that, we may ask you to sign in again for account privacy checks.

Record Retention

We keep account, wallet and support records only for operational, security and legal needs. When a record is no longer required, we delete it or reduce it so it no longer identifies you directly.

Change Requests

You can ask us to correct a phone number, update an email or check stored device records. We verify the request inside your account first, then record the outcome so the privacy trail stays clear.

Privacy Questions Before You Join

These answers focus on the privacy details you are most likely to check before opening an account or contacting us. They cover account data, wallet references, cookies, access requests and how we confirm that a request is really from you.

We collect the details needed to create and protect your account, such as username, mobile number, password data, device signals and contact settings. If you use DANA, OVO, GoPay or QRIS, we store payment references for account checks.

Yes. We may store session records such as game category, table or title, time, stake record and result reference. These records help us handle account disputes, security checks and privacy requests tied to your activity.

You can contact us through live chat or [email protected] and ask for an access check. We verify your account first, then share the account data we can provide where local law permits.

We store payment method names, timestamps and receipt references so we can match wallet activity to your account. We do not need your full wallet app access, and staff access is limited by task.

Sign in and go to Account > Security > Privacy Request, or contact chat during 09:00-23:00 WIB. We verify your current account details before changing contact data, because those fields affect access recovery.

Device and browser records help us spot unusual sign-ins and confirm privacy requests. For example, a new device after a QRIS transaction may need an extra check before we discuss account records.

We keep request logs long enough to show what you asked, how we verified you, and what action we took. After the record is no longer needed, we delete it or reduce identifying details.