Reference

Open menu168 Privacy Policy With Clarity

menu168 Privacy Policy explains how we handle your account details, wallet records and device access when you use our Indonesia service.

Account dataWallet recordsMobile accessPolicy contact
Browse The Lobby Read FAQ
menu168 Open menu168 Privacy Policy With Clarity
CONTACT THE DESK

Reach Support About Privacy Policy

A clear contact path helps you act on the Privacy Policy instead of guessing which account detail needs attention. Use the support route connected to your menu168 account when you need a copy of your stored details, want to ask why a wallet record appears, or need help correcting a phone number. Include the account phone number and a short description, but never send a wallet password or full payment credential. We use the account step to confirm that a request comes from you before discussing personal data.

Team online

Account data request

Ask support for the personal details linked to your account, including the account identifier, phone verification status and available contact records. We may ask you to complete an account check before sending those details, so the request does not expose your data to another person.

Wallet status question

If a DANA, OVO, GoPay or QRIS reference looks incorrect, send the transaction reference and approximate date through the account support route. We can compare the payment status with the account record without asking for your wallet password or private security code.

Correction request

Tell us which account detail needs changing and why it is no longer accurate. For a phone update or identity-related correction, we may request a fresh verification step, then confirm what was changed and retain the request record under the Privacy Policy.

DATA HANDLING

Browse menu168 Privacy Controls

We handle privacy through ordinary operating steps that you can recognise: account checks before disclosure, limited access to payment references, device signals used for security, and retention tied to the reason data…

What we collect

We receive details you provide during account opening and phone verification, plus technical data from the browser or device used to sign in. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account can show amount status and timing, while wallet passwords remain with the wallet service.

Why we use it

We use account and device details to let you sign in, keep the correct account connected to a payment, investigate a stalled status and respond to support requests. We do not turn a Privacy Policy request into a general marketing message; each use must relate to service operation or a legal duty.

Cookies and storage

Browser cookies or local storage can preserve a session, remember a language setting or help identify a broken page path. You can remove them through your browser settings. After removal, the account may require phone verification again, and some saved preferences may no longer appear.

Account security

We use phone verification and account checks before discussing personal records or changing sensitive details. Keep your sign-in details private, sign out on a shared device and contact support if an unfamiliar device appears. We can investigate the account event using its time, device path and related status record.

Retention period

We keep personal data only while it supports the stated service need, an open account request, a payment reconciliation or a legal duty that depends on local law. When the reason ends, records may be deleted, anonymised or retained in a restricted form where a documented obligation requires it.

Your request path

You can ask what personal data we hold, request a correction, ask about deletion or question a processing purpose through the account support route. Include your account phone number and request type. We verify ownership first, then explain any limit or next step that applies to your case.

Find Answers In Privacy Policy

These Privacy Policy answers address the account questions you are most likely to have before using menu168 from Indonesia. They explain what happens around phone verification, wallet records, browser access, correction requests and account closure without turning the page into a general service description. If your situation involves eligibility or access, the answer can depend on local law, so contact us with the account details needed to identify your request.

The menu168 Privacy Policy covers account details, phone verification, device and browser signals, support messages, cookie storage and payment references. It explains why we use those records, how we protect access, how long we retain them and how you can ask for access, correction or deletion where local law permits.

We may store a payment reference, status, timing and account connection for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those details to match a transaction and investigate a stalled status. We do not need your wallet password or private wallet security code.

Yes. Send an account data request through the support route linked to your account and include the phone number used for access. We first confirm ownership, then identify the records available for disclosure. The response can be limited when another person’s data or a legal duty is involved.

Describe the incorrect detail, the replacement and the reason for the change through account support. Phone changes may require a new verification step, while a payment reference may need the transaction date and reference. We confirm the result after checking the request against the account record.

We may use cookies or similar browser storage to keep a session, remember a setting or identify a page problem. You can clear this storage in your mobile browser, but doing so may sign you out and bring back phone verification. Your browser controls also let you manage stored site data.

We use phone verification, account ownership checks and device or browser signals to reduce the chance of a personal-data disclosure to the wrong person. Do not share sign-in details or wallet codes. If an unfamiliar device appears, contact support with the time and device path so we can examine the event.

You can submit a deletion request through the account support route and explain which records you want removed. We assess it under the Privacy Policy and local requirements. Some transaction or security records may need restricted retention for a legal duty, after which they can be deleted or anonymised.

Related Pages

menu168 Indonesia About Us No Commission Baccarat menu168 Casino Access guide