Reference

Privacy Policy For Your lotus404 Account

lotus404 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesContact route
lotus404 Privacy Policy For Your lotus404 Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A privacy question should not leave you searching through the payment screen. We provide a direct support path for questions about your account record, cookie choices, phone verification or a DANA, OVO, GoPay and QRIS transaction record. Include the contact detail linked to your account and describe the request in plain English so we can identify the relevant record without asking for unnecessary information. Do not send a password or payment PIN. Where local law permits, we can explain the available access route and the steps needed to correct an account detail.

Team online

Account privacy

Ask us which account details are held, why phone verification appears in your record and how to request a correction. We use the account contact route rather than asking you to post personal details in a public message.

Wallet records

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, contact support with the date, amount reference shown in your account and wallet name. We can check the payment record while avoiding requests for your PIN.

Cookie choices

Questions about cookies can be raised through the same support path. Tell us whether you are using a mobile browser or desktop browser, because device settings can affect which cookie controls appear during account access.

DATA HANDLING

How lotus404 Handles Policy Requests

Privacy work is tied to practical account events: signing in, confirming a phone number, checking a wallet status and keeping a record of a support conversation.

Account details

We may hold details you enter for account creation and the phone verification state connected with access.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create records needed to match a wallet action with…

Security checks

Sign-in events and verification steps help us identify unusual account access.

Cookies

Cookies can support sign-in continuity, preference storage and security checks. Your browser controls whether some cookies are accepted.

Retention

We retain account, support and transaction records only for the period described in our current Privacy Policy or when a…

Your request

You can ask what information is associated with your account, request a correction or ask a question about use and…

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account and wallet questions you are most likely to have before opening lotus404. They cover the information we collect, the reason for phone verification, cookie controls, payment records and the contact route for corrections. The wording is intended for Indonesian account access, while eligibility remains dependent on local law. If your question concerns a specific record, give us the account contact detail and the reference visible on your own screen.

It covers information you provide when creating an account, phone verification details, sign-in and security records, cookie use, support messages and payment records. It explains why we use each category, how retention works and how you can ask about access or correction.

Phone verification connects an account access step with the contact detail you provided. We use that status to help protect private account information and to identify the right record when you ask about DANA, OVO, GoPay, QRIS or another wallet entry.

We can receive transaction information needed to match a DANA or QRIS action with your account, such as a reference, status and timing. We do not need your wallet PIN for a privacy request. The current policy explains the purpose and retention of payment records.

Use the account support route and state which detail needs correction, such as a contact detail or phone verification status. Include the reference that helps us locate your account, but do not send a password, wallet PIN or full authentication code.

Cookies may support sign-in continuity, saved preferences and security checks. Your mobile or desktop browser controls some cookie behaviour. If you cannot find the relevant setting, tell us which device and browser you use and we will explain the available policy choice.

Retention depends on the category of record and the period described in our current Privacy Policy. Account, support and payment information may need to remain available for security or reconciliation. Ask us about a specific record rather than sending unnecessary personal details.

Yes. Where local law permits, you can ask which information is associated with your account and why it is used. Send the request through the account contact route with enough detail for identification. We may need phone verification before discussing private records.