The figure represents more than half of Raleigh’s department of more than 700 sworn officers. It also leaves public questions about who has access, what different users can search and how quickly inactive accounts are disabled.

What the August audit shows

The 416-user figure is an audit finding dated August 5, not a permanent current total. In this context, “active” describes how an account was classified in the system; it does not establish that every listed user logged in or conducted a search.

During the audit period, only about half of the listed users logged into Flock. WRAL also reported that an April 2026 audit listed 417 active users, including 239 who did not log in during that evaluation period. That audit said 148 had not logged into Flock at all in 2026.

Those figures matter because Flock systems collect automated license-plate data that law enforcement can use in investigations. The broader the account list, and the less clearly access is divided by job role, the harder it is for residents to evaluate whether permissions match investigative need.

Former employees appeared in earlier records

Internal audits from April and May identified former employees among people listed as active Flock users, according to WRAL Investigates. A follow-up audit in July no longer contained that language.

Raleigh police told WRAL that the former employees were still classified as having active Flock registrations but could not access the database because they no longer had active city-issued email accounts or phone numbers needed for two-factor authentication. The department said it had kept the accounts in the system in case those employees returned to work for Raleigh police.

After the audit findings, the department said it ended that practice and removed the former employees from the system. The available reporting does not say that the former employees accessed Flock data.

Key access questions remain unanswered

Raleigh police has not publicly provided a detailed breakdown of the 416 active users by role or assignment. That information would show how many accounts belong to patrol officers, detectives, supervisors, intelligence personnel, civilian analysts, administrators or other employees.

It also remains unclear how many users can conduct historical searches of vehicle and license-plate data, whether access is assigned automatically based on job duties, and what investigative need an employee must demonstrate before receiving access. The available reporting does not establish that every active user can conduct historical searches.

Another unresolved issue is the department’s inactivity threshold. The audits documented users who had not logged in during the review period or earlier in the year, but the public reporting does not establish when an unused account is reviewed or disabled.

How Raleigh says the system is used

Raleigh’s automated-license-plate-reader policy requires advance supervisor approval for employees outside the Raleigh Intelligence Center, according to WRAL’s review of the department policy. Raleigh police also told WRAL that the technology is used to support legitimate criminal investigations and public-safety efforts, not for random surveillance or monitoring people engaged in lawful activity.

WRAL reported that officers conducted 5,911 Flock queries in July. The audit reported 23 successes across outcome categories that included nine recovered stolen vehicles, 12 arrests or warrants and eight investigative leads. Because those categories can overlap, they should not be added together as separate cases.

The audit also recommended better completion of Flock’s outcome field so reported results are accurate and complete. The reported outcomes show how heavily the system was used, but they do not by themselves establish that every query was justified or that Flock alone caused an arrest, warrant or vehicle recovery.

What Raleigh should clarify next

The central accountability question is whether Raleigh’s access controls are narrow, current and auditable. The city could address that by disclosing updated account totals, access levels by role, historical-search permissions, inactivity rules and the methodology used to classify accounts as active.

For residents, the August 5 audit provides a clear number—416 active users—but not yet a complete picture of how access is distributed, what searches different users can conduct or how accounts are reviewed over time.

Sources

• WRAL: Over 400 Raleigh officers have access to surveillance cameras. How does that compare?
• City of Raleigh: Raleigh Police Department

DOJ expects to select two to four cities or contiguous jurisdictions through a competitive process. Phase 1 applications are due by 11:59 p.m. Eastern time on September 1, 2026, and the department anticipates initial award decisions in late 2026.

The program has moved beyond a federal announcement and into the local decision-making phase. In Charlotte, North Carolina, the police chief asked the City Council to support an application, while council members questioned the scope of proposed technology, immigration-related requirements and the terms attached to possible future federal intervention. Charlotte had not been confirmed as an applicant or award recipient as of August 14.

What the funding could cover

The initiative is broader than a conventional equipment grant. Eligible activities may include sworn and non-sworn personnel, crime-analysis operations, real-time crime centers, body cameras, license-plate readers, artificial-intelligence systems and drones.

Applications may also include behavioral-health and substance-use services, reentry programs, victim assistance and youth-violence prevention. DOJ guidance says proposals should present integrated public-safety strategies rather than stand-alone technology purchases.

Generally, an applicant must serve a population of at least 100,000. Contiguous jurisdictions may combine in a regional application if the combined area exceeds that threshold. Applicants must also document required partnerships involving local government, justice-system organizations and other key stakeholders.

Why the structure matters

DOJ is offering the awards as cooperative agreements rather than ordinary grants. Under the notice and its frequently asked questions, the department expects substantial involvement in developing and implementing projects, reviewing proposed partners and subrecipients, approving detailed plans and final budgets, and releasing funds as milestones are completed.

That arrangement could give cities federal support during planning and implementation, but it also means local officials would have less independence than they might have under a less-involved grant program.

Applicants must submit a certification related to compliance with 8 U.S.C. § 1373. DOJ guidance also lists immigration-law enforcement operations among its priorities and identifies activities that would impede enforcement of federal immigration law as outside the program’s scope. The documents establish federal conditions, but they do not by themselves resolve how every local policy or practice would be evaluated.

Uncertain reimbursement exposure

The funding notice says awards will include a condition related to reimbursement for federal law-enforcement intervention or assistance during a future surge in violent crime or public disorder. The notice says the specific terms of that condition will govern any future obligation.

That is not a current bill or a guaranteed payment. Any obligation would depend on a future intervention and the terms ultimately attached to the award. DOJ has not published a specific cost estimate in the materials reviewed, making the possible budget exposure difficult for cities to quantify before applying.

That uncertainty was part of the concern raised in Charlotte. Axios reported that city officials discussed a potential award of up to $150 million, along with concerns about surveillance infrastructure, federal oversight and the effect on immigrant and refugee communities. The report said several council members opposed moving ahead, although a formal halt to staff work was not adopted.

What happens next

Cities considering the program must assemble partnerships, prepare an integrated strategy and complete the required certifications before the September 1 Phase 1 deadline. DOJ says finalist presentations will be scheduled later for invited applicants before initial award decisions in late 2026.

The Charlotte debate offers a preview of the issues other jurisdictions may face: whether expanded policing and prevention resources justify federal involvement, how residents would be informed about surveillance tools, how immigration-related requirements fit local policy, and how officials would manage an unclear future obligation.

The competition therefore presents both a funding opportunity and a governance decision. Residents may see proposals involving staffing, technology, behavioral-health response, reentry and victim services—not simply a request to purchase new equipment.

Sources

• DOJ FY 2026 Model Cities Initiative funding notice
• Axios Charlotte report on the CMPD proposal

The charges include misuse of license-plate data and violation of oath of office. The case involves access to a system that collects and stores information connected to vehicles and their locations, making the allegations significant for public trust in Albany’s law-enforcement surveillance tools.

What the GBI announced

The GBI identified five former Albany police officers as defendants in the investigation. The agency’s announcement names the Albany Police Department and identifies Flock Safety as the system connected to the allegations.

At least one defendant was identified by name. Tytianna Davis, 27, is facing five counts of misuse of license-plate data and one count of violation of oath of office, according to the GBI.

The announcement describes the conduct as alleged misuse. The arrests and charges are not convictions, and the allegations have not been established as final findings of guilt.

Why the case matters in Albany

License-plate reader systems can give law-enforcement agencies access to vehicle-related information gathered over time. When officers are accused of using that information improperly, the case raises questions about how sensitive data is accessed and used by people with official authority.

For Albany residents, the investigation may affect confidence in a surveillance system used by local police. The central issue is not only the alleged conduct by the former officers, but also the public’s expectation that vehicle-location information will be handled within the rules governing police work.

The GBI’s announcement connects the investigation to five former officers rather than current members of the Albany Police Department. It does not, in the information released, establish that the allegations reflect the conduct of the department as a whole or describe any broader finding about the Flock Safety system.

What is known about the charges

The public announcement identifies the two types of charges: misuse of license-plate data and violation of oath of office. It provides Davis’ specific counts, including five misuse charges and one oath-of-office charge.

It does not provide the full charging details for every defendant. That means the available announcement does not establish whether each person faces the same number or combination of counts as Davis.

The GBI announcement also does not establish guilt or provide final court dispositions. The next significant developments will be the handling of the criminal charges in court and any additional public information released about the allegations, the defendants and the use of the license-plate reader system.

For now, the confirmed development is the July 6 announcement of arrests and charges involving five former Albany officers in an investigation focused on alleged misuse of Flock Safety license-plate data.

The central accountability question is not only what the policy promises. It is whether KPD is following those requirements and reporting the results as the network grows.

What the RTIC can access

KPD announced May 28 that the RTIC is housed at the Knoxville Public Safety Complex and operates five days a week, with additional use for special events and large-scale emergencies. At launch, the center was staffed by a sergeant and two full-time, non-sworn specialists, with two additional specialists being hired.

KPD also said it had purchased and installed 10 city-owned cameras approved by City Council. The department said the locations were selected using available infrastructure and a review of three years of police calls-for-service data. The cameras are supposed to be overt and clearly marked.

Private cameras enter the system through Connect Knoxville, but registration and integration are different choices. Registration shares the camera’s location and owner contact information so investigators can identify nearby cameras after an incident. It does not give KPD access to a live stream.

Integration uses the Fusus platform and required CORE hardware to provide live or recorded access according to the owner’s settings. Participation is voluntary. The RTIC policy says access to integrated cameras requires permission from the camera owner, and that permission may be revoked at any time.

When integrated cameras may be used

The policy limits RTIC access to integrated cameras to legitimate law-enforcement purposes connected to an active call for service, an investigation, a system audit or approved training. A connected camera is not, under the written policy, an unrestricted invitation to view the feed.

The policy also says the RTIC may not continuously record or store live feeds from integrated cameras. If footage is downloaded for a law-enforcement incident, it must be stored on KPD systems under applicable law and department policy. The RTIC supervisor is supposed to notify the camera owner with a summary after an incident in which camera access directly supported police action.

Private-camera owners retain ownership of their video. They are also responsible for purchasing required integration equipment, such as a Fusus CORE device, and for camera purchase, repairs, operation and related public or media inquiries.

How long footage may remain available

The RTIC SOP says video generally should not be retained beyond 30 days unless it has evidentiary or training value. Footage identified as evidence must be uploaded to Evidence.com, which maintains an audit log showing the associated complaint number and the personnel who access or retrieve the evidence.

Non-evidentiary footage may be retained beyond 30 days only after a documented request and approval from the RTIC commander. The policy lists training, potential civil liability involving the City of Knoxville and department operations as examples of possible exceptions.

There is a separate qualification for donor cameras connected through Knoxville Connect: the SOP’s retention schedule says their standard retention is governed by the owner agreement. Any donor-camera video retained by the RTIC must be downloaded to Evidence.com, and the contributing entity remains the owner of the video.

Privacy and oversight requirements

The RTIC standard operating procedure prohibits facial recognition in conjunction with RTIC systems. It also bars collecting, retaining or sharing information about people or groups based solely on race, ethnicity, religion, gender, political beliefs or other protected characteristics, except when those details are part of a specific, credible suspect description or relevant investigative information.

All RTIC system access is supposed to be logged and subject to audit. The policy requires documented random audits of specialist activity every quarter. It also requires daily activity logs covering calls monitored, cameras accessed, license-plate-reader queries, drone deployments, requests fulfilled and significant intelligence provided to officers.

Drone deployments have additional documentation requirements. The SOP says drone video or data with evidentiary value must go to Evidence.com, supervisors must review a sample of deployments, and all deployments must be documented on a publicly accessible dashboard with general information about the type of call assisted.

What Knoxville residents can check

The policy requires KPD to maintain an updated public list of fixed RTIC-managed camera locations. It also requires a public dashboard describing drone deployments while protecting sensitive or legally protected information.

KPD’s public dashboards page currently describes its calls-for-service dashboard, which is refreshed every morning at 4 a.m. But that page does not by itself establish that the RTIC-required fixed-camera list, drone dashboard or audit documentation is current or complete.

That distinction matters. The SOP is a set of operating requirements, not proof that every safeguard has been implemented or that every transparency measure is active. Residents evaluating the program can look for the updated fixed-camera list, drone-deployment information and records showing how often integrated feeds were accessed, for what approved purposes and under which retention rules.

They can also use KPD’s records process to ask for releasable information about RTIC activity, while recognizing that disclosure may be limited by state law, city rules, department policy, active investigations and other legal protections. As Knoxville’s camera network expands, the most important public test will be whether the department’s documented practices match the privacy and accountability promises in its written policy.

Sources

• KPD Standard Operating Procedure — Real-Time Information Center
• Connect Knoxville

The report does not identify the employees or describe the alleged searches. It also does not establish whether anyone has been suspended, fired or charged, or whether the investigation is being conducted internally or by an outside agency.

The case matters as Savannah expands a network that captures vehicle and license-plate information for use as a law-enforcement investigative tool. A camera record is not, by itself, proof of a person’s movements or conduct. The accountability questions are who can search the data, why searches are made and what controls exist when access is alleged to be misused.

What is known — and what remains unknown

GPB reported that six Savannah police employees are being investigated over alleged misuse of the Flock system. The available report does not provide their identities, the number or nature of the alleged searches, the dates involved or the suspected purpose.

No authoritative source reviewed for this article confirms arrests, criminal charges, firings or suspensions in the Savannah matter. The allegation should not be treated as a finding that the employees committed misconduct.

Savannah planned a larger camera network

A Dec. 11, 2025 Savannah City Council agenda item authorized the city manager to execute a Flock Safety contract for an amount not to exceed $193,500.

The city record said Savannah had 74 contracted Flock cameras and proposed adding 40 license-plate readers and 10 pan-tilt-zoom cameras, bringing the planned citywide total to 124 cameras. The authorization covered annual subscriptions, maintenance and equipment. It did not establish that every planned camera had been installed.

The record said the one-year acquisition and implementation cost would be fully paid from SCAD SERVE grant funds. The council approved the broader $971,935 SCAD SERVE public-safety technology grant on Aug. 14, 2025. The grant permits spending on enhanced Flock license-plate-recognition cameras, public-safety call boxes, AXON/FUSUS technology, crime mapping and geographic information systems.

Using grant money rather than the city’s general operating fund does not eliminate the public accountability question. Residents still have an interest in how the system is governed, audited and used.

A separate Albany case shows the stakes

The Savannah investigation follows a separate case in Albany. The Georgia Bureau of Investigation said five former Albany police officers were arrested July 6 and charged with misuse of license-plate data and violation of oath of office.

According to the GBI, Albany police requested the investigation after an internal audit found that the officers had accessed the Flock system multiple times and used retained license-plate data for non-law-enforcement purposes. The officers were no longer employed by the department, and the GBI said the investigation remained active.

The Albany allegations are separate from the Savannah investigation. They show, however, how system audit records can lead to disciplinary or criminal proceedings when an agency identifies alleged unauthorized use.

Recent Georgia reporting by FOX 5 Atlanta also described privacy concerns raised by the ACLU of Georgia and an information-security analyst. FOX 5 reported that a Flock representative described a vendor audit-assistance tool that flags unusual searches. That vendor tool should not be confused with an independent government audit.

The oversight questions for residents

For people whose vehicles pass Flock cameras, the practical questions include which employees have access, whether searches require a case number or written justification, how often agencies review audit logs, how long data is retained and what penalties apply to unauthorized searches.

Residents may also want to know whether agencies disclose search totals, publish records of searches, identify access policies and explain when data can be shared with other agencies. Agencies remain responsible for setting permissions, reviewing searches and enforcing discipline, regardless of whether vendor software helps flag unusual activity.

Chatham County offers a transparency comparison

Nearby, the Chatham County Police Department launched a public Flock transparency portal July 21, according to WTOC. The department said the portal provides the number of cameras deployed, descriptions of what the system does and does not track, the number of searches conducted and downloadable records of recent searches.

WTOC also reported that the department audits each search monthly. The department said data collected by its cameras is deleted every 30 days under state law. That statement describes Chatham County’s position and practice; it should not automatically be generalized to every Georgia agency without reviewing each agency’s policy and the applicable legal requirements.

The portal does not resolve every privacy or surveillance concern, but it gives residents concrete information with which to evaluate how the system is being used. Savannah residents now face a pending investigation alongside a growing camera network and a public-money question: whether the city’s access controls and audit practices are strong enough to protect the data it collects.

What happens next

The next significant developments could include investigative findings, personnel decisions, criminal referrals or additional public records about system access. Savannah residents can ask the city and police department for policies governing Flock searches, retention, audits, access permissions and public disclosure.

Sources

• GPB: Six Savannah police employees investigated over alleged Flock misuse
• Savannah City Council: Flock camera contract authorization
• Georgia Bureau of Investigation: Albany Flock-data arrests
• WTOC: Chatham County Flock transparency portal

The announced project would also upgrade the Glendale Police Department’s Real Time Intelligence Center ahead of the 2028 Olympic Games. The expansion is planned; the announcement does not establish that the additional cameras are already installed or operating.

What Glendale says the funding will add

The funding announcement says the project will nearly double public-space camera coverage and modernize the Real Time Intelligence Center. It also says Glendale’s existing four-person specialist team is expected to operate the expanded system without additional staff.

The announcement describes the investment as federally funded and says it will not require additional local taxpayer funding or divert money from other city services. Procurement documents, contractors, installation dates, detailed funding conditions and the final camera count were not identified in the materials reviewed for this report.

How the intelligence center operates

Glendale’s Real Time Intelligence Center officially launched on November 13, 2024, according to the city. The center combines livestream video, analytical software and public-private partnerships to provide information to first responders and support coordination with partner agencies.

The city says the center provides video and data intelligence to patrol officers, supervisors and managers; supports investigations; monitors quality-of-life issues and crime trends; and helps prepare for critical incidents and community events.

Officials have presented the expanded system as a way to give officers information more quickly and support investigations. The announcement does not independently establish that the cameras will prevent crime or guarantee faster emergency responses.

Retention and footage-sharing questions

The July 27 announcement says video will be stored on city systems and retained for 30 days before deletion. It also says requests to share footage will go through Glendale’s policies and procedures, with decisions remaining under local control.

Those statements leave practical questions for residents and city oversight bodies. Future records should clarify which departments or outside agencies may request footage, what approvals are required, whether vendors can access system data, how access logs are maintained, whether audits are conducted and what privacy safeguards govern camera placement, searches and data handling.

The rollout schedule, camera locations, vendor agreements, procurement records and any policy changes also remain to be detailed.

Separate from Flock Safety license-plate readers

The planned public-space camera expansion should not be treated as the same system as Glendale’s existing Flock Safety technology. The city describes Flock as an automated-license-plate-reader system used for retroactive searches and real-time alerts involving hotlist vehicles.

Public-space cameras and automated license-plate readers are separate technologies unless later city records show that they are being integrated. Residents should look for future disclosures that explain how the expanded camera network will be governed and whether any connection to other surveillance systems is proposed.

Sources

• Rep. Laura Friedman federal funding release
• City of Glendale Real Time Intelligence Center
• Friedman Unveils $1,031,000 Federal Investment to Strengthen Community Safety in Glendale Ahead of the 2028 Olympic Games

Existing Foreign Intelligence Surveillance Court certifications and related directives can remain operative under their stated terms. Rep. Warren Davidson, R-Ohio, said in a June 12 statement that the certifications then in place would continue through March 2027. That date should not be read as a universal expiration date for every Section 702-related authorization.

The distinction matters because Congress is now debating what comes next: whether to reauthorize the authority, whether to require a warrant before the FBI searches Section 702 information using an American’s identifier, and how to strengthen reporting and compliance rules.

What changed on June 12

Section 702 permits the government to collect foreign-intelligence information by targeting certain people outside the United States. Congress must periodically authorize the program, and the House did not pass a short-term extension before the June 12 deadline.

The result was a lapse in the statute’s current congressional authorization. It was not, however, an immediate termination of all collection, storage or related activity conducted under certifications and directives approved before the lapse. The precise legal and operational effects of the lapse remain part of the congressional and legal debate.

That leaves lawmakers facing a renewal decision rather than a simple restart. Congress could enact a long-term reauthorization, attach new privacy and oversight conditions, or allow existing certifications to run toward their stated expiration while negotiations continue.

How Section 702 affects Americans

Section 702 is designed to target non-U.S. persons reasonably believed to be outside the United States for foreign-intelligence purposes. Americans are not supposed to be the targets of that collection.

Americans’ communications can nevertheless be collected incidentally when they communicate with a foreign target or appear in information connected to a foreign target. A later search of stored Section 702 information is called a query. The FBI says a query does not create new collection; it searches information the government already acquired.

Under existing procedures, the FBI may use U.S.-person query terms such as a name, email address or telephone number. The FBI says such a query must have an authorized purpose, be reasonably designed for that purpose and have a specific factual basis indicating that it is reasonably likely to retrieve foreign-intelligence information or, in limited circumstances, evidence of a crime.

What the 2025 numbers show

The Office of the Director of National Intelligence estimated that 349,823 non-U.S. persons were targeted under Section 702 in calendar year 2025, up from 291,824 in 2024.

The ODNI report also counted 7,413 FBI U.S.-person query terms in 2025, compared with 5,518 in 2024. A query term is an identifier used to search the data. The figure does not necessarily represent 7,413 unique Americans, investigations or successful accesses to communications.

ODNI separately reported 1,081 FBI U.S.-person evidence-of-a-crime-only queries conducted for discovery purposes. FBI users accessed results in 245 of those queries. Those figures do not mean that 1,081 Americans were surveilled, charged or prosecuted. They describe searches of Section 702-acquired information under the reporting categories used by the government.

ODNI said the evidence-of-a-crime-only category is limited under the Reforming Intelligence and Securing America Act, which largely restricted that type of FBI query while retaining exceptions. The report also cautioned that year-to-year figures can change with litigation, criminal matters, operational priorities and other factors.

What safeguards exist

The FBI says its safeguards include case-specific justifications for U.S.-person queries, mandatory training, audits and recurring reviews by the Justice Department and ODNI. It also requires enhanced review for certain sensitive queries involving categories such as elected officials, members of the media, academics and religious figures.

The FBI has acknowledged serious past compliance problems, including improper queries involving Americans who took part in peaceful protests. The agency says reforms adopted beginning in 2021 added opt-in controls for unminimized information, attorney approval for large batch queries and stronger documentation requirements.

Those safeguards are the government’s account of its current compliance framework. Privacy advocates and lawmakers seeking additional restrictions argue that internal rules and executive-branch oversight do not provide enough protection, particularly when Americans’ information is searched without a traditional warrant.

What Congress is arguing over

The most prominent dispute is whether reauthorization should require a warrant before the government searches Section 702 information using an American’s identifier. That is a proposed reform, not current law.

Supporters of the program say U.S.-person queries can help identify Americans who are victims of foreign hacking, espionage, terrorism, kidnapping or other threats. The FBI has argued that a broad warrant requirement could delay the use of information already lawfully collected.

Critics say searching Americans’ communications without a warrant creates a serious Fourth Amendment concern, even when the original target was overseas. Other potential reforms include putting FBI compliance policies into statute, expanding reporting to Congress, tightening provider obligations and increasing penalties for violations.

No replacement framework was established by the June lapse itself.

What to watch next

The next important markers are any bill to reauthorize Section 702, congressional oversight hearings, new court filings and additional transparency reports. Davidson identified March 2027 as the point through which the existing certifications and directives would continue, but the timing and scope of any future certifications could depend on further legal and congressional action.

For the public, the immediate question is not whether every surveillance activity stopped on June 12. It is what Congress will authorize next and whether lawmakers require a warrant, stronger reporting or other controls before restoring the statute.

Sources

• ODNI Annual Statistical Transparency Report for Calendar Year 2025
• Rep. Warren Davidson statement on the lapse of FISA Section 702
• Associated Press: Congress fails to extend FISA spy tool as deadline closes in
• FBI: Oversight of Section 702 and Related Surveillance Authorities

The delay gives residents more time to review the proposed contract extension, the program’s data practices and concerns raised during a May council meeting. The Aug. 13 meeting will involve scheduled consideration, not an automatic renewal.

What changed

A notice attached to the July 16 agenda said the renewal item had been withdrawn by the department and would be considered at the Aug. 13, 2026, regular City Council meeting. ABC15 reported that the city said the delay would give council members more time to get questions answered.

ABC15 also reported that council members were expected to meet with experts before the August meeting. The report said a previously expected executive-session discussion was not going forward at that time. Councilmember OD Harris told ABC15 he had not received information about such a meeting and called for more transparency.

What is proposed

Chandler’s May 21 council record lists a proposed renewal of fixed-camera automated license-plate-reader services from Flock Group Inc. The proposed amount is not to exceed $153,400, using the City of Tempe’s contract.

The council record says Chandler began using Flock readers as a pilot program in March 2024 and had reached agreements allowing up to 40 automated license-plate readers in the city. The record describes the technology as assisting police with identifying and recovering stolen vehicles and locating vehicles associated with missing or endangered people.

KJZZ reported that Chandler had about 40 Flock cameras and roughly 7,600 alerts during the fiscal year. Those alerts measure system activity; they do not by themselves establish crimes, arrests or confirmed matches.

Data retention and sharing

KJZZ reported that Chandler owns the collected data, decides who may receive it and keeps it for 30 days. Chandler shares Flock data with local law-enforcement agencies and the U.S. Marshals Service.

During the May council discussion, city and Flock representatives also discussed access controls and data security. The council record states that data reaching the 30-day retention limit is deleted through Flock’s cloud-storage process. Those practices, along with any changes to the proposed terms, should be checked against the final August agenda packet and contract materials.

Resident concerns

Public comments documented in the May council record included objections to surveillance, camera locations, data control, retention, sharing and privacy. Some speakers questioned the program’s effectiveness and asked how many arrests or cases had been helped by the cameras. Others urged the city not to renew the contract or to redirect the money to community programs.

Other speakers supported the cameras and cited public-safety uses. The comments show competing views about the technology; they do not establish that Chandler or Flock committed a legal violation.

How residents can participate

Chandler’s meeting information lists Aug. 13 as a regular City Council meeting, when formal action may be taken. The city says comments on posted agenda items are heard before the council vote. Speakers generally must sign up no later than 10 minutes before the regular meeting begins and may speak for up to three minutes. Written comments may be submitted online or at the meeting and become part of the meeting record.

Residents should review the final Aug. 13 agenda, staff recommendation, contract language and funding information when those materials are posted. They should also check whether the item remains on the agenda and whether the proposed amount or terms have changed.

The council could approve, reject or delay the renewal. Its action will determine the next step for Chandler’s Flock program.

Sources

• City of Chandler — City Council Meetings & Agendas
• City of Chandler — May 21, 2026, Council minutes and public-comment packet
• ABC15 — Chandler delays Flock license plate reader vote to August
• KJZZ — Chandler council to consider contract renewal for Flock Safety cameras

This Is Reno reported that police agencies outside Nevada searched Flock data associated with vehicles traveling in the Sparks area. The report also described a dispute over Reno’s refusal to provide requested audit information and said the city had not announced a decision on renewing its Flock contract. Those are reported developments and records-access claims, not a final legal finding that Reno officials acted unlawfully.

What Reno has funded

Reno records describe a broader enhanced-public-safety technology project involving Flock Safety, Fusus, Axon and Coplink. The city’s recovery-fund records identify the project at $6.45 million, with a performance period listed as October 26, 2022, through December 31, 2026.

That broader project figure is separate from the reported Flock agreement. This Is Reno reported that the Reno City Council unanimously approved a $450,000 Flock contract in November 2024 using federal coronavirus-relief funds.

The city’s 2025 Recovery Plan Performance Report, covering results through June 30, 2025, identified 103 Flock devices at different installation or permitting stages, plus 31 surveillance cameras downtown and 10 along major thoroughfares. Those are the latest identified report figures in the available record, not a confirmed Reno inventory as of August 1, 2026.

How the technology works

Flock’s automatic license-plate recognition system can record a license plate, the date and time, location, direction of travel and vehicle characteristics such as roof racks, stickers or visible damage. According to the July 24 report, agencies with Flock contracts can set sharing permissions that allow authorized users from other agencies to search data through the company’s cloud platform.

That capability does not establish that every search is unlawful. It does mean ordinary drivers may be recorded while traveling through Reno even when they are not suspected of a crime. The key unanswered question is what current Reno policies require before an officer or outside agency can search the data.

Reno and Sparks police also launched a regional Real-Time Information Center in January 2025. Official city materials describe Fusus as a platform that can bring together live video and data feeds from public and participating private cameras, along with other sources such as body-worn cameras, small drones and sensors.

Private cameras have different rules

Reno’s ReSecure program uses the city’s Connect Reno camera-registration and integration program for participating businesses. The city says participation is voluntary, businesses retain ownership and control of their installed systems, and participation does not provide police with continuous or unrestricted access. Any potential data sharing with Reno police must occur through a separate agreement or lawful request.

That distinction matters. City-owned cameras, Flock license-plate readers, Fusus-connected private cameras and other surveillance tools are separate parts of the public-safety technology system. Each may have different contracts, permissions, retention rules and audit requirements.

The accountability gaps

The available public record does not establish Reno’s precise August 2026 device count, the complete active contract terms, the retention period for Flock records or the full rules governing searches by outside agencies.

Residents and businesses also need clearer information about search logs, supervisor approval, routine audits, improper-access investigations and whether the Flock contract will return to the Reno City Council. The reported denial of audit records remains a public-records dispute; it should not be characterized as a final court or state finding that Reno violated Nevada law.

For Reno residents, the practical stakes include the recording of vehicle movements, surveillance near homes and businesses, investigations involving stolen or missing vehicles, private-camera participation and the use of public money for technology that may be searched across jurisdictions. Businesses considering camera integration need to understand what they control, what they may be asked to share and which agreements govern access.

The public-safety case for the technology and the civil-liberties case for stronger limits can be evaluated only if Reno discloses current counts, access rules, retention policies, search-audit results and contract terms. The immediate issue is not simply whether cameras can assist police. It is whether the city has built enough transparency and oversight around the system it has funded.

Sources

• This Is Reno: Flock contract and surveillance backlash report
• City of Reno 2025 Recovery Plan Performance Report

Council meeting highlights say the ordinance passed 9–6, and they describe the amendment as a bridge while the City prepares a request for proposals for a different ALPR vendor.

What Council changed in Ordinance 683-2026

Under the amended terms, the contract authorization language replaces the prior one-year and $250,000 cost cap with: six months and $125,000.

Stricter ALPR data rules: warrant-centered disclosure

The amendment adds clear restrictions on what Flock Safety can do with ALPR data. In plain terms, it:

• Bars sale/sharing for non-law-enforcement purposes: Flock Safety “shall not sell, share, publish or exchange” ALPR data for any purpose other than law enforcement purposes.
• Restricts third-party access/use: Flock Safety “shall not access, use, preserve or disclose” ALPR data to any third-party government authority or other third party except pursuant to a valid search warrant issued by a court of competent jurisdiction on a finding of probable cause and describing with particularity the data to be produced.
• Limits disclosure in response to other legal requests: the amendment says Flock Safety shall not disclose ALPR data in response to subpoenas, administrative requests, informal inquiries, preservation letters, national security letters, or any other legal process that does not constitute a search warrant—unless disclosure is required by applicable law. If disclosed under a warrant, the amendment requires the disclosure be limited to the data identified in the warrant and produced only to the law enforcement authority named in the warrant.
• Requires notice to the City before disclosure: unless legally prohibited, Flock Safety must provide prompt written notice to the Director of Public Safety before disclosure and allow a reasonable opportunity to seek protective relief.

Penalties for privacy or data-sharing violations

The amendment specifies that violating these data-handling provisions would be a material breach of the contract. It also requires the contract to include a financial penalty of up to 25% of the contract amount for violations of privacy and data-sharing provisions.

More public oversight: Transparency Portal and quarterly reporting

Residents looking for concrete accountability are directed to two requirements added by the amendment:

• Transparency Portal: the Division of Police must establish and maintain a public Transparency Portal—an online webpage where the public can access information about the Division’s ALPR use.
• Quarterly reporting: the Safety Director must submit a written report quarterly to the Clerk and the Safety Committee on the use and monitoring of the ALPR system.

Fusion Center sharing is specifically restricted

The amendment also includes a specific prohibition: the Division of Police shall not share data derived or downloaded from the City’s Flock Safety cameras with the Northeast Ohio Regional Fusion Center under the contract authorization in the ordinance.

What residents can do next

• Watch for the Transparency Portal: when it goes live, scan it for how the City describes ALPR use, monitoring, and any disclosed/search-warrant information.
• Look for the first quarterly report: the amendment requires written quarterly reporting to the Clerk and the Safety Committee—those reports should be your best checkable record of what the City says it’s monitoring and how the system is being used.
• Ask pointed questions about third-party sharing: once reports/portal updates are posted, residents can ask whether any external sharing is documented as warrant-based (probable cause + particularized data) and how the City is complying with the Fusion Center restriction.

Emergency timing note: The ordinance text says emergency ordinances can take effect immediately upon passage and Mayor approval only if they receive the required two-thirds vote of all members elected; otherwise, the emergency measure takes effect at the earliest period allowed by law.

Sources

• Cleveland City Council meeting highlights (7/15/2026) — Flock Cameras vote and six-month/$125,000 amendment
• Legistar attachment — 683-2026 Legislative Summary (as amended: six months/$125,000)

What Section 702 does

Section 702 lets the government collect foreign-intelligence communications of non-U.S. persons outside the country. It remains controversial because Americans’ communications can be collected incidentally and later queried under certain rules.

Why the lapse is not a clean shutdown

CRS says a lapse does not necessarily end all collection right away. If a FISA court order was already in effect when Section 702 sunset, the government can keep acquiring information and querying under that order until it expires, and the court can keep administering previously approved procedures.

How Congress got here

Congress had already extended the program once through June 12, but lawmakers split over whether to pair renewal with tighter warrant and oversight rules. AP and CBS reported that the final push collapsed amid the Pulte fight, with Democrats saying they would not back renewal unless Trump changed course.

What to watch next

The next questions are whether Congress tries another extension, whether leaders strike a reform deal, and how long existing court orders keep the program operating in practice.

Sources

• Associated Press report on the Section 702 lapse and Pulte fight
• CBS News report on the Senate FISA vote
• Sen. Dick Durbin Judiciary Committee statement
• House Democratic leadership statement on Section 702
• Sen. Chuck Grassley Judiciary Committee statement
• Congressional Research Service report on FISA Section 702

The move prevents an immediate lapse in the government’s authority to collect foreign intelligence information under the program. But it is only a stopgap. The broader fight over how Section 702 should be renewed or revised is still unresolved, and the next few weeks now matter a great deal for lawmakers, the intelligence community, and privacy advocates.

What Section 702 does

Section 702 is a federal surveillance authority that lets the U.S. government collect communications of foreign targets located outside the United States. Officials say it is a key tool for national security and counterterrorism work. Critics argue the program needs stronger limits and more oversight because Americans’ communications can sometimes be swept up incidentally.

The short extension keeps the existing framework in place while Congress continues negotiating. It does not settle the underlying policy debate, and it does not amount to a full reauthorization.

Why the new deadline matters

The new June 12 deadline gives Congress a narrow window to decide whether to renew Section 702 for a longer period and whether to change the rules around how the power is used. That includes questions lawmakers have debated for months: how much court oversight should apply, what limits should govern searches, and how to balance intelligence needs against civil-liberties concerns.

For ordinary readers, the practical takeaway is straightforward: the government avoided a surveillance lapse, but only temporarily. Nothing about the larger debate has been resolved yet.

That means the next vote, filing, or compromise language in Congress could matter as much as the extension itself. If lawmakers reach a deal, they could lock in a longer-term version of the program. If they do not, they may again face a last-minute scramble before the June 12 deadline.

What to watch next

Watch for renewed House and Senate talks over what any longer extension should include, whether leaders try another temporary patch, and whether the White House weighs in more forcefully on the terms. The AP reported that the extension cleared Congress after a broader reform push again stalled, and the White House later confirmed the bill was signed into law.

For now, the immediate answer is that Section 702 remains active. The bigger question is whether Congress can settle the issue before the next deadline arrives.

Sources

• Associated Press report on the 45-day FISA extension
• White House bill-signing notice for S. 4465