Reference

mpoyes Privacy Policy For Your Account

The mpoyes Privacy Policy explains how we collect, use and protect the details needed for your account, lobby access and wallet checks.

Clear data purposesWallet details explainedPhone verification contextPolicy contact path
mpoyes mpoyes Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Questions Through Account Support

A clear contact route helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from the support path connected to your signed-in account and include the email or phone detail attached to it, without sending a password or full payment credential. We can then check the relevant account trail, explain the next step and direct payment-specific questions to the appropriate wallet or bank route. Access depends on local law and account verification.

Team online

Policy questions

Use our account support path to ask how the Privacy Policy applies to your login, phone verification, device record or contact detail. Include the subject of your request and the account identifier we can safely match, but keep passwords and one-time codes private.

Wallet record checks

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, tell us the date, amount reference and wallet name shown in your account. We use those details to trace the relevant payment event without asking you to disclose a wallet PIN or full banking password.

Correction requests

For a wrong phone number, email detail or account record, contact support through the signed-in account path. We may ask for a verification step before making a change, because the Privacy Policy requires us to protect the account from an unapproved request.

DATA HANDLING

How mpoyes Handles Policy Details

We apply the Privacy Policy to practical account events rather than treating it as a page you only read once.

Account collection

We collect the account details needed to create and maintain access, including contact data used for phone verification. When you move from login to a lobby or wallet page, related records help us connect the request to the correct account rather than another person's profile.

Device signals

Browser type, device details and connection records can be used to keep sign-in sessions working and flag unusual activity. This matters when you move between a mobile browser and desktop while checking a wallet status or opening a title such as Mines Fast Round.

Cookie choices

Cookies may store session settings, remember choices and help protect account pages. Your browser controls many cookie options, but turning some off can affect login or policy access. We do not describe a cookie as a payment credential, and we do not ask for wallet PINs.

Account security

Phone verification and sign-in checks help us confirm that an account request belongs to you. Keep your password and one-time code private, and contact support if a device record or login event looks unfamiliar. We use the available account trail to investigate the concern.

Retention approach

We keep account, device and payment-reference records for the period needed to operate the service, resolve disputes, investigate misuse and meet legal duties. A request to remove data may be limited where a record is needed for an open check or a required business record.

Your request route

You can ask about access, correction, deletion or the purpose of a data record through account support. We may verify your identity before responding, and we will explain any limit that applies. If the request concerns QRIS, a bank transfer or another provider, that provider may also need to respond.

Privacy Policy Answers For mpoyes

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep each answer tied to a practical step, from phone verification and cookies to a request for correction or deletion. Where local law permits, you can use the account support path to ask for a more specific explanation of your records.

The Privacy Policy covers details used to open and maintain your account, such as contact information, phone verification records, sign-in activity and support messages. We use them to provide account access, protect sessions, investigate issues and meet legal duties, subject to local requirements.

Phone verification helps us connect an account request to the person making it and supports account recovery or security checks. We may refer to the verified contact when you ask about a login, device record or wallet status, but you should never share a one-time code with support.

Yes. The Privacy Policy explains how we use payment references and account records related to DANA, OVO, GoPay and QRIS when matching a request or answering a status question. The wallet or bank provider separately controls its own collection and handling under its terms.

We may record browser, device and connection details linked to sign-in and account activity. These records help keep a mobile session or desktop session working, identify unusual access and investigate support requests. They do not replace your password, phone verification or wallet credentials.

Use the support path connected to your account and state which detail is wrong, such as a phone number or email address. We may ask for an identity check before changing it. After checking the request, we explain the correction step or any reason a change cannot be made.

You can send a deletion request through account support. We first verify that the request comes from the account holder, then check whether any records must remain for security, dispute handling or legal duties. The Privacy Policy explains that these limits can apply even when deletion is requested.

Open the Privacy Policy link from the account or site policy area before completing phone verification or choosing a payment route. If the page does not load on your mobile browser, check the connection and contact account support with your device type and account identifier.