Reference

Privacy Policy for Your langit200 Account

Our Privacy Policy explains what langit200 collects when you create an account, sign in from a phone, contact Support Chat Center or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice signalsSupport contact
langit200 Privacy Policy for Your langit200 Account
CONTACT THE TEAM

Three Ways To Ask About Privacy

A direct contact path helps you ask what we hold, why we use it or how to correct an account record. Start with Support Chat Center when a sign-in or wallet status needs context, and include your account identifier rather than sending a wallet PIN. We can use your payment reference, device path and message history to locate the right record while keeping the request focused on Privacy Policy matters.

Team online

Support Chat Center

Send a privacy question through Support Chat Center and include your account identifier, the relevant date and a short description. We use those details to locate the correct record without asking you to post a DANA, OVO or GoPay password in chat.

Account correction

If your name, phone detail or verification record is inaccurate, tell us which field needs correction and why. We may ask for an account step to confirm that the request comes from you before changing the stored record.

Payment trace

For a QRIS, bank transfer or virtual account question, provide the transaction reference and account date. We compare that reference with the payment status we received, rather than requesting full card or wallet credentials.

DATA CONTROL POINTS

Six Practical Privacy Controls

Privacy work is part of the account path, not a separate promise detached from daily access. We limit internal handling to the records needed for account support, payment matching, technical protection and…

Account security

We use sign-in records, device signals and phone verification to help detect unusual access. Never send a password, wallet PIN or one-time code through Support Chat Center. If your phone changes, contact us before attempting repeated sign-ins from a new device.

Cookie choices

Cookies and related browser storage can keep a session active, remember a security setting or help us identify a technical fault. You can clear or restrict them in your browser settings, although some account steps may then need to be completed again.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references and status details rather than wallet passwords. These records help us reconcile an account request, respond to a dispute and explain why a payment remains pending.

Retention period

We keep personal and transaction records only for as long as needed for the stated service, account protection, dispute handling or legal duties. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers.

Access request

You can ask what personal data we hold, the reason for its use and the categories of source involved. Send the request through Support Chat Center with your account identifier; we may verify your identity before releasing account-linked details.

Change request

You may ask us to correct incomplete or inaccurate account data, subject to checks needed to prevent changes by another person. Describe the exact field, provide the supporting context and tell us whether the issue concerns access, payment or contact details.

Privacy Policy Answers For langit200

These questions cover the account situations we hear about most often, including payment matching, device access and requests to see or change personal records. Our answers apply to the data handling described on this page, and any access or eligibility question remains where local law permits.

It covers account details, phone verification, device and sign-in records, cookies, support messages, payment references and retention. It also explains how we use those records to protect access, match DANA or QRIS activity and answer requests to see or correct your personal data.

No. Our Privacy Policy distinguishes wallet credentials from transaction references. When you use DANA, OVO, GoPay or QRIS, we may retain the reference, amount and status needed to match your account activity, while your wallet password and PIN stay with the relevant payment service.

Use Support Chat Center and state that you are making a personal data access request. Include your account identifier and the records you want clarified, such as sign-in history or payment references. We may complete an account verification step before sharing account-linked data.

Yes, you can ask for an inaccurate or incomplete record to be corrected. Tell us the exact field, explain the issue and provide relevant context. We may verify your identity first, especially where the change could affect phone access, payment matching or account protection.

Device and browser signals help us identify unusual sign-ins, keep a session secure and diagnose a page problem. They can include technical details rather than the contents of your device. Clearing cookies may remove a session setting, so you might need to sign in again.

We keep payment references and status records only for the period needed for account support, reconciliation, disputes, security or legal duties. This can include bank transfer and virtual account details. We do not describe a single period for every record because the purpose and legal requirement can differ.

Yes. Contact Support Chat Center and ask which categories of data were shared, the purpose and the relevant recipient category. We may work with payment or technical providers for a requested transaction or security function, and we will verify the account before discussing account-linked details.