Reference

losari88 Privacy Policy for Your Account

Our Privacy Policy explains how losari88 handles the details you provide before account access, including phone verification and wallet records from DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesSecurity checks
losari88 losari88 Privacy Policy for Your Account
CONTACT YOUR WAY

Get Privacy Policy Help Through Support

A direct support route helps when your Privacy Policy question concerns a phone number, wallet reference, cookie setting or account record. We ask you to contact us from the signed-in account where possible, so we can separate a genuine request from an attempt to access someone else’s data. For a request from Semarang or another Indonesian location, include the relevant account step and payment reference.

Team online

Account chat

Use our support chat from the account area for Privacy Policy questions about phone verification, sign-in records or a device session. We may ask for account details before discussing private data.

Wallet query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference through support. We use it to locate the correct transaction without requesting your wallet password.

Data request

Ask support to access, correct or remove eligible account details. State the requested change clearly, and we will explain any identity check or account condition that applies under the Privacy Policy.

CONTROL YOUR RECORD

What losari88 Does With Personal Data

We keep the Privacy Policy practical by connecting each data use to an account action: phone verification protects sign-in, device signals help spot unusual access, and payment references help resolve wallet questions.

Account details

We use the phone number and account details you submit to create access, complete phone verification and respond to account requests. We do not treat those details as a public profile.

Device signals

Login time, browser type and basic device signals can help us identify unusual account access. On mobile, these checks support the path from sign-in to the lobby without exposing your private wallet credentials.

Cookies

Session cookies help keep your account path active between pages, while optional cookies may support settings or measurement. Your browser controls can clear or restrict cookies, though sign-in functions may change.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a wallet request with the correct account. Bank transfer and virtual account details support reconciliation without requiring your banking password.

Retention approach

We retain account, security and transaction records only for account operation, dispute handling, safety checks and legal duties. When a record is no longer needed, we remove or anonymise it where practical.

Your request

You may ask what account data we hold, request a correction or ask about removal through support chat. We verify the requester first and explain when a record must remain for security or legal reasons.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording tied to actual steps: phone verification, device sign-in, cookies, payment references and support requests. If your situation is not covered, contact us through the account support route and describe the record you need checked.

The losari88 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank routes.

Phone verification connects the account to the contact detail you supplied and helps protect sign-in. We may use the result when handling account access or a Privacy Policy request about your records.

Yes. The Privacy Policy includes payment references and status details for DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account records used to match an account request.

Contact support chat from your signed-in account where possible and ask for an account data request. We verify your identity, locate the relevant record and explain the available response under the Privacy Policy.

Yes. Send the requested correction through support and identify the affected account detail, such as a phone number. We may verify the request before changing the record or explaining why it must remain.

Session cookies help keep your mobile sign-in path working between pages. Browser controls can restrict optional cookies, but changing those settings may affect account access, saved preferences or security checks.

We keep records for as long as needed for account operation, security, disputes and legal duties. We then remove or anonymise them where practical; support can explain the reason for a particular record.