Reference

Open bigwiner Privacy Policy Clearly

The bigwiner Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification and wallet records from DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesContact steps
bigwiner Open bigwiner Privacy Policy Clearly
HELP WITH PRIVACY

Ask About Your Policy Choices

A clear contact route helps when a Privacy Policy question concerns your phone verification, wallet record or cookie choice. Tell us which account detail you mean and what change you are requesting; we can then match the request with the correct account step and payment reference.

Team online

Account privacy request

Use the account support path when you want to ask what phone, login or verification details we hold. Include the account identifier you can safely provide, and we will use it to locate the relevant record before discussing a change.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt, send the payment reference rather than a full wallet password or secret code. Our support path can check the status record and explain why that detail appears under the Privacy Policy.

Cookie preference help

If cookies affect login continuity on your phone or desktop browser, ask us about the setting involved. We can explain the purpose of the storage and point you to the browser control used to clear or restrict it.

DATA HANDLING

Explore Our Account Privacy Controls

Your Privacy Policy questions often relate to small account actions, so we connect each explanation to a practical control.

Phone verification

Before account access, phone verification helps us connect a request with the right account. We use the verification step to reduce mistaken disclosures, while your phone number remains part of the account record described in the Privacy Policy.

Payment references

A DANA, OVO, GoPay or QRIS payment reference can identify a receipt or status check without requiring your wallet password. We use the reference for reconciliation and support, then handle it under the retention rules set out in the policy.

Device signals

Your browser and device may create technical records such as session details, language settings or security events. These signals help maintain a safer login path on mobile and desktop, and the Privacy Policy explains their purpose rather than treating them as account content.

Cookie controls

Cookies can keep a session connected, remember a page preference or support a security check. You can clear or restrict them through your browser, though some account steps may then require another login or verification action.

Retention period

We retain personal and payment-related records only for the purposes and periods needed for account service, security, dispute handling or legal duties. The applicable Privacy Policy wording is the place to check how a particular record is treated.

Change request

You can ask us to correct eligible account details or clarify how a record is used. Send the request through the privacy contact path, identify the relevant account step, and expect an account check before we disclose or change personal data.

Find Answers About Privacy Policy

These search-style answers cover the account and payment questions you may have before opening an account. Each response points back to the Privacy Policy process, including local access wording, device records, wallet references and requests for changes.

The bigwiner Privacy Policy covers account details, phone verification, device and browser records, cookies, payment references and support requests. It also explains why we use each category, how retention works, when disclosure may occur and how you can ask about or change eligible data.

We may handle transaction references and payment status linked to DANA, OVO, GoPay or QRIS when you use those rails. The Privacy Policy concerns these records, not your wallet password. Do not send secret wallet credentials when asking us to check a receipt.

Phone verification connects an account request with the correct account and helps reduce mistaken disclosure. We may retain the verification result and related account detail for the stated service, security or legal purpose. The Privacy Policy explains the relevant use and retention approach.

You can contact us to ask what eligible account data we hold or to request a correction. Describe the account step involved, such as phone verification or a wallet receipt. We may confirm account ownership before responding or changing the record.

Cookies may keep your session active, remember a browser preference or support a security check on mobile and desktop. Clearing them can sign you out or repeat a verification step. Your browser settings control many cookie choices, while our Privacy Policy explains their purposes.

Retention depends on why a record exists. Account service, security events, payment reconciliation, disputes and legal duties can require different periods. The Privacy Policy sets out the relevant approach, and you can ask support to clarify the category connected with your request.

Access and eligibility depends on local law, so the Privacy Policy does not replace local requirements. Before opening an account, check the access wording shown for your location. If a privacy request concerns access, include the account step and location context safely.