Reference

Privacy Policy for chakibet accounts

Our Privacy Policy explains how chakibet handles the details connected to your account, device, wallet status and support requests.

Account dataCookie choicesWallet recordsRequest support

Explore Our Lobby Read FAQ

How our Privacy Policy applies in Indonesia

chakibet Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers data you provide when you create an account, confirm your phone number, sign in, contact support or request a change to your details. We also receive limited technical data from the browser or mobile device used to reach the account, such as

1
device type, session identifiers, security events and approximate network location. Payment records can show the selected rail, reference number, amount, status and time when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to match account activity, investigate a
2
stalled status and meet applicable account and legal duties. Cookies help keep a session open and remember selected settings; you can manage them through your browser. Access or eligibility depends on local law, and this policy does not change that requirement. You can read the current
3
wording from the account Help path before submitting personal details.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP PATH

Where to send a privacy request

A clear account route helps when you need a copy, correction or explanation about personal data. Sign in, open the account menu, select Help and choose the privacy contact option. Include the email or phone number linked to your account, the request you are making and any relevant payment reference. We use those details to locate the correct record without asking you to send a password.

Team online

Account Help

Use the Help path after sign-in for a privacy request about your account details, phone verification, login record or a correction to your stored contact data.

Payment Status

For DANA, OVO, GoPay, QRIS or bank transfer records, include the transaction reference and status shown beside the cashier entry so we can check the matching account event.

Device Access

If a browser or phone keeps an old session, tell us the device type and approximate sign-in time. We can help identify the session without requesting your password.

DATA PRACTICE

Data choices across your account journey

We handle policy requests by checking the account details needed to identify you and the record you mean.

Account creation

When you open an account, we use the submitted contact details and phone verification status to create access records.

Wallet references

A DANA, OVO, GoPay or QRIS entry may be linked to an account reference, status and time.

Cookie controls

Cookies can keep your sign-in session and selected settings available.

Device security

We record security events such as sign-in time, device type and session activity to help identify unusual account access.

Retention timing

We retain data only for the period needed for account operation, a support case, payment reconciliation or applicable legal records…

Changes and requests

To request correction, a copy or deletion where allowed, use Account Help and describe the record.

Privacy Policy questions from Indonesia

These Privacy Policy answers address the account details people usually check before opening access. We explain what may be collected, how wallet and device records are used, where a request goes and what local eligibility wording means. For a case-specific response, use the signed-in Help path and provide the account contact detail needed to find your record.

It covers account details, phone verification, sign-in and device events, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect the correct person to an account request and reduces mistaken changes. We store its status with the account record rather than asking you to place it in a support message.

Yes. It covers cookies and similar session tools used in a mobile browser or desktop browser. You can clear or block them through browser settings, though sign-in and preferences may need to load again.

We use the payment rail, reference, status and time to match an account event and resolve a support case. The Privacy Policy does not ask you to send wallet passwords or private wallet credentials.

Yes, where local law permits. Sign in, open Account Help and describe the field that needs correction. We may confirm your account contact detail before changing the stored record.

We keep records for the period needed for account access, payment reconciliation, an open support matter or applicable legal duties. After that, we remove or restrict data when continued storage is not needed.

Use the signed-in account menu, choose Help and select the privacy contact option. Include your linked email or phone number, request type and any payment reference, but never include your password.

Privacy Policy for chakibet accounts

Where to send a privacy request

Account Help

Payment Status

Device Access

Data choices across your account journey

Account creation

Wallet references

Cookie controls

Device security

Retention timing

Changes and requests

Privacy Policy questions from Indonesia

01 What does the chakibet Privacy Policy cover?

02 Why does chakibet collect phone verification data?

03 Does the Privacy Policy cover cookies on mobile?

04 How are DANA and QRIS records handled?

05 Can I ask chakibet to correct my account data?

06 How long does chakibet keep personal data?

07 Where can I ask about a Privacy Policy request?

Related Pages