Reference

lintas66 Privacy Policy For Your Account

Our Privacy Policy explains how lintas66 handles the details you provide when opening an account, signing in, using DANA, OVO, GoPay or QRIS, and contacting Account Wallet Help.

Clear data purposesWallet record contextAccount access requestsCookie choices
lintas66 lintas66 Privacy Policy For Your Account
ACCOUNT HELP PATH

Ask About Your Privacy Policy Rights

A direct support path helps you raise a Privacy Policy question without guessing which account screen to use.

Privacy request Use Account Wallet Help to ask what account details we hold, why a record…
Wallet record check For a DANA, OVO, GoPay or QRIS reference, send the account identifier and transaction…
Access concern If a sign-in or device issue affects your Privacy Policy request, explain the device…
HANDLING DETAILS

How lintas66 Applies This Policy

We apply the Privacy Policy through practical account controls rather than treating it as a page you read once and forget.

Account details

We use the details attached to your account to provide sign-in support, confirm requested changes and connect your account with…

Phone verification

Before we discuss account-linked data or change an important account detail, we may require phone verification.

Cookies and browser use

Cookies can keep account pages working and remember technical session details. You can review cookie controls in your browser.

Security signals

We may examine sign-in time, device type and related security signals when protecting an account.

Record retention

We keep account, support and payment references only for the period needed for their stated purpose, account protection and applicable…

Requesting a change

To request access, correction, deletion or a clarification, contact us through Account Wallet Help with a clear description of the…

Privacy Policy Answers For lintas66

These Privacy Policy questions address the account, wallet and device situations you are most likely to encounter before opening or using your lintas66 account. Each answer stays focused on how we handle personal data and how you can ask us to act.

It covers account details, phone verification, sign-in and device signals, cookie use, support messages, and references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction, deletion or retention where local law permits.

Phone verification helps us confirm that an account request comes from the person with access to that account. We may use it before discussing stored details or changing an important field, particularly when your request comes from a new device or an unfamiliar sign-in path.

We may retain payment references, status details and matching account identifiers for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us check a receipt or stalled status; we do not need your wallet PIN or password for that check.

Yes. Send a clear correction request through Account Wallet Help and identify the account field you believe is wrong. We may complete phone verification before making a change, then confirm what we can update under the Privacy Policy and applicable local requirements.

Cookies can support session continuity, account pages and technical functions in your browser. You can adjust cookie settings through the browser controls on your mobile or desktop device. Disabling some cookies may interrupt sign-in flow, while existing account records remain handled under the Privacy Policy.

Retention depends on why a record exists, such as account access, security checks, support handling or payment reconciliation. We keep it for the period needed for that purpose and applicable requirements. Ask through Account Wallet Help if you want a retention clarification for a specific record.

Use the Account Wallet Help path and describe whether you want access, correction, deletion or a processing clarification. Include only the account details needed to identify your request. We may verify ownership, and the available action depends on local law and required retained records.