Reference

mega38 Privacy Policy For Your Account

mega38 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status in Jakarta and across Indonesia.

Account clarityWallet recordsCookie choicesRequest path
mega38 mega38 Privacy Policy For Your Account
REQUEST SUPPORT

Where To Ask About Privacy

A clear support route helps when you want to ask about a Privacy Policy record rather than a wallet transaction itself. From your account area, send a request about stored details, a cookie choice, device activity, or a payment reference that does not look familiar. Include the account phone number and the relevant date, but never send a password or full payment credentials. We use the request details to confirm ownership and keep the response tied to the correct account.

Team online

Account data request

Use our account support path to ask what personal details are linked to your profile or to request a correction. We may ask for the phone verification step before discussing account-specific records.

Wallet record check

If a DANA, OVO, GoPay, or QRIS reference looks unfamiliar, send the receipt and transaction date through support. We compare the reference with account records without asking you to share a wallet password.

Device access question

Tell us when a sign-in or device record seems wrong. Our support route can review the account event, confirm your identity, and explain the next account-security step without exposing another person’s data.

DATA PRACTICES

How We Handle Your Privacy Choices

Privacy Policy requests are handled against the account record, not treated as a general message.

Account details

We use the details you submit to create and maintain your account, confirm phone ownership, answer data requests, and connect…

Device records

A mobile browser or desktop sign-in may create records such as device type, session time, and security events.

Cookies

Cookies can remember sign-in preferences, support page settings, and security choices.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we retain references needed to match receipts and check…

Retention period

We keep personal and technical records for the period needed for account operation, security checks, dispute handling, or legal duties.

Change requests

You can ask us to access, correct, or remove eligible account data through the support path.

Privacy Policy Answers For mega38 Accounts

The questions below focus on the records you are most likely to notice while using an Indonesian account. They cover phone verification, mobile access, local wallet references, cookies, retention, and requests for changes. If your situation is not listed, use the support path with the relevant date and account phone number. We will first confirm ownership, then address the Privacy Policy point without asking for a password.

It covers account details, phone verification, device and sign-in records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. It also explains retention, account-security use, and how to request access or correction.

Phone verification helps us confirm that an account request comes from the account holder before we discuss personal details or change account data. It also supports account security when a new mobile device, unfamiliar sign-in, or wallet-status question needs checking.

We may keep a payment reference, amount status, date, and account connection needed to match a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account receipt. We do not ask you to provide a wallet password when checking that record.

Yes. Send a request through our account support path and identify the account phone number plus the specific record you want checked. We verify ownership, then explain which data can be supplied or corrected and whether any security or legal limit applies.

When you sign in through a phone browser, we may record device type, session time, and security events connected with that access. Those records help us investigate unusual activity and protect your account; they do not give us access to unrelated files on your device.

Use the cookie controls in your browser to review or remove stored choices. Some account or security functions may behave differently after cookies are blocked or cleared. The Privacy Policy explains why a particular cookie is used and how that choice affects the page.

We retain records while they are needed for account operation, security checks, payment reconciliation, dispute handling, or legal duties. When those needs end, the record moves toward deletion or anonymisation under our process. Access and retention requirements depend on local law.