Reference

Privacy Policy for langit 128 Accounts

Our langit 128 Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile device or use wallet options in…

Account recordsWallet detailsDevice accessPolicy requests
langit 128 Privacy Policy for langit 128 Accounts
CONTACT PATHS

Privacy Help Through Your Account

A direct account route helps you ask about personal data without sending sensitive details through an unrelated channel. Open the support path from your account area, describe the request, and include the affected phone number or payment reference only when it is relevant. Our team can explain a stored field, help locate the privacy request route and check whether a wallet record belongs to your account. We keep the conversation tied to your account so the response does not expose information to another person.

Team online

Account support

Use the support path after signing in to ask what account details we hold or why a verification record appears. We may ask you to confirm the phone linked to your account before discussing personal data.

Payment receipt

For a DANA, OVO, GoPay or QRIS question, send the payment reference shown on your receipt rather than a wallet password or full private credential. We use the reference to locate status and matching records.

Access request

If you cannot sign in, explain that your request concerns Privacy Policy access and provide the account phone number through the available support route. We will use account checks before discussing stored personal details.

DATA PRACTICES

Security Choices Across Your Devices

Your privacy controls start with simple account habits: use your own phone, complete phone verification before account access and sign out on a shared device.

Account records

We use your phone number, verification result and account activity to maintain sign-in access and investigate account requests. We do not ask for your wallet password. Keep your verification code private and contact support if it appears unexpectedly.

Cookies and devices

Cookies and device signals help keep a session connected, remember security choices and identify unusual sign-in behaviour. On mobile, clearing site data can remove the remembered session, so you may need to verify your phone again.

Payment references

A payment reference, status and timestamp help us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. We use this matching for support and reconciliation, not to request private wallet credentials.

Account security

Phone verification is required before account access, and our support checks are designed to prevent another person from receiving account details. If your phone changes, tell us through the account support route before requesting a data change.

Retention approach

We retain account and transaction records for as long as needed for the stated service, security checks, dispute handling and applicable legal duties. When a record is no longer needed, our process removes it or keeps it in a restricted form.

Changes and questions

You can ask what personal data we hold, request a correction or ask why a record is used through account support. Include a clear description and your account phone so we can verify the request before making any change.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we hear most often from people opening or using a langit 128 account in Indonesia. They cover wallet references, phone checks, mobile sessions, correction requests and access conditions. If your question is not listed, use the account support path and keep payment credentials out of your message.

It covers account details, phone verification, device and cookie signals, payment references, support conversations, retention and requests to correct or access personal data. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

No. Our Privacy Policy concerns the payment reference, status, amount and time needed to match a transaction with your account. We do not need your DANA or OVO password. Do not send wallet credentials in support messages or account requests.

Phone verification confirms that the account request is connected to the phone you control before account access. It also helps our support team avoid disclosing personal data to another person. Access remains subject to where local law permits.

Cookies can keep a session connected and remember security settings on your phone. Clearing browser data may remove that session and trigger another phone check. You can ask support about a device record without sending your password or wallet credentials.

Yes. Send a correction request through the account support path with the account phone number and a clear description of the field that needs changing. We verify the requester first, then explain the result and any reason a record must remain.

We keep payment references and related account records for the period needed for reconciliation, security checks, dispute handling and applicable legal duties. After that need ends, our process removes the record or restricts it rather than leaving it open for routine access.

Open the Privacy Policy from the account menu or the privacy link before entering account details. You can return to the same path from a phone or desktop browser. If the page does not load, contact account support and mention the policy link.