Reference

isu88 Privacy Policy for Indonesian Accounts

Your account details, wallet records and device sessions are covered by the isu88 Privacy Policy, so you can see what we collect and why.

Account clarityWallet record contextCookie choicesRequest access
isu88 isu88 Privacy Policy for Indonesian Accounts
HELP WITH PRIVACY

Get Privacy Policy Help From Your Account

A privacy question should not get lost beside a wallet issue. We connect your request to the account details already on file, so our team can check a DANA receipt, QRIS reference or login event without asking you to post sensitive details in an open message. Use the support contact displayed in your account area, include the email or phone linked to your account, and describe whether you need access, correction, deletion or a retention explanation.

Team online

Account contact

Open the support contact shown after login and identify the account email or phone connected with your request. We use that step to locate the correct privacy record before discussing DANA, OVO, GoPay or QRIS activity.

Wallet record check

If your request concerns a payment reference, send the date, rail and visible status rather than a wallet password. Our team can compare a QRIS receipt or bank transfer reference with the account record while limiting extra details.

Access request

Ask for a copy, correction or removal assessment through the same account support route. We may verify the request with a clear account step before changing records, which helps prevent another person from altering your privacy details.

DATA HANDLING

Privacy Controls Behind Your isu88 Account

We keep this policy practical by linking each data purpose to an account action you can recognise. Login checks, wallet reconciliation and device-session controls use different signals, while cookies help maintain the…

Account details

We may use your account name, contact route and verification result to connect a privacy request with the right account. A clear phone verification step can be required before we disclose, correct or change details tied to account access.

Device sessions

A phone or desktop session can create technical records such as login time, browser path and security signals. These help us identify an unfamiliar access attempt; they are handled as account-security data, not as permission to inspect unrelated device content.

Cookie choices

Cookies can keep your sign-in state and remember a page setting during a visit. You can adjust cookie controls in your browser, although removing a required session cookie may sign you out or interrupt a requested account action.

Payment references

DANA, OVO, GoPay and QRIS may provide a reference or status connected with an account transaction. We use that limited record to match a receipt, investigate a mismatch and document the account event without requesting your wallet password.

Retention period

We assess how long a record is needed for its stated purpose, account support or a legal duty. When a detail is no longer required, our handling process can remove it, separate it from direct account identifiers or restrict its use.

Request ownership

Send privacy requests through the contact route inside your account so we can confirm ownership before sharing details. State whether you seek access, correction, deletion or a reason for retention, and we will route the request for review by the relevant team.

Privacy Policy Answers for isu88 Accounts

The questions below cover the account and wallet situations most likely to matter before you open an account. Each answer stays within the isu88 Privacy Policy scope, from cookies on a mobile browser to a request about a QRIS record. If your case is not listed, use the account support contact and describe the exact detail you want us to check.

The isu88 Privacy Policy covers account details, verification records, login and device-session events, cookies, support messages and payment references. It explains why we use each type of record, how retention is assessed and how you can request access, correction or deletion where local law permits.

No. Our Privacy Policy does not require your DANA or QRIS wallet password. We may receive a transaction reference, amount status or confirmation needed to match an account event, while your wallet credentials remain with the relevant payment service.

Use the support contact shown inside your signed-in account and ask for an access copy under the Privacy Policy. Include the email or phone linked to the account and identify the record sought; we may complete phone verification before releasing account details.

Yes, you can request a correction or ask whether removal is available under the Privacy Policy and applicable rules. Tell us which detail is wrong or no longer needed. We first confirm account ownership, then explain any record that must remain for a legal duty.

Cookies can keep your mobile session connected, remember a selected page setting and help protect an account access step. You can change browser cookie controls, but removing a required cookie may sign you out. The Privacy Policy explains the purpose of each cookie category.

Retention depends on why the record exists, such as matching a QRIS receipt, resolving an account question or meeting a legal duty. The Privacy Policy does not treat every record identically. Contact support with the reference and ask for the applicable retention explanation.

Sign in and use the account support contact displayed near your account help route. Describe the concern without sending a wallet password, and include only the relevant reference, such as a DANA status or login date. Access depends on local law and where local law permits.