{"resourceId":"wa-police-lfr-trial-controls-202609","versions":[{"version":"external-2bf0f7e045a0fd81e5a5014484af3687c4b360691f09c5d61b4e44306bdb055e","resource":{"id":"wa-police-lfr-trial-controls-202609","title":"Western Australia publishes facial-recognition trial controls ahead of listed deployments","organization":"Western Australia Police Force","sector":"Policing and oversight","geography":"Western Australia; limited U.S. transferability","publishedAt":"Live page last updated September 8, 2026; original publication date unknown","publicationDate":null,"eventDate":null,"sourceName":"Government of Western Australia","sourceLabel":"Operator trial guidance, with linked equality impact assessment","sourceUrl":"https://www.wa.gov.au/organisation/western-australia-police-force/live-facial-recognition-technology","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The operator describes a facial-recognition trial with human alert review and deployment authorization; the inspected register contains no outcome results.","sledRelevance":"A recent international implementation-control example for U.S. oversight discussions, not transferable legal authority or proof of local effectiveness.","evidence":"The page lists Geraldton deployments for September 11 and 12 as planned. It states non-alert biometric data is immediately deleted and that results will be posted. The linked May 2026 equality assessment sets out accessibility and demographic monitoring controls. Supporting assessment: https://www.wa.gov.au/media/161113/download?inline=.","architectureImplications":"Interpretation: Separate temporary matching data from retained alert evidence and verify each retention path through the complete deployment stack.","governanceImplications":"Interpretation: Define stop authority, permissible watchlists and independent review before field use.","securityPrivacyImplications":"Interpretation: Test deletion claims and prohibit unauthorized secondary use; policy statements are not configuration evidence.","caveats":"No local accuracy, sample size, baseline or crime-outcome result is supplied. External benchmark claims were not independently verified. Planned dates are not completed deployments. Australian powers and equality obligations do not transfer to U.S. jurisdictions.","streamIds":["public-safety"],"roles":{"sales":"Interpretation: Police leadership, privacy officers, community representatives and procurement staff need to assess whether a proposed identification workflow is justified. Ask which problem requires live matching, whether less intrusive alternatives exist, and what evidence would support stopping the trial. A bounded engagement could build a decision and assurance plan before any purchase commitment. The value hypothesis is a testable, accountable decision rather than guaranteed arrests or efficiency. The operator's guidance supplies control questions, not a validated business case. Qualify local legal authority and community expectations separately; a foreign announcement does not establish a U.S. market opportunity or prove that the technology is appropriate.","engineering":"Interpretation: Fit is conditional on a locally authorized, bounded trial. Inventory cameras, watchlist versions, thresholds, temporary templates and retained alerts. Prerequisites include representative validation data and access to deployment configuration. Test low-quality images, changed appearance, duplicate records, network loss and unauthorized queries. Verify that deletion and audit requirements coexist without retaining unnecessary biometric data. A proof of value should independently adjudicate alerts and examine misses using an authorized reference set, then measure reviewer workload and demographic differences. Cloud or local processing should follow latency and sensitivity requirements; the public page does not establish the full architecture or validate any deployment choice.","delivery":"Interpretation: A deployment commander should work with privacy, independent assurance and accessible public-engagement teams. Establish the trial boundaries, train operators on uncertain matches, rehearse stop procedures and schedule reviews before scaling. Dependencies include usable logs, permissions to evaluate performance and a staffed complaint route. Proposed acceptance: every test alert has an accountable human disposition, deletion tests pass, and the agreed performance and community-impact scorecard is complete. These are suggested checks, not observed results. Risks include conflating published controls with actual compliance, treating a match as sufficient authority, and overlooking cumulative impacts from repeated exposure."},"retrievedAt":"2026-09-11T03:00:57Z","enrichedAt":"2026-09-11T03:05:16Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Rehearse public explanations and complaint intake with people who cannot rely on online notices.","procurementImplications":"Interpretation: Require inspectable configuration, performance definitions and audit access before a trial is expanded.","operatingModelImplications":"Interpretation: Assign separate deployment, alert-review and assurance responsibilities, with a documented route to halt use.","sourceVerification":{"openedUrl":"https://www.wa.gov.au/organisation/western-australia-police-force/live-facial-recognition-technology","referenceExcerpt":"An alert is not, by itself, grounds to arrest or exercise powers.","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}