Reference

dewa91 Privacy Policy For Your Account

Our Privacy Policy explains what account details we collect, why we use them and how you can ask about your records before opening or using an account.

Clear data purposesPayment status contextPhone verification stepsPolicy contact path
dewa91 dewa91 Privacy Policy For Your Account
CONTACT THE TEAM

Where Privacy Questions Go

A direct support route helps you ask about Privacy Policy matters without placing personal details in a public message.

Account privacy Ask through the signed-in account support path when your question concerns phone verification, account details, device sessions or a request to change personal records. We use the account context to reduce mistaken disclosures and may ask for a matching account step before discussing private data.
Wallet reference For a DANA, OVO, GoPay or QRIS receipt, send only the payment reference needed to locate the record. Do not send a wallet password, PIN or full security code. We use the reference to check status while keeping unrelated payment details outside the support exchange.
Policy request If you want a copy, correction or clarification under our Privacy Policy, state the request and the account email or phone detail connected to it. We may verify ownership before replying, especially when the request could expose another person’s account information.
OUR DATA PRACTICE

What We Do With Account Data

We keep the Privacy Policy practical by linking each data use to an account action you recognise. Phone verification supports account ownership checks; device and session records help us investigate unusual sign-ins…

Account details

When you open an account, we collect the details needed to create and maintain that account, including contact data used for phone verification. We use those details for sign-in, account messages and ownership checks, not as a public profile displayed beside lobby activity.

Device sessions

A mobile browser or desktop session can create technical records such as device type, approximate connection details and sign-in time. These records help us assess an unusual access attempt and respond to a security question without needing access to your private device contents.

Payment references

A payment reference can connect a DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI transaction to the correct account. We use the reference to check a receipt or status, while wallet PINs and bank login credentials remain outside our requested support details.

Cookies

Cookies and similar browser storage help preserve sign-in continuity, session safety and selected page settings. You can manage browser storage through your device controls, although removing it may require another account sign-in or affect a saved preference on the Privacy Policy page.

Retention

We retain account, security and payment-reference records for the period needed to operate the service, resolve disputes, detect misuse or meet a legal obligation. When a record is no longer needed for those purposes, we remove it or reduce its connection to your account.

Your requests

You can ask us to explain a data use, correct an inaccurate account detail, provide available account data or consider deletion where local law permits. Send the request through private account support, and we may verify your identity before making a change or disclosure.

Privacy Policy Answers For dewa91

These Privacy Policy answers address the account and payment questions you may search before opening an account from Indonesia. They explain the practical data trail around phone verification, mobile sign-in, cookies and local payment references without asking you to share sensitive credentials. If your situation is specific, use the private support path and include only the details needed to locate your account.

The Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains how we use those records for account access, security, receipt matching and legal or operational needs where local law permits.

Phone verification helps connect account access to the person who opened the account and helps us investigate a sign-in concern. We may use the verified contact detail for account messages and ownership checks, while the Privacy Policy describes the related data purpose.

Yes. The policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a reference to check a receipt or status against your account, and you should never send a wallet PIN or bank login.

We may receive technical session details such as device type, sign-in time, browser settings and approximate connection details. These records support account security and troubleshooting; they do not give us access to private files, photos or messages stored on your mobile device.

Use the private account support path and state whether you want an available data copy, a correction or a clarification. Include the account email or phone detail needed to locate your record. We may verify ownership before replying or changing account data.

We keep personal data and related payment or security records only while needed for account operation, dispute handling, misuse checks or a legal obligation. After the applicable need ends, we remove the record or reduce its link to your account.

The Privacy Policy is written for account and data questions in Indonesia, but access and eligibility depends on local law. We apply the service and any data request process where local law permits, and support can clarify the route for your account.