Reference

Privacy Policy For Your mrebet Account

Our Privacy Policy explains what we collect when you open a mrebet account, sign in from a mobile device, use DANA or QRIS, and contact support.

Clear data purposesWallet activity explainedAccount access requestsCookie choices
mrebet Privacy Policy For Your mrebet Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

Our support path is designed for privacy questions, not only stalled login or wallet status.

Policy questions Use the policy contact path when you want to know what account, device or…
Access requests Ask for a copy, correction or removal of eligible personal data through account help.
Status follow-up If a privacy request is waiting while a payment receipt is being checked, reply…
DATA HANDLING

What You Can Check Before Opening

We keep the practical parts of this Privacy Policy close to the account flow so you can decide what to share.

Collection

We receive details you enter during account creation, including contact and verification fields, plus technical data from your browser or phone. When you open a lobby such as Fortune Fishing Game, event records can show the session and time, helping us investigate account access without treating game activity as a public profile.

Cookies

Cookies help keep your sign-in path connected, remember selected settings and support security checks between pages. You can manage browser cookie controls, though removing essential cookies may interrupt account access or require another verification step when you return from a mobile device.

Account security

We use sign-in events, device signals and verification steps to detect account misuse. If a new phone opens the account after a wallet status change, we may request confirmation before showing sensitive records. Keep your password and wallet PIN private; our support path will not ask you to publish them.

Payment records

A payment reference can be linked to your account so we can reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN to check a receipt. Withdrawal verification may require matching account details, and the request remains subject to local law.

Retention

We keep personal data only for the period needed for the purpose described in this policy, account administration, dispute review, security work or legal duties. When a record is no longer needed, we remove it or retain it only in a form that no longer identifies your account where feasible.

Your requests

You can contact us to ask what data is held, request a correction, ask about deletion or raise a cookie question. Include your account contact route, not your password. We may verify ownership before responding, and access or eligibility depends on local law and the request type.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening or using an account from Indonesia. They explain the practical link between account records, device activity, local wallets and support requests. If your situation is unusual, use the policy contact path and quote the account step involved. Where local law permits, we can assess requests for access, correction or removal after confirming that you control the account.

The mrebet Privacy Policy covers account details, verification records, sign-in and device events, cookies, payment references, support messages and retention. It also explains how we handle records connected with casino and sportsbook areas, including Live Baccarat Diamond, subject to local law.

We collect account and device data to create access, confirm that a sign-in is yours, protect sessions and answer support requests. A device signal can help us investigate an unusual login, while your submitted contact details let us connect a privacy request with the correct account.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity. We use these references to reconcile an account transaction; we do not need your wallet PIN to check a receipt.

Use the support contact shown in account help or the policy footer and ask for a data access request. State the account contact route you used and the record type you want checked. We may verify ownership before sending a response, where local law permits.

You can request a correction or deletion through the same policy contact path. We assess whether the record is still needed for account administration, a dispute, security review or legal duties. If removal is restricted, we will explain the reason where local law permits.

Essential cookies help maintain sign-in continuity, remember settings and complete security checks. Browser controls can remove or block them, but that may interrupt a mobile session or require another verification step. The Privacy Policy explains these uses and the choices available in your browser.

We retain personal data for the period needed for the stated purpose, account administration, payment reconciliation, dispute handling, security work or legal duties. The period can differ by record type. You can ask support about a category of data without sending your password or wallet PIN.