Reference

Privacy Policy For Your Account

istana impian 1 Privacy Policy explains what we collect when you create an account, verify your phone, and use DANA or QRIS.

Account dataWallet recordsCookie choicesAccess requests
istana impian 1 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact path helps when you need to ask about a record, cookie choice, or account detail. Start from the support route shown after login and describe the specific Privacy Policy question, rather than sending payment credentials in an open message. Our team can check the account path connected to a DANA receipt, QRIS status, or phone verification step. If you are in Jakarta, keep the relevant date and reference visible so we can identify the right record while protecting unrelated account details.

Team online

Account contact

Use the support contact displayed in your account for a privacy request. Include your registered contact detail and the record you want checked, but never send your password, wallet PIN, or full payment credentials.

Wallet record check

When a DANA, OVO, GoPay, or QRIS entry needs clarification, tell us the payment rail, date, and status shown in your account. We use those details to locate the relevant record without requesting unrelated personal data.

Access question

For account access or eligibility questions, contact the same support path and explain the issue plainly. We may ask for a phone verification step before discussing private account details, where local law permits.

DATA HANDLING

What We Protect And How

Privacy work is tied to practical account actions, not a separate process you have to learn. We separate sign-in checks from payment-status records, use cookies for functions you request, and keep access…

Account security

Phone verification helps us confirm that a request comes from the account holder before private details are discussed. We do not need your password or wallet PIN to explain a policy record or identify a general data category.

Cookie choices

Cookies can remember a session, preserve a selected page setting, or help us understand whether a page is functioning. Your browser controls can remove stored cookies, although signing in again may then be required.

Payment matching

A payment reference, selected rail, amount status, and account identifier may be compared to connect a DANA, QRIS, bank transfer, or virtual account event with the correct wallet record.

Device details

We may receive browser, operating system, session, and login-event details when you use a phone or desktop. These details help identify unusual access and keep a session connected to the correct account.

Retention requests

We retain records only for the operational, security, dispute, or legal purpose described in the Privacy Policy. Ask us to explain a retention period or request a change through the account contact route.

Policy changes

If our data handling changes, we update this page so you can compare the current wording before continuing. Check the Privacy Policy from the account area after a significant change to cookies or wallet records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we expect before account creation or a wallet action. They explain the data connected to sign-in, payment status, cookies, device use, and contact requests in plain language. If your situation is not covered, use the account support route and identify the exact section or record you are asking about. We will use the details you provide only to locate the relevant privacy question.

It covers account details, phone verification, device and login events, cookies, payment-status records, retention, and requests about your data. It applies when you use the account area, including steps connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

We need a payment status and reference to connect a DANA or QRIS event with the correct account. The record can show that a request was submitted, matched, or still needs checking; it does not require you to send a wallet PIN or password.

Use the support contact displayed after login and state that you want an access request under the Privacy Policy. Include your registered contact detail and the data category, such as phone verification, cookie settings, or a QRIS receipt, so we can identify the request.

Yes, send a correction request through the account support route and name the field that is wrong. We may ask for phone verification before changing private account data. Payment records may also require the original rail and reference so the correction is applied to the right entry.

Yes. It explains cookies used for a session, selected settings, and page operation when you access the account from a phone or desktop. You can clear cookies through your browser controls, but doing so may sign you out and remove saved session preferences.

The retention period depends on the operational, security, dispute, or legal purpose stated in the Privacy Policy. Ask through the account contact route for the category and applicable period. Give us the payment rail and date, rather than sending complete wallet credentials.

Account access and eligibility depends on local law. If you need a privacy answer while travelling between Indonesian locations, contact us through the account route and avoid using a shared device. We can explain data handling without confirming private details before phone verification.