Reference

lenterabet Privacy Policy For Your Account

lenterabet Privacy Policy explains what we collect when you create an account, sign in, verify your phone and use local wallet routes such as DANA or QRIS.

Clear data purposesWallet record contextAccount access choicesIndonesia privacy focus
lenterabet lenterabet Privacy Policy For Your Account
CONTACT PATHS

Privacy Policy Help Through Account Support

A direct support request helps us match a privacy question to the right account record without asking you to resend unnecessary payment material. Use the account help path when login access, a wallet status, or a data request needs checking. If you are in Surabaya or elsewhere in Indonesia, include the account phone number and request type, but never send a password or one-time verification code.

Team online

Account privacy request

Ask us to locate, correct or explain account data through the account help path. Include your registered phone number and the specific Privacy Policy question so we can identify the record.

Wallet record check

For DANA, OVO, GoPay or QRIS records, tell us the payment rail, date and reference shown in your account. We use those details to check status without requesting your wallet password.

Access and device concern

If a new phone or browser shows unfamiliar access, contact support through your account route and describe the device path. We can check sign-in records and advise the next account-security step.

DATA PRACTICES

How We Apply Privacy Controls

We keep this policy practical by tying each data purpose to an account action you can recognise, from phone verification to a wallet status check.

Account data

We may store your account contact details, phone verification result and sign-in history. These records help us recognise your account when you move from a mobile browser to a desktop session.

Payment references

A DANA, OVO, GoPay or QRIS reference can be retained with cashier status data. We use the reference to reconcile an account action, not to request your wallet password or private wallet access.

Cookies and sessions

Cookies can remember a sign-in session, language choice or security setting on your device. You can clear browser cookies, although doing so may require phone verification when you access the account again.

Device protection

We may record browser type, device signals and access time to identify unusual sign-in behaviour. This helps us distinguish your normal mobile path from a session that needs an account check.

Retention choices

We retain records only for the period needed for account security, transaction tracing, dispute handling or legal duties. A request can ask which category remains and why it has been kept.

Changes and questions

You can ask for a copy, correction or explanation of personal data through support. We may verify account ownership by phone before changing a record, so another person cannot alter your details.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often. They explain what to send, what we may verify and how local access wording applies. If your request concerns a specific record, include the account phone number and the relevant date so we can follow the correct path.

It covers account details, phone verification, sign-in activity, device signals, cookies, wallet references, support messages and retention. We use each category for stated account, security, payment tracing or legal purposes.

Phone verification helps connect an account to the person opening it and protects access when a new device appears. We may request it before discussing or changing personal account data.

Yes. The Privacy Policy includes DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status. We use these references to match a transaction to the correct account.

You can contact account support to request access, correction or an explanation of your personal data. Include your registered phone number and request type; we may verify ownership before responding.

Cookies can maintain your sign-in session and remember security or language settings. Clearing them may end the session and lead to another phone verification when you return from the same mobile browser.

Retention depends on the record type and the reason it was created. We may keep account, security or payment references for account protection, transaction tracing, dispute handling or legal duties.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains how we handle data for supported account activity where local law permits, while your location may affect available access.