Reference

Open bigcor78 Privacy Policy Clearly

The bigcor78 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
bigcor78 Open bigcor78 Privacy Policy Clearly
PRIVACY HELP DESK

Switch To A Clear Support Route

A direct support path makes a Privacy Policy request easier to follow when an account or wallet record needs checking. Start from the signed-in account area and include the phone number linked to your profile, the request you want answered and any relevant payment reference. We use those details to locate the correct record without asking you to send a password. If access is unavailable, explain that your request concerns privacy and account data so our team can route it correctly.

Team online

Account data request

Ask us to identify the personal details connected with your bigcor78 account. Include your registered phone number and the account step involved, such as phone verification or a sign-in attempt. We may ask for a matching account check before sending data or changing its record.

Wallet record check

For a DANA, OVO, GoPay or QRIS privacy question, share the payment rail and reference shown in your account. We use that narrow detail to find the related record, check its status and avoid exposing another account's transaction history.

Correction route

If your contact detail or account record is inaccurate, tell us what should change and why. Keep your password and one-time verification code private. We can review the request against the account details already held before applying a correction.

DATA CARE DETAILS

Browse The Safeguards Behind Privacy

Privacy is handled through ordinary account controls rather than a hidden process. We separate sign-in checks from payment references, limit access to staff who need a record for support or security, and…

Account details

We may hold your name or contact details, registered phone number, verification status and account activity because those records support sign-in and privacy requests. We use the smallest practical set for the stated purpose and do not treat a game selection such as Aviator as a reason to collect unrelated details.

Payment references

A wallet action can create a rail, amount, reference and status record. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries help us match a request to your account. We do not need your wallet password or banking login to investigate that reference.

Cookies and devices

Cookies can keep a session connected while you move from a phone login to the lobby, while device signals can help identify unusual access. You can manage cookies in your browser. Clearing them may sign you out and can require phone verification again before account access.

Account security

Phone verification is used before account access where that check is required, and we examine sign-in details when activity appears unusual. We do not ask you to reveal a password or one-time code in a support message. Sign out on shared devices after reading your account data.

Retention timing

We keep personal and wallet records while they are needed for account operation, support follow-up, dispute handling or legal requirements. When a record no longer has a valid purpose, our process removes it or changes it so it no longer directly identifies your account.

Your request

You can ask what personal data we hold, request a correction, seek a copy or ask a question about use and retention. Send the request through the signed-in support route with your registered phone number. Access or fulfilment depends on local law and account verification.

Ask About Privacy Policy Before Access

These Privacy Policy answers cover the account and wallet questions you may have before opening access from Indonesia. We keep the route practical: identify the account, name the record or payment rail, and tell us whether you want access, correction or clarification. Where local law permits, we use that request to explain the next step.

The bigcor78 Privacy Policy covers account details, phone verification, sign-in activity, device and cookie records, support requests and wallet references. It applies when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, and explains why each record may be needed.

We use the registered phone number to connect your account to phone verification, help protect sign-in access and locate a privacy request. It also helps us distinguish your record from another account. Do not send a password or one-time code when asking for support.

Sign in, open the account support route and state that you want a copy of your personal data. Include your registered phone number and the records you mean, such as account details or a QRIS reference. We may verify account ownership before providing a response.

Yes, you can ask us to correct an inaccurate contact detail or account record. Describe the current entry, the correct replacement and the reason for the change. We compare the request with your account checks before editing it, and the available process depends on local law.

Yes. The Privacy Policy covers records linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use a rail and reference to match a wallet request to your account, check its status and answer a related privacy question.

Cookies can keep your signed-in session and selected account path available while you move between a mobile device and the lobby. You can remove or restrict them in your browser. After that change, you may need to sign in again and complete phone verification before access.

Use the signed-in support route and ask specifically about removal or retention of your account, device or wallet records. Tell us which record you mean and provide your registered phone number. We assess the request against operational, dispute and legal needs, where local law permits.