Reference

Privacy Policy for Your istana56 Account

Our Privacy Policy shows how istana56 handles the data connected with your account, wallet activity and device access.

Account dataWallet recordsCookie choicesAccess requests
istana56 Privacy Policy for Your istana56 Account
HELP WITH YOUR DATA

Where to Ask About Privacy Policy

A clear contact path helps when you want to understand a record rather than change your account settings alone.

Account data requests Use the account help route to ask what personal data is held for your…
Wallet record questions For a DANA, OVO, GoPay or QRIS record, attach the payment reference, date and…
Login and privacy help If a login session or phone verification blocks your privacy request, tell us which…
DATA HANDLING DETAILS

What We Protect Inside istana56

Privacy work follows the same account steps you see on screen: phone verification, login, wallet status and support contact.

Account collection

We collect the details needed to create and maintain your account, including your phone number, verification result and sign-in events.

Cookie choices

Cookies and device markers can keep your session open, remember a selected language or help us understand whether a login…

Payment matching

A payment reference is used to match a wallet or bank event with the correct account.

Account security

Phone verification comes before account access, and session details help us investigate an unfamiliar sign-in.

Retention periods

We keep account, security and payment records only while they serve an operational, dispute, safety or legal purpose.

Changes and contact

You can ask us to correct account data, explain a processing purpose or provide an eligible copy.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a data request. They explain phone verification, wallet records, cookies, account access and correction steps in plain English for Indonesian customers. If your situation involves a specific payment reference or device, use the support route so we can check the relevant record directly.

The istana56 Privacy Policy covers personal data connected with account creation, phone verification, login sessions, device markers, payment references, cookies and support requests. It also explains why we use those records, how long they may remain available and how you can request access or correction.

Phone verification links an account request to the phone number you provide and helps us investigate sign-in activity. It can also reduce confusion when a wallet record is matched to an account. We use the verification result for account access and security checks, not as your wallet PIN.

Yes. The Privacy Policy covers records created when you use DANA, OVO, GoPay or QRIS, including a reference, timestamp, amount and status. Bank transfer and virtual account reconciliation can create similar records so we can answer receipt questions and identify a pending account entry.

Send a request through the account help route beside the cashier path and include your registered phone number plus the data category you want checked. We may verify account ownership before responding. Access requests are handled where local law permits and may be limited by legal duties.

You can ask us to correct inaccurate account details by contacting support with the phone number on your profile and a clear description of the change. If the request concerns a DANA, QRIS or bank record, include its reference so the correct entry is checked.

Cookies and device markers can maintain your login session, remember a language choice and help identify whether an access step completed. They may behave differently in a mobile browser and on desktop. Ask support which marker relates to your request before clearing browser data.

You may contact us to request removal of eligible personal data, and we assess the request under applicable requirements. Some account, security or payment records may need to remain for a defined operational or legal purpose. Access and eligibility depends on local law.