Reference

bigwinner Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details, phone verification record and wallet activity connected with your bigwinner access.

Account dataCookie choicesWallet recordsPolicy access
Explore Our Lobby Read FAQ
bigwinner bigwinner Privacy Policy for Your Account
HELP CHANNELS

Privacy help for DANA and QRIS

A clear contact path matters when a wallet reference or account detail looks unfamiliar. Our support chat and account contact form can receive Privacy Policy questions, including requests to correct a phone number, explain a QRIS receipt record or confirm why a DANA status appears in your account history. Include your account identifier and the relevant date, but do not send a password or full payment credentials. We use the details you submit only to locate the request and provide a reply.

Team online

Account contact form

Use the contact form from your account area when you want to ask about stored profile data, a phone verification record or a correction to your account details. Add the date and account identifier so we can locate the right record without asking you to share a password.

Support chat

Our support chat can explain a Privacy Policy question while you are checking a wallet event such as an OVO, GoPay or QRIS status. We may ask for a limited reference number, but we will not ask you to reveal your login password or full wallet security code.

Receipt status request

If a DANA receipt, bank transfer or virtual account event needs clarification, send the visible reference and approximate time through our support route. We compare it with the account record, limit access to the case, and tell you what data was used to investigate the status.

DATA PRACTICE

How account data stays in order

We keep this policy practical by linking each data category to an account action: phone verification supports access, device signals help detect unusual sessions, and wallet references help trace a payment question.

Phone verification

Before account access, we use the phone number and verification result to connect you with the correct profile. If that number changes, contact support rather than opening a second profile, because duplicate details can make a correction request harder to match.

Device sessions

A browser or mobile session may create technical records such as device type, sign-in time and network details. We use these signals to investigate unusual access and account recovery questions, not to read private content stored on your device.

Cookie choices

Cookies can keep your sign-in flow and selected lobby settings consistent between pages. You can adjust cookie controls in your browser, although blocking some storage may remove session preferences or require another account sign-in on that device.

Wallet records

DANA, OVO, GoPay and QRIS references are kept with the related account event so we can investigate a receipt or status question. We use the reference needed for matching and do not ask support contacts to send a full wallet credential.

Retention requests

We keep records only for the period needed for account operations, security checks, dispute handling or legal duties. You can ask which category remains on file and request deletion of eligible data, while required transaction or security records may stay longer.

Policy changes

When this Privacy Policy changes in a material way, we place the updated wording in the policy area and may show an account message. You can contact us to ask what changed, which date applies, and how the update affects your stored account data.

Privacy Policy answers before account access

These questions focus on the records you are most likely to notice while creating an account or checking a wallet status. Our answers describe the practical path for requests about account data, cookies, device sessions and payment references. If your situation is specific, use the support chat or account contact form and include only the minimum details needed to locate your record.

It covers account details, phone verification, device and browser events, cookies, support messages and payment references connected with your use of bigwinner. It also explains why we use each category, how retention works, and how you can request access or a correction where local law permits.

We use payment references and status details needed to match an account event, such as a DANA receipt or QRIS transaction. Do not send a wallet password, security code or full credential to support. The Privacy Policy explains the payment records we may retain.

Phone verification links an account request to the correct profile and helps us investigate unusual sign-ins or recovery requests. We retain the number and verification result according to the Privacy Policy. If your number changes, ask support to correct the existing account record.

Send an access request through the account contact form or support chat, using your account identifier and a clear description of the records you want. We may verify ownership before responding. The Privacy Policy sets out any legal or security reasons that limit a request.

Yes, you can request a correction or deletion of eligible account data through our support route. We first confirm which profile is yours, then assess the category and any retention duty. Records needed for security, disputes or legal requirements may remain available for that purpose.

Cookies and similar storage can keep a mobile sign-in session, selected settings and error preferences working between pages. Your browser controls whether they remain. Blocking them may require another sign-in or remove preferences, as explained in the Privacy Policy.

Open the Privacy Policy page from the account or footer menu on your phone or desktop browser. The displayed version includes its current wording and update date. If a change is unclear, contact support chat with the section name and we will explain the relevant data practice.

Related Pages

bigwinner Indonesia Register Speed Blackjack Genie Three Wishes FAQ