Reference

idn789 Privacy Policy For Your Account

idn789 explains how we handle the details connected with your account, including phone verification, DANA, OVO, GoPay and QRIS records.

Clear data purposesWallet record handlingDevice and cookie choicesAccount contact path
idn789 idn789 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you ask what data we hold, why a record appears or how to request a correction. Keep your account identifier ready, but never send a password, wallet PIN or one-time verification code. We use the account support route shown on our site so your request can be matched with the right account record.

Team online

Account request

Use the account support path to ask for a copy, correction or deletion request connected with your idn789 account. Include the phone number attached to verification so we can locate the record.

Payment query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, share the transaction reference and date. We use those details to check the wallet status without asking for your secret PIN.

Access concern

If a new device, login alert or verification message seems unfamiliar, contact support through the account route before sending further documents. We may ask account questions to confirm the request is yours.

DATA PRACTICE

How We Handle Your Account Records

Our Privacy Policy is designed around practical account events rather than broad promises. We separate access checks from payment references, explain cookie use in plain terms and give you a route to…

Account details

We use your submitted account details, including your verified phone number, to create access, send account messages and connect your requests with the correct record. We do not need your wallet PIN for these steps.

Payment references

A DANA, OVO, GoPay or QRIS transaction may leave a reference, amount and status in our records. Bank transfer and virtual account checks use matching references so we can resolve an account query.

Cookies

Cookies and similar device storage can keep your session active, remember selected settings and help us detect repeated sign-in failures. You can manage cookies through your browser, though some account steps may then need repeating.

Security checks

We may compare a sign-in with device, browser and timing signals to identify unusual access. A phone verification request or extra account question can appear when those signals do not match your usual pattern.

Retention period

We retain account, payment and support records for as long as needed for the stated purpose or a legal requirement. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Your request

You can ask what we hold, request a correction or ask about removal through the account support path. We may verify your identity first, and access depends on local law for the request involved.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. If your situation is unusual, use the support route with a transaction reference or verified phone number, and we will assess the request under the rules that apply where you are.

The idn789 Privacy Policy covers account details, phone verification, device signals, cookies, support records and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to complete account verification, connect you with the correct account and protect access when a sign-in or account request looks unusual. We do not ask for your wallet PIN.

Yes. The Privacy Policy covers payment references and status checks for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity connected with your account.

Use the account support path and state that you want a copy of your account data. Include your verified phone number or account identifier, but leave out passwords, wallet PINs and one-time codes.

Yes. Send a correction request through the account support route and explain which detail is wrong. We may ask an account question before changing it, and the request depends on local law.

We keep payment references and related account records only as long as needed for account support, reconciliation, security or a legal requirement. After that, we remove them or separate them from identifiers.

Yes. Our Privacy Policy explains that cookies can support sessions, settings and security checks. You can manage them in your browser, although disabling them may require repeated sign-in steps.