Reference

Privacy Policy For Your cincinbet Account

cincinbet Privacy Policy explains what we collect when you open an account, sign in, verify your phone and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity requests
cincinbet Privacy Policy For Your cincinbet Account
CONTACT YOUR WAY

Ask About Your Privacy Policy Rights

A clear contact route helps you act on the Privacy Policy instead of searching through account screens.

Account privacy requests Send a message through the account support channel when you want a copy of your stored profile details, a correction to your phone record or an explanation of why verification information appears on your account. We check ownership before discussing account-specific data.
Wallet record questions Use the cashier support path for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference that you do not recognise. We compare the payment reference with your account record and explain the status without asking for your wallet password.
Security contact If your sign-in, device session or phone access looks unusual, contact us through the support channel shown on the site. We can review recent account events, guide a password change and place a temporary check on account actions while we confirm ownership.
HANDLING YOUR DATA

What Our Privacy Policy Does With Information

Privacy Policy choices should be understandable before you open an account or connect a wallet. We separate information used for sign-in, payment matching, security checks and service messages, so each request has…

Account creation

When you open an account, we collect the contact details needed to create your profile and send account messages. Phone verification confirms that you control the number connected to access. We use this step for account protection, not to request your DANA, OVO or GoPay password.

Payment matching

A wallet or bank payment creates a reference that helps us match the amount and status to your account. DANA, OVO, GoPay and QRIS may show different reference formats, while BCA, BRI, Mandiri and BNI transfers can carry a bank-side reference for checking.

Cookies and devices

Cookies can keep your selected session and policy settings available when you move between the login page and the lobby. Device and browser signals help us spot repeated failed access or an unfamiliar session. You can manage cookies through your browser, though some account functions may then need another check.

Account security

We use phone verification, sign-in event checks and ownership questions before discussing private account details. If your device changes or a session appears unusual, we may ask you to confirm the account step again. Do not share passwords, wallet PINs or one-time codes with a contact agent.

Retention period

We keep profile, payment and security records for as long as they serve account operation, dispute handling, fraud checks or legal duties. When a record no longer has a stated purpose, we delete it or remove identifying links where practical. A request can ask us to explain the category and reason for retention.

Changes and queries

You can ask us to correct inaccurate data, explain a processing purpose, provide available account information or clarify a cookie choice. We may request proof that you control the account before making a change. The Privacy Policy page remains the place to check the current wording and contact route.

Privacy Policy Answers For cincinbet

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the wording tied to practical actions: phone verification, cookie controls, payment references, device sessions and requests for copies or corrections. If your question concerns a specific record, use the support path and avoid sending secret wallet or login credentials.

It covers information used for account creation, phone verification, sign-in security, payment matching, cookies, support requests and service records. It also explains retention and your available requests. The policy applies to your use of the site where local law permits and does not ask for wallet passwords.

Yes. We may receive a payment status, reference and account-matching detail when you use DANA, OVO, GoPay or QRIS. We use those records to identify a transaction and answer a status question. We do not need your wallet PIN or password to check the payment reference.

Phone verification helps confirm that you control the number used for account access and gives us a safer way to investigate a sign-in concern. We may ask you to repeat the account step after a device change or unusual session before discussing private information.

You can contact support to ask what account, payment or security data we hold about you, subject to identity checks and local requirements. Include enough detail for us to locate the account, but do not send a password, wallet PIN or one-time code with your request.

Send a correction request through the account support channel and identify the field that is inaccurate, such as a contact detail. We may verify account ownership before changing it. Payment references cannot simply be rewritten, but we can investigate a mismatch and explain the record.

We retain payment references while they are needed for account operation, transaction questions, security checks, disputes or legal duties. After that purpose ends, we remove the record or reduce its identifying detail where practical. Support can explain the category and reason for a stored record.

Yes. Your mobile browser settings let you clear or restrict cookies used for session preferences. Blocking them may mean that login, policy choices or account checks need to be repeated. The Privacy Policy page remains available, and access depends on local law and device settings.