Reference

cat4d Privacy Policy Explained Clearly

The cat4d Privacy Policy explains what we collect when you open an account, connect DANA or QRIS, and move from phone login to the lobby.

Account dataWallet recordsCookie choicesPolicy requests
cat4d cat4d Privacy Policy Explained Clearly
CONTACT YOUR WAY

Get Privacy Policy Help From Account

A clear contact route helps you act on the Privacy Policy without sending sensitive details into a public message. Start from your signed-in account support path and tell us whether your request concerns access, correction, deletion, cookies or a wallet record. Include the phone number linked to your account only through that private route. If a DANA receipt, QRIS reference or login event needs checking, we use the relevant account record to locate the request and ask for only the details needed to respond.

Team online

Account request

Use the support path inside your account for a Privacy Policy question. We can match your request to the phone verification step, login record or device session without asking you to post account details in an open channel.

Wallet record

For DANA, OVO, GoPay or QRIS questions, send the transaction reference through account support. We compare the reference with the wallet status and account record, then explain which data was used to check the payment.

Access concern

If your policy request follows a blocked login or a device change, tell us the account step where access stopped. We check the relevant security event and respond according to local requirements and permitted access.

DATA CONTROL

How cat4d Handles Privacy Requests

We handle Privacy Policy requests through the same account controls used to protect your login. Phone verification helps us distinguish an account holder from an unverified requester, while device and session signals…

Account data

We use your account details to create access, confirm the phone verification step and answer support requests. The account path may connect your identity with wallet status, but we use that link for account operation and record matching.

Device signals

A phone or desktop session can provide device and login signals that help us detect unusual access. These signals support account security; they are not a request for unrelated device content, and you can ask us what was recorded.

Cookies

Our cookies can keep essential account settings and help the mobile path return you to the correct lobby step. We can explain cookie categories and their purpose when you contact support about a browser or device record.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be matched with your account to check a receipt or wallet status. We use the reference for reconciliation and support, rather than requesting a wallet password.

Retention timing

We keep account, security and transaction records only for operational, security or legal needs that apply to the service. Ask through your account support path for the retention reason connected with a particular record.

Your request

You can ask for access, correction, deletion, restriction or a consent change where local law permits. We may verify the request through your account phone step before changing data, so another person cannot alter your records.

Privacy Policy Answers For cat4d

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. Each answer stays focused on data handling, account control and the route for requesting help.

It covers account details, phone verification, login and device signals, cookies, support messages and wallet references. It also explains retention and your available requests. Access depends on local law, so the policy applies to permitted Indonesia access rather than every location.

Yes. When you use DANA, OVO, GoPay or QRIS, we may store a transaction reference and wallet status needed to match a receipt with your account. We do not ask for your wallet password through support, and you can ask how a record was used.

We use the phone verification step, login events and device signals to help identify unusual access. Support may ask you to confirm account ownership before changing data. Keep your account details private, and contact us through the signed-in support path if access looks unfamiliar.

Yes, where local law permits. Send a correction request through account support and identify the record that appears wrong. We may verify your phone step before making a change, then use the account record and request details to process the correction.

You can ask about deletion or restriction through the account support path where local law permits. Some account, security or transaction records may need to remain for operational or legal reasons. We will explain the reason connected with the requested record.

We retain records for the operational, security or legal need that applies to them, rather than keeping every record without purpose. Ask support about a specific login, DANA receipt, QRIS reference or account detail to receive the relevant retention explanation.

Open the support path inside your account and select the issue that matches your request, such as access, correction, cookies, deletion or wallet data. Describe the account step involved and include a transaction reference only when it is relevant to the request.