Reference

Privacy Policy for Your cinahoki Account

Your account data, wallet checks, and cookie choices are covered here before you open the lobby from Semarang or any supported Indonesia region.

Account data useDANA wallet contextCookie controlsSupport contact paths
cinahoki Privacy Policy for Your cinahoki Account
CONTACT ROUTES

Ask Us About Your Privacy Request

Privacy questions need a direct route, not a generic inbox. You can contact us when you want to update account details, ask what data we hold…

Live chat Use live chat daily from 09:00 to 23:00 WIB for privacy questions tied to…
WhatsApp help Send a WhatsApp message when you need to confirm a phone number change or…
Email request Email works well for data access, correction, or deletion questions that need written detail.
DATA HANDLING

What We Store and Why

Privacy is part of how we run the account flow, not an afterthought. We separate login records, payment references, cookie preferences, and support messages so each team sees only what it needs.

Account profile

We store your username, phone number, account status, and profile changes so we can identify you when you return. If a detail is wrong, send a correction request from the profile menu.

Payment references

We record payment rail, timestamp, and transaction reference for DANA, OVO, GoPay, and QRIS. These records help us match deposits, check withdrawal requests, and answer wallet questions without exposing full account balances.

Cookie choices

We use cookies for login sessions, language preference, and basic page measurement. On mobile Chrome, you can manage them through Settings > Site settings > Cookies before returning to the lobby.

Device signals

We may read browser type, IP range, and device pattern to spot unusual access. If a new device signs in, we may ask for extra account confirmation before wallet actions continue.

Retention periods

We keep records while your account remains active and for a reasonable period after closure where needed for payment checks, dispute handling, or legal requests. Data no longer needed is removed or anonymised.

Request handling

For access, correction, or deletion questions, we check the account owner first. This protects you from changes requested by another person using only a screenshot or partial payment detail.

Privacy Questions Before You Join

A clear policy should answer what happens before and after you open an account. These answers cover account data, payment traces, cookies, device checks, support records, and how you can contact us about changes.

We collect details needed to create and protect your account, such as username, phone number, login activity, device pattern, and payment references. We do not ask for extra data unless it is needed for verification.

Those payment names help us match your wallet activity to your account. We store rail name, time, status, and reference code so support can trace a deposit or withdrawal question without guessing.

Yes. Send a request through live chat, WhatsApp, email, or Account > Profile > Privacy Request. We confirm account ownership first, then explain what data is held and how it is used.

Cookies keep your session active, remember basic preference settings, and help us understand page errors. You can remove or block cookies in your browser settings, but login and wallet pages may need them.

Only the support and account teams who need the case can view your messages. We use chat history to follow privacy requests, confirm earlier answers, and avoid asking you for the same details again.

Open Account > Profile > Privacy Request or contact support from 09:00 to 23:00 WIB. We may ask for your account ID and recent payment rail before applying the correction.

We remove or anonymise data that is no longer needed, while keeping limited records required for payment checks, dispute handling, or legal obligations. You can ask support what remains after closure.