Governance

Security

Last updated: 28 October 2026

Protecting data is part of building medical software responsibly. These are the practices that apply to TamRx today.

Protecting data

Company and development data is encrypted in storage and in transport. Development uses de-identified public datasets only, so no identifiable patient data is held.

Controlling access

Access follows the principle of least privilege: people and services receive only the access their work requires. Multi-factor authentication is required on the accounts that hold company and development data.

Resilience

Regular backups are kept offline, separate from working systems, so that data can be recovered if a system is compromised or fails.

This website

This website is static: it has no database, no login and no tracking cookies. It is served only over HTTPS, with security headers including HTTP Strict Transport Security and a Content Security Policy.

Certification

TamRx does not currently hold a security certification. We describe our practices here rather than display badges we have not earned.

Reporting a vulnerability

If you believe you have found a security issue, email mounsif@tamrx.co.uk with "Security" in the subject line, describing the issue and how to reproduce it. Please allow us reasonable time to fix it before disclosing it publicly. The same contact is published in our security.txt file.