Reference

Privacy Policy for Your mpoad Account

We keep your privacy policy simple: we collect only the account data needed to verify you, keep your session stable, and handle DANA, OVO, GoPay, and QRIS records.

IndonesiaDANAOVOGoPayQRIS

Explore the lobby Read FAQ

How Local Law Shapes Privacy Policy

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

Local rules shape what we collect and how long we keep it. When you register, we may save your name, phone number, email, IP address, device type, and the payment reference that matches your DANA, OVO, GoPay, QRIS, or bank transfer activity. We use that record

1
to verify ownership, stop duplicate requests, and match support messages to the right account. If a withdrawal needs extra confirmation, we may ask for a KTP image or a code sent to your phone, then store the proof for a limited period before archiving it. If
2
you want a correction or a copy of your data, send the request from the contact method tied to the account so we can confirm it belongs to you.

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

CONTACT PATHS

Where to Send a Privacy Request

If your request is about access, a correction, or a payment record, send it through the same channel you used on the account.

Live Chat Open live chat from the site and send the exact request. We use it for access checks, correction requests, and data-location questions, and the thread stays tied to your account for follow-up.

Email Email our team when you want a written trail. Add your registered phone number, the email on file, and any DANA, OVO, GoPay, or QRIS reference if the request touches a payment record.

WhatsApp Use WhatsApp for time-sensitive privacy questions outside desktop hours. We still verify you against the account details before changing data, sharing stored records, or discussing a withdrawal check, so the request stays matched to your record.

DATA CONTROLS

How We Handle Account Data

We keep this part practical. Cookies remember your language, session, and whether you already confirmed a form, while device logs help us spot repeated login attempts and stop account takeover attempts.

Data Use

We collect only what we need to run the account: name, phone number, email, device type, login time, and payment references. If you open from mobile or desktop, the same record follows your session.

Cookies

Cookies keep your language, login state, and form progress on the same browser. You can clear them in Chrome, Safari, or Firefox, but some fields will need to be entered again after that.

Device Logs

We store device logs such as browser version, IP address, and repeated error codes to detect unusual access. Those logs help us block a risky session before it reaches your balance or account settings.

Retention

We keep account and payment records for the period needed to settle checks, handle disputes, and meet local record duties. After that, we archive or remove parts that are no longer needed for our files.

Your Requests

If you want a correction, access copy, or account update, send the request from the email or phone number on file. We may ask for one extra check so we do not change the wrong record.

Security Steps

For sensitive changes, we use step-up checks such as a code sent to your phone or a confirmation message inside the account. That keeps data changes tied to the person who opened the request.

Questions About Privacy and Access

These questions cover the parts you usually ask first: what we store, why we ask for it, and how you reach us when something needs correcting. If your account details change, start with the contact route that matches your record, then we can check the request against your email, phone number, and recent activity. Where local law sets a limit, we follow that limit and explain what we can process.

We collect the details needed to create and protect the account: your name, phone number, email, device type, login time, and payment reference. If you use DANA, OVO, GoPay, or QRIS, we also store the matching reference.

We use phone and device data to check that the account activity comes from you and to spot unusual logins. That helps us verify requests, keep sessions stable, and stop someone else from changing your details.

Yes. Send the request through live chat, email, or WhatsApp using the contact tied to the account. We may ask for one extra check before we share a copy or update a record, so the right file changes.

Yes, we use cookies on browser and mobile web sessions to remember language, login state, and form progress. If you clear them, you may need to confirm your details again the next time you open the account.

We keep records for the period needed to handle account checks, payment tracing, and local legal duties. After that period ends, we archive or remove parts that are no longer needed for our files.

Contact us through live chat, email, or WhatsApp. Our team is available 08:00-22:00 WIB, and we will ask for the registered phone number plus the email on file before we discuss your data.

Yes. What we can collect, store, share, or remove depends on the law that applies to your account. If a request is not available where local law permits, we will explain the limit and the reason.

Privacy Policy for Your mpoad Account

Where to Send a Privacy Request

How We Handle Account Data

Data Use

Cookies

Device Logs

Retention

Your Requests

Security Steps

Questions About Privacy and Access

01 What data do you collect when I open an account?

02 Why do you ask for my phone number and device data?

03 Can I ask for a copy or correction of my data?

04 Do you keep cookies on my browser or phone?

05 How long do you keep my records?

06 Who can I contact about a privacy request?

07 Does local law change what you can share with me?

Related Pages