Reference

Privacy Policy for Your indcash Account

Our Privacy Policy explains how we collect, use and protect the details linked to your indcash account, including your phone verification and wallet status.

Clear data purposesCookie choicesAccount access requestsWallet status checks
indcash Privacy Policy for Your indcash Account
HELP WITH REQUESTS

Get Privacy Policy Help Through Your Account

A direct support route helps when you want to ask about a data record, cookie choice or account access request.

Account request Open the account help path and state whether your request concerns access, correction, deletion or a copy of data. We may ask for phone verification before discussing private account records, keeping the request connected to the right account.
Wallet record For DANA, OVO, GoPay or QRIS questions, send the payment name and receipt reference through the account support path. We use those details to trace status without asking you to post wallet credentials in a public message.
Policy question If a Privacy Policy paragraph is unclear, quote the relevant wording and tell us what you want to know. We can explain the purpose of a data field, cookie, retention period or security step used on your account.
DATA CONTROLS

What We Do With Account Data

Privacy starts with limiting each account record to a stated purpose. We use account and transaction data to provide access, check security, record wallet outcomes and respond to requests under this Privacy…

Data collection

We collect details such as your account contact, phone verification result, session activity and payment reference when those details support access or a wallet status check. The Privacy Policy links each category to a stated operational purpose.

Cookie use

Cookies can keep your signed-in browser path working while you move from account settings to the lobby. You can review browser cookie controls, although changing them may interrupt session access or require phone verification again.

Account security

Phone verification helps us confirm an account access request before private details are discussed. Keep your login details private, and contact support if a session, device path or wallet record does not match your activity.

Payment records

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference lets us match a transaction event to the correct account. We use the reference for status checks and do not need your wallet password.

Retention periods

We retain account, security and transaction records only for the period needed for the stated purpose, account safety or a legal requirement. You can ask which category applies to your record and why it remains stored.

Changes and contact

To request a correction, access copy or deletion where available, use the account support path and describe the record clearly. We may verify your phone before making a change, then explain any limit under local law.

Privacy Policy Answers For indcash

These Privacy Policy answers focus on the account questions you are most likely to have before opening access or checking a wallet record. We explain what we collect, how browser access works and how to reach us when you want a change. If your question involves eligibility, access depends on local law and we may need to confirm your account before sharing private details.

The indcash Privacy Policy covers account details, phone verification, browser cookies, security activity and payment references. It explains why we use each category, how we protect access, when records may be retained and how you can request access, correction or deletion where local law permits.

Phone verification helps us check that an account access or data request comes from the account holder. It can be required before we discuss private records, change account details or investigate a wallet status linked to DANA, OVO, GoPay, QRIS or another payment route.

Yes. The Privacy Policy covers the transaction reference and status details needed for QRIS, DANA, OVO, GoPay, bank transfer and virtual account checks. We use those records to match an event to your account and investigate a failed step without requesting your wallet password.

Use the account support path and ask for a data access copy under the Privacy Policy. Describe the account record you want reviewed, such as phone verification or a payment reference. We may confirm your phone first, then explain the available format and any local-law limits.

You can request a correction through account support when a stored detail is inaccurate or no longer current. Include the record and the change you want, but do not send your password or wallet credentials. We may verify your phone before updating the account.

Cookies can preserve a browser session while you move between account settings and the lobby. Your browser controls let you remove or restrict them, but the account path may then ask for access checks again. The Privacy Policy explains which cookie purposes apply to your session.

Open the account support path and identify your request as a Privacy Policy matter, such as deletion, retention or a security concern. We may verify the account before acting. Deletion can depend on a legal or transaction-record requirement, and access depends on local law.