Reference

lesehantoto Legal: Clear Access Before You Join

lesehantoto sets out its Legal position before you open an account, including local eligibility, identity checks, wallet use and requests about your data.

Local-law accessAccount checksData requestsWallet records
lesehantoto lesehantoto Legal: Clear Access Before You Join
CONTACT ROUTES

Get Policy Help Beside Your Account

A clear contact path matters when a Legal question affects account access or a wallet record.

Account access Use the account support route when phone verification, eligibility wording or a sign-in decision needs clarification. We can point you to the relevant Legal section and ask for the account reference needed to identify the request.
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, keep the payment receipt and reference ready. Our support path can connect a policy question with the transaction record without asking you to share your password.
Data requests Ask through the account contact path if you want to correct, access or question personal data held for your account. State the request plainly, and we will explain the next identity check before making a change.
DATA PRACTICE

How We Apply These Legal Rules

Legal wording is useful only when it matches what happens during an account action. We connect policy handling to phone verification, wallet references, device sessions and the records needed to resolve a…

Data handling

We use account details to support access checks, phone verification, wallet reconciliation and policy-related replies. Share only what the requested step requires, and use the account route rather than sending identity documents through an unlisted contact.

Cookies and sessions

Cookies and device-session records can help keep an account path working between login and the lobby. You can ask support about a cookie or session concern; clearing browser data may require you to complete phone verification again.

Account security

Keep your sign-in details private and check that your phone access remains under your control. We may use a phone verification step before account access or a sensitive account change, helping connect the request with the correct account holder.

Record retention

Some account, payment and support records may remain after a request because they help reconcile DANA, QRIS, bank transfer or virtual account activity. Ask through support which record category your request concerns and why it may need to remain.

Policy contact

The account support route is the first place to raise a Legal question about access, data handling, cookies, wallet checks or account closure. Include the relevant date and reference so we can identify the policy point without guessing.

Change requests

You can request a correction to account details or ask how a policy change is handled. We may confirm your identity before editing records, and a request does not remove records needed for an unresolved payment or account matter.

Answers Before You Open An Account

These Legal answers address the checks most likely to matter before you create an account or ask us to change an existing record. They cover local eligibility, identity, wallet evidence, cookies, retention and the support route, so you can choose the correct next step without relying on assumptions.

Our Legal position is conditional: access depends on local law. You should open or use an account only where local law permits and only when your own circumstances meet the applicable requirements. The account page may also require phone verification before access continues.

A phone verification step may be required before account access or a sensitive account change. It helps connect the request with the correct account holder. Keep control of the phone linked to your account, and use the account support route if the code or decision is unclear.

DANA and QRIS references can be used to reconcile an account action or answer a wallet question. Keep the receipt and transaction reference, but do not send your password. If you request a correction, support may confirm identity before changing the related account record.

Yes, you can use the account contact path to ask for access to, correction of or clarification about personal data connected with your account. Describe the requested change clearly. We may complete an identity check before editing a record or disclosing account-specific details.

Some records may need to remain after an account request because they support payment reconciliation, an unresolved support matter or account administration. This can include references connected with GoPay, OVO, bank transfer or virtual account activity. Support can explain the category involved.

Cookies and device-session records can help maintain the route from login to account pages. If you clear browser data or switch devices, you may need to complete verification again. Ask support about a cookie concern without sharing passwords or private access codes.

Start with the support route displayed inside your account and identify whether your question concerns access, data, cookies, wallet evidence or a record change. Include a transaction or account reference when relevant. We can then direct the request to the applicable Legal section.