Reference

Privacy Policy for Your lesti77 Account

Our Privacy Policy explains what we collect when you open an account, sign in on a mobile browser, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesMobile access
lesti77 Privacy Policy for Your lesti77 Account
CONTACT YOUR WAY

Get Policy Help Beside Your Account

A clear contact route helps when you want to ask what a data field means, correct an account detail, or check a wallet reference.

Policy questions Use the account support route to ask how we collect, use, or store a particular detail. Include the relevant account identifier and describe the request plainly; we will use that context to explain the Privacy Policy without asking for your wallet password.
Data correction If your phone number, email, or account detail needs changing, send the request through support after signing in where possible. We may ask for an account step or phone verification so a change is attached to the correct record.
Wallet reference For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account question, share the transaction reference rather than private wallet credentials. This lets us trace the account record and explain how the payment detail is handled under this policy.
YOUR PRIVACY CONTROLS

What We Do With Your Account Details

Privacy choices work best when each control has a practical purpose. We separate account access details from wallet references, use device signals to help identify unusual sign-in activity, and keep policy requests…

Collected details

We may hold the details you submit for account creation, phone verification, sign-in activity, support messages, and payment references. For DANA or QRIS activity, the reference helps match a transaction to your account without requiring your wallet password.

Cookie settings

Cookies can keep your mobile browser session connected while you move between account access and policy pages. You can clear or restrict cookies in your browser settings, although doing so may require you to sign in again.

Account security

Phone verification can be required before account access, and device signals may help us identify an unusual sign-in pattern. Never send a password or wallet PIN through support; use the account route so we can check the request safely.

Storage period

We retain account, support, and payment-reference records only for the period needed for the stated account, security, service, or legal purpose. Ask support about a specific record, and we will explain the applicable retention reason and next step.

Your requests

You can ask what account details we hold, request a correction, ask about use, or raise a concern about a cookie or payment reference. Send the request from the linked support route and identify the account without sharing confidential wallet credentials.

Policy changes

When our data process changes, we update the Privacy Policy page and keep the current wording available through the account area. Check this page before opening a new account or changing your phone verification details, especially where local law permits access.

Privacy Policy Questions for lesti77

These Privacy Policy answers focus on the decisions you make before account access: what we collect, why wallet references appear, how cookies affect a mobile browser, and how to contact us about stored details. If your question concerns a particular DANA, QRIS, sign-in, or phone verification record, use the account support path so we can address the correct record.

The lesti77 Privacy Policy covers account creation details, phone verification, sign-in records, device signals, cookies, support messages, and payment references. It explains why we use each category for access, security, payment status checks, or policy requests, with eligibility depending on local law.

Yes. Privacy Policy treatment includes the transaction reference connected with DANA, QRIS, OVO, GoPay, bank transfer, or a virtual account. We use that reference to match account activity and check status; you should not send a wallet password or wallet PIN.

Phone verification helps connect the person requesting account access with the correct account record. It can also support a correction or security request. Our Privacy Policy treats the phone detail as account data, and we may ask for an account step before making a change.

Cookies can keep your session connected while you move between account access and the Privacy Policy page on a mobile browser. You can clear or restrict them in browser settings, but you may then need to sign in again or repeat a phone verification step.

Yes. Send a correction request through the support route linked to your account and identify the phone number or email used for access. We may verify the request before changing the record, so the correction is applied to the right account.

We keep payment references for the period needed for account matching, security, service records, or a legal purpose. The exact period can depend on the record and local requirements. Ask support about a specific DANA, QRIS, or bank transfer reference.

Use the support path connected to your account and state whether you want access details, a correction, cookie clarification, or payment-reference help. Include the account identifier but not a password or wallet PIN. Account eligibility and access depends on local law.