Reference

chou4d Privacy Policy for Your Account

chou4d Privacy Policy explains how we handle your account details, device signals, wallet records and support messages when you use our services.

Account clarityWallet recordsDevice controlsContact route
chou4d chou4d Privacy Policy for Your Account
CONTACT PATHS

Three Ways To Ask About Privacy

A clear contact path helps when you want to understand a record, correct an account detail or ask why a security check appeared. Start from the account help route and include the email or phone detail used for registration, without sending a password or wallet PIN. If your question relates to a DANA, OVO, GoPay or QRIS receipt, attach only the reference needed to locate the transaction. We use the same privacy process whether you contact us from a phone or computer.

Team online

Account help

Use the account help route for access records, phone verification questions or a request to correct your registered contact detail. We may ask you to confirm the account step involved before discussing personal data, so a different person cannot obtain details about your chou4d profile.

Payment status

For a wallet or transfer record, tell us the method and reference shown on your receipt. Our support team can check whether the entry relates to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity without asking for your wallet password.

Privacy request

Ask for a copy, correction or deletion review through our support contact and describe the exact record involved. We verify the account holder first, then explain what we can change, what must be retained and when you can expect a response.

HANDLING DETAILS

How chou4d Handles Device And Account Data

Privacy is part of the account path rather than a separate screen you never see.

Account records

When you open an account, we use your submitted contact details and phone verification result to create the profile and protect later sign-ins. We keep a record of verification attempts because it helps us investigate access disputes and distinguish your request from an unauthorised change.

Device signals

A phone or browser can send session, language, operating-system and security signals when you sign in. These signals help us flag an unusual session around account access; they do not give us access to your photos, contacts or other unrelated files on the device.

Cookie choices

Essential cookies support sign-in, session continuity and security checks. Preference cookies may remember settings such as language or display choices. You can manage available cookie choices in your browser, although removing essential storage may require you to verify your account again.

Wallet matching

Payment records are matched using method, amount reference and account details supplied during the transaction. For DANA, OVO, GoPay and QRIS, we use the status returned through the payment flow; bank transfer and virtual account checks use the relevant transfer reference.

Retention steps

We keep account, security and transaction records while they serve access, dispute handling, fraud prevention or legal duties. When a record no longer has one of those purposes, our process removes it or separates it from direct account identifiers where that is workable.

Change requests

You can ask us to correct contact details, explain a data use or remove eligible records through support. We confirm your identity before making a change, describe any limit created by retention duties and avoid changing records needed to settle an open payment or access dispute.

Privacy Policy Questions For chou4d

These answers address the privacy questions we expect before an Indonesian account is opened: what we collect, how wallet references are used, how device checks work and how you can request a change. If your case involves a particular receipt or sign-in event, use the support route with the smallest useful set of details. Where local law permits, we will explain the available next step clearly.

It covers account details, phone verification, device and session signals, cookie preferences, support messages, game activity records and payment references. It also explains why we use those records, how retention works, how security checks operate and how you can request access, correction or removal.

Yes. The Privacy Policy covers payment status and transaction references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use the details needed to match a payment to your account and do not request your wallet PIN.

Phone verification links the account to the contact detail you supplied and helps prevent another person from changing access details. We also use verification records when investigating a sign-in dispute. The check does not give us access to unrelated content stored on your phone.

Yes. Contact support with the account detail that needs correction and explain what is wrong. We first confirm that you control the account, then update eligible records or explain why a transaction or security record must remain unchanged for an open dispute or legal duty.

We keep records while they support account access, security investigation, payment matching, dispute handling or a legal requirement. After that purpose ends, we remove the record or separate it from direct identifiers where workable. The exact period can depend on the record and local law.

Essential cookies help maintain your sign-in and security session, while preference cookies can remember display settings. Your browser can restrict optional storage. If essential cookies are removed, you may need to repeat phone verification or another account check before access continues.

Use the account help or privacy contact route and state whether you want access, correction, an explanation or removal of eligible data. Include your registered phone or email and a payment reference only when needed. Never include a password, wallet PIN or full security code.