Reference

cinacipit Privacy Policy For Your Account

Account data, phone verification, wallet status and cookie choices are set out plainly in the cinacipit Privacy Policy, so you can decide what happens before opening the casino…

Account dataWallet recordsCookie choicesPhone verification
cinacipit cinacipit Privacy Policy For Your Account
CONTACT ROUTES

Account Help For Data Requests

A clear contact path matters when a Privacy Policy question involves your account or a wallet receipt. We ask you to contact support from the signed-in account path where possible, because that lets us match the request to your phone verification and reduce mistaken disclosures. Include the relevant date, payment rail and reference when a DANA, OVO, GoPay or QRIS record needs checking.

Team online

Account data

Use the account help route to ask what personal data is linked to your cinacipit profile. We may request a verification step before discussing records or applying a correction.

Wallet receipt

For a wallet-status question, send the payment rail, reference and date through account support. We use those details to locate the transaction record without asking for your wallet password.

Privacy request

Ask for access, correction or deletion through the same support path. We will explain any identity check, required wording or local-law reason that affects how the request can be handled.

CONTROL LAYER

Six Controls Around Your Data

We keep this policy practical by connecting each data choice to an account action. The controls below cover what enters our records, how cookies and device behavior support a session, who can…

Collection

We collect details needed for account creation, phone verification, sign-in protection and payment matching. Data connected with Live Roulette, bahasaselot or another lobby title is handled as account activity rather than used as a separate identity.

Cookies

Cookies and similar device signals can keep your session open, remember a selected path and help detect unusual sign-in behavior. Your browser controls can clear or restrict them, although some account functions may then need to be repeated.

Security

Phone verification and sign-in checks help protect account access. We limit internal access to records according to work needs, and we may pause a request when the details supplied do not match the account.

Retention

We retain account, security and payment records only for the period needed for the stated service, dispute handling, fraud checks or legal duties. A deletion request may not remove records that must be kept for those reasons.

Sharing

A payment reference can be shared with the relevant rail or technical service when needed to confirm status. We do not turn that request into permission to seek your DANA, OVO, GoPay or QRIS password.

Changes

You can ask us to correct account details, explain a processing purpose or change available communication choices. Send the request through account support, and we will confirm the next step after checking that you control the account.

Privacy Policy Questions For cinacipit

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account records, device behavior, local wallet references, deletion requests and access conditions. If your situation does not fit one answer, use the signed-in support route with the relevant account or payment details.

It covers account and phone-verification details, device and cookie signals, lobby activity, support messages, and payment references. It also explains why we use each category, when a service partner may receive necessary details, how retention works, and how you can request access or correction.

Our Privacy Policy does not ask for your DANA, OVO, GoPay or QRIS wallet password. We may keep a transaction reference, amount, status and timing so a receipt can be matched to your account or a payment question can be checked.

Phone verification helps connect the account to the person requesting access and reduces mistaken disclosure of account or wallet records. We may ask for that check before discussing a data request, changing account details or taking action on a security concern.

Yes, you can ask for access to the personal data linked to your account through account support. Include the account detail needed to locate your record. We may verify control of the account first, then explain the format, scope and timing of the response.

Send a correction request through the signed-in support path and identify the field that is wrong. We may compare the request with phone verification or an account record before making a change, especially when the detail is connected to a DANA, OVO or bank transfer reference.

You can request deletion through account support. We will explain what can be removed and what may need to remain for security, payment disputes, fraud checks or legal duties. Access and eligibility depend on local law, so the result can vary by request.

Cookies and device signals can support session continuity, sign-in checks and the return from login to the lobby on mobile. You can restrict them in your browser, but some Privacy Policy-related account actions may require another sign-in or verification step.