Privacy and data handling
eny Clinic is built to UK GDPR and Data Protection Act 2018 requirements. This is a trial, and it is not a certified clinical system. It must not hold real patient data.
Who is responsible
eny is the data controller for this trial. Contact info@enyinc.uk. You can complain to the Information Commissioner's Office at ico.org.uk.
What we collect and why
At signup: your practice name and work email, and nothing else. The lawful basis is contract (running the trial you asked for) and legitimate interest (getting in touch about it). eny staff see the signup name, email and usage counts, such as how many actions a workspace has taken, to support the trial. They do not see the records inside it.
Health data
Health data is special-category data under UK GDPR Article 9. The trial is designed so it never holds any: patients are generated by the system, there is no field to type a patient's name or NHS number, and at signup you confirm you will not enter real patient data. Notes are marked as synthetic. We apply the NHS Data Security and Protection Toolkit and Caldicott principles to how the trial is built:
- Least privilege: three roles. Only the clinician can read or write consultation notes. Reception and the practice manager cannot.
- Every view of a patient record is written to an access log with who and when. The practice manager can read it for each record.
- No patient data in web addresses or server logs. Records are reached by random IDs, and patient search is sent in the form body, not the address.
- Notes cannot be edited or deleted. A correction is a new note.
How long we keep it
30 days from signup. Then the workspace locks, and a daily job deletes every record in it. There are no backups of trial data. The practice name and email are blanked at the same time.
Your rights
The practice manager can download everything in the workspace as JSON at /account/export (Articles 15 and 20), and delete it all immediately at /account/delete (Article 17). For anything else, email info@enyinc.uk.
Security
HTTPS only. Sessions are signed and kept in an HttpOnly, Secure, SameSite=Lax cookie. PINs are hashed with PBKDF2. Database queries are parameterised and every one is limited to your workspace. Signup and sign-in are rate limited, and pages carry a strict Content Security Policy and refuse to be framed.
No tracking
This site loads no analytics, advertising or tracking scripts and sets no tracking cookies. The only cookie is the sign-in session. The only third-party script is Cloudflare Turnstile on the signup page, to keep bots out. Data is hosted on Cloudflare.