Reference

latar88 Privacy Policy For Your Account

Our Privacy Policy explains what latar88 collects when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount access stepsCookie choices
latar88 latar88 Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact path helps when you want to understand a record, correct an account detail or ask how long a payment reference remains stored. We connect privacy questions with the same account support route used for phone verification and wallet status checks. Include your account identifier and the subject of your request, but do not send a wallet password or full card details. Where local law permits, we may ask for an account check before releasing or changing personal data.

Team online

Account help path

Open the account help route beside the cashier area and select the privacy subject. We can explain which account field, phone verification record or wallet status reference your request concerns without asking you to share a DANA, OVO or GoPay password.

Payment record check

If your question concerns QRIS, bank transfer or a virtual account, send the transaction reference and approximate date through the account contact path. We use that detail to locate the relevant record and explain its purpose, status and retention period.

Correction request

Tell us which personal detail needs changing and why it is inaccurate. We may request phone verification before making an adjustment, then confirm the result through your account contact route. Access to any request depends on local law and the applicable identity check.

DATA CONTROL POINTS

Six Privacy Controls Inside Your Account

Privacy is easier to manage when each data use has a practical account step.

Account details

We collect the details needed to create and maintain your account, including contact information and verification data.

Phone verification

Phone verification helps us connect a sign-in attempt with the right account before access is granted.

Device signals

A phone or desktop browser may provide technical signals such as browser type, session time and security events.

Cookies

Cookies can keep a session active, remember a language or help us understand whether a page loads correctly.

Retention periods

We retain account, support and payment references only for service needs, reconciliation, security checks or legal duties described in the…

Policy contact

Use the account help route when you want a copy of stored details, a correction, an explanation of processing or…

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect you to ask before opening access. They cover wallet records, cookies, phone verification, device activity, corrections and contact steps. If a request concerns eligibility or access in Indonesia, the result depends on local law. For a record-specific answer, use the account help route and provide the relevant reference rather than sending sensitive wallet credentials.

The latar88 Privacy Policy explains how we collect account details, phone verification results, device signals, cookies, support messages and payment references. It also sets out purposes, retention, security handling and request steps. We use information for account service, reconciliation and security where local law permits.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay and QRIS. We use them to match a wallet event with your account and resolve a receipt question. We do not ask you to provide a wallet password through our contact route.

We use phone verification to connect a sign-in attempt with your account and help prevent access by someone else. The policy explains what result we retain and why. If your phone number is no longer correct, request a correction through account help after the required account check.

You can request a correction or ask about removal through the account privacy contact path. Tell us which record is wrong or which data you mean, and we may verify account control first. Removal can be limited when a payment, security matter or legal duty requires retention.

Our Privacy Policy describes cookies that support sessions, language settings and page performance on a phone or desktop browser. You can manage them through browser controls, although blocking required cookies may affect sign-in or account pages. We do not use cookies to request private files from your device.

Retention depends on the record and its purpose. Payment references may remain for reconciliation, support records for resolving a request, and security events for account protection or legal duties. The policy contact route can explain a specific record, subject to identity checks and local law.

Start from the account help route and choose the privacy subject, then include your account identifier and the relevant payment or support reference. This helps us find the right record without unnecessary data. Do not send wallet passwords. Access to a request depends on local law.