We use some essential cookies to make our website work. We’d like to set additional cookies so we can remember your preferences and understand how you use our site.
You can manage your preferences and cookie settings at any time by clicking on “Customise Cookies” below. For more information on how we use cookies, please see our Cookies notice.
Your cookie preferences have been saved. You can update your cookie settings at any time on the cookies page.
Your cookie preferences have been saved. You can update your cookie settings at any time on the cookies page.
Sorry, there was a technical problem. Please try again.
This site is a beta, which means it's a work in progress and we'll be adding more to it over the next few weeks. Your feedback helps us make things better, so please let us know what you think.
Live Facial Recognition
ACC Andrew PRITCHARD
Serious Crime Directorate
12/08/2024
05.10.23
Project Lead
D/SUPT Stephen JENNINGS
Initial Draft
13.10.23
SRO
Written
SRO Approved Draft
06.08.24
DPO
Scheduled update
Capitalised terms used in this Essex Police LFR Legal Mandate shall have the meaning given to them in the Essex Police LFR Policy Document unless otherwise defined in this Essex Police LFR Legal Mandate.
1.1 Live Facial Recognition (LFR) for law enforcement purposes is not subject to dedicated primary legislation. LFR is regulated by a number of sources of primary and secondary legislation as well as both national and local policy. This ‘tapestry’ of legislation combines to provide a multi-layered legal structure to use and regulate the use of LFR.
a) Common Law
b) Police and Criminal Evidence Act 1984 Code D (revised)
Operational
b) Human Rights Act 1998
c) Equality Act 2010
Data Management
d) Data Protection Act 2018 (Part 3)
e) UK General Data Protection Regulation
f) Protection of Freedoms Act 2012
g) Freedom of Information Act 2000
h) Data Protection Act 2018 (Subject Access Requests)
a) Secretary of State’s Surveillance Camera Code of Practice.
b) Guidance issued by the Surveillance Camera Commissioner (Facing the Camera)
c) Information Commissioner’s Office Code of Practice for Surveillance Cameras and associated guidance issued by the Information Commissioner
a) EP Policy Document
b) EP Standard Operating Procedures
c) Data Protection Impact Assessment
d) Equality Impact Assessment
e) EP Legal Mandate
2.1 The police have a number of long-established policing responsibilities and powers derived from common law which have been recognised by the courts. Essex Police (EP) is obliged to comply with common law and statutory safeguards in delivering its policing operational duties and relies on common law to discharge a number of its duties.
2.2 Key common law powers EP may rely on when utilising LFR technology include the policing common law powers to:
(a) protect life and property;
(b) preserve order and prevent threats to public security;
(c) prevent and detect crime;
(d) bring offenders to justice; and
(e) uphold national security.
Example: EP has detailed uses of LFR as a policing tactic for reducing violence through the arrest of those who are wanted for violent offences. In this context the use of LFR technology to preserve order by facilitating officers to promptly locate those who are suspected to have caused violence, this would enable EP to discharge its responsibilities to protect life and property. It would also be compatible with EP’s duty to bring offenders to justice by facilitating a prompt and effective investigation.
2.3 The use of common law powers as a legal basis to support the deployment use of LFR has been considered and recognised in the ‘Bridges’ case:
a) R (on the application of Edward Bridges) v The Chief Constable of South Wales Police (SWP) [2019] EWHC 2341 (Admin) (the “High Court Bridges” decision); and then on appeal in,
b) R (on the application of Edward Bridges) v The Chief Constable of South Wales Police [2020] EWCA Civ 1058 (the “Court of Appeal Bridges” decision).
The Court of Appeal further summarised the legal basis in relation to compilation of Watchlists as being “both authorised under the Police and Criminal Evidence Act 1984 and within the powers of police at common law.” The reference to the 1984 Act is a reference to imagery obtained pursuant to Section 64A (Photographing of suspects etc.) of the Act and particularly section 64A(4)(a) which allows a photograph taken under the section to be “used … for any purpose related to the prevention or detection of crime, the investigation of an offence or the conduct of a prosecution or to the enforcement of a sentence”. The Court of Appeal notes that “this was not an issue which we have to address in this appeal, since it is now common ground that SWP do have the power to deploy [LFR].”
Authorising Officers: When considering the use of LFR technology, must be clear as to the common law policing power that is relied upon for lawfully authorising the use of LFR and record this as part of the decision-making process.
3.1 Section 64A of PACE allows photographing a person who is detained at a station.
3.2 Allows for the photographs to be used for the prevention and detection of crime, the investigation of offences or the conduct of prosecutions.
4.1 EP use of LFR must be in compliance with the Human Rights Act 1998. LFR technology engages the Human Rights Act 1998 and in particular has the potential to impact upon an individual’s Article 8 rights, the right to respect for private and family life. This provides:
‘ There shall be no interference by a public authority with the exercise of the right except such as in accordance with the law and is necessary in a demographic society in the interests of national security, public safety or the economic well-being of the country, for the prevention of disorder or crime, for the protection of health or morals, or for the protection of the rights and freedoms of others.’
4.2 As a qualified right, any interference with an individual’s Article 8 rights is only permissible if:
a) there is a legal basis for the interference with the qualified right that the public can understand;
b) the use of LFR seeks to achieve the legitimate aim;
c) it is necessary for the purposes of that aim in a democratic society; and
d) the use of LFR is proportionate to the legitimate aim being sought.
4.3 It is well-established that the reach of Article 8 can be broad. The case of S v. United Kingdom[1] confirms that this can relate to a person’s right to their biometric data and any storing of data relating to it. Recognising that LFR involves biometric processing, that case went on to recognise that, in protecting the personal data and other forms of biometric processing, the interests of the data subject and the community as a whole “may be outweighed by the legitimate interest in the prevention of crime”.[2]
4.4 The High Court and Court of Appeal Bridges cases considered Article 8, specifically in the context of LFR technology and confirmed that Article 8 is engaged in so far as someone passes through the Zone of Recognition and in so far as someone is placed on a LFR Watchlist for a Deployment. Depending on the nature of the deployment, the then Surveillance Camera Commissioner has identified that there are also potential impacts on other human rights. These include the right to freedom of assembly, freedom of thought, belief and religion, freedom of expression, freedom of association, and the protection of discrimination in respect of those rights and freedoms. Authorising Officers should contact the EP Legal Department should they consider a proposed deployment may have a wider human rights point to consider.
4.5 There is a legal basis for the interference with the qualified right that the public can understand
LFR will be used to allow the EP to discharge its well-established operational duties pursuant to common law. The courts have recognised that “the rules need not be statutory, providing they operate within a framework of law and that there are effective means of enforcing them”.[3]
In the case of R (Catt) v Chief Police Officers [2015] A.C. 1065, Lord Sumption recognised that applicants could have their personal information noted down and retained by the police as they occupied publicly accessible space. The court recognised the police’s common law powers to collect and store information are subject to an “intensive regime of statutory and administrative regulation” under the Data Protection Act and various guidance documents on the management of police information.
The courts have further recognised the right of the police to make use of a photograph of an individual. The courts accepted the purposes of preventing and detecting crime, the investigation of alleged offences and the apprehension of suspects or persons unlawfully at large. This was the case whether or not the photograph is of any person they seek to arrest or of a suspect’s accomplice or of anyone else. The court confirmed the “key is that they must have these and only these purposes in mind and must … make no more than reasonable use of the picture in seeking to accomplish them”.[4]
4.6 In the case of the EP’s use of LFR, the LFR Legal Framework outlines the legal basis for any interference with an individual’s Article 8 rights. The High Court Bridges case confirmed the police’s common law policing powers to be “amply sufficient” in relation to this type of use of LFR and confirmed that “the police do not need new express statutory powers for this purpose”. This was further considered in the Court of Appeal Bridges case which also recognised the sufficiency of the legal framework, noting[5]:
“the legal framework which regulates the deployment of [SWP’s use of LFR] does contain safeguards which enable the proportionality of the interference with Article 8 rights to be adequately examined.”
4.7 The Court of Appeal Bridges decision further noted that, to be ‘in accordance with the law’ the legal basis must:
“be ‘accessible’ to the person concerned, meaning that it must be published and comprehensible, and it must be possible to discover what its provisions are. The measure must be ‘foreseeable’ meaning that it must be possible for a person to foresee its consequences for them and it should not ‘confer a discretion so broad that its scope is in practice dependant on the will of those who apply it, rather than on the law itself”.
4.8 In considering accessibility and foreseeability, the Court of Appeal considered the level of discretion that South Wales Police officers held in the case before it to determine where they deployed facial recognition technology and who they deployed it to locate those on a Watchlist. The court refers to this as the “Who Question” and the “Where Question”.
a) The ‘Who’ Question: When considering how the ‘Who Question’ should be answered, the Court of Appeal made it clear that, the law does not seek specific confirmation as to who is on a Watchlist (they recognise the NCND principle[6]). The Court of Appeal recognised that individuals could be added to a Watchlist on the basis that they are wanted on suspicion of an offence, wanted on warrant and vulnerable persons”.
b) The Court of Appeal also explains why a category of those “other persons where intelligence is required” was not accessible and foreseeable to meet the ‘in accordance with the law’ test. They noted that the category was not readily understood, nor was it objective – it left “too broad a discretion vested in the individual police officer to decide who should go onto the watchlist” – essentially it allowed police officers to decide what ‘other persons where intelligence is required’ meant on a case-by-case basis rather than deciding if a subject met the criteria set out in the force policy.
c) Following an approach recognised by the Court of Appeal[7], EP addresses the ‘Who Question’ in its published EP LFR Documents, particularly at Section 3.7 of the Force Procedure. EP sets the criteria that applies to govern the images that may be included on a Watchlist and in what circumstances. It sets out the standard required for inclusion on a Watchlist, linking the necessity and criteria for the inclusion on a Watchlist with the policing need and the proportionality of taking any action.
d) The ‘Where Question: The Court of Appeal noted that the South Wales Police team “was not able to draw to our attention anything which specifies where AFR Locate may be deployed”. EP LFR Documents answers this question, particularly at Section 3.6 of the Force Procedure. In answering this question, in many instances, the need to locate a person will determine where it is best to site LFR to facilitate making a successful location. However, other factors will also be relevant and these include the nature of the site itself from a privacy perspective, those passing the site, and the policing need to be at the site (including for the public’s protection, supressing crime hotspots, and getting ahead of crime trends).
With the benefit of the Bridge’s decisions, the law has now been applied to the live use of facial recognition technology. These judicial decisions, taken together with the EP’s published documentation to support the use of LFR allows the LFR Legal Framework principles to be predictably applied to the use of LFR in an accessible and understandable way. It allows the public passing an LFR system and those who may be placed on a Watchlist to understand the standards EP operate to, including setting out the authorisation process and requirements to deploy LFR, details about where LFR may be used, and the considerations and constraints relevant as to who may be placed on an LFR Watchlist.
4.9 The use of LFR seeks to achieve a legitimate aim
Article 8 recognises action in the interests of national security, public safety and the prevention of disorder and crime as legitimate aims. The use of LFR in the context of assisting EP reduce violence by locating violent offenders will help EP achieve its law enforcement purposes.
The means by which EP may use LFR will be an operational decision within the parameters of the law and EP LFR Documents. It will need to be driven by the policing issue at hand. This may vary from the need to locate those wanted in connection with criminality or otherwise pose a risk of harm, to more preventative tactics designed to bring reassurance to communities and enable the use of precision technology to more proactively focus policing resources.
Authorising Officers: At the point that it is decided to deploy LFR, the decision maker must be clear as to its purpose and how using LFR will help EP realise a legitimate aim. In deciding if the use of LFR is a suitable way to achieve a legitimate aim, the decision maker must consider if benefits of using LFR justify its use for the legitimate aim when compared to any impact on the individual’s Article 8 Rights.
4.10 The use of LFR is necessary for the purposes of that legitimate aim in a democratic society
LFR will be used in response to a pressing social need by helping EP combat crime in areas where LFR has the greatest potential to assist. It is a tool that helps EP to discharge its operational responsibilities, primarily to help prevent and detect crime and protect the most vulnerable.
Authorising Officers: When considering the Deployment of LFR, its use is to be underpinned by an intelligence case to highlight the need to combat the relevant crime or public safety issue or policing need to deploy. Having identified a need, this will allow the Authorising Officer to consider the use of LFR. Authorising Officers must decide the use of LFR is necessary and not just desirable to enable EP to achieve its legitimate aim. In deciding the use of LFR to be necessary, the issue which LFR was intending to address and how LFR would be deployed to address that problem.
The following is an example of why LFR may be used as a necessary tool to assist EP in preventing crime and disorder. The examples are illustrative only and there will be other scenarios where the use of LFR is justified.
Violence: The use of LFR will assist EP in tackling violence. LFR could be deployed based on intelligence and analysis to areas of the county in which violence is high and continues to be high despite Police intervention. LFR will assist be allowing EP to locate those suspected of violent offences within that policing area and arrest them. The arrest of these outstanding suspects along with the deterrent effect of LFR deployments would reduce the changes of disorder occurring within that locality.
Additionally, in a climate where police forces need to operate efficiently, EP has also identified that technology such as LFR can assist with the challenges of quickly and cost efficiently locating those with outstanding warrants or who have otherwise breached their bail conditions. It is right and appropriate to bring those who are unlawfully at large to justice noting the need to protect the public in such circumstances. The High Court Bridges case supports that there is a “considerable additional benefit to the public interest to including those wanted on a warrant” for a Deployment of LFR, even when there is no specific intelligence to place them in the area of the Deployment. The intrusion to those passing the system is no greater, but (i) the potential to protect the public from those wanted by the courts, (ii) the results from Deployments where those with outstanding warrants were included and (iii) the resultant arrests justified the inclusion of those with outstanding warrants from the courts as a necessary action to bring offenders to justice.
4.11 The use of LFR is proportionate to legitimate aim being sought
When considering the Deployment of LFR, the benefits of using LFR for an investigation or operation should not be disproportionate or arbitrary. In this respect the Surveillance Camera Commissioner recognises that:
“used appropriately, current and future technology can and will provide a proportionate and effective solution where surveillance is in pursuit of a legitimate aim and meets a pressing need”.
In this respect, the following factors (amongst others, depending on the nature of the Deployment) will guide Authorising Officers:
a) The use of LFR should be a reasonable use of EP powers - it will not be proportionate if the proposed use of LFR is excessive in the overall circumstances of the investigation, operation or wider operational strategy to tackle a policing issue.
Authorising Officers will need to consider the seriousness of the policing issues at hand and the potential benefits of using LFR and balance this with any wider impact its Deployment may have to those on a Watchlist and the public at large. This will allow a decision to be made as to whether LFR is appropriate for use. Authorising Officers must give consideration to the composition of the Watchlist compiled for the LFR system to match against, to ensure that it is not compiled in an excessive manner. The Watchlist needs to satisfy the necessity and proportionality test and will therefore be driven by the intelligence case and bespoke for each Deployment of LFR to ensure it meets the aims of each Deployment.
With this in mind, the Watchlist compiled for each deployment of LFR should be current; based on those currently of interest to EP and/or wider UK law enforcement to mitigate the risk of the LFR system matching with those no longer of interest to EP and/or wider UK law enforcement.
b) Consideration should be given as to the extent of any proposed interference with privacy against what is sought to be achieved and if there are other viable methods to achieve the aim which involve a lower level of interference.
The use of LFR should be considered against other methods of locating persons of interest to EP and/or UK Law Enforcement and other policing tact ics which may help tackle the policing issue at hand. Consideration should be given as to the effectiveness and intrusiveness of other viable methods that could give the same result, with the least intrusive, viable method being adopted to progress an investigation or Deployment.
Example: Circulating a wanted image in the media may be considered as an alternative to the use of LFR.
The use of LFR can be targeted to a specific area and does not result in the public being made aware of the identity of a person being sought by the EP. It can also be used for a limited period, targeted, based on wider intelligence, to times and places when it might be most expected to locate an individual.
By comparison, media results in a person’s image being put into the public domain in a less targeted way. Once released, the image is public, and EP no longer has control of that image. It therefore has potential to remain online even when the person has been traced and thus is a greater intrusion into the privacy of the individual being sought.
The Authorising Officer considering the use of LFR should balance any intrusion into privacy against the need for the investigative activity. If the Authorising Officer uses LFR in a way which minimises any impact it may have on a person’s privacy as far as possible, it may offer a more appropriate, less intrusive alternative to a social media
Authorising Officers: When taking a decision to deploy LFR, Authorising Officers should record what other methods, as appropriate, were either not implemented or have been employed but which were assessed to be insufficient or inappropriate to fulfil EP’s aim.
c) How and why the methods adopted will cause the least possible interference to the person(s) sought and others must be addressed.
All uses of LFR under this Legal Mandate will be overt. LFR will be used for a limited time –with a limited footprint, with a defined purpose (controlled by way of EP LFR Documents). The LFR system will be visibly deployed in an open and transparent way. Consistent with the principle of engaging with the public, EP LFR Documents also provides a structure for awareness measures which respond to the nature and objectives of the use of LFR.
Proportionality controls. Controls are also designed in to the LFR system and its operation to help minimise any impact on the public and those placed on a Watchlist as follows:
I. LFR cannot be used to locate persons unless they have been included on a Watchlist.
II. The creation of any Watchlist is specific to the Deployment of LFR and informed by the intelligence case for the Deployment; this is to ensure the currency, relevancy, necessity and proportionality by which any image is included for potential matching.
III. Images on a Watchlist will be lawfully held by EP with all reasonable steps being taken to ensure that the image is of a person intended for inclusion on a given Watchlist.
IV. Authorising Officers need to expressly consider and approve the use of non-police originated images on any Watchlist. This is because particular privacy considerations may attach to an image where it originates from outside of a policing context. For example, it may be that the image was not placed in the public domain, was taken in a place that attracts a higher expectation of privacy or is an image that was supplied to, or taken by a third party for a specific purpose that does not usually see routine data sharing with the police. Even when EP can lawfully hold the images, the need for the Watchlist to be a proportionate policing response requires the Authorising Officer to undertake a careful assessment of an individual’s privacy expectations against the policing need to locate them using LFR. The EP Force Procedure outlines considerations for Authorising Officers at Section 3.7.
V. On adding an image to the Watchlist the LFR system will assess the image for quality and suitability for matching in order to allow EP personnel to consider and manage the risk of poor-quality images generating inaccurate LFR Alerts.
VI. All Watchlists are deleted as soon as practicable, and in any case within 24 hours following the conclusion of the Deployment.
VII. The cameras used in the LFR system are of sufficient quality for the LFR system’s needs.
VIII. The LFR system is designed to assist EP personnel locate people. The LFR system will always flag potential matches to at least one officer for a decision on any further action rather than autonomously taking a decision on any action after making a potential match.
IX. LFR Deployments and the materials that support LFR Deployments will be subject to periodic review to ensure that the LFR system and its operation remains necessary, proportionate and effective in terms of meeting its use case.
Controls have also been implemented with regards to personal data retention to minimise the impact on the wider public and those on the Watchlist. The controls provide that:
1. where the LFR system does not generate an Alert, then a person’s biometric data is immediately automatically deleted; and
2. watchlists are deleted as soon as practicable, and in any case within 24 hours following the conclusion of the Deployment.
3. where the LFR system generates an Alert, all personal data is deleted as soon as practicable and in any case within 24 hours following the conclusion of the Deployment.
All CCTV footage generated from LFR Deployments is deleted within 31 days, except where retained:
1. in accordance with the Data Protection Act 2018, MOPI and the Criminal Procedures and Investigations Act 1996; and /or
2. in accordance with the EP’s complaints / conduct investigation policies.
Deployment location privacy considerations. Many Deployment locations will be identified as being necessary by the intelligence case supporting the prospects of locating persons at the site and/or how LFR plays a role within wider policing tactics. However, Authorising Officers must also consider the reasonable expectations of privacy the general public may have as a whole may have when traversing a public place where LFR is being considered for Deployment. Some places, and the people expected to be at some places by their nature attract greater privacy expectations than others. Authorising Officers also need to consider what measures are appropriate to identify the use of LFR when it is deployed, particularly where expectations of privacy may be greater. This is important to establishing if the proposed use for LFR, and the Deployment location itself is proportionate.
Authorising Officers should also consider if a proposed Deployment location attracts particular privacy concerns by reference to those expected to be at a particular location.
Example: Areas particularly focused on providing facilities or attractions aimed at children would typically attract greater privacy expectations over an area that typically sees attendance from the public more broadly. The public would not typically expect LFR to be sited outside a toy shop or school that may disproportionately see children passing the LFR system if the LFR system could be sited elsewhere. There may nevertheless be instances where the intelligence case, and the need to protect children makes it necessary and proportionate to deploy LFR to these areas. For example, if it is known that wanted sex offenders are targeting those that visit the location and it not possible to locate them by siting LFR elsewhere or using other less intrusive policing tactics. If it is necessary to use LFR at the location, mitigations to reduce the privacy impact should be used wherever possible. This could include extra measures to ensure that the signage and information about the LFR Deployment is accessible to children who pass through the Zone of Recognition. The signage should be tailored to children where necessary. Where it is possible to so, and does not increase the risk to children, the time of a Deployment and configuration of a Zone of Recognition should also seek to minimise the numbers of children assessed by the LFR system.
Areas assessed as having high expectations of privacy which give the public little option to avoid the LFR area without substantial inconvenience should generally be avoided unless the following mean that the Authorising Officer is satisfied the use of LFR in the circumstances remains necessary and proportionate:
1. the importance of using LFR in that location to realise a legitimate aim supports LFR’s use;
2. the lack of a viable, less intrusive alternative available for use in the circumstances; and
3. any further mitigations to reduce any impact to the wider public in so far as it is possible to do so.
Example: If there was a necessity and proportionality case, based on intelligence, to deploy LFR in a residential suburban area to locate a group of burglary offenders, then we understand there may be a greater expectation of privacy in this area when compared to a non-residential area. To mitigate this, depending on the circumstances we may provide additional communication about the use of LFR, for example by leafleting local residents or posting on local neighbourhood social media groups.
Authorising Officers: When taking a decision to deploy LFR, Authorising Officers should record the measures taken to ensure the use of LFR causes the least possible interference to the person(s) sought and others. This should include explicit reference to any particular privacy considerations that may be relevant to a Deployment location and any mitigations in place to impact the impact of the LFR Deployment. Authorising Officers should then continue to review Deployments of LFR to ensure the use case remains appropriate.
4.12 Wider Human Rights Act considerations
The right to privacy is a value which protects the autonomy and human dignity of individuals by enabling them to conduct their lives in a way of their choosing. There are therefore circumstances when freedom of thought, conscience and religion (Article 9), freedom of expression (Article 10) and freedom of assembly and of association (Article 11) may be particularly relevant.
a) Article 9. The clothing people wear can be an act of thought, conscience and religion and in normal circumstances, the police do not have the legal power to require a person to remove clothing (including any headdress) simply because they are passing the LFR system. Additionally, the location where people may pass the LFR system may also engaged Article 9.
Example: The use of LFR can assist EP to ensure public safety, including at a place of worship where the intelligence case has identified a threat to the public. A decision to place a LFR Deployment outside a place of worship or in a way that substantially impedes access to a place of worship can engage Article 9. In this context, the public safety considerations need to be balanced against the need to use LFR at that location. If the public safety policing objectives could be achieved by deploying the LFR system elsewhere, it would not be necessary to deploy LFR at the proposed location. If the threat that makes it necessary to site LFR near to a place of worship, Authorising Officers also need to determine if the infringement on Article 9 rights is disproportionate to the likely benefits of using LFR. Considerations would typically include the impact on those seeking to access a place of worship, the likely impact on the same people without LFR (being potentially impacted by other policing measures or site closures) and the benefits to safety LFR brings the public.
b) Article 10 and 11 have particular relevance when considering both the policing of assemblies and demonstrations and any use of LFR which may impact on an assembly or demonstration. Article 10 is especially pertinent should people have reservations about expressing themselves as a result of an LFR Deployment. Article 11 is also relevant should the use of LFR deter people from attending an assembly or demonstration at all or otherwise cause people to minimise their involvement.
Example: The use of LFR can assist EP in policing an assembly or demonstration, particularly where there is an intelligence case supporting there being a risk to public safety. Specifically, LFR can support police officers by efficiently searching for perpetrators of violence in crowded locations where it might otherwise be difficult to locate them. In deciding the use of LFR is necessary and proportionate, regard should be had to an individual’s Article 10 and 11 rights – noting there may be expectations of anonymity in a crowd and that individuals may choose to alter their means of demonstration as a result of the LFR Deployment.
Article 10 and 11 rights must be weighed against the need to use LFR to enable an assembly that might otherwise be disrupted by the risk to public safety. In making this decision, consideration should be given to factors which could minimise the impact of LFR. These include limiting the use of LFR in time and scope to the minimum needed to ensure safety. They could also include there being focus placed on ensuring the public understand the use of LFR is to help them safety undertake their assembly.
c) Operational Duties
The ‘operational duty’ was first outlined in the case of Osman v United Kingdom[8] and concerned an alleged failure to prevent the young victim and his family from the risk to life posed by a stalker. The European Court of Human Rights in Osman found that the police were under a positive duty to take reasonable measures to avert a real and immediate risk to the life of an identified individual or individuals of which the police were, or ought to have been aware. Caselaw also supports that the police are under an Osman style duty to investigate serious allegations in a timely and efficient manner in order to uphold an individual’s Article 3 rights.
The Osman operational duty has particular relevance to LFR in two contexts (i) being used to locate those posing a threat to the public or themselves where a real and immediate risk to life is identified and LFR is thought to provide an appropriate response to such risk and (ii) on an Alert being generated where the need to locate that person may engage the Osman operational duty with measures being put in place should a person generating an Alert seek to evade officers.
d) Article 14. This right requires that all of the rights and freedoms set out in the Human Rights Act 1998 must be protected and applied without discrimination. This is based on the principle that everyone, no matter who they are, should enjoy the same human rights and have equal access to them. Article 14 is not a stand-alone right – there is a need to show that discrimination has affected the enjoyment of one or more of the other human rights, not that the other rights have been actually breached. The use of LFR will be relevant in circumstances where demographic performance of the LFR algorithm varied to such an extent that people of a particular demographic were more or less likely to see a False Alert generated against them. As a result there are two points to consider in relation to the LFR system (i) does the LFR system’s demographic differential performance vary by a particular demographic such as it results in a person suffering a discriminatory effect and (ii) if there is a different in treatment, is this capable or an objective and reasonable justification.
[1] (2009) 48 EHRR 50, at [66 and 67]
[2] At [104]
[3] R (Catt) v Association of Chief Police Officers [2015] A.C. 1065 at [11].
[4] Per Laws J in Hellewell v Chief Constable of Derbyshire [1995] 1 WLR 804 at 810F
[5] At [69].
[6] At [95].
[7] At [118].,
[8] [1999] 1 F.L.R. 193 (ECtHR)
5.1 The Equality Act 2010 provides a legal framework to protect the rights of individuals and advance equality of opportunity for all. The Equality Act 2010 prohibits discrimination based on different treatment on the basis of a protected characteristic. The prohibition of discrimination applies to both direct and indirect discrimination. As a public authority, EP must comply with section 149 of the Equality Act 2010 which is most commonly known as the Public Sector Equality Duty (“PSED”).
5.2 EP is required to take measures to ensure that the use of LFR complies with the Equality Act 2010. Particular attention is needed in two respects: (a) the technical performance of the LFR system (and then, if performance varies by any particular demographic), and (b) the operational Deployment of the LFR system:
a) The technical performance of the LFR system.
The Court of Appeal Bridges decision makes it clear that the PSED requires EP to take reasonable steps to satisfy itself, either directly or by way of independent verification, that the algorithm in this case does not have an unacceptable bias on grounds of race or sex. To assist the public with understanding how EP meets its PSED duties, EP has published the EP LFR Equality Impact Assessment.
The selection of a live facial recognition (LFR) provider by Essex Police had a strong focus on the need to satisfy the PSED and in this context the chosen provider of the LFR software was asked to provide details of any independent bias testing that had been conducted. Currently there is no nationally agreed standard for LFR, and no nationally approved or mandatory testing is available. It is therefore up to individual police forces to make reasonable endeavours to obtain details of any independent testing that has been conducted in relation to their chosen software from the supplier and to ensure that the software is as accurate and free from bias as possible. In addition to ensuring that independent bias testing has taken place, and that the results of the testing are acceptable to the Force in terms meeting the PSED, Essex Police have also developed robust operational policy and procedures to ensure that the criteria for the deployment of LFR and the way it is used by officers helps the Force further reinforce their compliance with the PSED. In addition, work has been undertaken to develop an evaluation framework for LFR which will be subject to independent academic review, and the Force is committed to ongoing testing of the software. Essex Police have also sought advice from their own independent Data and Digital Ethics Committee in relation to their use of LFR generally its deployment.
Essex Police have contracted with Digital Barriers for LFR who provide LFR software from Corsight. Corsight have provided information in relation to the independent testing of their LFR software
Corsight has advised that their “algorithms have been vigorously tested independently for both accuracy and bias by the National Institute of Standards and Technology (NIST) and the Department of Homeland Security (DHS) in the US and have provided details of the results of testing in 2022. In both tests, Corsight’ s algorithms were found to have one of the lowest bias differentials available of any algorithm tested. Bias differential is a calculation that distinguishes false-match rates (FMR) between varying demographic groups (gender, skin tone) to distinguish if there is more, or less, likelihood of a false-match when comparing two images of different demographics. The aim of all algorithms is to have a small as possible FMR difference between all demographic categories to ensure there is no more likelihood of a false match between one demographic or another. Within NIST testing, when focusing on bias, every algorithm’s performance is summarized and compared to one another via setting a common FMR (0.0010) on the most likely demographic to give the lowest FMR (Male White: Male White). By doing this, all other demographics are then compared to the same base line to produce an FMR to give a comparable value between algorithms. Within this test, Corsight’ s algorithm is identified by NIST as having the lowest bias variance between demographics and is used in every algorithms report as a direct comparison underlying its superior performance.” The NIST report gives the Corsight_003 algorithm a bias differential FMR of 0.0006 overall, the lowest of any tested within NIST at time of writing according to the supplier.
Corsight have also provided details of testing completed by the Department of Homeland Security testing in the US, also in 2022, which was “focussed on testing biometric algorithms in realistic, high-traffic conditions based on varying qualities of image acquisition systems. The Corsight algorithm was top-ranked for accuracy and for being unbiased toward gender or race based on their test conditions. DHS testing is based on system aliases … It achieved a 99.8% overall Matching True Identification Rate (TIR) and over 99.3% TIR for all skin tone groups across all acquisition systems, and under some acquisition systems had 100% TIR, demonstrating Corsight’ s capability to perform equally across all demographics.”
b) The operational Deployment of the LFR system.
EP LFR Documents are also responsive to the Subject, System and Environmental Factors to ensure the LFR system is suitable for its intended use and operating correctly. Subject, System and Environmental Factors including aspects such as camera configuration, camera location, lighting conditions, the distance at which people will pass the LFR system, crowd flow levels in so far as this may result in occlusion (including by reference to the height of the subjects being sought) and points relating to an individual’s age and appearance have been considered carefully in EP LFR Documents to ensure the efficacy of the LFR system and the EP’s compliance with its Equality Act 2010 duties.
By way of example, EP LFR Documents provide that LFR Operators are trained to identify Watchlist issues with proposed images which may impact on system performance. Where the need to use an image is deemed to be necessary and proportionate, those using the LFR system have received training to maximise the LFR system’s performance and to effectively consider any issues arising from the use of such images as part of the identification process.
As a result of having taken reasonable steps to understand the statistical accuracy and demographic performance of the EP LFR system and then in light of points relating to Subject, System and Environmental Factors, and the framework of safeguards implemented as a result, EP has adopted a ‘fail-safe’ position to ensure that absent there being other lawful grounds to take policing action:
No Engagement will occur with a member of the public unless at least one officer has reviewed an LFR system potential match and reached their own opinion that there is a match between the member of the public and the Watchlist image.
This means the LFR system is not making any decision to Engage with the public, the officer is making this decision - just as officers make similar decisions to Engage with members of the public every day (without the support of LFR). The officer is best placed to make this decision, drawing on their training and policing experience.
Similarly, the officer is best placed to consider the impact of any Subject, System and Environmental Factors which may have influenced the LFR system when it generated an Alert and if such factors combine to mean an Engagement with a member of the public is not appropriate in the circumstances.
Authorising Officers: In order to ensure that the officer is best able to make an informed decision on any Engagement, all officers who are part of an LFR Deployment are to have been briefed on the operation of the LFR system. This includes Subject, System and Environmental Factors that can impact performance. LFR Engagement Officers should also have been given training relating to unconscious bias given their key role in the Engagement decision making process.
Beyond Subject, System and Environmental factors, EP personnel are also familiar with managing the PSED requirement whilst undertaking policing activities from a number of other crime fighting techniques, for example, ‘stop and search’. In this respect, it is important that the use of LFR is driven from the need to meet a legitimate aim, such as the prevention of crime and disorder. The Equality Impact Assessment informs the policing plan to support the Deployment of LFR to mean EP upholds the Public Sector Equality Duty. Compliance with the Equality Impact Assessment will then be monitored and reviewed for the duration of that Deployment.
6.1 EP processes personal data for LFR ‘based on law’; specifically, its legal powers identified in relation to the common law as well as human rights and equality considerations as outlined in this Legal Mandate, and the policies put in place by EP LFR Documents. The Appropriate Policy Document and other EP LFR Documents published by the EP as a public body allows the public passing an LFR system and those who may be placed on a Watchlist to understand the standards EP operates to, including setting out the authorisation process and requirements to deploy LFR, details about where LFR may be used, and the considerations and constraints relevant as to who may be placed on an LFR Watchlist.
6.2 For the purposes of preventing crime and disorder, Part 3, Data Protection Act 2018 (DPA) regulates the processing of personal data, including sensitive processing, whether processed on a computer, CCTV, still images or other media. Any recorded image from a device which can identify a particular person is ‘personal data’. The DPA therefore applies to the processing of data for LFR both in terms of locating those on a Watchlist but also in terms of processing biometric information of members of the public to confirm they are not on a Watchlist. These actions are covered by the processing of data for law enforcement purposes, as defined in s.31 DPA:
“For the purposes of this Part, "the law enforcement purposes" are the purposes of the prevention, investigation, detection or prosecution of criminal offences or the execution of criminal penalties, including the safeguarding against and the prevention of threats to public security.”
Authorising Officers: Authorising Officers already need be satisfied of the necessity to use LFR to prevent crime and disorder and ensure public safety in the context of the Human Rights Act 1998. Similarly, to satisfy Section 35(5) DPA, they need to be content that the LFR system’s processing of biometric data is strictly necessary for the law enforcement purpose. The law enforcement purpose should be clearly identified and the way in which the strictly necessary standard has been met explained.
a) Strictly necessary in this context means that the processing has to relate to a pressing social need, and it is not reasonably viable to address this through less intrusive means. Any personal data collected via LFR is not used in a manner that is contrary to the identified law enforcement purpose.
Example: alternative policing methods to prevent threats to public security: LFR may be deployed to police a high profile well-attended public event. When considering alternatives, in this example, other measures such as extra CCTV may be considered. However, they will not always be a viable less intrusive alternative in the circumstances. For example:
1. Whilst CCTV can help ensure event safety, it lacks the ability to actively Alert officers to the potential presence of individuals of interest to them.
2. It may not be practical to expect officers to recognise larger numbers of people of interest to the Police given the nature and scale of the event, the numbers of officers available to police the event and the flow rate and number of people passing the CCTV system. This is especially relevant where the importance of making such identifications supports the use of a more suitable alternative such as LFR.
3. Where LFR is thought to offer further important protection to the public as opposed to other policing methods. For example, this may apply where the law enforcement purposes for a Deployment include wider public safety considerations. These may include the need to locate those wanted by the courts. Such persons may attend such a high-profile event and, in line with the decision of the courts to require their arrest, pose a risk to the public generally.
b) The ‘strictly necessary’ standard may be informed by the Authorising Officer considering factors including:
1. what other policing methods have been used / discounted when seeking to locate an individual(s) on the Watchlist or to provide a series of tailored security measures;
2. the importance of achieving the law enforcement purpose and the prospects of achieving the law enforcement purpose through the Deployment of LFR at the proposed location with the proposed Watchlist (for example, is the Deployment intelligence-led or otherwise supported by information which confirms that LFR can be expected to get results in the circumstances being contemplated);
3. the size and scale of the planned LFR Deployment and associated Watchlist and the level of sensitive processing anticipated as a result of the LFR Deployment; and
4. if the law enforcement purpose which underpins the use of LFR is strictly necessary and proportionate to the need to undertake sensitive processing and the risk to individuals’ rights this entails (subject to the protections and safeguards implemented).
Authorising Officers: Authorising Officers need to be satisfied that the processing satisfies one of the Schedule 8 conditions set out below and complies with the six data protection principles.
6.3 Schedule 8 conditions of the DPA are engaged:
Example: The use of LFR will assist EP in fighting knife crime in support of its common law policing powers. LFR could be deployed to identify wanted offenders who have failed to comply with court bail relating to such offences. Used in this way, LFR would assist in the prevention, investigation, detection or prosecution of criminal offences.
LFR offers advantages over other potential policing methods such as a police officer using a picture or a physical description to scan a crowd and try and spot an offender where positive results would otherwise be less likely and the risk of people being missed, higher. Given the importance of tackling serious and violent crime, a clear law enforcement purpose can be identified. In this context LFR’s use may be seen as strictly necessary to support the investigation of knife crime, to enable the EP to effectively respond to a pressing social need.
Similarly, the Schedule 8 condition of being necessary for judicial and statutory purposes for reasons of substantial public interest can be seen in this context to include a police officer working for the prevention, investigation, detection or prosecution of offences to keep the public safe. For similar reasons, the court in the Bridges cases accepted the substantial public interest in the police using LFR to discharge their common law policing duties.
6.4 EP has also undertaken a number of steps in accordance with the Data Protection Impact Assessment (DPIA) to manage and mitigate the impact of any personal data processing using the LFR system. Particular actions are set out in the remainder of this section.
6.5 Data Protection Impact Assessment:
A DPIA has been conducted to support the use of LFR in order to identify and minimise the data protection risks. Whilst the LFR DPIA will be under constant review and no later than on an annual basis, Authorising Officers authorising the use of LFR should ensure there is a DPIA in place which is sufficient for each Deployment. Specifically, consideration should to be given to:
a. if the risks and controls remain current and sufficient for the planned use of LFR; and
b. if the planned use for LFR poses any other risks which are capable of mitigation beyond those identified in the DPIA.
6.6 Data Protection by Design:
A number of data protection controls have been designed into the LFR system in order to mitigate processing impacts on privacy and to comply with the general obligation in Part 3 of the DPA to implement appropriate technical and organisational measures having considered and integrated the principle of data protection into LFR processing activities. The designed-in measures identified at paragraph 4.11(c) of this document, include measures to:
a. limit the amount of personal data collected;
b. limit the extent of personal data processing;
c. limit the period of personal data storage.
Additionally, EP has acted to ensure that the LFR system performs to a level where the statistical accuracy of the data being processed and fairness ‘by design’ is ingrained into EP’s LFR system. EP LFR Documents and other published supporting information explain how EP is assured that its LFR system operates with a high degree of statistical accuracy and in a way that does not lead to unjust results between demographics.
Further consideration has been given to limiting access to any personal data retained for the 31 day period. The LFR system also includes a number of physical and technical security measures including:
a. Images are transferred onto the LFR system using a secure file transfer system.
b. The LFR system is a fully closed system with two layers of password protection to access the application. The LFR system is physically protected when in use and securely wiped following each Deployment;
c. Role based access controls with limited user permissions are implemented on the LFR system;
d. The LFR application is connected to mobile devices using a private access point with three levels of protection (i) specific IP addressing, (ii) password access to the access point, and (iii) password access to the mobile app. The mobile app has a RESTful API and will be covered by SSL;
e. The Dashboard and RESTful API are secured with SSL and TLS by default;
f. All connections are directed through HTTPS within a closed system;
g. A full audit is maintained of all user initiated actions undertaken during the course of a Deployment; and
h. Technical issues with the LFR system are always dealt with by member of the technical staff who support the Deployment of the LFR system.
6.7 Appropriate Policy Document:
Section 42 of the DPA requires that, at the time that the processing is carried out, the controller has an appropriate policy document in place. EP has produced this document and published it. This document allows the public to understand details of the:
a. the data being processed by the LFR system, how often it is processed and whose data is processed;
b. procedures, safeguards and accountability principles for complying with the data protection principles when relying on a condition from Schedule 8 to process biometric personal data both for those on the Watchlist and those passing an LFR system;
c. EP policy for the retention and erasure of personal data for LFR processing.
6.8 Data Protection Officer:
EP has appointed a Data Protection Officer (DPO) in compliance with Part 3 DPA who has been consulted in relation to LFR. The DPO is available to inform and advise the Chief Constable (as data controller) and EP personnel about their obligations in relation to the DPA. The DPO also provides an internal function to monitor compliance with the DPA.
7.1 As part of EP’ common law powers to protect and preserve life and property, we process special category data in accordance with the requirements of Article 9 of the UK GDPR (which is incorporated into UK law under and supplemented by Part 2 and Schedule 1 of the DPA).
7.2 The Schedule 1 DPA conditions for processing special category data require EP to have an APD in place, setting out and explaining our procedures for securing compliance with the principles in Article 5 GDPR (relating to processing of personal data) and policies regarding the retention and erasure of such personal data.
7.3 Article 9 conditions of UK GDPR are engaged:
7.4 Section 10 DPA supplements Article 9 GDPR, requiring the following conditions of Schedule 1 to be satisfied (historical research part 1 of schedule 1 / substantial public interest part 2 of schedule 1).
7.5 Schedule 1 DPA (part 1) are engaged:
7.6 Schedule 1 DPA (part 2) are engaged:
7.7 Appropriate Policy Document (APD):
Schedule 1 DPA conditions for processing special category data require EP to have an APD in place, setting out and explaining our procedures for securing compliance with the principles in Article 5 of the UK-GDPR. EP has produced this document and published it. This document allows the public to understand the details of the:
a. the data being processed by the LFR system, how often it is processed and whose data is processed;
b. procedures, safeguards and accountability principles for complying with the data protection principles when relying on a condition from Article 9 to process biometric personal data for those on the Watchlist and those passing the LFR system.
c. EP policy for the retention and erasure of personal data for LFR processing.
The Protection of Freedoms Act 2012 (PoFA) has seen the introduction of a new surveillance camera code issues by the Secretary of State (the Code) and the appointment of a Biometrics and Surveillance Camera Commissioner. Section 33(1) PoFA requires EP to have regard to the Code for the use of LFR. This includes compliance with the 12 guiding principles that system operators should adopt. The Code makes a number of specific points in relation to automated recognition technologies which EP have regard to as follows:
EP processing information publicly available to data subjects. It makes information relating to the LFR and data processing available via its website. The LFR Deployments are publicly disclosed with supporting information.
The necessary systems are addressed EP LFR Documents.
These measures have been addressed by design and are also covered in EP LFR Documents.
This requirement is addressed by the design of the LFR system.
The LFR system will always flag possible matches to a trained member of EP personnel for a decision on any further action. In this way, the LFR system works to assist EP personnel to make identifications rather than acting as an autonomous machine-based process devoid of user input.
The Freedom of Information Act 2000 (FOIA) provides public access to information held by public authorities. It does this in two ways:
9.1.1 public authorities are obliged to publish certain information about their activities;
9.1.2 members of the public are entitled to request information from public authorities.
In recognition of its FOIA duties, EP makes significant LFR information available via its website. This includes summary information relating to LFR Deployments including the Watchlist size, the total number of Alerts, positive action and incorrect identification numbers, arrests and disposal numbers and estimates of the total number of faces seen as people passed the LFR system. EP will also be responsive to FOIA requests.
10 summary of existing legislation and related governance regards policing’s overt use of Live Facial Recognition Technology