Reference

istana338 Privacy Policy For Your Account

Our Privacy Policy explains how istana338 collects, uses, stores and protects the data connected with your account, wallet activity and support requests.

Clear data purposesWallet details explainedAccount request pathIndonesia access wording
istana338 istana338 Privacy Policy For Your Account
CONTACT DATA HELP

Use Our Account Privacy Support Path

A direct support route helps you ask what data we hold, why a record appears or how to request a correction. Sign in first when you can, because the account path lets us match your request without exposing details to the wrong person. If you are in Semarang or elsewhere in Indonesia, include the relevant device, account step and payment reference so we can check the case accurately.

Team online

Account support link

Send a Privacy Policy question through the support link inside your account. We can match your message with the phone-verification step and respond without asking you to share a wallet password.

Payment data check

For a DANA, OVO, GoPay or QRIS query, include the payment reference and approximate time. We use those details to locate status records while keeping the wallet credential outside our support request.

Access request

If you cannot sign in, explain the failed account step and device path in your message. We may ask for extra confirmation before discussing personal data or changing account contact details.

DATA HANDLING

Explore How We Handle Privacy Requests

We keep our Privacy Policy practical: each data purpose connects to an account, security, payment or support action.

Data collection

We collect details needed for account creation, phone verification, sign-in protection, support replies and payment matching. We do not need your DANA, OVO or GoPay wallet password to check a transaction reference.

Cookies and devices

Cookies and similar device signals help keep your session active, remember security choices and identify unusual access. Your phone browser may create a new session after cookies are cleared or device settings change.

Account security

Phone verification helps connect account access to the contact detail you supplied. We may compare sign-in time, device signals and account actions before discussing data or changing important account details.

Payment records

A QRIS, bank transfer or virtual account reference helps us match a payment status. Records may mention BCA, BRI, Mandiri or BNI, but wallet passwords and banking credentials should remain with your provider.

Retention periods

We retain account, security and transaction records only as long as needed for the stated service purpose, dispute handling or applicable legal duties. After that period, records are deleted or separated from direct account use.

Changes and contact

Ask us to correct, access or clarify your personal data through the account support link. Include your registered contact detail and request type; we may verify ownership before making a change.

Browse Privacy Policy Answers

These questions cover the Privacy Policy points Indonesian account holders usually need before sharing details with us. Each answer focuses on a practical step, from phone verification and cookies to payment references and requests for access or correction.

It covers data linked to account creation, phone verification, sign-in events, device signals, payment references, cookies and support messages. It also explains retention, security checks and how to request access or correction.

Phone verification helps confirm that the person requesting account access or a data change controls the registered contact detail. It also helps us investigate unusual sign-in activity without relying only on a password.

No. The Privacy Policy describes payment references and status details used to match DANA, OVO, GoPay or QRIS activity. Your wallet password and banking credentials should stay with the relevant payment provider.

We may collect browser, device, session and sign-in details connected with account security. If you clear cookies or switch from a phone to a computer, the new session may require another security check.

Use the support link inside your account and state that you want a data access request. Include your registered contact detail and the records involved; we may verify ownership before responding.

Yes. Send a correction request through the account support route, explain which detail is wrong and provide the updated value. We may ask for phone verification before changing contact or payment-related records.

We keep records for the operational purpose described in the Privacy Policy, including security checks, payment matching, disputes or applicable legal duties. When no longer needed, they are deleted or separated from direct account use.