Reference

How mpomm Handles Your Privacy

We wrote this policy so you know exactly what happens with your personal information when you fund via DANA, OVO or GoPay, access the lobby from your phone, or reach our support channels.

Account Data TransparencyPayment Info SafeguardsYour Rights ExplainedLive casino and slots
mpomm How mpomm Handles Your Privacy
PRIVACY HELP CHANNELS

How to Reach Us About Your Data

If you want to ask about your stored information, request a correction, or ask us to delete something, our support paths are ready. We handle privacy queries with the same speed we handle deposit issues — directly and without unnecessary waiting. You can raise a data request through any of the channels below, and our team will confirm receipt and outline next steps.

Live Chat Open live chat from any page on the site. Tell the agent your query is about personal data and they will route it to the privacy handling queue — expect a structured reply covering what data we hold and what actions are available to you.
Email Send a message to our support email with the subject line 'Data Request' and include your registered account email. We respond to privacy-related emails ahead of general queries so your request reaches the right team without delay.
Account Settings Inside your account dashboard you can view your stored details, update contact info, and toggle communication preferences. For deletion requests that go beyond what the dashboard allows, use live chat or email to initiate the full process.
DATA HANDLING PRACTICES

How We Protect and Manage Your Information

We built our data practices around a simple principle: collect what the platform needs to function, secure it properly, and give you clear control. Below is a breakdown of how each layer works — from the encryption on your DANA or GoPay transaction data through to what happens when you close your account entirely.

Encryption in Transit

Every connection between your device and our servers uses SSL encryption. When you submit a deposit through OVO or GoPay, the payment identifiers travel through an encrypted channel that prevents interception — the same standard your banking app relies on…

Cookie Management

We use session cookies to keep you logged in and analytics cookies to understand how pages perform. No cookie stores your wallet PIN or payment credentials.

Account Security Layers

Your account is protected by a password you set at registration plus an OTP sent to your registered phone number during sensitive actions like withdrawal confirmation.

Data Retention Period

Active accounts retain full transaction history so you can review past DANA and GoPay deposits at any point. After you close an account, we keep records for a limited period aligned with applicable regulations in eligible regions, then permanently delete…

Third-Party Sharing Policy

We share data only with payment processors needed to complete your DANA, OVO or GoPay transactions, and with security partners who help detect fraud. No personal data goes to advertisers or data brokers. Each partner operates under strict data-processing agreements.

Requesting Changes or Deletion

You can request a full copy of your stored data, ask us to correct inaccurate details, or request deletion of your account and associated records.

Common Questions About Your Data Rights

We know privacy policies raise specific questions. Below are the ones our support team fields most often — each answer explains what we do, why, and what you can do about it.

We collect your full name, email address, phone number, and the wallet identifier linked to your chosen payment method (DANA, OVO or GoPay). This lets us verify your identity, process deposits and send transaction confirmations to the right account.

No. Your wallet PIN is entered inside the DANA or OVO app on your own device and never passes through our servers. We receive only a transaction reference and confirmation amount — enough to credit your account balance without handling sensitive credentials.

Yes. Send a data-access request through live chat or email with your registered account details. We compile and deliver a structured summary of your stored personal data, transaction history, and any communication logs tied to your account.

Contact support via live chat or email and state you want full account deletion. We verify ownership through your registered phone number, then proceed to remove personal identifiers. Some records may be retained briefly for regulatory audit before permanent deletion.

Only you and authorised support agents handling your specific request can view your transaction history. Access is logged internally, so every view of your account by a staff member is recorded and auditable — no casual browsing of your records occurs.

We do not share, sell or trade your personal information with any advertising network or marketing partner. Data leaves our system only when necessary for payment processing through DANA, OVO or GoPay or when required by law in your eligible jurisdiction.

Inactive accounts retain stored data while they remain open. If you formally close the account, we keep records for a limited retention window to resolve any pending disputes or meet regulatory requirements, then delete personal identifiers permanently.

SSL encryption covers every connection regardless of device. On mobile, our site does not cache sensitive payment data in local storage. Session tokens expire after a set idle period, meaning an unlocked phone does not grant ongoing access to your account without re-authentication.

Yes. When we update this policy, the revision date at the bottom of the page changes, and we post a notice inside your account dashboard. Significant changes that affect how we handle payment data or personal identifiers trigger a direct notification to your registered email.

Availability of our services depends on local law and eligible regions. Where applicable regulations require specific data-handling procedures — like shorter retention windows or expanded disclosure — we comply with those requirements for accounts in the relevant jurisdiction.