Privacy Policy 2026

krikya App Privacy Policy and Data Security

This page shows how the krikya App collects data, uses cookies, and respects the rights of Bangladesh users, with a clear Dhaka-based explanation provided for clarity.

Download krikya APK See krikya Login guideline
krikya Privacy Policy Screen

How the krikya App works for data protection

Metric

4.6

Average Rating

Metric

30,981

Review

Metric

852K+

Active users

Metric

99.2%

Uptime

The main point of this policy is simply that your login data, device information, and session tokens are used only for necessary tasks.

Many Dhaka users log in with bKash, Nagad, and Rocket; only the necessary information is processed for those transactions.

Who can see your data?

01 / Access

Only authorized team

Support and Security teams have limited access; they see only as much as is necessary for their work.

02 / Control

Internal control

No single member can see all data for each role, and nothing is accessible without login.

03 / Scope

Only work-related data

Account verification, login, and keeping the session stable require information; personal data is not spread unnecessarily.

Although strict, it is not open to any employee based in the Dhaka office.

Access requires permission, reason, and a timestamp; this makes auditing easier and reduces risk.

Training and data discipline in the krikya App

01 / Training

New team training

Each new member is taught privacy, encryption, and reporting; onboarding normally ends in 2 steps.

02 / Rules

Written policies

Which data may be viewed and which may not is predefined; if operating outside policy, access is blocked.

03 / Review

Regular reviews

In monthly reviews, permissions are reconciled; if old access is not needed it is removed.

There is no extra talk here; those who view data also have defined responsibilities.

Thus the chance of data falling into the wrong hands decreases, and user trust is easier to maintain.

Why are background checks and log records important?

01 / Checks

Pre-employment checks

Identity and experience verification before sensitive roles reduces internal risk significantly.

02 / Logs

Access logs

Who, when, and what data was viewed is recorded; whether viewed from Dhaka or elsewhere, traces are kept.

03 / Audit

Fast audit match

With logs, issues are detected faster; typically system reviews begin within 24 hours.

Background check does not mean strictness; it is just a basic layer to keep your information safe.

With log records, mistakes are detected quickly and accountability is clear.

Why are cookies needed, and what controls will you have?

Cookie

Session persistence

Cookies remember sign-in state, so you don't have to log in again.

Preference

Save preferences

Language, interface, and notification preferences are stored, making the experience a bit faster.

Controls

Limit cookies

You can reduce cookies from browser settings, but some features may load slowly.

Cookies are not a mystery; they simply remember your last state to make things easier.

If you want, you can clear history and sessions from the browser, and start anew.

User rights and contact options

You can view, correct, and delete your data; if needed, you can request limited processing.

krikya Download remains same rights whether APK is installed or accessed via browser; policy doesn't change ever.

Right to information

Policy to provide a clear answer about what information is kept

Right to correction

If your name, number, or profile is wrong, you may update it quickly

Delete request

If no longer needed, request account closure; after verification, steps proceed

If you have questions, write to the contact page for Dhaka or another city; the same support is available to all users

Read this krikya App policy to see the full picture; data security, cookies and rights are in one place

See related page

krikya data request form

krikya Register

Lite APK See the setup after registration

Log in Registration