Reference

id789 Privacy Policy For Your Account

The id789 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet status for DANA, OVO, GoPay and…

Clear data purposesWallet records explainedCookie choicesContact route
id789 id789 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Through Support Chat

A clear contact route matters when you want to ask about the Privacy Policy, correct account details or understand a wallet record.

Policy questions Use the Support Chat Center to ask why a phone number, device signal, cookie…
Correction requests If your contact detail or account record needs correction, send the request through the…
Wallet records For a DANA, OVO, GoPay or QRIS status question, include the visible reference and…
HANDLING DETAILS

What We Do With Account Records

Privacy depends on practical handling, not broad promises. We separate account access from wallet credentials, use phone verification before sensitive changes and keep policy requests tied to a clear contact path.

Account details

We collect the details needed to create and maintain your account, including contact data and verification status. We use them to identify your account, respond to requests and keep the correct person connected to account changes, rather than asking for unrelated personal details.

Wallet references

A DANA, OVO, GoPay or QRIS action may create a reference, status and timestamp in the account record. We use that limited payment context to match a requested action and resolve a receipt question; we do not ask you to place wallet passwords in chat.

Cookies and devices

Cookies help keep a signed-in session working, remember selected settings and support security checks. Device and browser signals may be compared when access looks unusual. You can manage browser cookie settings, although disabling some cookies may interrupt account access or policy preferences.

Account security

Phone verification comes before sensitive account access or changes. We also use session controls and security event records to investigate unfamiliar sign-ins. Keep your password and verification code private; support will not need those secrets to explain a Privacy Policy request.

Record retention

We retain records for as long as their stated purpose requires, including account support, transaction checking, security review and legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account identification where the applicable rules allow.

Changes and contact

To request access, correction or clarification, contact us through the Support Chat Center from your account path. Tell us which record concerns you and use the verified account route when asked. We may update this Privacy Policy when our handling or legal obligations change.

Privacy Policy Answers For id789

These Privacy Policy answers address the searches we hear most often from people preparing an account in Indonesia. They cover the records created during phone verification, wallet actions, browser access and support contact. If your situation is specific, open the Support Chat Center from your account path and describe the exact record or request.

The id789 Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet references, support messages, security events and retention. It explains why we use each category, when we may disclose it for a legal duty and how you can request access or correction.

Phone verification helps connect account access and sensitive changes to the correct account holder. We may request it before discussing personal records or changing contact details. Keep the code private, and use the Support Chat Center if the verification step does not match your account.

Yes. The Privacy Policy covers payment references, status and timestamps connected with DANA, OVO, GoPay and QRIS actions. We use that context to match an account request or receipt question. We do not ask you to send wallet passwords or one-time codes through support.

You can ask for access, clarification or correction through the Support Chat Center from your account path. Describe the record, such as a phone detail or wallet reference. We may verify your account first, and some requests can be limited by legal or security requirements.

On a mobile browser, cookies can keep your session active, retain selected settings and support security checks. Browser controls let you manage them. If you block required cookies, the account path may not work correctly, so you may need to adjust settings before contacting support.

We keep each record for the period needed for its stated purpose, such as account support, transaction matching, security work or a legal duty. When that purpose ends, we remove the record or reduce its direct connection to your account where applicable rules allow.

Use the Support Chat Center from your verified account path and ask which Privacy Policy section changed or affects your request. We may update the policy when handling practices or legal duties change. Account access and eligibility still depends on local law, even after a policy update.