Reference

maujp Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your maujp account, including login records, device signals and wallet status.

Account dataWallet recordsDevice controlsPolicy requests
maujp maujp Privacy Policy for Your Account
REQUEST HELP SAFELY

Where to Ask About Privacy Policy

A clear contact path matters when a wallet reference, login record or device detail looks unfamiliar. Start from the support link inside your account rather than sending identity or payment data through an unverified message. We can use the account step, receipt reference and affected wallet status to route a Privacy Policy question without asking you to repeat unnecessary details.

Team online

Account support link

Open the support link beside your account and describe the Privacy Policy request. Include the account phone number only through that signed-in route, not in a public message.

Cashier status path

For DANA, OVO, GoPay or QRIS questions, share the cashier reference and status shown in your account. We use those details to locate the relevant record.

Device access check

If a mobile or desktop login looks unfamiliar, tell us the device path and approximate time. We can compare the session record and help secure the account.

CONTROL YOUR RECORDS

Account Security Across Mobile and Desktop

We keep Privacy Policy requests tied to the account details they concern, so a change request can be checked before action is taken.

Data handling

We use account, device and transaction references for access checks, wallet status and support. A page such as Mega Fishing may appear in activity records, but it is handled as account data rather than shared as a public profile.

Cookie choices

Cookies can support sign-in continuity, security checks and language or access preferences. You can manage cookies through your browser, although some account paths may not work correctly when required cookies are blocked.

Account security

Phone verification is used before account access, and device signals help us identify an unusual session. Never send a password or wallet credential through support messages, even when a request appears urgent.

Retention approach

We keep records only for the period needed for account administration, payment reconciliation, security checks or a legal duty. When a record is no longer needed, our handling process moves it toward removal or restricted access.

Who to contact

Send Privacy Policy questions through the support link within your account. This gives us the account step and contact route needed to check ownership before discussing personal or wallet-related records.

Change requests

You may ask us to correct an account detail, explain a data use or address a deletion request where local law permits. We may ask for phone verification before changing protected records.

Privacy Policy Answers for maujp Accounts

These Privacy Policy answers cover the account and wallet questions we expect you to ask before opening access. Each answer points to a practical step, from checking cookies on your phone to sending a verified request through the account support route.

It covers account details, phone verification, device and cookie records, wallet references, support messages and activity linked to account access. It also explains how we use, retain and protect those records.

Yes. We record the platform-side reference, status and account connection for DANA or QRIS requests. The payment provider may handle other transaction data under its own privacy terms.

Device type, browser signals and session timing help us identify unusual access and protect your account. A mobile session opening Rise of Apollo can therefore create a security record without exposing your device publicly.

Use the support link inside your account and describe the correction or access request. We may ask for phone verification so the requested change is connected to the correct account.

Retention depends on the record and the reason it was created, including account support, payment reconciliation, security or legal duties. When the reason ends, access is restricted or the record is removed where permitted.

Yes. Your mobile browser provides cookie controls. Blocking required cookies may interrupt sign-in, security checks or the path from account access to the lobby, so review the setting before contacting support.

Use the available account support route and provide the minimum ownership details requested, such as your verified phone path and approximate login time. Access depends on local law and our identity checks.