Reference

victory39 Privacy Policy for Indonesia

Our Privacy Policy explains how we collect, use and protect the details attached to your victory39 account, including phone verification and wallet records for DANA, OVO, GoPay and…

Account clarityWallet recordsCookie choicesAccess depends on local law
victory39 victory39 Privacy Policy for Indonesia
CONTACT THE TEAM

Privacy Questions Have A Clear Route

A direct support path helps you ask what we hold, why we use it and how to correct an account detail.

Account access If your phone verification or sign-in stalls, contact account support from the same account path where possible. We use the request to check access records and can explain which detail needs correction without asking you to send unrelated personal material.
Wallet status For a DANA, OVO, GoPay or QRIS receipt question, share the payment reference and approximate time rather than a wallet password or private security code. We compare the reference with the account record and explain the status check through support.
Privacy request Ask us to access, correct or clarify personal details through the account support route. State whether your request concerns phone verification, device records, cookies or payment history, and we will use that scope to keep the response focused.
DATA HANDLING

Six Practical Privacy Commitments

We handle the Privacy Policy as an operating process, not a link placed away from your account.

Account details

We collect details needed to create and maintain your account, such as contact information and phone verification status. This lets us distinguish an access request from a general question and helps us send account-related messages to the right destination.

Payment references

A wallet or bank record can include a reference, amount status and time linked to your account. We use this narrow payment context to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity when a receipt needs checking.

Device behaviour

When you sign in from a mobile browser or desktop, we may process basic device and session details for security and fault diagnosis. These details help us identify repeated access problems without requiring the contents of your device.

Cookies

Cookies can keep a session active, remember essential settings and help us understand whether a page request completed. You can manage cookie controls in your browser, though switching off essential cookies may interrupt sign-in or the account path.

Account security

Phone verification and sign-in checks protect the account from requests that do not match its recorded access path. Never send a password, wallet PIN or one-time security code in a support message, even when asking about Privacy Policy.

Retention and changes

We retain records only while they support account operation, security, payment reconciliation or required checks. You can ask which details are held, request a correction or ask how a record is used through support, subject to access rules where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions you are most likely to ask before opening access or contacting victory39. We keep each response tied to a specific data action, such as phone verification, cookie use, wallet reconciliation or a request to change personal details. Where a legal condition affects access, it depends on local law.

The Privacy Policy covers account details, phone verification, sign-in activity, device and session data, cookies, support messages and payment references. It explains why we use each category, how it supports account access or security, and how you can ask about correction or access.

Phone verification helps connect an account request to the correct contact path and helps protect sign-in activity. We use its status for access and security checks, not as a reason to request your wallet PIN, password or one-time security code.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use the reference, time and status to match a receipt with your account when support checks a payment.

You can contact support through your account path and ask which personal details, device records, cookie settings or payment references are associated with your account. We may need an account verification step before discussing private records, and the response depends on local law.

Send a focused request through account support and identify the detail that needs changing, such as a phone number or contact record. We may ask for confirmation through the recorded account path before applying a correction or explaining why a record must remain.

We keep records for as long as they are needed for account operation, sign-in security, payment reconciliation, support history or required checks. The exact handling can vary by record and legal requirement, so ask support about the category and reason for retention.

You can manage cookies through your browser controls. Essential cookies may be needed for sign-in, session continuity and account pages, so disabling them can affect access. For a cookie question, tell support which device path you used and what changed.