Reference

lintas33 Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open a lintas33 account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity steps
lintas33 lintas33 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear support path helps you act on the Privacy Policy without guessing which account detail matters.

Account privacy request Use the account support path to ask what personal details are linked to your lintas33 profile. Include your verified phone number so we can distinguish your request from a wallet receipt or an unrelated account record.
Wallet record check When DANA, OVO, GoPay or QRIS status needs checking, send the payment reference shown in your account. We use the receipt and account step together to review the relevant record without requesting your wallet password or private access code.
Policy clarification Ask us to clarify a Privacy Policy section through the same support route used for login help. Tell us whether your question concerns cookies, retention, account security or a data change, and we will keep the reply focused.
DATA PRACTICES

How We Handle Account Details

We shape our data handling around the account actions you actually take. Phone verification helps us confirm who is requesting account access; wallet references help us trace a status; device signals help…

Phone verification

Before account access, we may use the phone detail connected to your profile to confirm a sign-in or account request. This step helps separate your request from an unfamiliar device and gives support a precise account reference.

Payment matching

A DANA, OVO, GoPay or QRIS reference is used to match a wallet event with the correct account status. Bank transfer and virtual account references can serve the same purpose when support checks a receipt or pending record.

Device signals

Our mobile browser path may record basic device and browser signals connected with sign-in security. We use these signals to spot unusual access patterns, while your phone remains the practical route for verification before account entry.

Cookie controls

Cookies can keep a sign-in path consistent and remember selected site settings. You can manage browser cookie controls on your phone or desktop, although changing them may affect account access steps or saved preferences.

Retention choices

We retain account, payment and support records only for the operational or legal period that applies to them. A request to change or remove data can be assessed where local law permits, with required records treated separately.

Account protection

Keep your phone access, password and verification details private, and contact support if a sign-in looks unfamiliar. We can then use the account reference and device context to help secure the affected access path.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may search before opening an account. We keep each answer tied to an actual lintas33 step, from phone verification and mobile browser use to payment records and requests for data changes. If your situation is different, use the account support path and describe the specific record or access issue. Any access or eligibility decision depends on local law and the details available for your account.

It covers details supplied during account creation, phone verification, sign-in, wallet activity and support contact. It also explains device signals, cookies, retention and requests to access, correct or remove eligible data, subject to local law and records we must keep.

We use the phone number connected to your account to support verification before account access and to identify the correct profile during support. Keep that number current, and contact us through the account support path if you cannot complete a verification step.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These references help us match a receipt with your account status; we do not need your wallet password for that check.

When you use the mobile browser path, we may use basic browser and device signals to support sign-in security and identify unusual access. These signals are handled with account details and are not a reason to request private wallet credentials.

You can contact us through the account support route and ask to review or correct eligible personal data. Include your verified phone number and the requested change. We assess removal or correction where local law permits and explain any retention requirement.

Retention depends on why the record exists, such as account security, payment reconciliation, support history or a legal duty. We keep information for the period needed for that purpose. Some records may remain when local law requires continued storage.

Open the account support area and state that your request concerns the Privacy Policy. Mention cookies, account access, device data, wallet status or retention, then provide the relevant account reference. We will use that detail to route the request accurately.