Reference

Open lotus4d Privacy Policy for Your Account Data

DANA, OVO, GoPay and QRIS records are covered here alongside your login and device details.

Clear data purposesWallet record detailsAccount request path
lotus4d Open lotus4d Privacy Policy for Your Account Data
REQUEST HELP

Choose Your Privacy Support Path

A clear request route helps when you want to ask about a stored detail, correct an account record or understand a wallet reference.

Account data request Use the support link inside your signed-in account to ask which personal details we hold. We may ask for a verification step before discussing records connected with DANA, OVO, GoPay or QRIS.
Correction request If your phone detail, identity record or payment reference needs correction, tell us what appears wrong and provide the matching account step. We compare the request with existing records before changing anything.
Wallet privacy issue For a privacy question tied to bank transfer or virtual account activity, keep the receipt reference and date ready. Our support route can check the account match without requiring your password.
DATA PRACTICES

Explore How lotus4d Handles Policy Requests

We keep this policy practical by linking each data purpose to an account action you recognise, such as login, verification or a wallet status check.

Purpose-led collection

We collect account details for a stated operational reason: opening access, confirming a phone step, matching a payment receipt or answering a request. We do not ask for unrelated personal details during routine support.

Cookie controls

Necessary cookies help keep your signed-in session and selected settings working. Browser controls can limit optional cookies, although changing them may affect remembered preferences or parts of the account path.

Device signals

When you move from login to the lobby on a phone or desktop, we may receive device type, browser version, IP address and session events. These signals help identify unusual access rather than replace your account details.

Account protection

A clear phone verification step helps connect account access with the right account holder. Never share your password or wallet PIN; support does not need either detail to check a policy request.

Retention periods

We keep verification, support and payment references only while they serve account, security, dispute or legal needs. When a purpose ends, we remove, anonymise or restrict the record where the applicable rules allow.

Change requests

You can ask who handles a record, why it was collected or whether a detail can be corrected or removed. Send the request through account support with enough context to locate it, not your password.

Find Answers About Privacy Policy

These questions cover the points Indonesian account holders usually want settled before opening access or contacting us. Each answer connects the Privacy Policy to a practical step, from phone verification and QRIS receipts to cookie settings and requests for account records. If your situation involves a particular region, access depends on local law, and our support route can explain which request path applies.

It covers account details, phone verification, login activity, device signals, cookies, support records and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use them to create and protect your account, complete the phone verification step, keep a session active and investigate unusual access. We do not need your password for a privacy request.

Yes. The policy covers QRIS receipts and status details from DANA, OVO and GoPay when they are linked to your account. We use references to match an action and resolve a status question.

Sign in, open the support link near your account or cashier area, and describe the record you want to access or correct. Include the relevant date or reference, but leave out passwords and wallet PINs.

Retention depends on the purpose. We keep account, security, support and payment references while they are needed for access, dispute handling, security checks or legal duties, then remove or anonymise them where appropriate.

You can adjust cookie settings in your mobile browser. Necessary cookies support login and session functions, while limiting optional cookies may change remembered settings or require you to repeat an account step.

Use the support route inside your account and describe the privacy concern clearly. For a bank transfer or virtual account question, add the receipt date and reference so we can locate the correct record.