Reference

Privacy Policy for Your Account

leletogel explains the account data, DANA, OVO, GoPay and QRIS records, cookies and login signals we use before you open your account.

Account data explainedDANA and QRIS recordsCookie choicesSupport request path
leletogel Privacy Policy for Your Account
CONTACT PATHS

Policy Contacts You Can Reach Today

Fast privacy help matters when your account details or wallet records look wrong. Our support desk is available every day from 09:00 to 23:00 WIB through live chat, email, and account messages…

Live chat Use live chat from the account footer between 09:00 and 23:00 WIB. Share your username, last login date, and the privacy request type, then we route it to the data team.
Email request Send privacy questions to the support address shown inside your account. Include the email or phone number you registered, but do not send passwords, full QRIS screenshots, or card-like private images.
Account message Open Profile > Help > Privacy Request after logging in. This path attaches your account ID automatically, which helps us confirm ownership before we change stored details or release account records.
DATA CONTROLS

Six Privacy Controls You Can Use

Your privacy settings sit beside real account actions, not in a separate legal corner. You can update contact details, change your password, check device sessions, manage cookies, and ask for eligible records…

Account data

We store the name, contact details, username, and verification status needed to run your account. To change an eligible field, open Profile > Account Details and submit the correction request.

Payment records

DANA, OVO, GoPay, and QRIS references are recorded with time, amount, and wallet status. These records help us match deposits and withdrawals, answer disputes, and spot account misuse.

Cookie settings

Cookies keep your session active and remember device choices. On Android Chrome, go to Settings > Site settings > Cookies if you want to clear browser cookies before logging in again.

Login security

We log device type, IP range, login time, and failed password attempts. If a login looks unfamiliar, change your password at Profile > Security and contact us right away.

Game session logs

When you open Live Roulette, Mystical Spirits, Royal Fishing, or Aviator, we record session IDs and time stamps. These logs help settle account questions without exposing private chat or password data.

Retention requests

Some records must remain while wallet checks, disputes, or legal duties are active. For data we no longer need, you can ask us to remove or anonymise eligible records.

Privacy Questions Before You Join

Privacy questions usually come up before registration, after a device change, or when wallet activity needs checking. These answers explain what we collect, why we collect it, how you can reach us, and what steps we ask you to take so we can confirm the account belongs to you.

We collect the details needed to create and protect your account, such as username, phone or email, login records, device signals, and wallet references. We do not ask you to send your password through chat or email.

We keep payment references so your wallet activity can be matched with your account. The record normally includes method, time, amount, and status, which helps us answer disputes and check withdrawal ownership.

Yes. Open Profile > Account Details and send the correction request, or contact support if you cannot log in. We may ask for account proof before changing phone, email, or wallet-related details.

Cookies keep your session active, remember language and device choices, and support security checks. You can clear them in your browser settings, but you may need to log in again afterward.

We keep privacy request records long enough to answer you, confirm the account, and show what action was taken. When a record is no longer needed, we aim to remove or anonymise it.

Only support staff and account teams who need the case can see the request. We use chat records to answer your privacy question, confirm follow-up steps, and prevent repeated identity checks.

Yes. Where access or eligibility is discussed, it depends on local law and is available only where local law permits. We may use region and device signals to apply those access rules.