Reference

diamon123 Privacy Policy for Your Account

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

Account dataWallet detailsDevice accessContact requests
Explore Our Lobby Read FAQ
diamon123 diamon123 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Policy Help Near Your Account

A direct support route helps you ask about the Privacy Policy without posting personal details in a public channel. Sign in first when you can, then use the support path shown in your account area and include the email or phone linked to your profile. We can match a DANA, OVO, GoPay or QRIS reference more accurately when you share the transaction date and status, while sensitive credentials should stay out of every message.

Team online

Account support

Use the support route inside your account to ask what data we hold, why a verification step appeared, or how to request a correction. Include your registered contact detail so we can locate the right record without asking you to send a password.

Wallet status

For a Privacy Policy question linked to DANA, OVO, GoPay or QRIS, send the payment rail, date and visible status from your account page. We use those reference details to investigate the record while keeping your wallet PIN and login secret private.

Data request

If you want a copy, correction or deletion request assessed, contact us through the account support path and state the exact request. We may ask for an account check before acting, so one person cannot change another person’s records.

SIX DATA CONTROLS

Six Privacy Steps Behind Your Login

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

Account collection

We collect the contact and verification details needed to create and protect your account. A clear phone verification step can be required before account access, helping us connect the right person to the right profile.

Payment matching

DANA, OVO, GoPay and QRIS can provide a payment reference or status, not your wallet PIN. Bank transfer and virtual account records may also be matched to your account so a support request can be checked.

Device signals

When you sign in on a mobile browser, we may record device and session signals used for account security. These signals help us notice unusual access; they are not a request for permission to read unrelated files on your phone.

Cookies

Cookies can keep your session active, remember basic page choices and help us understand whether a login page loads correctly. You can manage browser cookie settings, although changing them may require you to sign in again.

Retention

We retain account, support and payment references only as long as needed for the stated account purpose, security checks or a legal requirement. Ask support which record you mean, and we can explain the applicable retention position.

Your request

You may contact us to ask for access, correction or deletion where applicable. After an account check, we record the request, review the relevant data and reply through the contact route connected with your profile.

Privacy Policy Questions for Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often from people considering an account in Indonesia. They explain how diamon123 treats wallet references, phone verification, cookies, device access and requests to change personal data. If your case involves a particular account or payment, use the support route shown after sign-in so we can check the correct record.

The Privacy Policy covers contact details, verification records, sign-in activity, device signals, payment references and support messages connected with your account. We use them for access, security, payment matching and requested support, rather than collecting unrelated phone files or wallet credentials.

Yes. The Privacy Policy explains that these rails may send a transaction reference or status that helps us match activity with your account. We do not need your wallet PIN. Bank transfer and virtual account references can be handled in the same account-check process.

Phone verification helps connect account access with the contact detail you supplied and can reduce mistaken or unauthorised sign-ins. The Privacy Policy treats the verification result as account-security data. We may request a fresh check when access comes from a new device.

You can ask for access to, or correction of, data connected with your account through the support route shown after sign-in. State the record you mean and use your registered contact detail. We may verify account ownership before releasing or changing anything.

Cookies can support a mobile session, remember basic settings and help us identify page-loading problems. They do not give us access to unrelated files on your device. Browser controls can remove or restrict cookies, though you may need to sign in again.

We keep account, support, security and payment references for the time needed for their stated purpose, account protection or a legal requirement. The exact period can depend on the record. Ask support about a specific item so we can assess its retention status.

Sign in and use the support path in your account, then describe whether you want access, correction or deletion where applicable. Include the relevant account contact and, for a wallet query, the date and payment status. Availability depends on local law.

Related Pages

diamon123 Indonesia Account information FAQ top77slot 11bolabet