Security
Built around the data it holds
A clinical record is among the most sensitive data there is. Here is how we protect it, plainly, without the certificates-as-decoration.
Where your data lives
-
Hosted in the European Union
Patient records stay in the European Union, under European data protection law. Where data lives is a starting constraint, not a setting, and nothing in the system depends on services outside Europe.
-
A website that minds its own business
This site runs without trackers, analytics or outside services, and the product holds itself to the same standard. What happens in a consultation is nobody else's business.
How records are protected
-
Encrypted at rest and in use
Records are encrypted while stored and while being worked on, not only while moving over the network. The keys are managed separately from the software that uses them.
-
Ready for the computers of the future
Medical records outlive the systems that store them. Our encryption is chosen to withstand future quantum computers, not only today's attacks, so what is protected now stays protected for decades.
Who can see what
-
The least access that works
People and services get only the access their role requires, with hardware security keys guarding the most privileged accounts. Sensitive data stays protected even from someone inside a facility trying to extract it.
-
Every action leaves a trace
Every access and every change is recorded by construction. An audit trail that can be switched off is a promise; ours is a property of the system.
How we build
-
A foundation without the old flaws
The system is written end to end in Rust, a modern memory-safe language that rules out by construction the kind of software flaw behind many well-known breaches.
-
Security as a lifecycle, not a checkbox
Security is designed in from the start, reviewed, and maintained for as long as the system runs, following recognised security practice for health software.