Reference

Privacy Policy for master138 Accounts

Our master138 Privacy Policy explains what account, device and wallet details we collect, why we use them, and how you can request access or changes.

Account dataWallet recordsDevice controlsCookie choices
master138 Privacy Policy for master138 Accounts
CONTACT ROUTES

Where To Ask About Privacy

A direct contact route helps you resolve a privacy question without explaining your account history repeatedly.

Account privacy request Send an access, correction or deletion question from the contact path connected to your…
Wallet data question For a DANA, OVO, GoPay or QRIS record, mention the date and receipt reference…
Login data concern If you notice an unfamiliar sign-in, device session or phone-verification event, contact us through…
DATA PRACTICES

How We Handle Your Privacy Choices

We keep this policy practical by connecting each data category to an account action you can recognise.

Account details

We use your registration details and phone verification status to identify the account you ask about. We do not need your password in a privacy request, and we use the contact detail already attached to the account for identity checks.

Device records

When you sign in from a phone or tablet, technical details such as session time, browser type and device signals may be recorded. These records help us examine unusual access around the account without reading unrelated content on your device.

Cookie controls

Cookies and similar browser storage can keep sign-in state and selected preferences available during your session. You can adjust browser settings or contact us about cookie questions, although removing required storage may affect account access.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be linked to an account transaction reference. We use those references for status checks and payment reconciliation, not as a request for your wallet PIN.

Security checks

A request to view or change private data may require phone verification or another account check. This step protects your details when a request comes from a new device or does not match the registered account contact.

Retention requests

We retain records only as long as needed for the stated account, security, dispute or legal purpose. Ask us about a specific record, and we will explain whether deletion is available or why a limited retention period applies.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened or checked. They cover the data connected with phone verification, sign-in devices, cookies, game pages and local wallet records. If your situation is not listed, use the account contact route and describe the exact record or account step you want us to check.

It covers registration and phone-verification details, device and session records, cookies, support requests, game-page activity and payment references. The Privacy Policy also explains your access and correction options, plus limits that may apply where local law permits.

Our Privacy Policy does not ask you to send a DANA or QRIS PIN in a support request. We may keep a transaction reference, receipt status or payment method label so we can check account activity without receiving your wallet authentication code.

Use the contact route connected to your account and request an account-data copy. Include your registered phone detail, but never include your password or wallet PIN. We verify the request before explaining which records can be provided and in what format.

Yes. Send a correction request through the account privacy route and identify the field that is wrong, such as a phone detail or contact record. We may complete a phone check first, then update eligible data or explain why a record cannot be changed.

Cookies and browser storage can remember sign-in state and account preferences on your phone or tablet. You can adjust your browser controls or contact us about a cookie choice. Removing required storage may mean that phone verification is requested again.

Retention depends on the reason the record exists, including account security, payment reconciliation, dispute handling or a legal requirement. Ask about a particular account or QRIS, OVO, GoPay, DANA or bank-transfer record, and we will explain the applicable retention position.

You may ask us to delete eligible personal data through the account contact route. We first verify your identity and check whether a record must remain for security, payment reconciliation, disputes or legal duties. We will explain any limit rather than removing records without review.