Reference

cod4d Privacy Policy for Your Account

Your account data, wallet records and device details stay tied to clear purposes.

Account clarityWallet recordsCookie choicesRequest access
cod4d cod4d Privacy Policy for Your Account
PRIVACY HELP DESK

Reach Support About Privacy Requests

A clear account-help route keeps privacy questions separate from ordinary lobby requests.

Access requests Ask through the account help route for the personal data connected with your cod4d…
Correction requests If your phone number, verification detail or account setting is wrong, tell us which…
Wallet records For a DANA, OVO, GoPay or QRIS record, share its reference and date through…
ACCOUNT DATA CARE

Explore How We Handle Your Data

Privacy controls work best when each account step has a defined reason. We separate login protection, payment matching, cookie operation and request handling so you can ask a…

Data handling

We use phone details, verification status, sign-in events and account settings to maintain access and protect the account.

Cookie choices

Cookies can keep a session active and remember browser choices on mobile or desktop.

Account security

We check sign-in signals and account ownership before discussing private records.

Record retention

We retain account, security and payment references for the period needed to operate the account, resolve disputes, meet record duties…

Request changes

You can ask us to access, correct or remove eligible personal data through support.

Policy contact

Privacy questions belong in the account help route, including questions about cookies, device records or wallet references.

Browse cod4d Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet is connected. They explain the data path, the request path and the checks we use when a privacy question involves a phone, device or payment reference.

It covers account details, phone verification, sign-in events, device signals, cookies, payment references and privacy requests connected with your account and access where local law permits.

We keep transaction references, status details and receipts to match activity with the right account, resolve wallet questions and maintain necessary records. We do not need your wallet password.

Yes. Send an access request through the account help route using the phone number linked to your account. We verify ownership before discussing or releasing private account records.

Tell support which phone, verification or account-setting detail is incorrect. Include a precise correction request and complete the account check so we can update the eligible record.

Yes. Cookies may retain a session or browser choice on your phone. You can change browser controls, but removing required cookies may sign you out and require another login.

We limit account-data handling to defined service and security purposes, check sign-in signals, and verify ownership before private discussions. Keep passwords and one-time codes out of support messages.

You can request removal through support, and we assess which records are eligible. Some security, payment or dispute records may need retention for a defined operational or legal reason.