Reference

Open mahkota 188 Privacy Policy

mahkota 188 Privacy Policy explains what we collect when you create an account, sign in from mobile or desktop, and use payment screens such as DANA Wallet Topup.

Account dataDevice accessCookie choicesPayment status
Explore Our Lobby Read FAQ
mahkota 188 Open mahkota 188 Privacy Policy
CONTACT THE TEAM

Reach Support About Privacy

A clear contact path matters when you want to ask about the Privacy Policy or correct account data.

Account privacy request Use the account support path to ask what personal data is linked to your…
Wallet data question For a DANA, OVO, GoPay or QRIS query, send the payment reference rather than…
Access or deletion request Ask through support when you want a copy, correction or removal assessment for your…
HANDLING YOUR DATA

Explore Our Privacy Controls

The Privacy Policy is supported by practical controls rather than a broad promise. We separate sign-in details from payment references, limit account discussions until ownership is checked and use device signals to…

Collected account details

We may collect your contact details, verification result, sign-in events and account choices needed to provide account access. We do not need your password in a support message. When you ask for a copy of your data, we match the request to the verified account record.

Device and session signals

A mobile browser or desktop session can produce technical signals such as device type, browser version, approximate region and session time. We use these signals to maintain access and flag unusual sign-ins, not to inspect unrelated files or messages stored on your device.

Cookies and browser storage

Cookies can keep a sign-in session connected and remember selected page settings. You can clear or restrict them through your browser controls, although doing so may require another sign-in or affect a saved preference. Our policy explains which cookie purpose applies to the page you open.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may create a reference, amount, status and timestamp for account reconciliation. We use that record to match your receipt and cashier result, while avoiding requests for wallet passwords or unnecessary credential details.

Account security steps

Phone verification can be required before account access or before we discuss private account details. If a session appears unusual, we may ask you to sign in again or confirm ownership. Keeping your password private and using your own device helps us protect the account record.

Retention and changes

We retain personal data only while it serves account operation, security, transaction matching or a legal need. You can request correction, access or removal assessment through support. If the policy changes, we place the updated wording on this page so you can check the effective handling rules.

Browse Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain account data, device behaviour, cookies, wallet references and requests for access or changes. If your situation is specific, use the account support path with your verified contact detail rather than posting private payment credentials in a message.

The mahkota 188 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and retention. It also explains how to request access, correction or removal assessment. Any access or eligibility question depends on local law and the region where you are located.

Phone verification helps us connect a request or sign-in to the correct account before private details are discussed. It can also support an unusual-session check. We do not ask you to place a password in support messages, and we use the verified account path for privacy requests.

A DANA or QRIS transaction can create a reference, amount, status and timestamp so we can match a receipt with the account record. The same approach can apply to OVO, GoPay, bank transfer or virtual account activity. We do not need your wallet password for this check.

Yes. The Privacy Policy covers technical signals from a phone or desktop session, such as device type, browser version, approximate region and session time. We use them for sign-in continuity and unusual-access checks. We do not inspect unrelated files or messages stored on your device.

Use the account support path and request a correction, copy or removal assessment. We confirm account ownership before sharing or changing private records. Some data may need to remain for transaction matching, security or legal reasons, and we explain that reason before completing the request.

We keep personal data while it supports account operation, security checks, payment reconciliation or a legal need. Retention can differ by record type. Ask support for the category linked to your account, and we will explain the applicable period or removal assessment under the Privacy Policy.

Open the support link from your account and include the contact detail tied to your profile. For a wallet question, add the receipt reference without sending a password or full credential. We use that route to identify the correct record and respond to your Privacy Policy concern.

Related Pages

mahkota 188 Indonesia Esports Valorant Access guide About Us FAQ