Reference

Privacy Policy For Your dewa1131 Account

Our Privacy Policy explains how we handle the details linked to your dewa1131 account, including phone verification, wallet records and device access.

Account dataWallet recordsDevice accessPolicy requests
dewa1131 Privacy Policy For Your dewa1131 Account
REQUEST HELP DIRECTLY

Privacy Support For Login And Wallet Records

A clear support route helps you ask about personal data without sending sensitive wallet credentials.

Account data request Use the account support route to ask what personal details are linked to your dewa1131 profile. We may ask you to complete a phone verification step before discussing account-specific records, so another person cannot receive your data.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the payment reference and date rather than a wallet password or full secret code. We compare that reference with the account record and explain the status linked to your request.
Correction pathway If your name, phone detail or account record needs correction, tell us which field is wrong and why. We review the request against account evidence, then reply through the account contact route after confirming that you control the profile.
HANDLING YOUR DETAILS

What We Do With Account And Device Data

Our Privacy Policy separates information needed for account operation from optional browser preferences. A phone number supports account verification, while device and cookie signals help us recognise a returning sign-in and investigate…

Account details

We may hold your phone number, account identifier, verification result and sign-in history because these details help connect your requests to the correct profile. We do not treat a support message as permission to disclose account data to an unverified contact.

Cookies and browser signals

Cookies can remember choices such as a selected language or an active session. Your mobile browser may also provide device type, browser version and network details when you open the lobby; you can manage cookie permissions through that browser's settings.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us connect a receipt to the correct account and investigate a mismatch. We use the reference and status data for this purpose, not your wallet password or private wallet login.

Account protection

Phone verification and sign-in checks help us respond when access looks unusual. If you use a shared device, sign out after checking your account and remove saved browser credentials so another person cannot reopen the same session.

Retention periods

We keep account, payment and support records only for operational needs, dispute handling, security checks or legal duties that apply to the service. When a record is no longer needed for those purposes, our handling process removes or separates it.

Changes and questions

You can ask for a copy, correction or explanation of personal data through the account support route. State the request clearly, include your account identifier, and complete any identity check needed before we discuss or change the record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open access from Indonesia. They cover phone verification, wallet records, cookies, device behaviour, correction requests and the route for asking about personal data. Where eligibility or access is relevant, it depends on local law.

The dewa1131 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, payment references and support messages. It also explains why we use those records, how long operational or legal needs may require retention, and how you can request access or correction.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. We use those records to match a receipt, investigate a mismatch and protect the account. We do not need your wallet password to check a transaction reference.

Phone verification connects an account request to the person controlling that phone detail and helps us limit unauthorised account discussions. If you ask about personal data, a completed verification step may be needed before we disclose account-specific records or process a correction.

The Privacy Policy describes practical technical details such as device type, browser version, IP address, session signals and cookie choices. These details help load the requested page, remember browser preferences and investigate unusual sign-in activity when you use a mobile browser or desktop.

Use the account support route and state whether you want access, correction or an explanation. Include your account identifier and the specific field or record involved. We may complete an identity check before releasing a copy or changing information connected to your profile.

We retain personal data while it supports account operation, payment matching, support handling, dispute checks, security work or a legal duty. The period depends on the record and purpose. When those needs end, our process removes, anonymises or separates the data.

Start with the account support route and label your message as a Privacy Policy request. Describe the account detail, cookie matter, device signal or wallet reference involved, without sending passwords. We use the verified account contact path for any account-specific reply.