Reference

Open loby88 Privacy Policy for wallet data

Clear handling for your account, wallet records and device activity is the purpose of our loby88 Privacy Policy.

Account clarityWallet recordsCookie choicesAccess requests
loby88 Open loby88 Privacy Policy for wallet data
CONTACT PATHS

Find your Privacy Policy contact route

Questions about our Privacy Policy should include the account detail or payment reference that helps us locate the correct record.

Account request Use the support route inside your account when you want to ask what personal…
Wallet status For DANA, OVO, GoPay or QRIS records, include the date, amount reference and wallet…
Privacy change If you want a correction, access copy or removal request, state the action clearly…
CONTROL DETAILS

Explore loby88 data controls and account security

Privacy work is easier to assess when each control has a clear purpose. Our Privacy Policy connects collection, use, cookies, access protection and retention to the account steps you actually take, including…

Collection

We may collect account identifiers, phone verification results, device signals, support messages and transaction references. The exact reason should match the account, security, payment-status or support action involved.

Use

We use these records to open and protect your account, connect a DANA or QRIS reference to its status, investigate access problems and respond to a Privacy Policy request.

Cookies

Cookies and similar device storage can keep a session active, remember a setting or help us understand a technical failure. Your browser controls may restrict them, although some account steps may then need repeating.

Security

Phone verification, sign-in checks and limited staff access help protect account records. We will not ask you to disclose a password or one-time code through the Privacy Policy contact route.

Retention

We keep personal and transaction records for the period needed for the stated purpose, account security, dispute handling or applicable legal duties. When a record is no longer needed, our process addresses its removal or restriction.

Your request

You can ask for access, correction, clarification or deletion where available. We may verify your identity first, explain any restriction, and record the outcome through the support path shown in your account.

Browse Privacy Policy answers for your account

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They explain wallet records, cookies, verification and contact steps without replacing the full policy text. If your situation is unusual, send the request through the account route with the relevant reference.

It covers account details, phone verification, device and cookie activity, support messages, payment references and how we use, protect, retain or respond to requests about those records.

Yes. We explain how DANA and QRIS references help match a transaction status or receipt to your account. The wallet provider may separately handle data under its own privacy notice.

Phone verification helps connect the correct person to an account and detect access problems. We may use the result for account protection, but you should never send a verification code through support.

Open the support route shown after account access and ask for a data copy. Include enough account context for identity checks, but leave out your password, wallet PIN and one-time code.

You can request a correction through the account support path, such as an incorrect phone detail. We may check identity and ask for the specific field that needs changing.

Cookies can maintain your sign-in session, remember settings and help diagnose device errors. Browser controls can restrict them, though limiting necessary storage may require you to repeat account steps.

Where local law permits, you may ask us to delete or restrict personal data through the listed support route. We may retain records needed for security, disputes or applicable legal duties.