Reference

Open cie168 Privacy Policy With Clarity

cie168 Privacy Policy explains how we collect, use and protect the data connected with your account, from phone verification through wallet status checks.

Clear data purposesWallet record controlsPhone verificationPolicy request path
cie168 Open cie168 Privacy Policy With Clarity
REQUEST SUPPORT

Ask About Privacy Beside Your Account

A clear support route helps when you want to ask what data we hold, correct an account detail or question a wallet record.

Account data request Use the account support path to ask which profile details, phone verification records and sign-in events are connected with your account. We may ask you to confirm ownership before discussing them, so a private request is matched to the correct cie168 record.
Wallet record question For a DANA, OVO, GoPay or QRIS query, send the payment reference rather than your wallet password. We compare the reference with the account ledger, explain the status we hold and limit the response to the data needed for that request.
Correction request If your phone number or account detail is wrong, tell us the field that needs changing through support beside the cashier path. We verify the request, update the relevant record where permitted and keep a trace of the change for account security.
DATA CONTROLS

Check How cie168 Handles Privacy

Privacy controls work across the same account path you use on mobile or desktop. We separate sign-in checks from wallet matching, restrict staff access by operational need and review unusual device activity…

Account security

Phone verification is used before account access and selected account changes. We do not ask you to disclose a password through support. Device and browser signals help us identify a session that differs from your usual sign-in path.

Cookie choices

Session cookies keep your signed-in path working between the lobby and account area, while preference cookies remember settings. Removing them may close the session or require phone verification again; the policy explains why each cookie category is used.

Payment matching

A payment reference lets us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with the right account. We use the reference for status checks and do not need your wallet password to investigate a receipt.

Device behaviour

Your mobile browser and desktop browser can produce different session signals. We use those signals for sign-in protection, not to read unrelated files on your device. A new browser may trigger an ownership check before account details appear.

Retention timing

We keep account, payment and support records only for account operation, dispute handling, security checks or legal duties. When a purpose ends and no duty requires storage, we delete the record or remove identifying links.

Your privacy request

You can contact the account support path to ask for a copy, correction or deletion of eligible data. Include your registered phone number and request type; we verify ownership first and explain any lawful reason a record must remain.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the questions you may have before opening a cie168 account in Indonesia. We explain the data linked to phone verification, the way payment references are used, what cookies do on mobile and desktop, and how to send a correction or deletion request. If your situation involves a local eligibility question, account access depends on local law. For a record-specific answer, use the support path beside the cashier area.

The cie168 Privacy Policy covers account details, phone verification, sign-in events, device and browser signals, cookies, support messages and payment references. It explains why we use each category, when we share it, how long we retain it and how you can request access or correction.

When you open an account, we may collect your registered phone number, account details, verification events, device or browser signals and sign-in records. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may also receive the transaction reference.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match a receipt, check wallet status and resolve an account request without requesting your wallet password.

You can request a correction through the account support path beside the cashier area. State the field that is inaccurate and provide your registered phone number. We verify account ownership before changing it, then explain the action taken or any lawful reason the old record remains.

Cookies keep a mobile or desktop session working, remember selected settings and support form security. Clearing them can sign you out or trigger phone verification again. The Privacy Policy describes these uses; cookies do not give us access to unrelated files on your device.

We retain personal data for as long as it is needed to operate your account, match a payment, handle a dispute, protect sign-in activity or meet legal duties. After the purpose ends, we delete the record or remove identifying links where permitted.

Send a deletion request through the account support route and include your registered phone number plus the data category you want removed. We verify ownership, assess account and legal requirements, then delete eligible data or explain why a limited record must be retained.