Rujukan Laman

How mrong Handles Your Privacy

This page explains what we collect, why we collect it, how long we keep it, and the choices you can make.

Data UseCookie RulesAccount RecordsLocal Law
mrong How mrong Handles Your Privacy
CONTACT PATHS

How to Reach Us About Data

If you want to ask what we hold, correct a detail, or ask for deletion where the law allows it, use the contact path that matches…

Privacy form Send the request through the form on mrong.
Email follow-up If you prefer email, send the same details from the address linked to your…
Chat handoff Use chat for quick privacy questions, then move to the form if you need…
DATA HANDLING

How We Handle Records and Access

Privacy handling starts with collection limits: we ask for what we need, keep it tied to the purpose, and stop using it once that purpose ends unless the law asks us to…

Cookies and sessions

We use session cookies to keep you signed in, remember page state, and reduce repeated checks while you move through the site. You can clear them in your browser, but some parts may ask you to sign in again.

Login security

When a login looks unusual, we may ask for a fresh verification step before we let the session continue. That check helps protect your profile, your contact details, and any wallet changes linked to it.

Payment records

Deposit and withdrawal traces are stored with the matching account so we can confirm what moved, when it moved, and which method was used. That record helps with audits, dispute handling, and account support.

Retention windows

We keep records only for as long as they are needed for the reason collected, the support case, or a legal duty. After that, we delete or anonymise them in line with internal retention rules.

Request changes

You can ask for a copy, correction, or deletion of the data we hold, subject to local law. We may need to confirm your identity before making a change, especially for wallet or contact updates.

Who to contact

If something in your record looks wrong, use the privacy form or chat handoff from this page. We route the request to the right team and keep the reply attached to your account trail.

Questions About Privacy and Access

These are the privacy questions we hear most often before and after an account is opened. We keep the answers plain so you can see what is collected, how records are used, and where to send a request if you want a copy or a correction. When a request depends on local law, we say so and keep the process tied to the account that made it.

We may collect the details you give when you open an account, plus login records, device signals, cookie data, and payment references. We use them to run the account, keep records accurate, and handle support or verification work.

Payment records help us match each deposit or withdrawal to the right account, confirm the method used, and resolve disputes later. They are kept as account records, not as marketing data, and remain subject to retention rules.

Yes. Send a request through the privacy form or chat handoff, and we will verify the account before sharing a copy. If local law limits part of the request, we will explain what can be provided.

Cookies help remember your session state, language choice, and recent actions so the page does not reset every time you move around. You can clear them in your browser, but some features may ask you to sign in again.

We keep records only for as long as they are needed for service, dispute handling, audit, or legal duties. When the reason ends, we delete or anonymise the data unless another duty requires us to keep it longer.

Use the contact path on this page and tell us which detail is wrong, what it should be, and any date that helps us find it. We may ask for a quick identity check before updating the record.

If a request depends on local law, we follow the rule that applies in your region and only process what is allowed there. That keeps access, retention, and correction steps aligned with the place your account is used.