Reference

megatoto Privacy Policy for Your Account

Our Privacy Policy explains how megatoto handles the details connected with your account, device and wallet activity before you open the casino lobby.

Account dataWallet recordsDevice privacyRequest access
megatoto megatoto Privacy Policy for Your Account
DATA HELP ROUTE

Where to Ask About Privacy Policy

A clear account help route lets you raise a privacy question without explaining the whole issue twice.

Account access If phone verification blocks your sign-in, use the account help path and identify your…
Wallet records For a DANA, OVO, GoPay or QRIS record, include the transaction reference rather than…
Privacy requests Ask us to access, correct or remove eligible account data through account help.
DATA HANDLING DETAILS

What We Do With Your Personal Data

We keep this Privacy Policy practical by linking each data use to a recognisable account step.

Account details

We may receive your registered phone, sign-in details and account activity when you open an account or move from login…

Cookies and sessions

Cookies can retain session preferences and help the mobile path return you to the right account area.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be stored with its status and reference.

Device security

Browser, device and sign-in signals can help us spot an account session that does not match your usual path.

Retention period

We retain personal records for the period needed to operate your account, settle a transaction question, handle a dispute or…

Changing your details

To request a correction or deletion, contact us through account help with the affected field and your registered contact detail.

Privacy Policy Questions About megatoto

These answers address the searches we hear most often about the megatoto Privacy Policy. They cover account creation, mobile browsing, local wallet records, cookies, retention and the steps for asking us to access or change personal data. If your situation is different, use the account help path and describe the specific record involved.

It covers account details, phone verification, device signals, cookies, lobby activity, wallet references and support requests. It also explains retention, security checks and how to request access or corrections.

We may store a payment reference, status and related account record for DANA, OVO, GoPay or QRIS. We use those details to match cashier activity and resolve receipt questions, not to request your wallet password.

Device and browser signals help us recognise a sign-in path and investigate unusual account activity. On mobile, this can connect your login with the correct session without storing the contents of unrelated device activity.

Open the account help path and ask for a copy of the data linked to your profile. Include your registered phone or email, and we may verify ownership before releasing account-specific records.

Yes, you can request a correction or removal of eligible records through account help. Tell us which field or record is affected; retention may continue where a transaction, dispute or legal need requires it.

Cookies can keep a session active and remember selected account settings on mobile or desktop. You can adjust browser controls, but disabling certain cookies may require another sign-in or verification step.

Yes. Requests, account eligibility and the records we can provide depend on local law. We apply the relevant process to your account and explain any necessary verification through the support path.