Reference

megasloto Privacy Policy for Your Account

Your megasloto Privacy Policy explains what account, device and wallet records we use, why we use them and how you can ask about them.

Account data clarityWallet record controlsCookie choices
megasloto megasloto Privacy Policy for Your Account
PRIVACY HELP PATH

Get Policy Help Beside Account Support

A clear contact path matters when you want to question a record, correct a phone detail or understand a wallet reference. Start from the support route linked to your account area and include the email or phone detail connected to your request. We use that step to locate the right record without asking you to send an unnecessary payment password.

Team online

Account requests

Ask us to correct account details through the support path connected with your login. We may request a matching phone detail before discussing records linked to your megasloto account.

Wallet records

For a DANA, OVO, GoPay or QRIS query, include the receipt reference and date shown in your account. We use those details to trace the relevant payment record.

Cookie questions

If a device keeps a cookie after you change browser settings, contact support with the device path and browser choice. We can explain the policy purpose connected with that cookie.

DATA CONTROL PRACTICES

Cookies, Devices and Account Records

We apply the Privacy Policy to the points where data is created: account opening, phone verification, lobby access and wallet checks.

Purpose-based use

We use account details to create access, complete phone verification and respond to requests. Payment references help us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Cookie settings

Cookies can remember a session or help us understand whether a login is returning from the same browser. Your browser controls let you remove or restrict them.

Device signals

Device and connection details may be checked when an account returns from a different phone or browser. This supports access checks without treating the device as your identity.

Account protection

Phone verification is an account step before access. Never send us a password or wallet PIN in a request; our support path needs only the details required to locate your case.

Retention approach

We keep records for the period needed to operate the account, answer disputes, meet legal duties or protect access. When that need ends, the record is reviewed for removal.

Change requests

You can ask about a stored detail, request a correction or question a cookie through support. Include your account contact and a clear request so we can respond accurately.

Privacy Policy Questions About megasloto

These Privacy Policy answers address the account and access questions we expect before registration. They cover the records created by phone verification, wallet checks, browser use and support requests, so you can decide what to provide before opening an account where local law permits.

It covers account details, phone verification, device signals, cookies, payment references and support requests created while you access megasloto. It also explains retention, corrections and contact steps.

Phone verification helps connect the access step with the account you opened. It can also help us investigate an unusual login or correct an account record without requesting your wallet PIN.

Yes. The policy covers receipt references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity when those records are linked to your account.

You can send a correction request through the account support path. Include the contact detail linked to your login and describe the field that needs changing; we may verify ownership first.

Cookies may keep a session active or help recognise a returning browser. You can remove or restrict them through browser controls, then contact support if a policy question remains.

Retention depends on the purpose: account operation, dispute handling, legal duties or access protection. When a record is no longer needed for those purposes, it is reviewed for removal.

Use the support route linked from your account area and state whether your request concerns access, correction, cookies or a wallet reference. Eligibility for access depends on local law.