Reference

mulia303 Privacy Policy for Your Account

The mulia303 Privacy Policy shows how we handle your account data, phone verification and wallet records across mobile and desktop access.

Account dataCookie choicesWallet recordsYour requests
mulia303 mulia303 Privacy Policy for Your Account
ACCOUNT HELP

Privacy Questions Near Your Wallet Path

A clear support route helps when you need to ask about personal data, a phone check or a wallet receipt. Start from the support link connected to your account so we can match your request with the right login record. From a mobile browser, keep the relevant DANA, OVO, GoPay or QRIS reference ready without sending your password.

Team online

Data access request

Use the account support path to ask what personal data is linked to your mulia303 login. We may request an account identifier before sharing records with you.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt question, include the transaction reference and approximate time. We use those details to locate the matching account event.

Account correction

Tell us which account detail needs correction, such as a phone number or device entry. We check ownership first so another person cannot alter your record.

DATA PRACTICE

What Your Privacy Policy Covers

We keep the policy practical by connecting each data use to an account task you can recognise. Phone verification supports account access, cookies support a usable browser session, and transaction references help…

Data we receive

We receive details you enter during account creation, including contact data used for phone verification. Login events, device signals and support messages can also form part of your account record.

Cookie controls

Cookies can keep a mobile browser session active or remember a setting. You can clear browser cookies through your device settings, although a fresh login may then be required.

Account security

Phone verification and login checks help us connect access to the correct account. Never send your password or a full wallet credential when asking about DANA or QRIS activity.

Record retention

We retain account, access and transaction records only for operational, security or legal needs described by the policy. A retention question can be sent through account support.

Your data request

You can ask to access or correct personal data linked to your account. Include the account identifier and the requested change; we verify ownership before responding.

Policy contact

For a Privacy Policy question, use the support path while logged in when possible. If login is unavailable, describe the issue without sharing a password or complete wallet secret.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the account, device and wallet questions you may have before opening access. We keep the wording tied to actual steps such as phone verification, browser cookies and payment references, so you know what to prepare when contacting us. Eligibility and access depend on local law.

It covers account details, phone verification, login events, device data, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect account access with the correct person and reduce mistaken or unauthorised entry. The check is part of the account path before access, where local law permits.

Yes. The policy covers references needed to match DANA or QRIS activity with your account, including a receipt reference and timing. We do not need your password to investigate a wallet question.

You can send a data access request through the account support path. Include your account identifier, and we may verify ownership before showing records connected with your login or payment activity.

Contact support with the account detail that needs correction, such as a phone number or device entry. We check the request against your account before making a change or explaining why it cannot be made.

Cookies may keep a browser session active or remember a setting. You can clear them in your phone browser controls; after clearing, you may need to complete login and phone verification again.

We retain records for operational, security or legal needs described in the Privacy Policy. Ask support about a particular account or transaction record, and we will explain the applicable retention position.