Reference

Privacy Policy for DANA and QRIS

dewa langit 77 Privacy Policy explains how we handle the account, device and payment details you provide when you use our Indonesia site.

Account dataWallet recordsBrowser choicesPolicy requests

Browse Our Lobby Read FAQ

What DANA and QRIS records we keep

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

Our Privacy Policy covers details you enter during account creation, including your phone number, verification status and selected access settings. We also record transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account so we can match a receipt to the correct

1
account and investigate a stalled wallet status. Device type, browser session, approximate connection data and cookie choices help us protect sign-in activity and keep the policy page usable. We use these records for account administration, payment reconciliation, fraud checks, support responses and required retention. We do
2
not use a payment reference as a reason to send unrelated messages. Where local law permits, you can ask us to explain a data use, correct an entry or close access; some records may remain when a legal, dispute or accounting need applies.

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

CONTACT ROUTES

Three ways to ask about your records

A clear contact path helps when your Privacy Policy question concerns a phone check, wallet receipt or browser session. Start with the support contact shown in our account area and include the phone number linked to your account, without sending a password or full payment credentials. You can also use the policy contact in the site footer, or raise the matter beside the cashier path when a DANA, OVO, GoPay or QRIS reference needs matching. We reply through the contact route you provide.

Team online

Account contact

Use the support contact inside your account area for a Privacy Policy request about phone verification, sign-in records or a correction to your personal details. Include the relevant date and account phone number, while keeping passwords, one-time codes and complete wallet credentials out of the message.

Policy footer

The policy contact in our site footer is suitable when you cannot reach the account area. Tell us whether your request concerns access, correction, deletion or a question about cookies, then add enough account detail for us to locate the right record without exposing sensitive payment information.

Cashier path

If a wallet receipt is part of your request, use the support route beside the cashier path and attach only the transaction reference. We can compare DANA, OVO, GoPay, QRIS, bank transfer or virtual account records with your account while keeping the request focused on privacy handling.

SIX DATA CONTROLS

Six controls around account data

We apply the same Privacy Policy thinking across a mobile browser and a desktop session: collect what an account step needs, limit access to the people handling that request and retain records…

Collection

We collect account details when you open an account or complete phone verification, and we collect payment references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. Fields not needed for the stated account or payment task are not requested through that step.

Cookies

Cookies and similar browser storage can remember a session, preserve a selected setting and help us understand whether a policy page loads correctly. On mobile, you can clear site data through your browser settings; doing so may sign you out and remove saved access preferences.

Account safety

Phone verification comes before account access, and session details help us examine unusual sign-in activity. We will not ask for your password or one-time code in a support reply. If a device is shared, sign out after checking the lobby or your account records.

Retention

We keep account, support and payment references only for the period needed for account administration, dispute handling, reconciliation or a legal duty. A request to remove data may therefore have a different result from a request to correct a phone number or explain a record.

Your request

You can ask us to access the personal data linked with your account, correct an inaccurate entry, explain a processing purpose or ask whether removal is available. Send the request through the account contact or policy footer and include enough detail for identity matching.

Policy changes

When this Privacy Policy changes, we place the revised wording on this page and update its visible date or version detail. Check the page before a new account step, especially if you use a mobile browser in Bandung or switch from wallet payment to bank transfer.

Privacy Policy questions before account access

These Privacy Policy answers address the points you may search before opening an account with dewa langit 77. They explain the practical treatment of account details, wallet references, cookies, device sessions and contact requests. If your situation is not covered, use the policy footer or account contact and describe the record you want us to check.

It covers information you provide for account creation and phone verification, device and browser session details, cookie choices, support messages and payment references. Those references may relate to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account used with your account.

We use a DANA or QRIS reference to match a payment event with the correct account, check a receipt and investigate a wallet status question. The same approach applies to OVO, GoPay, bank transfer and virtual account references, without requesting your password.

Yes. Send an access request through the account contact or the policy contact in the site footer. State the phone number linked to your account and the records you want reviewed. We may need account details to confirm that the request concerns your data.

Use the account contact and identify the incorrect field, such as a phone number or verification status. We will assess the change against account records and may ask for a verification step. Do not include a password, one-time code or complete wallet credentials.

Cookies can support session continuity, saved settings and page performance checks. You can clear them through your mobile browser settings, but this may sign you out or remove stored preferences. The Privacy Policy remains available through the site footer after browser data is cleared.

You may ask whether removal is available through the account contact or policy footer. We assess the request against active account needs, payment reconciliation, disputes and legal duties. Some records can remain for a required period even when access to the account has ended.

The page is available for you to read, while account eligibility and certain data rights depend on local law. Where local law permits, we respond to access, correction, explanation or removal requests using the contact route stated in this policy.

Privacy Policy for DANA and QRIS

Three ways to ask about your records

Account contact

Policy footer

Cashier path

Six controls around account data

Collection

Cookies

Account safety

Retention

Your request

Policy changes

Privacy Policy questions before account access

01 What does the dewa langit 77 Privacy Policy cover?

02 Why does Privacy Policy handling include my DANA or QRIS reference?

03 Can I request access to my dewa langit 77 data?

04 How do I correct a phone number or account detail?

05 How does Privacy Policy treat cookies on mobile?

06 When can my data be removed from dewa langit 77?

07 Does access to the Privacy Policy depend on local law?

Related Pages