Reference

mainlotre Privacy Policy for Your Account

mainlotre Privacy Policy explains how we handle your account details, phone verification, wallet references and cookie choices before you open the Live Dealer Lobby or other game areas.

DANA and QRIS contextCookie choicesAccount access recordsPhone verification
mainlotre mainlotre Privacy Policy for Your Account
HELP PATHS

Where To Ask About Privacy Choices

A clear support route helps when you want to understand a record rather than change a game setting.

Account privacy Use the account help route to ask for the personal details connected with your…
Wallet reference If a DANA, OVO, GoPay or QRIS receipt looks unfamiliar, send the transaction reference…
Cookie request Ask support about cookie choices or a mobile session that does not clear as…
SECURITY DETAILS

How We Protect Account And Cookie Data

Privacy decisions work best when the handling steps are visible. We limit account access through phone verification, separate payment references from wallet credentials, and describe how browser cookies support a continuing session.

Data handling

We use account details to provide access, verify the phone step and respond to support requests. Payment references help us trace DANA, QRIS or bank transfer status without treating them as public profile details.

Cookie controls

Cookies can keep a mobile browser session connected while you move between account pages and the lobby. Our Privacy Policy explains their purpose and what changes when you clear them.

Account security

Phone verification is checked before account access, and support should never need your wallet password. Keep login details private and use the account help path for suspicious activity.

Retention timing

We retain selected account, support and payment references only for the period described in the policy, including time needed for security checks, dispute handling and legal duties.

Change requests

You can ask us to correct an inaccurate account detail through support. Include the affected record and your account identifier so we can verify the request before changing it.

Access requests

To ask what personal data we hold, use the account-based privacy route. We may confirm your identity first, then explain the record, purpose and any lawful reason for keeping it.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account actions most likely to matter before you open access. We focus on phone verification, local wallet references, browser cookies, correction requests and the support route, with eligibility always depending on local law.

It covers account details, phone verification, wallet and bank transaction references, browser cookies, security handling, retention, access requests and corrections connected with your account.

Our policy distinguishes payment references from wallet credentials. Do not send a DANA, OVO, GoPay or QRIS password to support; use the transaction reference when asking about status.

Phone verification helps connect the right person to an account before access. The policy explains how that phone detail is used, protected and handled when you ask for account assistance.

Use the account help path and ask for a personal-data access request. We may confirm your identity first, then provide the available record and explain any retention reason.

Yes. Send a correction request through support with your account identifier and the inaccurate field. We check the request before changing records connected with phone verification or payment references.

Cookies can keep a mobile browser session connected across account pages. Clearing or blocking them may end that session, while the policy explains their purpose and the available account choices.

Access and eligibility depends on local law. The Privacy Policy explains data handling for permitted access, while support can clarify an account or verification question through the account help route.