Reference

What Our Legal Page Covers

We keep the legal side of mpoatam plain: what data we ask for, which account actions need checks, and when access depends on local law and is available…

Local-law accessAccount checksDANA OVO GoPay QRISWhatsApp support

Explore lobby Read FAQ

When Access Depends On Local Law

mpoatam Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We set our legal terms around one rule: if local law says an action is not available, we do not open it. Before you confirm an account or request a sensitive change, we may ask for the name, phone number, and payment trace that match your

1
profile. That can include the last reference from DANA, OVO, GoPay, or QRIS so we can link the request to the right account and reduce mistakes. When a request needs more time, we keep the thread open and tell you which proof is still missing. If
2
a request is denied, we explain the reason in plain language so you know which step to fix next. The text on this page can change when our handling steps change, but any new rule is applied only where local law permits and after it is
3
shown in the same account flow.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Where To Send Legal Questions

If a legal question needs a human reply, we route it through the same channels we use for account checks. You can send it by WhatsApp, email, or the in-account ticket form, and we ask for your account name plus the request type so the right team sees it. That keeps corrections, data requests, and access questions in one thread during 09.00-23.00 WIB.

Team online

WhatsApp Desk

Send the legal request on WhatsApp between 09.00 and 23.00 WIB. Include your account name and the reason for contact so we can match the message to the right file.

Email

Use email when you need a written trail for a data, access, or correction request. We reply in the same thread and may ask for a matching phone number or transaction reference.

In-Account Ticket

Open the support form after login if the request is tied to your profile. That path is useful for change requests because we can see the account record without asking you to repeat every detail.

DATA HANDLING

How We Handle Data And Requests

We keep legal records to the minimum needed for account checks, request handling, and dispute follow-up.

Data We Keep

We keep the name, contact method, and request history needed to verify a legal question or account change. If payment verification is involved, we use the reference that matches your DANA, OVO, GoPay, or QRIS record.

Session Cookies

Cookies store your login session and language choice so you do not repeat steps on every page load. If you clear them, the login screen may ask you to verify the same device again.

Account Security

When a login comes from a new phone, browser, or IP path, we may ask for a quick match against your registered contact details. That step protects the account before any sensitive request is processed.

Retention

We keep legal and support records only for the period needed to process the request, settle a query, and meet local handling rules. After that period, access is reduced or removed according to our retention rules.

Request Changes

To change stored account details, use the profile or help form inside your account and send the field you want updated. We may ask for a matching document or reference before we make the edit.

Who Handles It

If your case needs a decision, our support desk is the first contact point. Send the request from the same phone number or email tied to the account so we can route it without delay.

Common Questions About Legal Steps

These questions focus on access, data, request handling, and the contact path you can use from your account. We answer them here so you know what we keep, how long we keep it, and which step to take if something in your profile needs attention. If the rule text changes, the new version appears here only where local law permits.

Yes. We can tell you which contact details, session records, and request history we hold for your account. If payment verification is involved, we may also cite the matching DANA, OVO, GoPay, or QRIS reference.

Use the profile form or send a ticket from your logged-in account. We check the request against your registered contact method first, then update the field once the match is clear and allowed.

A new device can trigger an extra check. We may ask you to confirm your phone number, email, or recent login path before we let the account continue, especially after a password reset.

Cookies keep session and language data so the page loads with your last choices. They do not replace the account record, and clearing them only removes browser memory, not the policy text attached to your profile.

Send the request through WhatsApp, email, or the in-account form. Include your account name, the contact method on file, and the exact request so we can route it without back-and-forth.

Yes. If local law changes the way access, storage, or request handling works, we update the text and apply it only where the new rule is allowed. Your screen should always reflect the current path.

What Our Legal Page Covers

Where To Send Legal Questions

WhatsApp Desk

Email

In-Account Ticket

How We Handle Data And Requests

Data We Keep

Session Cookies

Account Security

Retention

Request Changes

Who Handles It

Common Questions About Legal Steps

01 Can I ask what data you keep about my account?

02 How do you handle a change to my details?

03 What if I sign in from a new phone?

04 Do cookies affect my legal settings?

05 How do I contact you about access or deletion?

06 Does local law change what I can see here?

Related Pages