Reference

Privacy Policy For Your mahkota118 Account

Our Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile device or use DANA, OVO, GoPay and QRIS…

Account dataWallet recordsDevice controlsCookie choices

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies

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

This Privacy Policy covers data connected with your mahkota118 account, including the details entered during account opening, phone verification records, sign-in events, device signals, support messages and payment status. When you select DANA, OVO, GoPay or QRIS, we use the transaction reference and status needed to

1
match your account with the cashier record; we do not need your wallet password. Bank transfer and virtual account references may also be retained so we can investigate a pending receipt. We restrict internal access to staff who need the record for account, security or support
2
work. Where local law permits, our service processes account access for the Indonesia market; where local law differs, that rule controls. The policy applies to the website and its mobile browser path, not to a separate wallet provider’s own handling of your data.

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

PRIVACY HELP ROUTES

Where To Ask About Your Data

A clear contact path matters when a privacy question is tied to an account or payment record. Start from your signed-in account help area and include the email or phone detail attached to your account, plus the relevant receipt or status reference. We use that context to locate the correct record without asking you to send a wallet password. If you are checking access from Jakarta or another Indonesian location, mention the device path and browser involved so we can separate account data from local device storage.

Team online

Account help

Use the signed-in account help path for questions about your stored name, phone verification, sign-in history or a correction request. We may ask you to confirm the account detail before discussing records, so another person cannot obtain private account data through a casual message.

Cashier records

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, share the payment reference and date shown in your cashier record. We use the reference to find the matching status without requesting your wallet password or full wallet credentials.

Device access

If your concern follows a mobile sign-in, tell us whether you used the mobile browser, a desktop browser or a shared device. We can then explain account session data, cookie settings and the steps to sign out without treating your device contents as part of our account records.

SIX DATA CONTROLS

What We Do With Your Privacy Choices

We keep this policy practical by linking each data use to an account action you can recognise. Phone verification supports account access, device signals help identify unusual sign-ins, and payment references let…

Account opening

When you open an account, we store the registration details needed to create your profile and connect later sign-ins. A clear account path helps us tell your request apart from another person’s request. We do not treat a failed registration as permission to collect unrelated device content.

Phone verification

A phone verification step confirms that the contact detail used for account access belongs with the account request. We retain the verification result and related event details for account security. We do not ask you to place a wallet password or payment PIN in a support message.

Device signals

We may record browser type, device identifiers, session time and sign-in events to help detect unusual access. These signals do not give us access to photos, messages or other files on your phone. Signing out on a shared device closes the account session in that browser.

Cookie settings

Cookies can keep a session connected while you move from account access to the cashier or lobby. Your browser lets you remove or block them, although a blocked session cookie may require you to sign in again. We use cookie data for the stated site and security purpose.

Retention period

We keep account, support and payment references only as long as needed for the purpose described here, security checks and applicable record duties. When a record is no longer needed, we remove it or separate it from direct account identifiers where our process allows.

Requests and changes

You can ask us to access, correct or delete personal data through the account help route. Include the account contact detail and describe the requested change. We verify the request first, then explain the result, including any reason a transaction or security record must remain.

Privacy Policy Questions For Indonesia

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. They explain what the Privacy Policy covers, how to ask for account data and what happens when a question involves DANA, OVO, GoPay, QRIS or a mobile browser. Where access is discussed, it depends on local law.

The mahkota118 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how we restrict internal access and how you can request access, correction or deletion through the account help path.

No. Our Privacy Policy does not require your DANA or OVO password, wallet PIN or similar secret. For a cashier question, we use the transaction reference, date and status connected to your account. Keep wallet credentials inside the relevant wallet service and never send them to support.

We use the QRIS or GoPay payment reference and status to match a cashier event with your account and investigate an incomplete receipt. The Privacy Policy does not give us access to unrelated wallet activity. We retain the necessary transaction record for support, security and applicable record duties.

Yes. Send the request through the signed-in account help route and identify the account contact detail involved. Under this Privacy Policy, we verify that you control the account before sharing or changing records. We then explain what can be corrected, supplied or retained for security or transaction reasons.

The Privacy Policy permits records such as browser type, device signals, session time and sign-in events when they support access security. We do not treat photos, messages or unrelated files on your phone as account data. On a shared device, sign out and clear the browser session afterward.

Use your mobile browser settings to view, remove or block cookies. A session cookie may keep your account connected while you move between sign-in and the cashier, so blocking it can require another sign-in. Our Privacy Policy explains that cookie use is limited to the stated site and security purpose.

Use the account help route and include the email or phone detail attached to your account, plus a short description of the request. For DANA, OVO, GoPay, QRIS or bank transfer records, add the payment reference. We verify ownership before discussing private data or applying a change.

Privacy Policy For Your mahkota118 Account

Where To Ask About Your Data

Account help

Cashier records

Device access

What We Do With Your Privacy Choices

Account opening

Phone verification

Device signals

Cookie settings

Retention period

Requests and changes

Privacy Policy Questions For Indonesia

01 What does the mahkota118 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or OVO password?

03 How does mahkota118 use QRIS and GoPay data?

04 Can I request a copy or correction of my account data?

05 What device data is collected when I sign in?

06 How can I manage cookies on the mobile browser?

07 Who should I contact about a mahkota118 Privacy Policy request?

Related Pages