Reference

lum4d Privacy Policy For Your Account

lum4d Privacy Policy sets out what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS for wallet activity.

Account clarityWallet recordsDevice controlsPolicy requests
lum4d lum4d Privacy Policy For Your Account
REQUEST PATHS

Where To Ask About Privacy Policy

A clear contact route helps you control your account data without guessing which team to reach.

Account request Use the account support path for a copy request, correction request or question about…
Wallet query For DANA, OVO, GoPay or QRIS data, send the payment reference with your privacy…
Access concern If you cannot reach the privacy request path, use the login help route and…
HANDLING PRACTICES

What Our Data Controls Cover

We keep the Privacy Policy practical by connecting each data use to an account step you can recognise.

Account details

When you open an account, we use the details you submit to create the profile and complete the phone verification…

Device signals

A phone or desktop session can produce sign-in time, browser type and security signals.

Cookies

Our site may store necessary browser data so your session, language choice and account route continue working.

Payment records

A DANA, OVO, GoPay or QRIS transaction can leave a reference and status in our systems.

Retention checks

We review stored account, security and payment records against their operational purpose.

Policy changes

If we change a material part of this Privacy Policy, we place the updated wording on this page and identify…

Privacy Policy Answers For lum4d

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or a wallet record is queried. They cover the data used for access, payment matching, device security and policy requests. If your case does not fit one answer, send the account support request with the relevant reference and we will check the applicable record and local requirements.

The lum4d Privacy Policy covers account details, phone verification, sign-in and device signals, browser storage, support messages and payment references. It explains why we use each category, who may handle it for account operations, how long it may remain and how you can send a data request.

Yes. The Privacy Policy covers the transaction references and status details returned during DANA, OVO, GoPay and QRIS activity. We use those fields to connect a wallet result with your account, investigate a mismatch or confirm a receipt, without requesting your wallet password.

We collect the details needed to create your account and complete phone verification before access. A sign-in can also create a time, browser or device-security record. If you leave before completing the account step, we do not treat that incomplete form as an active account.

You can send a copy or correction request through the account support path. State the registered phone detail, the record involved and the change you seek. We may verify account control first, then assess the request under the Privacy Policy and where local law permits.

Retention depends on the record's purpose. We may keep account, payment or security details while they are needed for access, reconciliation, dispute handling, fraud checks, accounting or a lawful request. After that purpose ends, the record can be deleted or placed in restricted storage.

Necessary browser storage helps keep a session, language choice and account route working. Security signals can also record a browser or device pattern for unusual-access checks. Clearing cookies removes local session data, but it does not automatically erase server-side account or payment records.

Send a deletion request through the privacy contact path and identify the account record involved. We assess it against the Privacy Policy, account security needs, open disputes, payment reconciliation and legal retention duties. Where local law permits, eligible data is removed or restricted after the checks finish.