Reference

find66 Privacy Policy for Your Account

Our Privacy Policy explains how find66 handles the details you provide when you open an account, sign in, use the lobby or check wallet status.

Account dataWallet referencesDevice choicesCookie controls
Browse the lobby Read FAQ
find66 find66 Privacy Policy for Your Account
CONTACT YOUR WAY

Privacy Help Beside Your Account

A clear contact route matters when a Privacy Policy question concerns your login or wallet record. We ask you to contact support from the account connected to the request where possible, because that lets us check identity before discussing personal data. Include the email or phone used for your account, the date of the relevant event and the payment reference if your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We will use the details you send only to locate and resolve the policy request.

Team online

Account message

Send a Privacy Policy request through the account support route and include your registered contact detail. We can then match the request to your login record without asking you to post private data in a public message.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, add the transaction reference and date, not your wallet password or security code. This gives our support team enough context to check status while reducing unnecessary disclosure.

Access concern

If you cannot sign in, explain the device path you used, such as mobile browser or desktop browser, and state that the request concerns privacy. We will first verify account ownership before discussing stored records or changing contact details.

DATA HANDLING

What We Protect And Retain

The Privacy Policy is applied at the points where data enters the service: account creation, phone verification, login, wallet status checks and support contact.

Account creation

When you open an account, we use the contact details and verification result needed to provide access. Clear phone verification helps us connect later privacy requests to the correct account rather than relying on an unverified name.

Payment references

Our records can show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We do not need your wallet password to investigate a receipt, so never include that secret in a request.

Device signals

Login time, browser type and device signals may help us identify an unusual access attempt. On mobile, these checks support the path from sign-in to the lobby; on desktop, they help protect account changes and contact updates.

Cookies

Necessary cookies support sign-in, session continuity and selected settings. Other cookie choices can be managed in your browser where available. Removing necessary cookies may sign you out or prevent the account path from working as expected.

Retention requests

We keep records only for the period needed for their stated purpose, security checks, dispute handling or legal duties. You may ask why a record remains and request deletion or restriction, subject to those duties and local law.

Policy changes

If our data practices change, we will update this Privacy Policy and identify the relevant section. Check the policy before opening an account or changing wallet details, and contact support if the wording is unclear.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the questions we expect you to ask before opening or using a find66 account. They cover the data connected to sign-in, phone verification, wallet status, cookies, retention and requests for correction or deletion. If your situation is different, use the account support route and give us the smallest amount of detail needed to locate the matter. Access depends on local law, and we may request an account check before sharing personal records.

The find66 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask questions or request a change.

We may collect the contact details used for your account, verification results, login events, browser or device details, cookie choices and support history. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may receive a reference and status rather than your private wallet credentials.

Phone verification helps us confirm that an account request belongs to you before account access or a personal-data change. It also helps support match a Privacy Policy request to the right record. We do not ask you to place a verification code or password inside a support message.

Yes. The Privacy Policy explains that necessary cookies can maintain sign-in, session continuity and settings, while browser controls may manage other choices. If you remove necessary cookies, you may need to sign in again or may not be able to complete the account path until they are enabled.

Contact us through the account support route and state that you are making a Privacy Policy data request. Include your registered email or phone and a short description of the records you need. We may verify account ownership before responding, which protects your data from an unrelated requester.

You can ask us to correct inaccurate account details or delete eligible records through support. We will assess the request against security, dispute and legal requirements. Some payment references or verification records may need to remain for a defined purpose, even when other details can be removed.

Yes. Account access and how we handle certain requests depends on local law. Where local law permits, we apply the rights and processes described here. If a rule prevents deletion, access or another change, we will explain the reason and identify the available support path.

Related Pages

find66 Indonesia Bundesliga Over Under Plinko Quick Arena FAQ About Us