Reference

Privacy Policy for kaktus55 Accounts

Our kaktus55 Privacy Policy explains what account, device and wallet details we use when you open Auto Roulette Live, Omaha Online Room or other lobby areas.

Account dataCookie choicesWallet recordsContact route
kaktus55 Privacy Policy for kaktus55 Accounts
CONTACT ROUTES

Ask About Your Account Data

A clear contact path helps when your privacy request and wallet status meet in the same account.

Account privacy request Tell us whether you need a copy of account data, a correction, or deletion.
Wallet record question If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the transaction reference…
Policy contact path For a question about cookies, retention or a third-party service, use the contact route…
DATA PRACTICE

Phone Verification and Cookie Choices

We keep this policy practical by tying each privacy request to a real account step.

Data we receive

We may receive your phone number, account identifiers, sign-in events, browser details and payment status.

Cookie controls

Cookies and similar browser storage can keep a session active, remember selected settings and help detect unusual sign-in behaviour.

Account protection

Phone verification is checked before account access and may be repeated when a security event needs confirmation.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we retain transaction references, selected rail and status details…

Retention timing

We keep records only as long as needed for account service, security checks, dispute handling or legal duties.

Changes and access

You can ask what eligible data we hold, request a correction, or ask whether deletion is available.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account steps you are most likely to check before using kaktus55 from Indonesia. We explain the data connected to sign-in, browser access and local wallet status, while keeping eligibility wording clear: access depends on local law. If your question is not listed, use the policy contact route rather than sending sensitive credentials.

It covers account details, phone verification, browser and cookie records, game-category activity linked to your account, payment status and support requests. It also explains retention, security, access requests, corrections and deletion options for eligible records.

Phone verification helps us confirm that the person requesting account access or a data change is connected to the account. We may repeat that check for a security event, but support will not ask for your password, wallet PIN or one-time code.

Yes. The Privacy Policy covers transaction references, selected payment rail and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity connected to your account. It does not require you to send a wallet PIN.

You can contact us through the route published on the Privacy Policy page and ask for access or correction of eligible account data. Include your account phone number and request type, then complete phone verification if we need to confirm your identity.

On a mobile browser, cookies can keep your session active, preserve selected settings and help identify unusual sign-in behaviour. You can change browser permissions, but blocking necessary cookies may interrupt phone verification or account access.

We retain account, security and payment-status records for the period needed to provide account service, handle disputes, detect misuse or meet legal duties. After that need ends, we delete, anonymise or separate eligible records where practical.

You may ask whether deletion is available for particular records through the policy contact route. Some data may need to remain for security, transaction reconciliation or legal duties. Access and eligibility depends on local law and the applicable request.