cd4 App Privacy policy: Data Protection and Cookies
On this page, what information the cd4 App stores, why it stores it, and how limitedly it is used is clearly stated for users in Dhaka and Bangladesh; information related to bKash, Nagad, and Rocket has also been examined separately
Download cd4 APK cd4 Login Guide
Effective date and short identity
Effective: August 2026 cd4 App's privacy policy mainly covers transaction data, log data, and session security
When a user opens an account, the system only views necessary information, keeping security, and unnecessary data does not accumulate
- Only information required to operate is kept
- Dhaka users' sessions are kept fast
- Information for bKash, Nagad, and Rocket goes via separate paths
For more details cd4 Terms And Help Page View
Card data tokenization in the cd4 App
Card numbers are not stored directly
If anyone validates with a card, the real number is replaced with a token, so the support team, developers, or log files do not see the full number
This provides 1 level of extra security; when the same card is used again, the system matches the token
- Real card data is kept separate
- Only verification with the token takes
- Refunds or testing have limited access
Anyone cd4 Download Downloading a new APK from the page keeps this security layer the same
PCI scope and system limits
Limited access, low risk
cd4 App keeps the payment section in a separate service, so more sensitive data does not circulate within the main app
This separate structure supports audits and reporting, and in a system in operation since 2015, this method increases user control
- App and payment layers are separate
- No unnecessary data is logged
- Regularly reviewed
If new users want cd4 Register They can view the page, then create an account
Processor list and local payments
bKash, Nagad, and Rocket
For Bangladesh users, cd4 App stores information related to bKash, Nagad, and Rocket in separate categories, making it easier for Dhaka users or people from other cities to reconcile
Transaction status, timestamps, and reference numbers are usually shown; personal notes or unnecessary messages are not kept
- bKash tracking remains separate
- Nagad references are kept limited
- Rocket logs are used only for verification
Local users often cd4 App Start a session quickly with cd4 App, especially on slow networks
Chargeback data and account verification
1 request, multiple verifications
If any transaction is questioned, the cd4 App first checks the reference, time, and device information, then the support team manually reconciles
This reduces incorrect reports; if users want, they can request a copy or explanation of their transaction history
- Request date is recorded
- A response is given after verification
- Unnecessary personal information is removed
Before installing cd4 Login Viewing the guide clarifies account verification steps
Crypto wallet data and user rights
Access, modification, and deletion requests
If wallet-related information exists, it is used for account security and reconciliation; the cd4 App does not permanently store any data unless there is a legal or security need
Users can request to view, change, or delete their own data; usually after 2-factor authentication is completed, the support team begins work
- Right to view own data
- Incorrect information can be
- If needed, limited deletion requests can be made
For further assistance cd4 contact Post on the page, especially Dhaka users will receive quick replies
Contact about policies
If you have any questions, write to support; the cd4 team usually provides clear answers about policy, cookies, and data protection.
The bottom line is simple: using the cd4 App keeps data limited, and user control remains if you want to know more. Help Page View
Download cd4 APK