Reference

istana 62 Privacy Policy: Your Account Data Path

Our Privacy Policy explains what we collect when you open an account, verify your phone and use DANA or QRIS, plus how we protect those records.

Clear collection rulesWallet record handlingAccount access choicesPolicy contact route
istana 62 istana 62 Privacy Policy: Your Account Data Path
CONTACT OPTIONS

Get Privacy Help Through Your Account

A direct support path helps when you want to ask about a phone number, wallet reference or stored account detail. Open your account support area and include the subject of your request, the affected account step and a safe way for us to respond. We do not ask you to send a password or full wallet credentials. The same route is available from mobile and desktop access.

Team online

Data questions

Ask which account details are held, why a phone verification record is needed and whether a specific DANA, OVO or GoPay reference belongs to your activity.

Change requests

Request a correction through account support, naming the field that needs attention. We may ask for an account step or phone check before changing personal details.

Access concerns

If a mobile session or desktop login shows unfamiliar activity, contact support through the account path and mention the device type without sharing your password.

HANDLING DETAILS

Six Practical Privacy Safeguards

Privacy work is part of each account step, not a separate page you need to chase. We separate identity checks from wallet references, limit internal access to operational needs and keep policy…

Account data

We may collect your phone number, verification result and account activity needed to provide access. We use those details for account control, security checks and support replies.

Wallet references

DANA, OVO, GoPay and QRIS records can show a payment reference, amount status or time. We use the reference to match activity, not to request your wallet password.

Cookie choices

Cookies and similar browser storage can keep a session active, remember basic preferences or help us identify technical faults. You can manage browser controls, though some account steps may then need repeating.

Session security

Phone verification supports account access, while session checks help flag unusual sign-ins. Sign out on shared devices and keep your password private; our support team will not need the password.

Retention period

We keep account, security and transaction records for as long as operational, dispute or legal needs require. When a record is no longer needed, we remove or restrict it where practical.

Policy changes

If this Privacy Policy changes, we place the updated wording on this page. For a correction, copy request or deletion question, contact support through your account and describe the record involved.

Privacy Policy Questions From Indonesia

These answers address the account and wallet questions we expect before you continue through registration. They explain how the Privacy Policy relates to phone verification, browser sessions and local payment references. If your situation is different, use the account support route and give us only the details needed to locate the request.

It covers account details, phone verification, browser sessions, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to confirm account access and help protect your session. The result can be retained with the account record for security, support and legal needs.

Our Privacy Policy does not require you to send a wallet password to support. We may handle payment references and status details, while your DANA or QRIS credentials remain with the relevant wallet service.

Open the account support path, identify the detail that needs correction and explain the account step involved. We may request phone verification before changing personal account data.

We retain account, security and transaction records while operational, dispute or legal needs continue. After that, we remove or restrict them where practical, subject to local requirements.

Yes. Send an access request through account support and describe the account record you want checked. We may confirm your identity before discussing personal data or wallet references.

You can request removal through the support route, explaining which record you mean. We assess the request against operational, security and legal retention needs because access depends on local law.