GDPR: rights and responsibilities
Understanding UK GDPR for England and Northern Ireland, EU GDPR for the Republic of Ireland, and the right to ask questions about a personal data breach.
Potential GDPR contraventions requiring investigation
The following are potential breaches, not regulatory findings. They arise from the publicly accessible backups described in this investigation. The legal analysis applies separately under UK GDPR for England and Northern Ireland and EU GDPR for the Republic of Ireland, subject to the relevant controller, processing and territorial rules.
Article 5(1)(f) — integrity and confidentiality
What the article requires: A controller must protect personal data against unauthorised or unlawful processing and accidental loss using appropriate security.
Why this incident raises concern: Publicly downloadable patient, payroll and staff files without authentication or effective access controls strongly raise questions about compliance.
Article 5(2) — accountability
What the article requires: Controllers must be able to demonstrate compliance with data-protection principles.
Why this incident raises concern: The length of exposure and unresolved questions about monitoring, breach assessment and notification call for documentary evidence of compliance; the exposure alone does not prove an accountability breach.
Article 24 — responsibility of the controller
What the article requires: Controllers must implement and review appropriate technical and organisational measures.
Why this incident raises concern: Repeated publication of backups to an open server suggests possible shortcomings in the design, review or enforcement of controls.
Article 25 — data protection by design and by default
What the article requires: Controllers must embed data protection into systems and ensure that, by default, personal data is not made accessible to an indefinite number of people.
Why this incident raises concern: An internet-accessible backup directory containing extensive personal records appears difficult to reconcile with secure default settings.
Article 32 — security of processing
What the article requires: Security measures must be appropriate to the risks, including confidentiality, resilience, testing and, where appropriate, encryption.
Why this incident raises concern: The reported absence of authentication and access restrictions, coupled with sensitive records and a prolonged exposure, provides particularly strong grounds for regulatory scrutiny.
Article 9 — special-category personal data
What the article requires: Processing information such as health data, religion, ethnicity and sexual orientation requires an Article 9 condition as well as an Article 6 lawful basis.
Why this incident raises concern: The files reportedly included these categories. Exposure does not by itself prove the original collection lacked a lawful condition, but the disclosure raises serious security and lawfulness questions.
Article 33 — notification to the supervisory authority
What the article requires: A controller must notify the competent authority without undue delay and, where feasible, within 72 hours after becoming aware of a personal data breach, unless risk to individuals is unlikely.
Why this incident raises concern: Given the scope and sensitivity, a documented risk assessment and a notification decision would be expected. Whether and when the company notified each regulator remains to be established.
Article 34 — communication to affected individuals
What the article requires: Where a breach is likely to result in a high risk to individuals’ rights and freedoms, affected people must generally be informed without undue delay, subject to statutory exceptions.
Why this incident raises concern: Exposed health, financial, identity and sensitive employee information may meet the high-risk threshold. The reported lack of individual notification is a central unresolved concern.
Articles 44–46 — transfers outside the jurisdiction
What the article requires: Transfers of personal data to a third country require an applicable transfer mechanism and safeguards; UK and EU rules must be considered separately.
Why this incident raises concern: A US-hosted server makes the transfer arrangements worth examining. Hosting in the USA is not automatically unlawful; the controller, processor, transfer mechanism and applicable adequacy arrangements must be verified.
Article 28 — processors
What the article requires: Controllers using processors must have compliant contractual terms and ensure appropriate guarantees.
Why this incident raises concern: If a third-party hosting provider processed the backups, processor due diligence, instructions and contractual safeguards warrant examination; no contract breach has yet been demonstrated.
Evidence and regulatory questions
- Which entity controlled each patient, employee and prison-healthcare dataset?
- What safeguards were applied to the Virginia host and when were they tested?
- What UK and EU international-transfer arrangements, if any, were in place?
- When did the controllers become aware of the exposure, and what reports were submitted to the ICO or Irish DPC?
- What Article 34 high-risk assessments and individual-notification decisions were documented?
Official references: GDPR text, ICO breach guidance, Irish DPC breach guidance.
Independent legal analysis for public information, not a determination of liability or legal advice.