Reference

Open with a Clear Privacy Policy

langit87 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsDevice securityPrivacy requests
langit87 Open with a Clear Privacy Policy
ASK ABOUT PRIVACY

Contact Us About Privacy Questions

A direct support request gives you a clear route for privacy matters, including an incorrect phone detail, an unfamiliar sign-in event, or a question about wallet…

Email Support Desk Send a written Privacy Policy request through the Email Support Desk when you need…
Account access check If a privacy request follows an unfamiliar login, tell us the device type, approximate…
Wallet record request For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, state the payment…
DATA HANDLING DETAIL

Check Your Data Choices and Security

Privacy controls work best when each request identifies the account step involved. We separate account details, device security signals, payment references, and support messages so a request can be routed to the…

Account creation

When you open an account, we collect the details needed to create and secure that account, including contact data and phone verification status. We use this information to recognise your account step and prevent another person from requesting account-specific data.

Device signals

A mobile browser or desktop session may provide device type, browser details, session timing, and security events. These signals help us identify unusual access around login, wallet status, or account changes without treating a device signal as your identity by itself.

Cookie choices

Cookies and browser storage can keep a signed-in session working and preserve security preferences. You can adjust cookie settings in your browser. Blocking some storage may require another phone verification step or prevent a session from continuing until the account check is complete.

Payment references

We retain transaction references for DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity so we can match status questions and resolve disputes. We do not need your wallet PIN or full bank password to investigate a payment record.

Retention choices

We remove or anonymise personal details when the stated operational, security, dispute, or legal purpose ends. A transaction or security record can remain longer when needed to settle a question or meet a duty that applies where local law permits the service.

Change request

Ask us to correct, access, restrict, or remove eligible personal data through the Email Support Desk. Describe the requested change and the relevant account step. We verify ownership first, then confirm what action we can take and any reason a record must remain.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect before an account is opened or a support request is sent. They explain the practical path for account data, cookies, device signals, wallet references, and changes to personal details. When your question depends on a specific transaction or sign-in event, contact the Email Support Desk with only the reference needed to locate it. Eligibility and access depend on local law.

The langit87 Privacy Policy covers account creation, phone verification, sign-in activity, device security signals, cookies, payment references, and support messages. It explains why we use each category, how long records may remain, and how you can request access, correction, restriction, or removal.

We do not need your DANA, OVO, GoPay, or QRIS wallet password to match a payment reference. For a status question, send the payment rail, date, and account reference through the Email Support Desk. Never include a wallet PIN or full banking password.

Privacy Policy mentions device and browser signals because they help us protect account sessions and identify unusual access. A mobile browser may provide device type, session timing, and security events around login or phone verification. These signals support security checks and do not replace account ownership verification.

Send a written request through the Email Support Desk and state that you want access to your account data under the Privacy Policy. Include the registered contact detail or account reference requested by support. We verify ownership before sharing account-specific records and explain any permitted limitation.

Yes, you can ask for a correction through the Email Support Desk. Name the detail that is wrong and identify the account step involved. We may require phone verification before changing or confirming personal data, because account security comes before a data-change request.

We keep payment references only for an operational, security, dispute, or legal purpose. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records may remain while a status question or dispute is open. We remove or anonymise them when the applicable purpose ends.

The Privacy Policy applies to the personal data handled through our account and support paths, but access and eligibility depend on local law. The position can differ by location or service context. Contact us before opening an account if you need a location-specific privacy answer.