Reference

mimi303 Privacy Policy for Your Account

mimi303 Privacy Policy explains what we collect when you open an account, verify your phone and use the mobile browser from Jakarta or elsewhere in Indonesia.

Account dataWallet recordsDevice choicesPolicy requests
mimi303 mimi303 Privacy Policy for Your Account
CONTACT ROUTES

Where Privacy Questions Get Answered

A clear contact route helps when a Privacy Policy question concerns a login, wallet reference or account record.

Account access If phone verification or login leaves you unable to reach your account, use the account support route and describe the step that stopped. We can connect the request with the relevant Privacy Policy record.
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment reference and rail name through the account support path. We use those details to check status while limiting unnecessary wallet data.
Data requests To ask about access, correction or removal of personal data, identify your account and state the request clearly. We may need a matching account detail before discussing records connected with you.
HANDLING DETAILS

Six Practical Privacy Controls

We handle this policy area through ordinary account controls rather than vague promises. Phone verification helps connect a request with the correct account, device settings affect cookies and session storage, and payment…

Data we collect

We may receive account details, phone verification status, device and browser signals, support messages, and payment references. The exact record depends on the action you take, such as opening an account or checking a wallet status.

Why we use it

We use account and transaction data to provide access, match a payment to the right account, investigate a stalled reference and answer your Privacy Policy request. We do not need your DANA, OVO or GoPay password.

Cookies and storage

Cookies and browser storage can keep a session open and remember selected settings. You can clear them through your mobile browser controls, although doing so may require phone verification again before account access.

Account protection

Phone verification is required before account access, and we use account details to distinguish your request from another person’s request. Do not send wallet passwords, card secrets or one-time codes in support messages.

Retention approach

We retain account, support and payment records for the period needed to provide the requested service, resolve disputes and meet applicable local requirements. Retention can differ by record type and depends on local law.

Changing your data

If your phone detail or account record needs correction, contact us through the account support path with the requested change. We may verify ownership first, then explain what can be updated and when.

Privacy Policy Questions Before Account Opening

These Privacy Policy answers address the practical searches we hear before an account is opened or a local wallet is used. They cover what we collect, how you reach your records, what happens on a mobile browser and which details help us respond. Where access is discussed, it depends on local law.

The mimi303 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Yes. Privacy Policy explains that we may use a payment reference, rail name, status and related account details to match DANA or QRIS activity. We do not ask for your wallet password.

Phone verification helps us connect account access and data requests with the correct person. It also helps separate your account from another account when you ask us to inspect or change a record.

You can contact us through the account support path and ask which personal records we hold. Include an identifying account detail, and we may verify ownership before responding to the request.

Send a clear correction request through account support, naming the field that needs changing. We may compare it with your verified account details before updating the record or explaining why it must remain.

Clearing cookies or mobile browser storage removes local session data from that browser, not necessarily account or payment records held by us. You may need phone verification again to access the account.

Retention depends on the record, the reason it was created and applicable local requirements. Privacy Policy requests about a DANA, OVO, GoPay or QRIS reference can be sent through account support.