Reference

Privacy Policy for Your megaparilogin Account

Our Privacy Policy explains how we collect, use and protect the details connected with your megaparilogin account.

Clear data purposesWallet checks explainedAccess depends on local law
megaparilogin Privacy Policy for Your megaparilogin Account
CONTACT PATHS

Ask About Privacy Through Your Account

A direct support route helps you ask what data we hold, why a wallet check is pending, or how to change an account detail. Start from the support contact shown after login and include the phone number linked to your account, but do not send a password or one-time verification code. If your question concerns a DANA, OVO, GoPay or QRIS reference, add the transaction time and reference so we can locate the relevant record without asking for unrelated details.

Team online

Account contact

Use the support path connected to your logged-in account for a data access, correction or deletion request. We may ask you to confirm the phone number on the account before discussing personal details, so a request is matched to the right record.

Wallet status

For a payment-status question, provide the rail used, such as QRIS, DANA or GoPay, together with the transaction reference. We use those details to trace the relevant status while avoiding a request for your wallet password or private security code.

Security concern

If you notice an unfamiliar sign-in or device session, contact us through the account support route and change your password before sharing further details. We may pause discussion of account data until phone verification confirms that the request comes from you.

DATA PRACTICES

What We Do With Account And Device Data

We keep this policy practical: each data use should connect to an account action, a security check, a payment status or a support request.

Account details

We may hold the phone number and account details you provide when opening access. Phone verification helps us confirm ownership before account data is shown or changed. Keep your contact detail current so a security request can be matched to your account.

Payment records

A wallet or bank transaction can leave a reference, amount and status record for account reconciliation. This includes QRIS, DANA, OVO, GoPay, virtual account and bank transfer activity. We use the record for the stated payment purpose and related support questions.

Device sessions

Browser type, device signals and session times can help us detect an unusual login and keep a mobile session tied to the correct account. These signals may appear when you move from the login screen to a casino lobby or payment status page.

Cookies

Cookies and similar storage can remember a session choice, protect account access and help a page load in the browser you selected. You can manage browser cookie settings, although turning them off may require you to repeat login or verification steps.

Retention

We retain account, security and transaction records only as needed for the stated service purpose, account protection, dispute handling or a legal obligation. A request to remove data can be assessed against those needs, so some records may remain when retention is required.

Your requests

You can ask us to access, correct or delete eligible personal data, or ask how a specific record is used. Send the request through support with your account phone detail and the relevant item, and we may verify ownership before acting.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account actions you are most likely to search for before opening access. They cover device records, wallet references, cookies, correction requests and local eligibility without changing the terms of the full policy.

It covers data connected with your account, phone verification, device sessions, cookies, payment references and support requests. It also explains how we use those details, how long records may be kept, and how you can ask for access, correction or deletion where the request is eligible.

We use the phone number supplied during account creation to support verification and account recovery. Before discussing private account details or changing a record, we may ask you to confirm that number. Do not place a password or one-time code in a support message.

Yes. The Privacy Policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those records to match an account transaction, answer a status question and handle a related dispute.

We may record browser type, device signals, session time and related technical details when you sign in or move between account pages. These records help identify an unusual session and keep mobile access connected to the correct account without requesting your private device password.

Use the support contact path shown in your account and state which detail needs correction. Include the phone number linked to the account and enough context to locate the record, but leave out passwords and verification codes. We may confirm ownership before processing the request.

You can submit a deletion request through account support. We assess which records are eligible for removal and which must remain for security, dispute handling, transaction reconciliation or a legal obligation. We will use the request details to explain the next applicable step.

Access depends on local law. The Privacy Policy describes our handling of account data for supported access, but eligibility and availability can differ by location or legal requirement. If you are connecting from Jakarta or elsewhere, complete the account steps shown for your region.