Reference

indoace Privacy Policy for Your Account

The indoace Privacy Policy explains what we collect when you open an account, sign in, use the mobile lobby or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
indoace indoace Privacy Policy for Your Account
ASK ABOUT DATA

Contact Us About Your Privacy Policy

A clear contact path matters when a name, phone number or wallet record needs attention. Start from your account help route and tell us which Privacy Policy request you are making, such as access, correction or deletion. Include the account phone number and a short description, but do not send a wallet PIN or login password. We use the account details you provide to locate the right record, then may ask for an account step that confirms you are making the request.

Team online

Account request

Use the account help path when you want a copy of personal data linked to your indoace login. Tell us whether the request concerns registration, phone verification, device history or a DANA, OVO, GoPay or QRIS reference, so we can check the correct record.

Correction request

If your account name or contact detail is inaccurate, describe the specific field and the replacement detail through support. We may compare the request with your phone verification step before changing it, helping us avoid edits made by someone who has only seen your public account name.

Payment query

For a privacy question connected with a receipt, include the payment rail and transaction reference rather than sending private wallet credentials. Our support route can check whether the record relates to QRIS, bank transfer or a virtual account and explain what information is retained for that check.

HANDLING YOUR RECORD

Explore How We Protect Privacy

We handle Privacy Policy requests around the real account journey: phone verification before access, wallet status checks during a deposit, and device activity when a sign-in looks unusual.

Account security

Phone verification helps connect account access to the contact detail you supplied. We may use sign-in and device signals to identify unusual activity, while your password and wallet PIN should remain private. If access stalls, support can guide the account confirmation step without asking for those secrets.

Payment records

A DANA, OVO, GoPay or QRIS reference can be needed to reconcile a cashier event with your account. Bank transfer and virtual account records may also be checked for the same reason. We use the reference for matching and support, not as a substitute for your wallet credentials.

Cookies

Cookies and device storage help maintain your sign-in path, keep the lobby language setting available and remember session choices. They can also support security checks when you move between the mobile lobby and desktop. Your browser controls whether some storage is accepted, although parts of account access may then need to be repeated.

Data access

You can ask what personal data we hold about your indoace account, including registration details, verification records and payment references. Send the request through account support with enough detail to locate you. We may confirm account ownership before providing a copy, especially when the request includes wallet or sign-in history.

Data changes

A correction request should identify the field that is wrong and explain the accurate replacement. We keep a record of the request and the action taken so the account history remains clear. Some transaction or security records may need to stay available where an operational or legal need still applies.

Retention contact

Ask support why a particular record remains stored if you believe it is no longer needed. We can assess registration data, device activity, cookie settings and payment references separately because each serves a different purpose. Where local law permits, we will explain the result and the next available request path.

Browse Privacy Policy Answers

These Privacy Policy answers cover the questions we expect before an Indonesian account is opened or used. They explain the information connected with your login, mobile device, wallet activity and support requests. If your situation is not covered, use the account help path and describe the specific record involved. Access and eligibility depends on local law, so we may need to confirm your region before explaining which request route applies.

The indoace Privacy Policy covers account registration, phone verification, sign-in activity, device signals, cookies, support requests and payment references. It explains why we use each category, how security checks work and how you can request access, correction or deletion of personal data connected with your account.

We may store references needed to match activity from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account with your account. These can include a transaction identifier, status and timing. Do not send us your wallet PIN or password when asking about a receipt.

Yes. Use the account help path and request access to the personal data linked with your indoace login. Mention whether you need registration, phone verification, device or payment records. We may confirm account ownership before sharing details because the request can contain private account history.

Tell support which account field is inaccurate and provide the replacement detail. We may ask you to complete phone verification or another account step before applying the change. This helps us prevent an unrelated person from altering your name, contact detail or account history.

Cookies and similar storage can keep your mobile sign-in path active, remember session settings and support device security checks. Your browser can restrict this storage, but you may need to sign in again or repeat a setting. The Privacy Policy explains these purposes rather than treating cookies as payment credentials.

You can send a deletion request through account support and identify the records involved. We assess registration data, device activity, cookies and payment references separately. Some information may remain where it is needed for security, transaction reconciliation or a legal requirement; where local law permits, we explain the outcome.

The Privacy Policy is available for you to read, but account access and eligibility depends on local law. Where local law permits, we process information for the services shown in your region. If you need a region-specific answer, contact support with your account location and the request you want to make.