Reference

Open lotus33 Privacy Policy with clarity

Clear control over account and wallet data is the purpose of the lotus33 Privacy Policy.

Phone verificationDANA and QRIS recordsMobile browser accessData request path

Explore how local data enters our policy

lotus33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details connected with your account, including contact data, phone verification results, device and browser signals, login activity, support messages, and payment references. When you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, we may retain the transaction status and

1
reference needed to match your account record. BCA, BRI, Mandiri, and BNI references are handled for the same account-checking purpose when supplied through a payment route. We use these records to provide access, investigate suspicious activity, answer policy requests, and keep account history consistent. Cookies and
2
similar browser storage can remember session choices and help us detect repeated login problems. We may share necessary data with service providers that process hosting, security, or payment status, while requiring them to use it for the stated service. Access is where local law permits, and
3
this policy may change when our data practices change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTE

Switch to the right policy contact path

A clear contact route helps when your account record or wallet status needs checking. Use the policy contact path shown on this page and include your account phone number, the relevant request…

Policy questions Send a Privacy Policy request through the contact path on this page. Tell us whether you need access, correction, deletion, or an explanation of a specific data use.

Account matching Include the phone number linked to your account and the affected device path, such as a mobile browser login. We can then separate your request from another wallet or session record.

Wallet references For a payment-data question, provide the DANA, OVO, GoPay, or QRIS reference and date shown in your account history. Never send your password or full security code.

ACCOUNT SAFEGUARDS

Browse our account data safeguards

We handle this policy area through practical account controls rather than broad promises. Phone verification helps connect a request to the right account, while device and session checks help protect login records.

Data handling

We collect account, device, session, support, and payment-reference data for stated operating needs. A DANA or QRIS status can help us match a wallet event to the correct account record.

Browser cookies

Cookies or related browser storage can preserve session choices and assist with login troubleshooting. You can inspect stored data through your browser settings, though removing it may require another account verification step.

Account security

Phone verification and session signals help us check account access. We do not ask you to place a password in a policy request, and you should never share one through support messages.

Data retention

We keep relevant account and transaction references for as long as needed for access checks, security reviews, support handling, and applicable legal duties. The policy route can explain a particular record.

Who to contact

Send privacy requests through the contact path displayed with this policy. Adding your verified phone number, request type, and affected wallet reference helps us direct the matter correctly.

Requesting changes

You can ask us to access, correct, or remove eligible personal data. We may verify account ownership first, especially when the request concerns phone verification or payment history.

Check common Privacy Policy questions

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. They cover phone verification, wallet references, browser data, retention, and requests made through the lotus33 contact route. If your case is unusual, send the relevant account details through the policy contact path.

It covers account and phone verification data, device and browser signals, session activity, support messages, cookies, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

Phone verification helps us confirm which account a request belongs to and helps protect login records. We may ask you to complete that account step before discussing, correcting, or removing personal data.

We may retain payment status and transaction references needed to match DANA or QRIS activity with your account. We do not need your password or full security code for a policy request.

Use the contact path shown with the Privacy Policy and state that you want data access. Include your verified phone number and the relevant device, session, or wallet reference so we can locate the record.

Yes, you can request correction or removal of eligible personal data through the policy contact route. We may first verify account ownership, and some transaction or security records may need continued retention.

Cookies or related browser storage can remember session choices and support login checks on a mobile browser. You can manage them in browser settings, but clearing them may trigger another account verification step.

Yes. Requests, account access, and certain data rights depend on local law. Where local law permits, we explain the applicable record, request route, and any reason a record must remain retained.

Open lotus33 Privacy Policy with clarity

Switch to the right policy contact path

Browse our account data safeguards

Data handling

Browser cookies

Account security

Data retention

Who to contact

Requesting changes

Check common Privacy Policy questions

01 What does the lotus33 Privacy Policy cover?

02 Why does Privacy Policy mention phone verification?

03 Does lotus33 store DANA or QRIS payment data?

04 How can I request access to my account data?

05 Can I ask lotus33 to correct or remove data?

06 How does Privacy Policy treat cookies on mobile?

07 Does access to my data depend on local law?

Related Pages