Safety and governance
Security, separating what exists from what is planned.
Reedley does not process real patient data today. That gives us the chance to design security in before it is needed — and the obligation not to claim controls that are not yet in place.
Statements reviewed 14 November 2026. Reedley is in development; nothing here describes a live service.
Approach
Security for Reedley is planned against recognised baselines — Cyber Essentials, the Data Security and Protection Toolkit and NCSC guidance — and will be independently tested before any real data is processed. The assurance register shows the status of each.
Status. The controls in this page are described as in the development build (not yet security controls), implemented for this website or planned. Planned controls are commitments, not claims.
Product design (in the development build, synthetic data only; not yet security controls)
- Practice-level separation of patient data in the development repository, with cross-tenant tests.
- Role-based access within a practice and a record of every access attempt, designed and tested in the development build but enforced only by Reedley’s own screens. On the branch awaiting review (since 14 November), a GP, pharmacist or nurse sees safeguarding-classified content with a flag and an audited view by default; non-clinical roles need an explicit grant, and a practice can withhold it from clinicians only by recording a rationale. Not reviewed by a Clinical Safety Officer, safeguarding lead or information-governance lead.
- The development build runs in the browser with no authenticated user, so none of these is a security boundary yet. Moving the clinical logic to a server with authentication is planned before any real data.
- Append-only event history for every work item and human decision in the development server store; the browser build keeps history in memory only.
- Document text treated as data, with defences against instructions embedded in documents (pattern-based; not yet tested against the intended production model provider).
Before any real patient data
None of the following is in place today. All of them must be, for the scope concerned, before Reedley processes any real patient data, including in a pilot:
- A clinical safety case report for the pilot scope, approved by a Clinical Safety Officer (DCB0129), and the practice’s own DCB0160 assessment
- A written opinion from a regulatory specialist on whether any feature is a medical device (MHRA), and any registration or conformity assessment that requires
- Reedley Clinical Systems Ltd incorporated and registered with the Information Commissioner’s Office
- A Data Security and Protection Toolkit submission at “Standards Met”
- A data protection impact assessment and a data processing agreement with each practice, covering data minimisation, retention and deletion
- Cyber Essentials Plus certification and an independent penetration test of the product
- UK hosting for clinical data, and a published list of sub-processors, including any AI model provider
- Encryption in transit and at rest, multi-factor authentication, separate environments with no real data outside production, and tested backup and restore
- An incident response plan with named roles and notification routes
- Professional indemnity, product liability and cyber insurance
- The relevant clinical-system supplier or national approvals (for example IM1) for any integration
- An agreed protocol with success measures and a way to stop at any time
The same list is the gate before stage 4 of a pilot and appears in the evaluation pack and the product briefing.
This website (implemented)
- Static pages with no user accounts, no cookies set by default, and no third-party scripts.
- A strict Content Security Policy, HSTS, and headers that prevent framing, MIME sniffing and unnecessary browser permissions.
- Enquiry forms validated on the server, with size limits, origin checks, screening for patient identifiers, a honeypot and a minimum completion time, and a per-server rate limit keyed on the address reported by the hosting platform, not one the browser can set. A platform firewall rate limit is required before the forms are switched on and is not yet in place. The form handlers write no form content to logs.
- Product-update subscriptions use double opt-in: a link alone cannot subscribe anyone, each link works once, and an old link cannot undo an unsubscribe. They are not switched on yet.
- The website is architecturally separate from the clinical product: it shares no databases, credentials or network access with it.
Automated security checks were run during development. They do not replace an independent penetration test, which is planned after launch.
Secure development
- Today: the product and this website are developed privately by the founder, with automated test suites; a secret and patient-identifier scan of the product repository was run on 14 November 2026, and continuous integration is defined but not yet running, and as few dependencies as practical.
- Planned once source repositories are hosted: protected branches, independent review of production changes, automated dependency and secret scanning, and continuous integration on every change.
- Deployment credentials are held only by the founder and are never stored in source code.
Reporting a security issue
If you think you have found a security issue in this website, please follow our vulnerability disclosure guidance.
This website
Where an enquiry goes.
The only data this website processes is what you type into its forms: business contact details. No patient data. Static; no motion.
- method and origin checks
- per-server rate limit on the address the platform reports, behind a platform firewall rule of 10 submissions per address per 10 minutes
- size limit and validation; text shaped like an NHS number, a date of birth or a hospital number is refused
- honeypot and timing checks
- You submit a form; your browser validates it first.
- A serverless function in London checks the request (method, origin, rate, size, content, bot checks) and rejects anything that fails.
- Once the email provider is set up, the message is delivered through it to the Reedley mailbox, and a reference is shown to you. Until then the form says that nothing was sent.
- The website shares no databases, credentials or network with the clinical product.