Reference

Privacy Policy for Your Indonesia Account

Our Privacy Policy explains what we collect when you open a ch3cooh account, check wallet status, or move from login into the lobby.

Clear data purposesWallet activity contextMobile and desktop accessAccount contact route
ch3cooh Privacy Policy for Your Indonesia Account
CONTACT THE POLICY TEAM

Ask About Your Stored Account Data

A direct question is easier to resolve when it includes the account step involved. We can use your account identifier, payment reference or device path to locate the relevant record without asking you to repeat the whole issue. If you are checking a wallet entry from Denpasar or a login event on mobile, describe the date, rail and screen shown. Our support route is intended for policy questions, correction requests and access concerns connected with your own account.

Team online

Policy questions

Send a question through the account support route when you need a plain explanation of collection, cookies, retention or access. Include the email or phone detail linked to your account so we can connect the request to the right record.

Wallet records

For a DANA, OVO, GoPay or QRIS entry, share the payment reference and status shown beside the cashier step. We use that detail to separate a payment query from a wider request about your stored account data.

Correction requests

If your contact detail or account record appears incorrect, tell us which field needs attention and why. We may ask for an account check before changing it, helping us avoid editing the wrong profile.

HOW DATA IS HANDLED

Security, Cookies and Retention Steps

We treat policy handling as an account process, not a vague promise. Login activity helps us identify the device path used to reach the lobby, while payment references help us reconcile DANA…

Account security

Your login details should remain private, and we may compare account signals when a recovery or data request is made. This check helps protect the profile connected to your phone or email from an unrelated change.

Payment references

We keep the reference needed to trace a wallet or bank status, not a free-form copy of every screen you viewed. DANA, OVO, GoPay and QRIS entries are handled as account-linked payment records.

Cookie choices

Cookies can keep a signed-in session available and remember a page setting on your device. You can adjust browser controls, although limiting cookies may require another login before the lobby or support path opens.

Device signals

A device type, browser path or login time can help us investigate an access concern. These signals are assessed alongside your account details when a request involves an unfamiliar mobile or desktop session.

Retention review

We keep records for the period needed to operate the account, reconcile payments and address a policy request. After that need ends, deletion or restricted storage is considered subject to applicable legal and account duties.

Request changes

You can ask for access, correction, restriction or deletion of eligible account data through our support route. We may request enough detail to confirm ownership before providing, changing or removing a record.

Privacy Policy Answers for ch3cooh

These answers focus on the account and payment questions you may have before using ch3cooh in Indonesia. They explain the practical route for checking data, cookies, wallet references and account access without turning the Privacy Policy into a general lobby description.

It explains the account, device, cookie, payment-reference and support data we may handle when you use ch3cooh. It also describes why we use those details, how we protect access, how retention works and how you can request a change.

A payment reference lets us connect a wallet action with the correct account and check its status. We may need it to reconcile a DANA, OVO, GoPay or QRIS entry, answer your support question and avoid changing an unrelated record.

You can ask for access to eligible account data through the account support route. State the email or phone detail connected to your profile and describe the records requested. We may verify ownership first so the response does not expose another account.

Send the correction request through support and identify the field that is inaccurate, such as a contact detail or payment reference. We may ask for an account check, then assess the request against the account and payment records we hold.

Yes. The Privacy Policy covers cookies and device signals used to keep a session active, remember selected settings and investigate an unfamiliar login. Browser controls can limit cookies, but you may need to log in again on that device.

We retain data for the time needed to operate the account, reconcile payment activity and handle a related request, subject to applicable duties. When that need ends, we consider removal or restricted storage rather than keeping the record without a purpose.

The policy can be read as the account rules for data handling, while account access and eligibility depends on local law. If you have a region question, contact support with your account path and location context so we can address the relevant clause.