TRUST & SECURITY
Protecting people, their dignity, and their health information — everywhere care happens.
Lokra is built for environments where safety, privacy, and reliability are essential. Our responsibility is simple: ensure people can carry their health information without exposing their identity, movements, or personal details — whether they’re navigating crisis or receiving
routine care.
We follow four core principles.
Privacy by Design
Lokra collects no personal identifiers — ever.
Our tools work without names, phone numbers, national IDs, or demographic data.
● No identity required
● No cloud copies
● No centralized database
People remain anonymous, and their health information stays under their control — essential for vulnerable populations, and reassuring for everyday users who want privacy-first health records.
Offline-First Operation
Care should never depend on connectivity.
Lokra supports care in camps, shelters, rural clinics, border crossings, and crisis zones anywhere infrastructure is uncertain.
Clinicians can:
● Create new records offline
● Read a patient’s existing records offline
This ensures continuity of care, even when networks fail or don’t exist at all. (Note: Record updates are not currently supported — ensuring clarity and
accuracy.)
Interoperable & Standards-Aligned
A continuity layer that fits into diverse health systems.
Lokra uses globally recognized health data standards to ensure:
● Records are consistent across clinics and regions
● NGOs and distributed teams can work together smoothly
● Ministries and public health programs can integrate Lokra into existing workflows
Our tools complement — not replace — national systems and traditional EHRs.
Secure & Trustworthy by Default
Health information must be both private and reliable.
Lokra protects records by ensuring:
● All data stored on the patient’s device is encrypted
● No personal identifiers ever pass through Lokra systems
● Records can be verified for integrity when viewed by clinicians
● People choose when and where their health information is shared
There is no central database to attack and no large-scale target for misuse.