cd44 App Privacy Policy
How data is stored on this page, how long it stays, and why it is shown clearly; the information provided by Dhaka users via bKash, Nagad, Rocket is also covered by this policy.
Get cd44 APK See cd44 Login
Retention Policy at a Glance
The policy's key points keep only as much data as needed; for security, verification, and support, some records are kept, and the rest are removed after a defined period.
Each data item in the cd44 App has its own time limit; view it quickly in the table below.
Account Information
Until the account is closed, verification and sign-in remain secure.
Transaction History
Under the policy, longer retention helps with audits and reconciliation.
Security Log
Short-term retention is used to detect suspicious activity.
Session Data
Login and device tracking are kept accurate for a few days.
| Data Type | How long data is | Why it is kept. |
|---|---|---|
| Registration Information | Until the account is active. | Identity, Help, and Sign-In |
| cd44 Login Log | 30 days | Security Review |
| Payment Records | Applicable Law | Account Reconciliation and |
| Device Information | 90 days | Login Risk Identification |
| Support Chat | 6 months | Troubleshooting and Follow-Up |
| Analytics Summary | 12 months | App Speed and Status |
Account Data in the cd44 App
The information needed to open an account in the cd44 App is very limited to basic name, contact, and security settings; the same rules apply whether using from Dhaka or Chattogram.
You cd44 Register Or cd44 Login If you proceed, only the required verification parts are shown; if you seek support via bKash or Nagad, those contact records are kept briefly.
What is kept
- Name and contact information
- Security Question Settings
- Device-Based Access Data
Transaction data and
In Bangladesh, many people complete transactions quickly with bKash, Nagad, Rocket, so transaction records are kept separately to facilitate quick reconciliation.
These records do not contain money, but references and status used in system audits.
How it's used
- Record Created
- Status Check
- If Problems Arise, Check Support
- It expires when time runs out
Usage data and security
Using usage data, you can tell which screen loads quickly, where problems occur, and on device load is high, improving app stability
At the same time the security team can detect unusual logins, wrong devices, unfamiliar locations, or repeated attempts, all of which trigger alerts
Which signal is seen
- Device type
- Last login time
- Error messages and speed
What happens when the account is closed
Closing the account doesn't delete everything all at once; for legal, security, and dispute resolution reasons, some records remain for a limited time
Personal profile, active sessions, and unnecessary alerts are removed step by step, then only the necessary audit section is kept
Easy rules for you
- Data decreases when not needed
- If you need support, an explanation is available
- Security records are kept separate
Your rights and contact
You can request to view, correct, and limit your data; if needed you may also request explanations for old records
If you have any questions cd44 Contact Page See more cd44 Help Common answers on the page
cd44 Download cd44 View App