Reference

djarum4 Privacy Policy For Your Account

djarum4 Privacy Policy explains what we collect when you open an account, sign in from a mobile device and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice securityPrivacy requests
djarum4 djarum4 Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Help For Login And Wallet Records

A clear contact route matters when a privacy question overlaps with account access.

Account privacy request Send your request through the support contact shown on our site and include your…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction reference…
Device access concern Tell us when an unfamiliar phone, browser session or login appears in your account.
DATA CONTROL

Inside Our Privacy And Security Process

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Account security

Before account access, we may use phone verification and sign-in checks to connect a session with your details. Device signals can help us identify an unusual login, but they are used for security review rather than as a public profile.

Cookie controls

Cookies can preserve your sign-in state and remember basic page preferences on a mobile browser or desktop session. You can adjust browser settings, but disabling required cookies may sign you out or prevent the account page from working as intended.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we retain references needed to match a receipt with your account. We do not need your wallet password, card PIN or banking login to check that record.

Retention timing

We retain account, device and payment-reference data only for the period needed for security checks, support history, disputes and legal duties. When that period ends, we delete the record or remove details that can identify you.

Correction requests

If your contact detail or verification record is wrong, contact us with the specific correction you need. We confirm ownership first, update the eligible field and tell you when the change has been applied to the account record.

Who can ask

The account holder can ask what personal data we hold, where local law permits. A representative must provide authority and pass our checks. We may refuse a request that would expose another person, weaken security or conflict with a legal duty.

Privacy Policy Answers For djarum4

These Privacy Policy answers cover the questions we expect you to ask before opening an account or contacting support. We keep the answers tied to real account actions, including phone verification, mobile sign-in, wallet references and requests to access or correct your data. If your situation is not listed, use the support path above and describe the record you want us to check. Account access depends on local law and is available where local law permits.

The djarum4 Privacy Policy covers personal data connected with your account, including contact details, phone verification, device signals, sign-in sessions, support messages and payment references. It explains why we use those details, how long we retain them and how you can request access or correction.

No. Our Privacy Policy distinguishes a payment reference from a wallet credential. When you use DANA, OVO, GoPay or QRIS, we may keep the reference and account matching details needed for support, but we do not ask for or store your wallet password or banking PIN.

We collect device and session details to connect a login with your account, identify unusual access and investigate a security question. The record can include browser or device signals and sign-in time. We use it for account protection, not as a public profile.

Use the support contact published on our site and state that you are making a Privacy Policy data request. Include your registered contact detail and the records you want checked. We verify account ownership first, then explain what can be provided where local law permits.

Yes, you can ask us to correct eligible account information, such as a contact detail or verification record. Send the request through support and identify the field that is wrong. After ownership checks, we update the record or explain why a legal or security restriction applies.

We keep payment references for the period needed to match receipts, investigate disputes, protect account security and meet legal duties. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account records. We then delete or anonymise the information under our retention process.

You may request deletion through the support route, where local law permits. We verify the request and review whether a record must remain for security, unresolved disputes or legal duties. If some data must stay, we explain the reason and remove eligible details.