Reference

Privacy Policy for raja langit 777

Your DANA and QRIS details stay connected to a clear Privacy Policy on raja langit 777, so you can see what we collect before opening an account.

Account dataWallet recordsCookie choicesAccess requests
raja langit 777 Privacy Policy for raja langit 777
CONTACT DATA CARE

Three Routes For Privacy Questions

A clear contact path helps you deal with a Privacy Policy question without repeating your account story.

Account access Ask us to check the personal details attached to your account or explain a phone verification record. We may confirm ownership before sharing any account-specific response, so another person cannot request your data using only a username.
Wallet records For DANA, OVO, GoPay or QRIS questions, send the payment reference rather than a wallet password. We use that reference to locate a status entry and can explain what was retained for a deposit or cashier inquiry.
Correction requests Tell us which profile field, device record or support message appears inaccurate. We review the request against your account details, ask for a safe verification step when needed and explain whether the record can be changed or must be retained.
SIX DATA PRACTICES

What We Do With Your Account Data

Our Privacy Policy works alongside the account steps you already recognise: enter your details, complete phone verification, sign in and use the relevant wallet path.

Collection at sign-up

We collect the details needed to create your account and complete phone verification. Login events and selected device signals help us identify an unusual access attempt. You can ask support which account field prompted a verification question.

Wallet references

A DANA, OVO, GoPay or QRIS transaction may leave a reference, amount status and processing time in our records. Bank transfer and virtual account inquiries can use the same type of receipt reference without exposing your banking password.

Cookies and devices

Cookies and device signals help keep your session connected as you move from login to a mobile lobby or from a desktop table to account support. Clearing browser data may remove a saved session, but it does not erase account records.

Account security

We use phone verification and login checks to reduce unauthorised account access. Never send a password, wallet PIN or one-time code in a support message. If a login looks unfamiliar, contact us through the account support path before changing payment details.

Retention and deletion

We retain account, payment-reference and support records for as long as needed for the stated service, dispute handling and legal duties. A deletion request may be limited where a record is required to resolve a receipt or meet an applicable rule.

Changing your details

To request a correction, identify the field and explain the change in your account support message. We may verify your phone before editing it. We will tell you what changed, what remains stored and why a particular record cannot be altered.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the questions you are most likely to ask before opening an account or sending a wallet receipt. We keep the response tied to real steps: phone verification, login activity, DANA or QRIS references, cookie settings and requests made through account support. Where access or eligibility is involved, it depends on local law.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may be included when they relate to an account or receipt question.

We use your phone number to create and verify account access, then to help distinguish your request from another person’s request. If you ask about a profile field or wallet reference, we may verify that number before discussing account-specific data.

Use the account support path and state that you are making a data request. Name the record you want checked, such as a login event, QRIS receipt or profile field. We may ask for phone verification before confirming what we can provide.

Yes. Send the field that appears wrong and the correction you are requesting through account support. We compare the request with your verified account details, make an eligible change and explain any record that must remain unchanged for a receipt or legal duty.

Cookies help keep your login session and remember the path between account access, a mobile lobby and support. Browser settings can clear or restrict them. Clearing cookies may sign you out, while account and payment-reference records remain subject to this policy.

We keep account, payment-reference and support records for the period needed to provide the account service, handle disputes and meet applicable legal duties. If you request deletion, we explain which records can be removed and which must remain for those purposes.

The policy applies to the data practices described on this page, while access or eligibility depends on local law. If you are in Indonesia, use the current account and payment paths shown to you, and contact support when a location or access question needs clarification.