Reference

mega338 Privacy Policy, Clearly Explained

Your mega338 Privacy Policy explains what we collect when you open an account, verify your phone, browse Dragon Tiger or use DANA and QRIS.

Account dataWallet referencesDevice sessionsCookie choices
mega338 mega338 Privacy Policy, Clearly Explained
PRIVACY SUPPORT

Get Privacy Help Beside Wallet Status

A clear contact path matters when a privacy request and a wallet status appear together.

Account request Use the account support form to ask about collected data, a correction or a copy of records linked to your verified phone number.
Wallet reference For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference and status rather than private wallet credentials.
Access trouble If phone verification or login blocks your request, tell us the device path and last completed step so we can separate access help from privacy handling.
DATA IN PRACTICE

Your Device Data Beside Account Security

We handle policy requests through the same account controls used to confirm your identity and protect your session.

Account records

We may hold your registration details, verified phone number and account changes so we can provide access, answer requests and connect the right record to you.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references, statuses and timestamps used to reconcile an account request.

Cookies

Cookies and similar storage can remember a session or language setting. Your browser controls can clear them, although clearing cookies may require another login.

Device checks

We may record browser type, device signals and session timing to investigate an unfamiliar login, protect phone verification and respond to access questions.

Retention

We keep personal records only for account operation, payment matching, dispute handling or legal duties. When the purpose ends, records are removed or anonymised where practical.

Change requests

Ask us to access, correct or otherwise address your personal data through support. Include your account phone and request purpose so we can verify the correct record.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet status. We keep the route practical: identify the account, name the data category and use the support path shown on the site. If a request concerns local access or eligibility, the answer depends on local law.

It covers account details, phone verification, payment references, cookies, device sessions, retention and requests to access or correct personal data connected with your account.

The policy uses payment references and statuses to match DANA, QRIS, OVO or GoPay activity. Do not send wallet passwords or secret credentials through our support route.

We may handle browser type, device signals, session timing and login events when you use a mobile or desktop path. These records support access checks and account security.

Open the account support form and state whether you want access or correction. Provide your verified phone number and the relevant data category so we can locate the record.

We retain records while needed for account operation, payment matching, disputes or legal duties. After that purpose ends, we remove or anonymise them where practical and permitted.

Yes. Account access and some data requests depend on local law. Where local law permits, we explain the applicable purpose, record category and next step through support.

Yes, use the public support route shown on our site and describe the blocked account step. We may need additional checks before discussing personal records linked to your phone.