{"check":null,"uid":"29cb00acf5622276","title":"Andrew Ezsias v Information Commissioner","title_generated":false,"country":"Великобритания","organ":"Суды Англии и Уэльса","kind":"case","kind_name":"Судебная практика","lang":"en","date":"2026-11-06","summary":"Суд рассмотрел заявление гражданина Эндрю Эзсиаса об ускорении рассмотрения жалоб, поданных им в Информационную комиссию и компанию Sky Group plc. Заявление было отклонено, поскольку жалоба была рассмотрена и решена, и больше не требовалось никаких дальнейших действий со стороны Комиссии или компании. Суд указал, что полномочия трибунала ограничены процедурой рассмотрения жалоб и не позволяют добиваться иных результатов, кроме тех, которые доступны через судебные процедуры.","snippet":"","topics":["Персональные данные"],"status":"ok","error":"","text_len":11108,"versions":1,"url":"https://caselaw.nationalarchives.gov.uk/ukftt/grc/2026/1528","first_seen":"2026-11-10","last_checked":"2026-11-16 05:29","relevance":"hit","score":3,"query":"data protection","source_key":"caselaw_uk","verdict":{"relevance":"hit","score":3,"topics":["Персональные данные"],"need_body":3,"authorities":[{"kind":"орган","name":"Information Commissioner","topic":"Персональные данные"},{"kind":"орган","name":"ICO","topic":"Персональные данные"},{"kind":"акт","name":"Data Protection Act 2018","topic":"Персональные данные"}],"evidence":[{"topic":"Персональные данные","term":"Information Commissioner","weak":false,"pos":16,"ctx":"Andrew Ezsias v Information Commissioner Acronyms used  DPA the Data Protection Act 2018  FtT the First-tier Tribunal General Regu","zone":"орган","weight":3},{"topic":"Персональные данные","term":"ICO","weak":false,"pos":146,"ctx":"DPA the Data Protection Act 2018  FtT the First-tier Tribunal General Regulatory Chamber  ICO Information Commissioner’s Office  SAR Subject Access Request  Background  1.  This Tribu","zone":"орган","weight":0},{"topic":"Персональные данные","term":"Data Protection Act 2018","weak":false,"pos":64,"ctx":"Andrew Ezsias v Information Commissioner Acronyms used  DPA the Data Protection Act 2018  FtT the First-tier Tribunal General Regulatory Chamber  ICO Information Commissioner’s O","zone":"акт","weight":0}],"dropped":[{"topic":"Персональные данные","term":"data protection","weak":false,"pos":23,"ctx":"acronyms used  dpa the data protection act 2018  ftt the first-tier tribunal general regulatory chamber  ico information commiss","why":"одиночное упоминание (нужно 3)"},{"topic":"Персональные данные","term":"gdpr","weak":false,"pos":6380,"ctx":"formed mr delo he considered the conduct in question was “likely” to be compliant with uk gdpr.  16.  therefore, the ftt on an application under section 166, has no power to deal with","why":"одиночное упоминание (нужно 3)"}]},"last_changed":"2026-11-10","meta":{"neutralCitation":"[2026] UKFTT 01528 (GRC)","court":"United Kingdom First-tier Tribunal (General Regulatory Chamber)"},"source_url":"https://caselaw.nationalarchives.gov.uk/ukftt/grc/2026/1528","text":"Acronyms used\n\nDPA\nthe Data Protection Act 2018\n\nFtT\nthe First-tier Tribunal General Regulatory Chamber\n\nICO\nInformation Commissioner’s Office\n\nSAR\nSubject Access Request\n\nBackground\n\n1.\n\nThis Tribunal is concerned with an application for a Section 166 Order to Progress. Mr Ezsias had made a SAR to the Motor Ombudsman on 11 March 2026 and a SAR to Sky Group plc on 01 June 2026.\n\n2.\n\nIn his GRC3 dated 26 August 2026, Mr Ezsias states the date of complaint to the ICO as 24 April 2026. This indicates that he sought an Order to Progress for the complaint he made to the ICO about the Motor Ombudsman (his SAR to Sky Group plc had not even been made on 24 April 2026).\n\n3.\n\nBy letter dated 06 July 2026, Mr Ezsias complained to the ICO about Sky Group plc’s handling of his SAR.\n\n4.\n\nBy letter dated 10 July 2026, the ICO told Mr Ezsias that reference number IC-537773-J9T6 had been allocated to a complaint. That correspondence from the ICO does not clarify which of Mr Ezsias’s complaints had been allocated that reference – by then, he had sent a complaint letter about each of the Motor Ombudsman and Sky Group plc. A further letter from the ICO and with the same reference was sent, dated 07 August 2026.\n\n5.\n\nOn 27 July 2026, Mr Ezsias sent to the ICO a complaint and a letter before action.\n\n6.\n\nThe FtT issued standard Initial Case Management Directions dated 28 August 2026.\n\n7.\n\nBy GRC5 dated 23 September 2026, supported by a Response and submissions document of the same date, the ICO applied to the FtT for the application to be struck out as, they submitted, there was no reasonable prospect of it succeeding.\n\n8.\n\nThe ICO in their response and Annexes thereto explains:\n\na.\n\nICO complaint reference IC-537773-J9T6 is the complaint made about Sky Group plc. This was confirmed to Mr Ezsias by letter dated 13 August 2026 (Annex 7).\n\nb.\n\nThe ICO allocated complaint reference IC-508958-N0J3 to the complaint made (by letter dated 24 April 2026) about the Motor Ombudsman. Confirming this case number by letter dated 14 August 2026 (Annex 2).\n\nc.\n\nOn 14 August 2026, the ICO wrote to Mr Ezsias asking that he raise his complaint directly with the Motor Ombudsman and to notify the ICO if no response was received within one month.\n\nd.\n\nOn 14 September 2026, the ICO sent further correspondence to Mr Ezsias about his complaint about the Motor Ombudsman.\n\ne.\n\nThe response also sets out what was done in connection with the complaint about Sky Group plc, including that in letters dated 1 and 14 September 2026, the ICO had sent to Mr Ezsias an outcome concerning that complaint.\n\n9.\n\nBy case management directions dated 24 September 2026, the FtT invited Mr Ezsias to make representations about the ICO’s application to strike out the application for an Order to Progress. Mr Ezsias made representations in a document dated 05 October 2026 and provided supporting documents.\n\n10.\n\nThe issue for the Tribunal is not whether the Commissioner reached the correct conclusion about the underlying complaint. The issue is whether there is any realistic prospect that the Tribunal could appropriately make a section 166 order requiring a further step to be taken in relation to the complaint.\n\nThe Law\n\n11.\n\nThe key authorities about the scope of the FtT’s jurisdiction are\nKillock and VeaIe v\nInformation Commissioner\n[2022] 1 WLR 2241\n(\nKillock\n),\nR (Delo) v Information\nCommissioner\n(\nDelo\n) in the High Court (\n[2023] 1 WLR 1327\n) and Court of Appeal\n(\n[2023] EWCA Civ 1141\n) and\nSmith v Information Commissioner\n[2025] UKUT 74\n(AAC) (\nSmith\n).\n\n12.\n\nIn\nKillock\n, the Upper Tribunal explained it did not rule out circumstances\nin which a complainant who had received an outcome to their complaint under section\n165(b) might ask the Tribunal to ‘wind back the clock’ and make an order for an\nappropriate step to be taken in response to the complaint under section 166(2)(a). The\nUpper Tribunal went on to explain: “However, should that happen, the Tribunal will cast\na critical eye to assure itself that the complainant is not using the s.166 process to\nachieve a different complaint outcome.”\n\n13.\n\nIn\nKillock\n, the Upper Tribunal also explained that in considering appropriateness (in\nterms of a step), the Tribunal will be bound to take into consideration and give weight\nto the views of the ICO as an expert regulator. The Upper Tribunal expressed\nthe view that in the sphere of complaints, the ICO has the institutional competence and\nis in the best position to decide what investigation they should undertake into any\nparticular issue and how they should conduct those investigations. The Upper Tribunal\nindicated these matters will be informed, not only by the nature of the complaint itself, but also by a range of other factors such as the ICO’s own regulatory priorities, other\ninvestigations in the same area and their judgement on how to deploy limited resources\neffectively. The Upper Tribunal emphasised the need for the FtT to recognise the wider\nregulatory context of a complaint and to demonstrate respect for the ICO’s special\nposition. See paragraph 85 of the judgment in\nKillock\n.\n\n14.\n\nIn\nR (Delo) v Information Commissioner\n\n[2023] EWCA Civ 1141\n, in the Court of Appeal,\nWarby LJ (with whom the other Court of Appeal judges agreed) concluded the relevant\nlegislation should be interpreted as requiring the ICO to receive and consider a\ncomplaint and gives him a broad discretion as to whether to conduct a further\ninvestigation and if so, to what extent. Warby LJ agreed with Mostyn J.’s decision that,\nhaving done this much, the ICO is entitled to conclude it is unnecessary to determine\nwhether there has been an infringement but sufficient to reach and express a view\nabout the likelihood this is so and to take no further action (paragraph 80).\n\n15.\n\nIn\nDelo\n, Warby LJ stated that while a conclusive determination or ruling on the merits\nwould clearly amount to an outcome, the word used was intended to have broader\nconnotations. Warby LJ agreed with the Upper Tribunal in\nKillock\nthat the word\n“outcome” embraced a decision to cease handling a specific complaint. Warby LJ also\nagreed with the analysis by Mostyn J. in\nDelo\nin the High Court that outcome would\nproperly capture the ICO’s decision to conclude considering Mr Delo’s complaint,\nhaving informed Mr Delo he considered the conduct in question was “likely” to be\ncompliant with UK GDPR.\n\n16.\n\nTherefore, the FtT on an application under section 166, has no power to deal with the\nmerits of a complaint or its outcome. That said, Upper Tribunal Judge Stout’s decision\nin\nSmith\nconfirms, at [59]-[60], that the mere fact that the ICO has issued a\ncomplaint outcome does not mean that there is no scope for a section 166 application.\nBut, as Judge Stout also explained in\nSmith\nat [60], in a case where the ICO\nhas carried out an investigation and provided an outcome, it is highly unlikely that a\nsection 166 application will succeed. This is for two principal reasons.\n\n17.\n\nThe first reason is because the case law has established that section 166 is a\nprocedural provision where the FtT’s jurisdiction is limited to adjudicating on whether\nthe ICO has done any of the things identified in section 166(1), and cannot\nbe used to obtain ‘by the back door’ a remedy normally only available on an application\nto the courts under sections 167/168 of the DPA 2018 for a compliance order/damages\nagainst the data controller or on a claim for judicial review of the ICO’s\ndecision (see further [74] of\nKillock\n).\n\n18.\n\nThe second reason is because the ICO has a wide discretion under section\n165 as to whether to investigate a complaint at all and as to the outcome, so that the\nscope for the FtT to interfere with that judgement on a section 166 application is\nlimited.\nEW\n, decided alongside\nKillock\n, was an exceptional case where the\nICO, in breach of his own stated policy, had undertaken no investigation at\nall. Yet, as the Court of Appeal made clear in\nDelo\n, the ICO is not required\nto determine every complaint, an “outcome” may be a decision not to investigate further\n([64]), the ICO is not required “to determine the merits of complaints” ([78])\nand\nhas a “broad discretion as to whether to conduct a further investigation and, if so,\nto what extent” ([80]).\n\nApplication of law to the facts\n\n19.\n\nMr Ezsias’s representations opposing strike out include:\n\na.\n\nHis application succeeded. The ICO had not responded to his complaint and only did so after they received his application to the FtT.\n\ni.\n\nI infer from that submission that the principal objective of the application was to obtain an outcome to the complaint and that that objective has now been achieved.\n\nii.\n\nStriking out is not about winning or losing; it is about whether there is a reasonable prospect of the FtT making an Order to Progress.\n\nb.\n\nHis application was on narrow grounds – section 166 – he invited the FtT to make comment on other matters.\n\ni.\n\nThe FtT will confine itself to application of section 166 of the DPA.\n\nc.\n\nHis application was only about the lack of response to the Motor Ombudsman complaint, the ICO wrongly conflates it with the complaint about Sky Group plc.\n\ni.\n\nI have deduced from the date set out for “complaint made” that the application was about the Motor Ombudsman complaint.\n\nii.\n\nIt was quite proper for the ICO to clarify the history of Mr Ezsias’ engagement with them as Mr Ezsias had been unable to provide the complaint number (only the date). It was, in fact, helpful as the clarification assisted the FtT to understand what had happened about the two separate complaints and may have assisted Mr Ezsias to also understand the position with both his complaints.\n\nd.\n\nThe ICO only applies for strike out because they have now remedied the error and the ICO should have contacted Mr Ezsias to find a mutually agreeable and satisfactory outcome.\n\ni.\n\nWhether or not the application prompted further action by the ICO, the position now is that an outcome has been provided.\n\nii.\n\nThere was no need for the ICO to see if Mr Ezsias could agree an outcome to Mr Ezsias’s application under section 166, and I note that he does not specify what other outcome may have been agreeable to him.\n\ne.\n\nMr Ezsias should be permitted to amend and substitute the originally suggested draft order.\n\n20.\n\nAn outcome has now been provided to Mr Ezsias. The FtT must consider whether, notwithstanding that outcome, there remains any realistic basis upon which it could appropriately make an order under section 166(2).\n\n21.\n\nI consider that there is no realistic basis upon which the FtT could appropriately make such an order. The proceedings have achieved the objective of the application, namely obtaining an outcome to the complaint dated 24 April 2026. Mr Ezsias has not identified any further step which could realistically be required of the Commissioner under section 166(2), beyond providing an outcome to the complaint, which has now occurred.\n\n22.\n\nTherefore, and pursuant to rule 8(3)(c) of the GRC Rules, I strike out the application for an Order to Progress.\n\nSigned:\nJudge Worth\n\nDate:\n06 November 2026","changes":[]}