Security
The same care for every channel
The mobile app, the staff portal, and Prescription AI handle the same people and the same personal information. A control on one channel only works if the others follow it. Detailed risk treatment stays in the internal overview, not on this public page.
Controls in place
| Control | Where | What it does |
|---|---|---|
| Encrypted connection | All channels | Traffic to the live service uses a secure connection |
| Signed-in session | Mobile app | The session stays in protected storage on the device and is replaced when the person signs in again |
| Session and roles | Staff portal | A signed-in session plus permissions. Administrators are a distinct role. |
| Limited access | Staff portal | A page only opens the records that role is allowed to see |
| Telemedicine log hygiene | Shukhee | Visit logs do not keep the service secret |
| Immutable originals | Prescription AI | The original model output is kept when a person corrects a line |
| Catalog gate | Prescription AI | A medicine that is not in the catalog cannot be accepted as a real product |
How access works
- 1On the device
The app keeps the signed-in session in protected storage. The staff portal uses a signed-in session over a secure connection.
- 2In transit
The live service requires a secure connection. Prescription AI runs as its own service, separate from the member app.
- 3Who is signed in
Members sign in on the app. Staff sign in to the portal with a role. Prescription AI uses its own access, separate from member sign-in.
- 4What they can open
A role check runs before a staff page opens. Uploaded files and the activity log sit with the member records.
Personal data the platform is responsible for
Beneficiary records include National ID numbers, nominee identity, bKash account details, photographs, and mobile numbers. Prescription images are clinical documents. Shukhee logs can contain an IP address and a mobile number.
Retention rules, masking outside production, stronger protection for identity and mobile-money fields, and an access log for who opened a prescription image are part of the hardening and platform phases. This page does not publish internal defect details or exploit paths.