Reference

istana777 Privacy Policy: Your Account Data Path

Our Privacy Policy explains what we collect when you open an istana777 account, why we use it, and how you can ask about your records.

Account clarityWallet data contextDevice accessRequest path
istana777 istana777 Privacy Policy: Your Account Data Path
PRIVATE HELP PATH

Get Privacy Help Beside Your Account

A clear contact route helps when you want a copy, correction, deletion request, or explanation of a wallet record. Send your request through the support path shown after account access, include the email or phone linked to your account, and describe the specific record. We may ask for an account check before discussing private data, including a DANA or QRIS reference.

Team online

Account contact path

Use the support contact displayed in your account to ask about stored details, a device record, or a Privacy Policy request. Include your linked phone or email so we can locate the correct account.

Cashier reference check

If your request concerns DANA, OVO, GoPay, QRIS, or bank transfer data, add the transaction reference and date. We use those details to separate your record from another account.

Access verification

Before releasing private account data, we may confirm that you control the registered contact. This step protects your login history and wallet references from an unrelated requester.

HANDLING YOUR RECORDS

What Our Privacy Process Covers

Our handling process follows the account journey rather than collecting details without a purpose. We separate login protection, payment matching, cookie function, and support requests so each record has a clear reason…

Account collection

We use your registration contact, verification result, and login events to create the right account record and respond when access fails. We do not need unrelated profile details for this account step.

Cookie choices

Session cookies can keep your account path active, while measurement cookies help us identify broken pages. You can clear browser storage, though doing so may require another login.

Device protection

We may record browser, device, and connection signals when you sign in from mobile or desktop. These signals help us spot unusual access before discussing wallet or account records.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be linked to the relevant cashier event. We use that link to resolve status questions, not to build unrelated profiles.

Retention timing

We retain records for account operation, security checks, disputes, and legal duties only as long as those purposes require. Afterward, we delete, restrict, or separate the record where practical.

Change requests

You can ask us to access, correct, restrict, or remove eligible personal details through the account support contact. We may request identity confirmation before changing a phone or login record.

Privacy Policy Answers Before Account Access

These answers address the questions you may have before opening an account or checking a wallet status. We keep the Privacy Policy practical: what we collect, how we connect it to your account, and which contact route to use when a record needs attention.

It covers account details, phone verification, login and device records, cookies, payment references, retention, and requests to access or change personal data. It applies to our service where local law permits.

We use your phone or linked contact to create the account, confirm access, and help prevent another person from requesting private records. We may verify control before discussing account history.

Yes. The Privacy Policy explains that DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may be used to match a cashier event and resolve its status.

Open the support contact shown in your account and request an account data copy. State the linked phone or email and the record you want; we may confirm your identity first.

You can request a correction through the account support path. Tell us which detail is wrong and provide the linked contact. We may retain the earlier record when needed for security or disputes.

We keep records for account operation, security, disputes, or legal duties while those purposes remain active. When they end, we delete, restrict, or separate the records where practical.

A mobile browser or desktop session may create device and login records used for account protection. Clearing browser storage can end a session, and your request still follows the support contact path.