Reference

Privacy Policy For Your migo303 Account

migo303 Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and contact support.

Clear data purposesWallet record contextCookie choicesAccount request path
migo303 Privacy Policy For Your migo303 Account
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear support route makes a Privacy Policy request easier to complete.

Account support Use the account help route when you want to ask what personal details are…
Wallet records For a DANA, OVO, GoPay or QRIS record, share the transaction reference and approximate…
Policy requests Ask us to correct, explain or remove eligible personal data through the same support…
DATA PRACTICES

Six Ways We Handle Your Data

Our Privacy Policy is put into practice at the account, wallet and device level. We separate details needed to open access from records used to confirm a payment status or answer a…

Account details

We collect the details needed to create and maintain your account, including your phone number, login data and verification result. We use them to identify your account, restore access and connect a support request to the right record.

Device signals

When you open the lobby on a mobile browser or desktop, technical signals such as device type, browser activity and security events may be recorded. These signals help us spot unusual access without reading unrelated files on your device.

Cookie controls

Cookies can keep an account session active, remember selected settings and support security checks. You can adjust cookie controls in your browser, though blocking necessary cookies may interrupt login, phone verification or the route to your account.

Wallet security

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status with your account. We do not need your wallet password for this check, and support should never ask you to publish a security code.

Retention checks

We retain account, transaction and support records only while a stated service, security review or legal duty requires them. When that reason ends, we assess the record for deletion, restriction or continued storage under applicable requirements.

Change requests

You can ask us to access, correct or remove eligible data by contacting support from your account path. We may verify your phone and ask for request details before acting, then explain the result and any required exception.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we hear most often from people deciding whether to open an account. They explain the data connected to login, wallet activity, cookies, device use and support. If your situation is not listed, send the question through the account route and include only the details needed to identify the request.

The migo303 Privacy Policy covers account details, phone verification, device signals, cookies, wallet status, transaction references and support messages. It also explains your choices to request access, correction or removal, subject to security needs, legal duties and where local law permits.

We may collect your phone number, login credentials, verification result and technical details from the phone or desktop used to access the account. We use these records to provide account access, protect sessions and connect later support or wallet questions to you.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a payment step to your account, investigate a status issue and answer a support request.

Contact support through your account path and ask for an access request under the migo303 Privacy Policy. Tell us which data period or activity you mean. We may complete phone verification before confirming account details, and we will explain the response through the protected route.

You can request correction or removal of eligible personal data through account support. We first check that you control the account, then assess the request against security records, transaction obligations and applicable law. Where local law permits, we will confirm the action or explain why a record remains.

Cookies can support login sessions, saved settings and security checks on your mobile browser or desktop. Your browser lets you adjust them, but blocking necessary cookies may affect phone verification or account access. The Privacy Policy explains which cookie purposes support the requested account function.

We keep personal data while it supports account access, security checks, payment status investigation, support handling or a legal duty. We periodically assess whether the reason still applies. You can ask support about a specific record, and we will explain any retention requirement that affects it.