Reference

lebah889 Privacy Policy Explained

Our Privacy Policy explains how lebah889 handles the details you provide when opening an account, checking wallet status or contacting support.

Account dataCookie choicesWallet referencesAccess requests
lebah889 lebah889 Privacy Policy Explained
CONTACT PATHS

Privacy Help Through Your Account Route

A clear contact route helps you ask about your personal data without searching through unrelated pages. Start from the account support route and include the phone number or account identifier connected with your request. We use those details to locate the correct record, while avoiding requests for a wallet PIN or full payment password. If you are in Bandung and a QRIS receipt appears unresolved, send the receipt reference rather than the complete wallet credentials. Support handles privacy questions alongside login and payment-status concerns.

Team online

Account support

Use the support path linked to your account when you want to ask what contact details, verification events or login records we hold. Include your account identifier and a short description of the request. We may ask for a phone verification step before discussing account-specific data.

Wallet status

For a DANA, OVO, GoPay or QRIS question, send the transaction reference, date and selected rail. We can compare that reference with our status record without asking for your wallet PIN. Bank transfer and virtual account questions follow the same privacy-conscious checking process.

Security concern

If you suspect that someone used your login, contact us through the account support route and describe the device or sign-in event. We may pause account discussion until phone verification is complete. Do not send a password, wallet PIN or full card credential in a message.

DATA PRACTICES

How We Handle Your Personal Data

We keep this Privacy Policy practical by connecting each data practice to an account action you recognise.

Account details

When you open an account, we use the submitted contact details to create your account record and send account-related responses. Phone verification may be required before access or before we discuss private account content. Please keep your details accurate so a data request can be matched to you.

Device signals

Your browser and device can provide session details such as device type, operating environment and login time. We use these signals to maintain a secure sign-in trail and investigate unusual access. They do not replace your account credentials, and support may ask which device you used.

Cookies

Cookies can remember a session, language choice or security setting on the browser you use. You can manage cookies through browser controls, although changing them may require another login or affect saved preferences. Our policy treats cookie records as part of your site-access history.

Payment references

A payment record may contain the chosen rail, amount status, reference number and processing time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use these fields to reconcile status. We do not need your wallet PIN to answer a receipt question.

Retention period

We retain account, security and transaction records for as long as needed for account operation, dispute handling, fraud checks and legal duties. When a record is no longer needed for those purposes, our process is to remove it or reduce its link to your account where practical.

Your request

You can ask us to confirm stored data, correct an inaccurate detail, explain a cookie record or consider deletion. Send the request through account support with your identifier and the reason. We may verify ownership and explain any record that cannot be removed because a legal or dispute hold applies.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account, device and payment questions you may have before opening an account with lebah889. We keep the route specific: use support for a personal record request, use your browser for cookie controls and never send private wallet credentials in a message. Account access depends on local law.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It explains why we use each category, how records support account security and status checks, how long records may remain, and how you can ask about access or correction.

Yes. The Privacy Policy includes the payment reference linked to a DANA or QRIS status check, such as the selected rail, reference number and processing state. We use that record to match activity and do not ask for your wallet PIN or private wallet password.

Use the account support route and provide your account identifier, phone number used for verification and the type of data you want to access. We may confirm ownership before replying. A clear request helps us locate login, cookie, support or wallet-reference records.

Yes. Tell support which account detail is inaccurate and what correction you are requesting. We may ask you to complete phone verification before changing it. If the detail is tied to a pending dispute or transaction record, we will explain why the record may need to remain unchanged.

On a mobile browser, cookies may remember your session and selected settings. You can remove or restrict them through the browser controls on your device. Doing so may sign you out or require another phone verification step when you return to the account.

We keep records for the period needed to operate your account, resolve a payment dispute, examine unusual access or meet applicable legal duties. A DANA, GoPay, bank transfer or virtual account reference may therefore remain after a session ends. We remove or reduce linkage when practical.

Contact account support with your request and the account identifier connected to it. We will explain any verification step, local restriction or retention reason that affects the response. Account access and eligibility depend on local law, or are available where local law permits.