Reference

Privacy Policy for Your cicakslot Account

Your account data, device checks, cookie choices, and wallet records for DANA, OVO, GoPay, and QRIS are covered here before you open an account.

DANA data contextOVO wallet recordsCookie choicesQRIS account checks
cicakslot Privacy Policy for Your cicakslot Account
CONTACT ROUTES

How You Reach Us About Privacy

Privacy questions need a clear route, not a copied form with no owner. We handle account-data requests through the same account identity checks used for wallet…

Live Chat Live chat is available daily from 09:00 to 23:00 WIB for privacy questions tied…
Email Request Email us for access, correction, or deletion review when you need a written trail.
Account Message Use the message area after login when your question involves recent device activity or…
DATA PRACTICE

How We Handle Account Privacy

We keep this Privacy Policy practical because your account data moves through several real steps: sign-up, login, wallet use, lobby access, and support contact.

Account Details

We collect details such as username, phone number, password credentials, and contact records to create and protect your account. If you ask to correct a profile detail, we confirm identity before making changes.

Payment Records

DANA, OVO, GoPay, and QRIS references help us match wallet activity to your account. We use these records for reconciliation, dispute checks, and fraud screening, not to display your payment activity publicly.

Cookie Choices

Cookies help remember session status, language preference, and basic device recognition. You can clear cookies through your browser settings, but doing so may require a fresh login and extra account verification.

Device Signals

We read practical signals such as browser type, IP range, and session timing to detect unusual access. If your account suddenly changes device or location pattern, support may add a verification step.

Retention Checks

We keep data only as long as needed for account operation, payment reconciliation, legal requests, dispute handling, and security checks. When records are no longer required, we reduce or remove them where possible.

Change Requests

You can ask us to access, correct, or review deletion of account data through live chat, email, or account message. We verify ownership first so another person cannot change your privacy settings.

Privacy Questions Before You Join

Before you open an account, you may want to know exactly what data is collected, why payment records matter, and how cookies behave on your phone. These answers focus only on the Privacy Policy, not on promo terms or general lobby choices. If your question involves account ownership, wallet history, or device access, contact us through a verified route so we can protect your data while answering.

We collect the details needed to create and protect your account, such as username, phone number, login credentials, device signals, and contact records. We use them for access, account safety, and support handling.

We keep payment references so wallet activity can be matched to the correct account, checked during disputes, and reconciled with transaction logs. These records are handled as account data, not public profile content.

Yes. Send the request through live chat, email, or account message and include the detail you want checked. We verify account ownership before changing phone numbers, profile records, or privacy-related account fields.

Cookies help keep your session active, remember basic preferences, and support device recognition. If you clear cookies in your browser, you may need to log in again and complete an added identity check.

We share only the details needed to process or verify transactions with relevant payment rails, such as DANA, OVO, GoPay, or QRIS. We do not sell your account profile or wallet history.

Contact us through a verified channel and state that you want a deletion review. Some records may need to remain for payment reconciliation, dispute handling, security checks, or legal duties where local law permits.

We may compare device signals, IP range, session timing, and login pattern. If the access looks unusual, support may ask for extra confirmation before discussing account data or changing privacy-related settings.