Limited verification
To run service, as much as needed, not more nor less.
During payment verification or account security, only necessary parts may be viewed.
How information is kept when using the okz App in Dhaka and across Bangladesh is clearly described here; in this policy in force since 2014, encryption, session security, and bKash-related verification are directly visible.
Download okz APK View okz Login instructionsAfter 11 o'clock, if you log in, system first checks your account's basic information; the okz App typically uses name, phone number, device ID, and session logs.
For more convenience, language preference and notification settings may be kept; if you want to change them later, return to okz Register.
For more convenience, language preference and notification settings may be kept; if you want to change them later, return to okz Register.
Even when mobile network is slow in morning, secure sign-in does not stop; data protection means not only locking, but also detecting wrong entries and unusual devices.
okz uses encryption here to organize transmitted data, so sensitive parts are not left dangling, and no one can read it in transit.
If you use the okz APK, this security layer is active as soon as installed; in the next section see who data may be shared with.
To run service, as much as needed, not more nor less.
During payment verification or account security, only necessary parts may be viewed.
Encryption remains active during data transfer, making reading in transit hard.
Local users seek this security more in bKash, Nagad, Rocket-type.
Some technical tasks are done with third-party tools, but access remains restricted until the work is completed and verified to ensure security.
This ensures login, notification, and device sync work properly.
If you don't want it, some data sharing can be stopped; changing settings is easy.
Clear controls make usage easier.
Just like a small notification, if there is no purpose-driven work during retention, data is not kept.
Okz typically keeps some logs for 30 days and some security records for 90 days, as long as needed to operate the account, security reviews, and legal requirements.
In Dhaka's slow networks, repeated login problems make that record useful; later, if needed, the support team will review it promptly.
When you open the account in the morning, all controls are in your hands; you may view or delete data.
Wrong phone number, old name, or unnecessary preferences can be updated; if you want, open the okz Login page and adjust settings.
If needed, you can ask about data usage limits; without transparency, security is not complete.
If you open the app at night and the previous language and screen are remembered, it makes things easier; cookies do exactly that.
okz App uses cookies to keep preferences, sessions, and visits; you don't need to re-enter the same data, and pages load faster.
If you switch browsers, settings may reset somewhat; that's normal, and it's good for privacy.
When logging in from a new phone, the system can recognize it as a new device.
It doesn't take long to detect unfamiliar access.
During transmission, session remains secure.
Data leakage risk drops even on weak networks.
okz App arranged for reading on small screens.
Hence viewing and changing information takes less time.
If unusual access occurs, warning appears.
Password must be changed immediately.
Nightly, if any questions remain, write directly to support; a one-line message suffices if clear.
The okz team reviews privacy, encryption, and data deletion requests; if necessary, they verify the account and inform you of next steps.
See Privacy Help pageFor those who regularly sign in with the okz App, this policy is a small but essential map of where the data goes, why it goes, and how long it stays, all laid out here.
If you use the okz APK, you will get this full framework of data protection, encryption, and session control; if needed, return to the okz Register or okz Login page and follow the steps.