Reference

lotte4d Privacy Policy For Your Account

Our Privacy Policy explains how lotte4d handles the details connected with your account, device, wallet status and support requests.

Account dataWallet detailsDevice controlsPolicy requests
lotte4d lotte4d Privacy Policy For Your Account
CONTACT PATHS

Get Policy Help Beside Your Account

A clear contact path helps when a privacy question appears during login or a wallet status check. We ask you to use the account help route and include the email or phone detail attached to your account, plus the relevant payment reference when your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a wallet password.

Team online

Account help route

Use the support path inside your account when you need a copy of personal data, want to correct a detail or need help identifying the record connected with your login.

Wallet status question

For a DANA, OVO, GoPay or QRIS privacy request, share the transaction reference and date only. We can check the record while keeping your wallet PIN and password out of the request.

Access concern

If a sign-in or phone verification step exposes an unexpected detail, contact us through the account support route. Tell us what appeared and we will direct the policy request to the relevant team.

HANDLING DETAILS

Keep Your Data Choices Understandable

We keep privacy actions close to the account flow so you can ask about data without leaving the place where the issue started.

Account records

We handle the name, contact detail, phone verification result and login history needed to maintain your account record. Before discussing those details, we may ask you to confirm the account contact route.

Device signals

Your browser or mobile device can provide sign-in signals such as session data and device type. We use these details to recognise account activity and investigate an access concern, not to request your wallet PIN.

Cookies

Cookies can keep a session working, remember a selected path and help us understand technical errors. You can manage browser cookie settings, although changing them may affect sign-in or account navigation.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records. We use the reference, amount status and timing to reconcile a request without storing your wallet password.

Retention control

We keep records only for the period needed for account support, security checks, dispute handling or a legal requirement. When a record is no longer needed, our handling follows the applicable retention process.

Change request

You can ask us to correct, access or clarify personal data through the account support route. Include the affected detail and your account contact so we can verify the request before making a change.

Answers Before You Open An Account

These Privacy Policy answers focus on the questions you may have before creating a lotte4d account from Indonesia. They explain account records, device behaviour, wallet references and the practical route for asking us to access or change your data. If your situation involves eligibility, access depends on local law.

It covers account details, phone verification, login activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the verification result to connect account access with the correct contact route and help investigate unusual sign-ins. It also lets us confirm a data request without asking for your wallet password.

No. A wallet status check may use a transaction reference, status and timing, but your DANA or OVO password and PIN should not be sent through an account support request.

Use the support route inside your account and ask for an access copy. Include your account contact detail and specify whether you need login records, device data, wallet references or support messages.

Yes. Send a correction request through the account help route and identify the inaccurate field. We may verify your account contact before changing the record, especially when it affects phone access.

Cookies can support sessions, selected account paths and technical checks. You can adjust them in your browser, but disabling certain cookies may interrupt login, phone verification or movement between account pages.

Start with the account support route and describe the concern in plain English. Add a payment reference only when needed, never a wallet password, and mention whether the issue involves access, correction or deletion.