Data protection
Sensitive data is kept in separate channels; names, devices, and usage types are not shown together
krikay App Privacy Policy in Bangladesh
This page explains what data the krikay App looks at, how it does it, and where it is used in research, all clearly stated. Many Dhaka users access it with bKash, Nagad, or Rocket, so the policy is kept straightforward.
There is no ambiguity in the policy; if you want krikay Download Go to the page to get the APK, and krikay Login You can view the steps in the guide
Download krikay APK
Effective date and brief overview
Effective: July 2026, data collected by the krikay App is compiled first, then used for research and development.
Here, personal identifiers are kept separate for Bangladeshi readers, with the language intentionally kept simple for Dhaka and Chittagong users.
Cookie control
Cookies are used to remember sessions, language, and preferences; if desired, you can limit them from the browser
User rights
Requests for access, correction, and opt-out can be made; responses are usually sent within 7 business days
Research use
Selected data is used to view trends; this analysis is done without personal identifiers
How anonymization works
In many apps, data blends together, making it hard to tell what is kept and what is not; in the krikay App, IDs, location, and behavioral signals are first filtered, then combined
Hence a single user cannot be identified; three-level filtering is used, and personal names do not appear in the same report
Daily usage data
Which screen opened how many times is tracked, but your chat, password, or payment notes remain separate
Local connection context
Many Dhaka users sign in with bKash, Nagad, or Rocket; that information is not shown directly in research, only as aggregated trends
Research scope and use
Not all data goes to research; from 590K+ active users only aggregate behavior, session length, and device type are observed
This makes it easier to understand new updates by viewing usage patterns for 847+ titles to see where features seem improved
What is seen, what is not seen
Usage patterns, browser type, and language preferences are observed; personal messages, credentials, or sensitive notes are not shown
Limitations
If cookies are disabled, some personal settings may not be remembered, but the main pages still load, and access remains stable due to 99.8% uptime
Sharing with researchers
Sometimes universities or research teams request statistics; then only filtered, aggregated, and anonymized data are provided
Not in 2010s, the experience since 2022 is useful; from a 4.4/5 average rating and 9,187 reviews, the trend that emerges is more valuable for analysis
Why this sharing is needed
Which features are understood, which ones seem difficult, that is the main goal, so reports show trends instead of personal identifiers
Transparency limits
Not all requests are honored; at least 24 hours of identity verification required before any raw file is sent
Opt-out and rights
If anyone wants, they can opt out of research-based profiling by going to the settings page, and the process usually completes in two steps
If cookies are deleted, tracking from new sessions decreases, but if security cookies are turned off you may have to log in repeatedly; it's a small inconvenience
Corrections and deletion
If there is incorrect information, you can request corrections; if personal identifiers exist, they are kept under a limited-use policy
Where to contact
Support team is available for any questions krikay contact page When you send a request from here, the team responds