Reference

Privacy Policy For Your koko33 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your koko33 account, from phone verification to wallet status.

Account dataCookie choicesWallet recordsAccess requests
koko33 Privacy Policy For Your koko33 Account
CONTACT OUR TEAM

Privacy Help Beside Account Support

A clear contact path helps you resolve a Privacy Policy question without sending unnecessary details. Use the support route connected with your account when you need a copy of stored data, want to correct a phone number or need help understanding a wallet receipt. Tell us the subject of your request and the account identifier we can safely use to find it. We may ask for an account step, such as phone verification, before discussing private records. Please do not send a wallet password or full payment credentials.

Team online

Data access request

Ask us to locate the personal data linked with your koko33 account. Include your account contact and the relevant date or payment reference, such as a QRIS receipt, so we can narrow the request before replying.

Correction support

If your phone detail or account record is inaccurate, contact support with the detail that needs changing. We check the account step required to prevent another person from altering your profile or wallet history.

Wallet privacy query

For DANA, OVO or GoPay status questions, send the transaction reference rather than a password. Our team can compare the reference with the account record and explain what data was used for the status check.

DATA HANDLING

What We Protect And Retain

Privacy controls work best when you know what happens at each account step. We separate sign-in checks from payment references, limit internal access to people who need a record for support or…

Account details

We use your account contact, phone verification result and sign-in record to provide access and respond to account requests. The exact details held can depend on what you submit and which account step you complete.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match a cashier event with your account. We use references and status details for checking, not your wallet password.

Cookies

Cookies can preserve a signed-in session, remember a setting and help us identify page errors. Browser controls let you remove or restrict them, although some account pages may not work as expected afterward.

Device security

We may record browser, device and connection signals around sign-in to spot unusual activity. These signals help protect your account and are assessed alongside phone verification before private account details are discussed.

Retention period

We keep account, support and payment records only for the period needed for access, security, dispute handling or legal duties where local law permits. After that, we delete them or remove links to your account.

Change request

You can ask us to correct, provide or remove eligible personal data through account support. We may need your verified account contact and a clear request, then explain any record that must remain for a stated purpose.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the account actions you are most likely to ask about before opening or using koko33. We keep the path practical: identify the record, confirm account control and send only the details needed for a response. Payment names such as QRIS and DANA are used here because their references can appear in account support requests.

The koko33 Privacy Policy covers account details, phone verification, device signals, cookies, support records and payment references. It explains why we use those details for access, security, wallet status checks and account requests, including records connected with DANA, OVO, GoPay, QRIS and bank transfer.

We may hold details you submit for an account, your phone verification result, sign-in and device signals, support messages, and payment references. The record depends on your account activity. We do not ask you to send a wallet password when checking a DANA or QRIS receipt.

Our cookies can keep a mobile session active, remember a setting and help identify page errors. Your browser controls can restrict or remove them. If a cookie is required for an account page, removing it may mean you need to complete the sign-in step again.

Yes. Contact account support and ask for a data access request. Include your account contact and, if relevant, a date or payment reference so we can locate the correct record. We may confirm phone verification before providing private account data.

You can ask us to correct inaccurate account data or remove eligible details through support. We confirm that you control the account before making a change. Some security, dispute or payment records may need to remain where local law permits.

We use payment references and status details to match a cashier event with your account, rather than requesting your wallet password. Sign-in and device signals help us identify unusual access. For bank transfer, virtual account or QRIS questions, send the reference only.

Yes, the Privacy Policy applies to account and support activity from supported Indonesia regions. Eligibility and access depends on local law. If you contact us from Bandung or another location, we still use the same account confirmation step before discussing private records.