Reference

mtr89 Privacy Policy For Your Account

mtr89 Privacy Policy explains what we collect when you open an account, use the lobby, contact support or pay through DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record checksPhone verification
mtr89 mtr89 Privacy Policy For Your Account
PRIVATE HELP ROUTE

Ask About Your Privacy Policy Rights

A direct support route helps you ask what data is linked to your account or report a wallet record that does not look right.

Account data request Ask us to confirm the personal data connected with your mtr89 account. We may request phone verification before replying, and we will use the support route inside your account so the request stays connected to the correct account record.
Wallet record question For a DANA, OVO, GoPay or QRIS status question, send the payment reference and date through the account support path. We can compare that reference with our ledger without asking you to share a wallet PIN or full login secret.
Correction request If your phone details or account record need correction, tell us which field is wrong and why. We may ask for a fresh phone verification step before changing it, helping prevent another person from altering your personal data.
DATA HANDLING DETAIL

Inside mtr89 Privacy Controls

We handle Privacy Policy requests through the same account checks used for phone verification and payment matching.

Data collection

We collect account data you provide, security events created during login, payment references from DANA or QRIS, and support messages you send. We do not need your wallet PIN for a payment status check, and you should never place that secret in a support message.

Cookie choices

Cookies can keep a signed-in browser session working and remember a setting you selected. If you clear them on your phone, you may need to verify your phone again or sign in again before opening Fortune Panda Slots or another restricted lobby page.

Account security

Phone verification comes before account access, while sign-in time, browser details and device signals can help us identify an unusual request. If a security check interrupts access to Lightning Roulette Room, use the account support path rather than sharing your password.

Payment matching

A QRIS receipt, DANA reference, bank transfer code or virtual account record helps us connect a payment event to your account. We use the reference to check status and resolve mismatches; the policy does not ask you to disclose a wallet PIN.

Retention period

We keep account, security and transaction records only while they serve account operation, dispute checks or legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers where that is practical.

Your request path

To request access, correction or clarification, sign in, open the support route and describe the exact record involved. We may confirm your phone before responding, and we will explain if a requested change cannot be made because a transaction or legal record must remain.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps most relevant to your use of mtr89 in Indonesia. They explain the data connected with phone verification, mobile access, local wallet payments, browser cookies and requests made through support. If your question concerns a particular record, include its date and reference after signing in so we can check the right account.

The mtr89 Privacy Policy covers data collected when you open an account, verify your phone, sign in, use the lobby, send support messages or make a payment. It also explains cookies, security signals, retention and the steps for requesting access or correction.

We use your phone number to create and verify the account, help prevent unauthorised access and connect support requests with the correct account. A phone verification step is required before account access, and we do not ask you to send a wallet PIN.

Yes. The Privacy Policy covers payment references and status data received or submitted for DANA, OVO, GoPay and QRIS. These details help us match a deposit or withdrawal request, but they do not give us your wallet password or PIN.

Sign in, open the support route shown in your account and ask for the personal data connected with your account. Include the account phone number and the records you mean. We may complete another phone check before releasing account-specific details.

You can request a correction through the signed-in support path. State which field is inaccurate and provide the reason for the change. We may ask you to verify your phone again, and transaction records may stay unchanged when they must support a payment check.

Cookies may keep your mobile session active and remember a selected setting. Clearing them can sign you out and require phone verification again. The Privacy Policy explains that browser storage and device signals are used for session function and account security.

Yes. Account access depends on local law, and some data requests may be limited where a security, payment or legal record must remain. We explain the reason through the support route. You can still ask us to clarify what data is held and why.