Krikya App Privacy Policy and Data Security

What to Know at the Start

Effective date of this policy August 2026; see here what data is required, why, and how long kept

Only essential information is taken to run Krikya App; when using bKash, Nagad and Rocket, payment processors keep data under separate rules

Krikya App Credibility at a Glance

How card data tokenization works

Card numbers need not be stored directly; tokenization uses a secure code instead of the actual data, reducing risk

If you use bKash or Nagad from Dhaka, the same level of security applies; this keeps the payment screen and backend separate from each other

Encryption in Krikya App: Why

Without encryption, reading data becomes easy; during transmission the data is locked, so no one can see it in transit

This helps login, account activity and payment verification areas; even with session changes using Rocket, connection privacy remains

What kinds of information do cookies remember

Cookies remember your language, session and recent preferences so you do not have to set the same settings again

Some cookies are necessary, and some are only to understand habits; you can limit these from browser settings, especially on shared phones

List of payment processors and data sharing

Not all payment processors are the same; local options like bKash, Nagad and Rocket use essential checks

There may be limited sharing for filing, support, and risk assessment, but personal notes, passwords, or unnecessary information are not provided

What happens during chargebacks and disputes

If any transaction is blocked, checking the support log and reference number helps find a faster solution

If you wish, you can email, send screenshots and times; usually 2 pieces of information suffice quickly

How crypto wallet data is handled

Crypto wallet addresses are sensitive, so separate protection is required; they are not merged with account data

Wallet records store only data needed for verification and audit; when the report is viewed, your access data is not disclosed

What users say about Krikya App

Why Krikya App security is different

Why is card information kept separate?

Separating it helps; if one place leaks, not everything is at risk, due to tokenization and permissions

How does encryption help?

Encryption makes data unreadable; only

On mobile networks, when the connection is weak, this becomes more important; many in Bangladesh use phones

What happens if cookies are disabled?

Some pages may require sign-in

However, main content is visible; if you want, use custom browser privacy controls

How much local payment data is shown?

For bKash, Nagad and Rocket transactions, only

Many Dhaka users prefer small transactions; this policy follows that habit closely

Login Record Retention

For security and audit, a limited

If you have questions about Krikya Login, the support log provides a specific answer

If you have questions about Krikya Login, the support log provides a specific answer

What information is kept separate in Krikya APK?

Krikya APK handles device data, session and cookies separately so account and browsing information do not mix

The same rules apply even after downloading Krikya, so on a new phone controls are easy to understand

Understand security in 4 simple steps

Contact and Support

If any part is unclear, write to support with questions about payment, cookies or data retention rules.

If you want Help page See it, or Contact page Send a message

Krikya APK Download