Reference

Open dewi108 Privacy Policy Clearly

Our dewi108 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, use the casino lobby, or check DANA, OVO, GoPay…

Account detailsWallet recordsDevice accessCookie choices
dewi108 Open dewi108 Privacy Policy Clearly
CONTACT YOUR WAY

Check Privacy Policy Questions With Us

A clear contact path matters when you want to understand a record, correct an account detail, or ask how a cookie works. Start from the support route connected to your account and include the email or phone detail used at registration, the relevant date, and a short description of your request. We can then locate the right account context without asking you to send a password or wallet PIN. For a cashier concern, mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account so the status can be checked in the correct place.

Team online

Account request

Use the account support path to ask about personal details held in your profile, a correction, or a copy request. Include your registered contact detail and the section of this Privacy Policy you are asking about; never send a password, PIN or one-time code.

Wallet record

For a payment-related privacy question, identify the rail shown in your account, such as DANA, OVO, GoPay or QRIS, and add the transaction date. Bank transfer and virtual account references help us separate a cashier record from unrelated account activity.

Access concern

If sign-in or device recognition creates a privacy concern, tell us whether you used mobile or desktop access and describe the message shown. We use that context to review the session path while keeping your secret login details out of the request.

DATA HANDLING DETAILS

Browse dewi108 Privacy Controls

We handle account and session data for defined service needs rather than treating every detail as a general profile.

Collection scope

We collect details you submit for an account and records created by your activity, including sign-in events, support messages and cashier references. A request involving DANA or QRIS can therefore be matched to the account and transaction context rather than handled as an anonymous message.

Cookie use

Cookies and similar storage can keep a session active, remember a selected setting, or help us understand page performance. You can adjust browser controls, although removing necessary storage may interrupt sign-in, the cashier path or movement from account access into the lobby.

Account security

We use account verification, session checks and limited device signals to reduce unauthorised access. If you change from mobile to desktop or sign in after a long gap, the extra check can protect the account without requiring us to store your wallet PIN.

Payment matching

A payment record may contain a rail name, reference, amount and status needed to reconcile the account. DANA, OVO, GoPay, QRIS, bank transfer and virtual account details are handled for that purpose; wallet credentials are not requested in a support message.

Retention choices

We retain each category only while its service, security, dispute or legal purpose remains relevant. When a record no longer needs to be kept, our process can remove it or separate it from direct account identification where that is suitable for the record.

Your requests

You may ask about access, correction, deletion where applicable, or the use of your data by contacting the support path linked to your account. We may verify identity before acting, and our response will account for local requirements and the original purpose of the record.

Find Answers About Privacy Policy

These Privacy Policy answers address the account and cashier questions you are most likely to have before continuing. They explain what data connects to sign-in, how wallet references are used, what cookies do on mobile or desktop, and how to contact us about a change. If a question concerns eligibility or service access, the answer remains subject to local law and the region attached to your account.

The dewi108 Privacy Policy covers account details, verification records, sign-in and device events, support messages, cookies, and payment references. It explains why we use each category, how security and retention apply, and how you can ask about access or correction through the account support path.

Our Privacy Policy can cover a rail name, transaction reference, status, date and account match for DANA, OVO, GoPay or QRIS. Bank transfer and virtual account records may be handled in the same way. We do not ask you to include a wallet PIN in a support request.

Yes, you can contact us through the support path connected to your account and request a correction. Include the registered contact detail, identify the field that appears wrong, and explain the change. We may verify your identity before updating the record or confirming what can be changed.

Privacy Policy covers cookies and similar storage used for necessary session functions, selected settings and page performance. On mobile, clearing or blocking them can interrupt sign-in or the move from the cashier path to the lobby. Browser controls let you change optional storage preferences.

Retention depends on the type of record and its service, security, dispute or legal purpose. We do not promise one period for every category. When a record no longer needs to be kept, it may be removed or separated from direct account identification where suitable.

Send an access request through the account support route and state that it concerns the Privacy Policy. Add your registered email or phone detail, the records you want clarified, and any relevant date. We may ask for identity confirmation before locating or releasing account-related data.

Yes. Privacy requests and service eligibility depend on local law. Where local law permits, we will explain the available process for access, correction or deletion; some records may remain necessary for security, transaction matching, dispute handling or another lawful operational purpose.