Reference

Privacy Policy For Your langit128 Account

Our Privacy Policy explains how langit128 handles the details you provide when opening an account, signing in on mobile, checking wallet status, or entering the lobby with access…

Account dataWallet recordsCookie choicesSecurity requests

Browse Our Lobby Read FAQ

How Privacy Works Around Wallet Activity

langit128 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to the account details, device signals and transaction references created when you use langit128 where local law permits. We may need your phone number for verification before account access, then connect your account record with the payment route you select, such as

1
DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. A payment reference helps us match a receipt with the correct account without asking you to send unnecessary wallet credentials. We also record sign-in events, browser details and security actions to detect unusual access. Our pages
2
may use cookies to remember a session and measure whether a page loads correctly. If you ask us to correct, export or remove eligible personal data, contact support through the account or cashier path so we can confirm your identity first. Access and eligibility depend on
3
local law, and this policy may be updated when our data practices change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE TEAM

Three Ways To Ask About Privacy

A clear contact route matters when a phone number, wallet reference or cookie choice looks wrong.

Account request Use the account support path when you want to access, correct or remove personal details. We may ask for a verification step before changing the phone number attached to your langit128 account, which helps prevent another person from taking control of the request.

Cashier question Choose the cashier support path for a DANA, OVO, GoPay or QRIS reference that appears under the wrong account. Share the receipt reference and approximate time, not your wallet password. We use those details to locate the relevant record and explain its status.

Security concern If a sign-in alert or device session looks unfamiliar, tell us through account support as soon as possible. Mention whether you used a mobile browser or desktop browser and whether phone verification was completed, so we can separate a session issue from an account access request.

DATA HANDLING

Six Practical Privacy Commitments

We handle this policy area through specific account and payment routines rather than broad promises. Phone verification supports account access, payment references help reconcile wallet activity, and device signals help us investigate…

What we collect

We may collect your account contact details, phone verification result, sign-in time, browser or device signals, and payment references. For DANA, OVO, GoPay and QRIS, the record is used to identify the transaction path, not to request your private wallet password.

Why we use it

Account data supports sign-in, phone checks, payment matching, security alerts and replies to your privacy request. Device details can show whether a request came from your usual mobile browser or a new desktop session, helping us investigate access without guessing.

Cookie controls

Cookies can keep a session active and help us see whether the account page loads correctly. You can manage cookies in your browser settings. Removing them may require another sign-in, and it can affect the path from phone verification to the lobby.

Account protection

We use phone verification before account access and examine unusual sign-in patterns. Keep your password and one-time code private, especially when moving between a mobile browser and a desktop browser. If a session is not yours, contact us through account support.

Retention choices

We keep account, security and payment records only for the period needed for the stated purpose, account administration or a legal requirement. When you ask about removal, we first check whether a transaction or security record must remain for that reason.

Change or access

You can ask what personal data we hold, request a correction, or ask about deletion through the account support route. Include your linked contact detail and the requested change. We confirm identity before action and explain any part that cannot be changed.

Privacy Policy Questions For langit128

These answers address the privacy questions that usually arise before account access, especially around wallet records, mobile sessions and data requests. If your situation is not covered, use the account support path and describe the specific record you want us to check. Access remains subject to local law.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, payment references and support requests. It explains why we use each category, how retention works, and how you can request access, correction or deletion where local law permits.

We do not ask you to send a DANA or QRIS wallet password through support. We may retain a payment reference, receipt detail or status needed to match an account action. Keep your wallet credentials private and share only the reference requested for a specific check.

Phone verification helps confirm that the person requesting account access controls the linked contact route. We may retain the result and related security event, rather than the contents of private messages. This step can also help us handle a later correction or access request.

Use the account support route and ask for a personal data access request. Include the email or phone linked to your account and explain the records you want, such as cookie details or payment references. We confirm your identity before preparing a response.

Yes, you can request a correction through account support. State which detail is wrong and provide the replacement value without sending your password or one-time code. We may complete phone verification before changing contact data, so the account remains under your control.

On a mobile browser, cookies may remember your session and help us identify whether the account page loaded correctly. Browser settings let you remove or restrict them. After removal, you may need to sign in again and repeat phone verification before access.

We retain payment, account and security records for as long as needed for the stated purpose, account administration or a legal requirement. If you request deletion, we check the specific record first and explain when a transaction or security entry must remain.

Privacy Policy For Your langit128 Account

Three Ways To Ask About Privacy

Six Practical Privacy Commitments

What we collect

Why we use it

Cookie controls

Account protection

Retention choices

Change or access

Privacy Policy Questions For langit128

01 What does the langit128 Privacy Policy cover?

02 Does langit128 store my DANA or QRIS password?

03 Why is phone verification mentioned in the Privacy Policy?

04 How can I request my langit128 personal data?

05 Can I ask langit128 to correct my account details?

06 How does the Privacy Policy handle cookies on mobile?

07 How long does langit128 keep payment and security records?

Related Pages