Reference

Open lotus33 with clear privacy terms

DANA, OVO, GoPay and QRIS wallet records, login device details and account steps are covered in this Privacy Policy so you know what we collect before you open…

DANA data contextOVO wallet recordsQRIS receipt checksDevice login controls
lotus33 Open lotus33 with clear privacy terms
CONTACT ROUTES

Reach us about your privacy choices

Privacy questions should reach the same team that can inspect account records, not a generic inbox. If you contact us from Jakarta or another Indonesia location, include your registered mobile number, payment rail used, and the date of the account action. We answer through live chat, email and account inbox from 09:00 to 23:00 WIB, with urgent access issues routed first.

Team online

Live chat privacy desk

Use live chat after signing in when you need a quick privacy check. We may ask for your account ID, recent DANA or QRIS reference and device type before we discuss personal records.

Email data requests

Send detailed privacy requests to [email protected] from the email on your account. Include the change you want, the mobile number used at account creation and any OVO or GoPay receipt reference.

Account inbox follow-up

When a request needs more checks, we reply inside your account inbox so the thread stays linked to your login. Keep that message until the data correction or access answer is complete.

ACCOUNT CARE

Manage your data across the account

Your privacy controls sit beside normal account actions so you can act without repeating your case. The policy covers account creation fields, wallet activity, cookie choices, game-session logs such as Starlight Princess…

Account data fields

During account creation, we ask for mobile number, email, password and payment name because those fields support login, wallet checks and privacy replies. Extra documents are requested only when account safety or payout verification requires them.

Cookie choices

Cookies remember language choice, session status and security alerts on your browser. You can clear them in Chrome through Settings > Privacy and security > Clear browsing data, but you may need to sign in again.

Device security logs

New device logins may trigger a code check or manual verification. We record IP range, device model and time stamp so we can investigate account access questions without exposing payment details in chat.

Wallet record use

DANA, OVO, GoPay and QRIS receipts are linked to your wallet record to match deposits and withdrawals. We use transaction references, account names and timestamps for reconciliation, dispute handling and privacy request checks.

Retention periods

We keep account and payment records only for operational, security and legal periods, then delete or anonymise data when it no longer serves those needs. Chat logs may remain while a request or dispute is active.

Privacy rights

You can ask us to access, correct or delete personal data where local law permits. We verify your identity first, then explain the action taken or the reason a record must remain.

Ask about lotus33 privacy controls

Use these answers before you open an account or when a privacy choice affects your wallet, cookies or login device. We keep the answers practical: what we collect, why a record exists, how long it may stay, and which channel to use. If your case involves DANA, OVO, GoPay or QRIS, include the receipt reference when you contact us.

We collect the details needed to create and protect your account: mobile number, email, password data, sign-in logs and payment name. If verification is needed, we may request extra proof before changing privacy records.

Wallet records let us match deposits, withdrawals, refunds and disputes to your account. The policy covers transaction references, timestamps and account names so we can answer privacy requests with the correct payment context.

Yes. Contact live chat or [email protected] from your registered email and state the field that needs correction. We verify your identity, check related wallet or login records, then confirm the completed change.

Cookies keep your session active, remember language choices and help us detect unusual sign-ins. You can clear browser cookies from your device settings, but doing so may require a new login code.

We share limited fields only when a service partner needs them for payment routing, hosting, analytics, security checks or customer care. Partners are expected to process the data for that task and not for unrelated use.

Send the request through live chat after signing in or email [email protected]. Deletion is handled where local law permits, and some payment or security records may remain for required retention periods.

If you lose access, we check identity before discussing personal data. We may compare mobile number, email, device history and recent QRIS or DANA references, then reply through the safest verified channel.