Reference

dewi138e Privacy Policy for Your Account

The dewi138e Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Clear data purposesWallet status recordsPhone confirmationCookie choices
dewi138e dewi138e Privacy Policy for Your Account
PRIVACY CONTACT ROUTES

Ask About Data Through Support

A direct support route helps when your Privacy Policy question concerns a login record, wallet status or a device session.

Privacy contact form Send a Privacy Policy request through our account support contact form. Include your account identifier, the data concern and the change you want us to assess. We may ask for phone confirmation before sharing account-specific details or changing a record.
Wallet record help If your question involves DANA, OVO, GoPay or QRIS, use the cashier-linked help route and provide the transaction reference shown on your account. We use that reference to locate payment status without asking you to send a wallet PIN or complete credential.
Access issue contact When a device session, phone check or login record looks unfamiliar, contact support from the account path you normally use. Tell us the device type and approximate access time. We can review the security event and explain the next account step.
DATA HANDLING PRACTICE

What We Do With Your Records

We keep the Privacy Policy practical by connecting each data use to an account task: confirming access, matching a payment reference, answering a support request or protecting a session.

Account details

We use your account details to create the requested account path, confirm your phone before access and respond to account questions. A support agent sees only the details needed for the case, while payment credentials remain with the relevant wallet or bank service.

Cookies and sessions

Cookies help remember a session, security preference and selected page path on your browser. If you clear them, the account may ask you to sign in or confirm the device again. We explain cookie use through the Privacy Policy rather than hiding it in a game page.

Device security

We may record browser type, device signals, access time and security events to identify unusual account activity. Moving from a phone to desktop can trigger another check. If a session is not yours, contact support and avoid sharing the password or wallet code.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to reconcile your account. We do not need your wallet PIN to investigate a receipt, and we do not treat a payment reference as a public profile.

Retention period

We retain account, security and transaction records for as long as needed for the stated account purpose, dispute handling, security checks or applicable legal duties. When a record no longer has a valid purpose, our process assesses it for deletion or further restriction.

Change requests

You can ask us to correct an inaccurate profile detail, explain a data use or assess deletion of eligible records through the privacy contact form. Include the account identifier and requested change. We verify identity first and reply with the action available under local law.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain what happens around phone verification, cookies, wallet references, device access and data requests. If your question concerns a specific record, use the contact route above and give us the account detail needed to locate it.

The dewi138e Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages, security events and payment references. It explains why we use each category, how we protect account access and how you can request correction, explanation or deletion where local law permits.

Yes. The Privacy Policy includes the transaction reference and status connected with DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. We use those details to reconcile your account and answer receipt questions. We do not need your wallet PIN to check a payment record.

Phone confirmation helps us connect the account request to the correct person and reduce access from an unfamiliar session. The Privacy Policy describes this use. If you switch from a phone browser to desktop, another security check may appear when our systems need to confirm the session.

You can request a correction through our privacy contact form. State the account identifier, explain which detail is inaccurate and provide the replacement wording. We verify your identity before changing a record, then assess the request under the Privacy Policy and local legal requirements.

We keep records for the period needed for the account purpose, payment reconciliation, security checks, dispute handling or legal duties. The Privacy Policy does not treat every record alike. When a record no longer has a valid purpose, our process assesses deletion or restricted retention.

Cookies can remember a browser session, security preference and page path. Clearing them may sign you out or prompt another device check. The Privacy Policy explains this use so you can make an informed browser choice. Cookies do not replace your password or phone confirmation.

Use the account support contact form and identify the request as a Privacy Policy matter. Include the account email or phone detail, the record involved and the action requested. Do not send a password, wallet PIN or one-time code. We verify identity before discussing account data.