Reference

Open task666 Privacy Policy With Clarity

task666 Privacy Policy sets out what we collect when you open an account, sign in from a mobile device, use DANA or QRIS, and move through the casino…

Account recordsWallet activityCookie choicesAccess controls
Explore Our Lobby Read FAQ
task666 Open task666 Privacy Policy With Clarity
CONTACT PATHS

Ask About Privacy Through Account Help

A direct contact path matters when a privacy question affects your account or wallet status. We ask you to start from the signed-in account help route so we can connect your request with the correct account record without asking you to send sensitive details through an open message. If your question concerns a DANA receipt, QRIS reference, phone verification, or a device sign-in, include only the reference needed to locate it. We use the same privacy checks when responding, and we may ask for account confirmation before changing personal data.

Team online

Account help

Use the signed-in account help path for a privacy request. We can link your question to the correct account without making you repeat wallet details from DANA, OVO, GoPay, or QRIS.

Wallet status

For a payment-data question, share the transaction reference and rail name only. Our team can check a QRIS, bank transfer, or virtual account record while limiting unnecessary personal details.

Access check

If a new phone or browser causes an account question, tell us the device path and sign-in time. We use account confirmation before discussing stored details or making a change.

DATA HANDLING

Explore Six Privacy Controls In Practice

Privacy work is part of the account flow, not a separate promise hidden from you. We separate identity details, device signals, cookie choices, and wallet references so each is used for a…

Account details

We use your submitted account details to create and maintain access, confirm a phone step, and respond to account requests. We do not need extra personal details merely because you browse the Privacy Policy.

Device signals

When you sign in from a mobile phone or desktop browser, we may record device and session signals. These help us identify unusual access around the account without treating every device change as misuse.

Cookie settings

Cookies help remember a session and your page choices. You can manage browser cookie controls, although removing necessary cookies may require you to sign in again before viewing account-linked pages.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity is matched using transaction references and status data. We use those records to reconcile your account, not to collect unrelated wallet content.

Retention period

We retain personal and transaction records for account operation, security checks, dispute handling, and legal duties. When a record is no longer needed for those purposes, our handling process moves it toward removal or anonymisation.

Change requests

You can ask us to correct account details or explain how a record is used through account help. We may verify ownership first, then confirm the action, its limits, and any reason a record must remain.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers cover the questions we expect you to ask before opening an account from Indonesia. Each response stays close to the actual account, device, cookie, and payment records involved, so you can decide what to share and how to contact us. If your situation is not listed, use the signed-in account help route and include a short description rather than sending full identity or wallet details.

It covers account details, phone verification, device and session signals, cookies, wallet transaction references, retention, and requests to correct or remove data. It applies when you create an account, sign in, use account-linked pages, or contact us about a privacy matter.

We record a payment reference, status, time, and related account link so a DANA or QRIS event can be reconciled correctly. The same approach applies to OVO, GoPay, bank transfer, and virtual account records without collecting unrelated wallet content.

Yes. Phone verification helps us confirm that an account access request is connected to the correct account. We store the verification result and related account record for access control, security checks, and support handling rather than asking for repeated details without a reason.

Start from the signed-in account help path and state which detail needs correction. We may confirm account ownership before acting. If a record must remain for security, dispute handling, or legal duties, we will explain that limit instead of removing it.

Cookies may remember your session and page choices, including whether a policy page has been viewed. Browser controls let you manage them, but disabling necessary cookies can sign you out or prevent account-linked pages from working until you sign in again.

We keep records for the period needed for account operation, security, transaction matching, dispute handling, or legal duties. Once a record is no longer needed for those purposes, our process moves it toward deletion or anonymisation, subject to applicable limits.

Yes, access and eligibility depends on local law. The Privacy Policy describes our data handling, but it does not change legal requirements in Indonesia or another location. Where local law permits, you can contact us through account help about your data choices.

Related Pages

task666 Indonesia Access guide About Us Serie A Match Bet Account information