Reference

diamond 138 Privacy Policy Explained

The diamond 138 Privacy Policy shows what we collect when you open an account, sign in through a mobile browser, or check wallet status for DANA, OVO, GoPay…

Account clarityWallet recordsCookie choicesContact access

Explore Our Lobby Read FAQ

How Wallet Records Fit Privacy Policy

diamond 138 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to account details, sign-in activity, device signals, support messages and payment references connected with your use of diamond 138. When you choose DANA, OVO, GoPay or QRIS, we may retain the wallet name, transaction reference, amount and status needed to match your

1
account request; we do not need your wallet PIN or one-time code for that matching step. Bank transfer and virtual account references can be handled in the same way. Access depends on local law, and we may ask for account verification before changing personal details or
2
discussing a payment record. The policy also explains cookies, retention, security controls and how to request correction or deletion.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Help Beside QRIS Records

A clear support path helps when a Privacy Policy question involves account access or a wallet reference.

DATA PRACTICE

Inside diamond 138 Account Privacy

We keep this policy practical by linking each data use to an account action: opening access, checking a wallet reference, protecting a session or answering a request.

Data collected

We may collect your account name, contact detail, sign-in events, device signals, support messages and payment references. A DANA, OVO, GoPay or QRIS record is used to connect a transaction status with the correct account request.

Cookie controls

Cookies can keep a session active, remember a selected language or help us detect unusual sign-in behaviour. You can manage cookies through your browser settings, although disabling some may affect account access or saved preferences.

Account security

We may ask you to verify the registered phone or email before changing account data or discussing a wallet reference. Never send a wallet PIN or one-time code in support messages; those credentials are not needed for Privacy Policy requests.

Retention period

We retain account and payment records for as long as needed to provide access, resolve disputes, meet legal duties or protect the service. When a record no longer has a stated purpose, our retention process can remove or anonymise it.

Correction requests

If your name, phone or email is inaccurate, use the account support route and identify the field you want changed. We may confirm ownership first, then update the record or explain why a particular entry must remain unchanged.

Deletion requests

You can ask us to delete personal data by contacting support from your registered account path. Some records may remain where needed for a payment dispute, security event or legal duty; we will state the reason when that applies.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account access. They cover wallet records, cookies, device changes, verification and requests for personal data. If your situation is not listed, contact us through the signed-in support path and include only the details needed to locate your account.

The diamond 138 Privacy Policy covers account details, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain, how security checks work and how you can request access or correction.

Yes. Privacy Policy coverage includes the wallet name, transaction reference, amount and status needed to match DANA, OVO, GoPay or QRIS activity with your account. We do not need your wallet PIN or one-time code to check that reference.

Use the signed-in account support route and ask for an access request under the diamond 138 Privacy Policy. Include your registered phone or email and describe the records you need. We may verify account ownership before preparing the relevant data.

You can request a correction to your name, phone or email through account support. State which field is inaccurate and provide the registered contact detail. We may confirm ownership first, then update the record or explain any limit on the change.

The Privacy Policy follows your account when you move between a mobile browser and the iOS App Install path. We may record device and sign-in signals to protect access, but a device change does not remove your ability to request or correct personal data.

Cookies may keep your session active, remember preferences and help detect unusual sign-in activity. You can manage them in your browser settings. If you clear or block certain cookies, sign-in and saved choices may work differently, while the Privacy Policy still applies.

Send a deletion request through the signed-in support path and identify the account record you want removed. We assess the request under the diamond 138 Privacy Policy. Records needed for disputes, security events or legal duties may remain, with the reason explained.

diamond 138 Privacy Policy Explained

Get Privacy Help Beside QRIS Records

Inside diamond 138 Account Privacy

Data collected

Cookie controls

Account security

Retention period

Correction requests

Deletion requests

Privacy Policy Answers For Your Account

01 What does the diamond 138 Privacy Policy cover?

02 Does Privacy Policy cover DANA, OVO, GoPay and QRIS data?

03 How can I request my diamond 138 account data?

04 Can I ask for a correction to my personal details?

05 How does Privacy Policy apply when I change devices?

06 How are cookies handled on diamond 138?

07 Where can I ask about a Privacy Policy deletion request?

Related Pages