Reference

Privacy Policy For Your mansion138 Account

Your account details, device signals and wallet activity have a clear place in our Privacy Policy.

Account clarityWallet recordsDevice securityPolicy requests
mansion138 Privacy Policy For Your mansion138 Account
CONTACT YOUR WAY

Privacy Help Near Your Account Route

A message through the account support route gives us enough context to handle a Privacy Policy request without asking you to repeat private wallet details in an open channel.

Account message Use the signed-in account message route for a Privacy Policy question, access request, correction request, or deletion enquiry. We can connect your message to the relevant account record and ask for a verification step before discussing private details.
Wallet status If QRIS, DANA, OVO or GoPay activity appears under the wrong status, send the transaction date and reference through account support. We check the matching record without requesting your wallet PIN, banking password, or full secret credentials.
Access check A failed sign-in or phone verification request may require an account match before we disclose personal data. We use the registered account path, confirm the request belongs to you, and keep the reply limited to the Privacy Policy matter.
DATA CARE DETAILS

What Our Privacy Policy Covers

Your account security depends on practical controls, not vague promises. We record the details needed for account creation, phone verification, cashier reconciliation, and device-session checks, then limit handling to those purposes.

Account data

We may hold your account identifier, contact details, phone verification result, login events, and selected access settings. These records help us connect a request to the right account and prevent private account details from being sent to the wrong person.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account event can create a reference, amount, time, and status record. We use that data to reconcile your cashier request and answer a status question without collecting your wallet password.

Device signals

We may record browser type, operating system, session time, and security signals from the device used to reach the lobby. These signals help identify unusual access and protect your account; they are not a request for files stored on your device.

Cookies

Cookies can keep your session available, remember a language or access choice, and show whether a page works on your phone. Our Privacy Policy explains their purpose, while your browser controls whether optional storage remains on the device.

Retention

We retain account and transaction records only for the period needed for security, reconciliation, legal duties, or a dispute described in the policy. When a record no longer serves those purposes, we remove it or separate it from direct account identifiers.

Your request

You can ask for access, correction, or deletion of eligible personal data through the account contact route. We may verify your identity first, explain any legal or security limit, and confirm what action we took on the request.

Privacy Policy Answers For Indonesia

Privacy Policy questions often arise while you create an account, check a wallet status, or return to the lobby from a phone. These answers explain how mansion138 approaches personal data in those moments, including what we need for verification and which request route to use. If a question concerns eligibility or access, that outcome depends on local law and applies where local law permits. For a record-specific matter, use the signed-in account contact path.

The Privacy Policy covers account details, phone verification, login events, device signals, cookies, wallet references, transaction statuses, retention, and your available data requests. It explains why we use each category, how we protect account access, and how to contact us about a correction or deletion.

We use a DANA or QRIS reference, amount, time, and status to match your cashier request with the correct account record. This helps us investigate a delayed or mismatched status. We do not need your wallet PIN, banking password, or secret wallet credentials.

You can send an access request through the signed-in account contact route. We may ask for an account or phone verification step before releasing personal data. Our reply identifies the records covered, explains any lawful restriction, and follows the retention terms in the Privacy Policy.

Send the correction request through account support and identify the field that needs changing, such as a contact detail or account setting. We verify that the request belongs to you, update eligible records, and explain if a transaction or security record must remain unchanged.

Retention depends on the reason for holding a record, including account security, cashier reconciliation, legal duties, or an active dispute. The Privacy Policy sets the applicable approach. Once the purpose ends, we remove the record or separate it from direct account identifiers.

You can ask for deletion through the account contact path, and we assess which records are eligible. Some information may need to remain for security, transaction reconciliation, legal duties, or a dispute. We explain the result and any limitation rather than silently ignoring your request.

Yes. The Privacy Policy describes device signals such as browser type, operating system, session time, and security events, along with cookies used for session and page functions. Browser settings can manage optional storage, while account verification still protects private account discussions.