Reference

Your Privacy Policy Starts With Clear Choices

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

Account clarityWallet recordsDevice choicesPolicy access
lotus33 Your Privacy Policy Starts With Clear Choices
CONTACT THE TEAM

Where To Ask About Your Privacy Policy

A clear contact path matters when a Privacy Policy question affects your account or wallet record.

Account request Use account help when you want to ask about personal data held for your lotus33 account, correct a contact detail or understand which account step created a record. We check the account before discussing private content.
Wallet receipt For a DANA, OVO, GoPay or QRIS privacy question, share the relevant receipt reference through the support path. We use it to locate the transaction record without asking you to send a wallet password or secret code.
Policy request Ask for a copy, correction or eligible removal under this Privacy Policy through account support. Tell us the exact request and the account detail used to reach us, so we can confirm identity before making a change.
DATA HANDLING

How lotus33 Handles Your Privacy Policy

We keep the Privacy Policy practical by linking each data purpose to an account action you can recognise.

Account data

We may hold the details you enter during account creation and verification so we can identify your account and answer a private request. Check your entries before submission, then contact account help if a correction is needed.

Cookies

Necessary cookies can keep policy pages, sign-in steps and selected settings working across a session. Your browser controls cookie storage, while our Privacy Policy explains why a cookie may be present and what it supports.

Device security

A phone or desktop session can create technical signals such as browser and access details. We use them to compare sign-in activity and investigate unusual access, not to request your device passcode or wallet secret.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can include a reference used to match a receipt with your account. That reference helps us check status without exposing another account's transaction details.

Retention choices

We retain records only for the purpose and period connected to account operation, security, support or a legal requirement. When you ask about deletion or correction, we assess the specific record and tell you what action is available.

Your request

You can ask what personal data relates to your account, request a correction or ask whether removal is possible under this Privacy Policy. Send the request through account help and complete the identity check before private details are disclosed.

Privacy Policy Questions About lotus33 Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record is queried. We keep the wording tied to real steps: account creation, phone verification, device access and payment receipt checks. If your situation is different, send the exact request through account help and we can assess the record connected to you.

The lotus33 Privacy Policy covers account details, verification responses, device and cookie records, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security and ways to request access or correction.

Phone verification helps connect an account request to the person trying to access it and helps us protect private account data. We may use the result when handling a correction, receipt query or access request. Eligibility depends on local law.

Yes. The Privacy Policy covers payment references received when you use DANA or QRIS, as well as comparable records from OVO, GoPay, bank transfer and virtual account steps. We use those references for status checks and account matching, not for wallet passwords.

Send an account data request through account help and identify the account using its linked email or phone detail. We may verify your identity before sharing private records. We then assess the request under this Privacy Policy and local requirements.

You can ask us to correct inaccurate personal data by stating which detail is wrong and what the accurate value should be. Use account help rather than a public message. We check the account first, then apply an eligible change under the Privacy Policy.

The Privacy Policy covers necessary cookies and technical device signals used for session settings, sign-in continuity and unusual-access checks. Your browser manages cookie storage, and you can inspect its controls. Some account steps may not work as intended if required storage is blocked.

You may ask whether removal is possible for a particular account record. We assess the request against its purpose, security needs and any period required for a transaction or legal obligation. Where local law permits, eligible data can be removed or changed after verification.