Flock Cameras and Gig Drivers: What License Plate Readers Mean for Uber, Delivery and Rental Cars

Flock cameras photograph every car that passes them, read the plate and log the vehicle's description, time and location into a database that police can search. If you drive for Uber, Lyft, DoorDash, Instacart or Amazon Flex, you pass those cameras more often than almost anyone, and if you drive a rented car, the plate they record is not registered to you. Neither fact means anyone is watching you. A camera collecting a plate is not an agency looking for it, and understanding that difference, along with what records actually tie a rental car to a driver, is most of what a gig driver needs to know. The rest is what has changed in 2026, which is a lot.

Every figure here is dated and sourced at the end. This subject moves weekly; re-check before relying on any number.

What a Flock camera actually does

A Flock camera is an automated license plate reader, usually a small black box on a pole at an intersection, a neighborhood entrance or a parking lot. It photographs the rear of each passing vehicle and software reads the plate and describes the car.

What Flock says it captures, in its own documentation: license plate images, vehicle characteristics, date and time stamps and camera location. Flock markets the vehicle description as a "Vehicle Fingerprint": make, model, body type, color, and distinguishing features such as bumper stickers, roof racks, dents and temporary or out-of-state tags. What Flock says it does not capture: biometric data, driver information or facial recognition data. The company's phrasing is that the system "captures vehicles. Not people."

Police use the data two ways. The first is a hot list: plates flagged as stolen, tied to a warrant or an Amber Alert, drawn from databases such as the FBI's NCIC, trigger an alert when a camera sees them. The second is a historical search: an officer enters a plate, a partial plate or a vehicle description plus a place and time window, and the system returns where that vehicle was photographed. The Electronic Frontier Foundation describes the second use as the one that lets an agency "track where that plate has been captured elsewhere."

Retention and sharing are where confirmed facts, company policy and reported concerns need to be kept apart.

• Confirmed, from Flock: the default retention period became 7 days in August 2026. Existing customers keep whatever period they had, and state law overrides the default where it exists. Every search is logged with the user, a stated reason and a timestamp.
• Confirmed, from Flock: sharing is a local setting. An agency can keep its data to itself, share with chosen agencies, or join statewide and nationwide lookup networks that let other members search its cameras. Flock told Senator Ron Wyden's office in 2025 that more than 75% of its law enforcement customers had opted into national sharing.
• Reported concern: the Bend, Oregon police department found in 2025 that the national lookup option had been left on by default, which exposed its cameras to outside queries for three weeks before anyone noticed.
• Reported concern: Flock also sells to private customers, including more than 3,000 homeowners associations and other organizations as of late 2025, and a neighborhood can opt to give local police ongoing access to its cameras.

Why a gig driver is photographed more than almost anyone

Flock cameras do not track Uber drivers, or anyone, as a category. They photograph every car. But exposure scales with miles, hours and the kinds of places you drive through, and a gig driver maximizes all three.

The best public measurement of ordinary exposure comes from a federal lawsuit in Norfolk, Virginia. Two residents represented by the Institute for Justice discovered through discovery that the city's 176 cameras had photographed their cars 475 and 325 times in about four and a half months of normal driving, roughly four times a day for one of them. Neither was suspected of anything. A full-time rideshare or delivery driver covers several times a commuter's mileage and routes it through exactly the places cities put cameras.

• City and county lines. Suburbs and small cities are heavy Flock adopters, and a driver crossing six jurisdictions in a shift is photographed by six separate camera owners with six different retention and sharing settings.
• Airports. Terminal roads, cell-phone lots and the arterials feeding them are among the most densely covered stretches in any metro, and an airport driver loops them dozens of times a week.
• Hotels, nightlife and entertainment districts. Late-night zones with high call volume are where police concentrate cameras and where surge sends drivers.
• Restaurant and retail corridors. Delivery drivers stage at the same shopping centers all day, and retailers themselves are now installing plate readers in parking lots. Connecticut lawmakers pressed Home Depot and Lowe's about theirs in May 2026.
• Residential neighborhoods. A DoorDash or Instacart driver enters dozens of subdivisions a week, and a subdivision with Flock at its entrance logs every entry and exit. Flock's own neighborhood marketing says the cameras log everyone who comes in, including delivery drivers.

The result is a record that is dense but not meaningful. Nothing happens to it unless an officer runs a search that matches your plate, and an audit trail attaches to that search when it happens. A driver whose plate shows up near a crime scene because that is where the order was is in the same position as any other car on the street at that hour: a data point, not a suspect, and one that trip records can explain in minutes.

Rental cars: whose plate it is, and what points back to you

This is the section for anyone driving a car they do not own, whether it is a weekly gig rental, a Turo car or a fleet vehicle.

Do Flock cameras record rental cars? Yes, exactly as they record any other car. The camera has no idea the car is rented. It records the plate and the vehicle's description. What differs is what that plate leads to.

Can Flock tell who is driving? No. Flock says its cameras do not capture driver information, and a plate search returns a vehicle history, not a person. Identifying a person takes a second step outside Flock: looking up the plate's registration.

Who the registration points to. A plate lookup goes to the state motor vehicle record, which names the registered owner. For a rental car that is the rental company, the fleet or the individual owner, never the renter. The federal Driver's Privacy Protection Act lets government agencies, including police, obtain those records in carrying out their functions, so the lookup itself is routine. For a gig rental on a marketplace like this one, the registered owner is the person or fleet that listed the car.

What connects the car to the driver at a given hour. Someone has to produce records. In practice that means one or more of:

• The rental agreement or booking, which names the renter and the rental period. Major rental companies have formal law enforcement request channels; Hertz, for example, routes subpoenas and warrants through a dedicated legal process and says it does not respond to requests from non-law-enforcement parties. Turo's privacy policy says it may disclose trip records in response to valid legal requests.
• Platform trip records. Uber's published law enforcement guidelines say it will provide trip details such as pickup and drop-off coordinates in response to a court order, and GPS location history only with a search warrant, with an emergency exception. Those records can place a specific driver account in a specific car at a specific time, which cuts both ways: they can confirm you were working, and they can confirm you were not the one driving.
• The owner's own records. A fleet that rotates drivers through a car weekly can say who had it when, if it keeps the paperwork.

Several drivers, one plate. A gig rental may carry a different driver every week, and a camera history for that plate is a history of all of them stacked together. A search covering six months of a fleet car's plate is a search of six or more people's working lives. Nothing in the camera data separates them; only the rental and platform records do. That is a confusion risk mostly for the owner, who is the name on the registration and the first call, and it is why a dated rental record protects the owner as much as the driver.

Where this varies. Whether an officer needs a subpoena, a court order or just a phone call to get a rental agreement depends on the state, the agency's policy and the company's own rules, and whether plate data can be shared across state lines at all now depends on the state: California, Illinois, Washington, Connecticut and New Mexico restrict it in different ways. The constant across all of them is that the camera record alone never names the driver. Paperwork does, which is one more reason the complete guide to renting a car for gig work tells you to get the agreement in writing.

Owners carry the mirror-image duty. If you rent cars to gig drivers, your plate is the one in the database and your name is the one on the registration, and a complete, dated record of who had each car is your protection. The owner guide covers the paperwork to keep; on GigCarFinder, applications, messages and verified driver profiles stay on the listing, which is the kind of record this section is about.

What changed in the past year

The pace of change since mid-2025 has been unusual for police technology, and it has run in both directions at once: cities leaving, states regulating, Flock tightening its own rules, and police departments defending results.

Cancellations. The advocacy tracker DeFlock counted 324 communities in 36 states that had canceled, paused, rejected or deactivated Flock as of late September 2026, including 174 outright contract cancellations. The ACLU says more than three communities a day took such a step in August 2026. Examples with a documented cause: Dayton, Ohio covered its 72 cameras with trash bags in June 2026 after an audit found more than 7,000 searches by outside entities tied to immigration enforcement, which its policy prohibited. Bend, Oregon shut off its four cameras in January 2026 after the default sharing incident. Austin, Evanston, Oak Park, Eugene and Sedona had already left in 2025.

State action. Texas Governor Greg Abbott ordered state agencies to stop funding Flock cameras on August 26, 2026, and the state transportation department stopped issuing permits for new installations on state roads; the state's Motor Vehicle Crime Prevention Authority had funded roughly 2,000 cameras through grants. Hewitt, Texas shut its system down on October 1 when the grant money went away. Florida's transportation department ordered unpermitted Flock cameras off state rights of way, and St. Lucie County found 14 that nobody had permitted, 11 of which no agency has claimed.

Documented misuse. A Washington Post investigation in August 2026 identified at least 50 officers charged with or accused of using plate readers for personal reasons, often to track former partners, and found that in many cases the departments did not know until the Post asked. In Lufkin, Texas, a former officer pleaded guilty on September 24, 2026 to 100 counts of misuse of official information after an audit tied roughly 25,000 searches to non-police purposes, most of them aimed at an ex-girlfriend, her family and her partners; he was sentenced to five years. Prosecutors in Indianapolis charged five current and former officers on September 23, 2026 with fraud and official misconduct over thousands of searches of ex-partners and acquaintances. Illinois suburbs including Homer Glen, West Chicago and Channahon suspended use or officers in September 2026 after finding unauthorized searches, and a former Holiday Hills police chief faces felony charges over roughly 250 of them.

Wrong-car stops. The Institute for Justice documented at least 27 cases since 2018 of innocent drivers stopped, held at gunpoint or jailed after plate reader errors, most since 2023, including a Sherwood, Arkansas couple with a six-week-old baby detained in February 2026 after a camera misread one digit. Flock says it sees fewer than nine human-reported alert errors per million alerts.

The courts. In the Norfolk case, Chief Judge Mark Davis ruled on January 27, 2026 that the city's network, with Virginia's 21-day retention and gaps between captures, is not an unconstitutional search today, while writing that such surveillance "could become too intrusive" as it expands. The plaintiffs have appealed to the Fourth Circuit, the first Flock challenge to reach a federal appeals court.

What police say the cameras do. Flock reports that in July 2026 alone its system detected more than 1,000 missing people and located more than 20,000 stolen vehicles, and claims assistance in more than a million investigations a year. Texas police chiefs in Belton and Groesbeck told a local station in October 2026 the cameras led them to a shooting suspect's vehicle and to a felony assault suspect's door the next morning, and a McLennan County prosecutor said camera footage tracing a victim's car to Kansas helped convict a murder suspect. The Indianapolis police chief's framing after her officers were charged was: "This technology increases safety in our community. It is the misuse we have to focus on." That is the honest shape of the debate: the recoveries are real and so is the misuse, and the question cities are voting on is whether the audit trail is enough.

What Flock changed, and what the states now require

On August 13, 2026 Flock announced a set of changes that take effect through the end of the year. In its own words and numbers:

• The default retention period for plate data drops from 30 days to 7. Flock says more than 90% of searches that lack a full plate happen within 7 days. Existing customers keep their current period unless they opt in, and a new Evidence Mode lets investigators preserve specific records tied to an active case.
• Audit Assistance, which flags abnormal search patterns for an administrator, becomes mandatory for every law enforcement customer by the end of 2026, with a proactive lockout that suspends a user pending review. Flock credits the tool with recent arrests of officers who misused the system.
• Every law enforcement search must carry a case code by the end of 2026. Emergency searches can bypass it and are flagged automatically for review.
• Multi-factor authentication is mandatory, an outside security review was published in September 2026, and agencies can now filter which offense types other agencies may search their cameras for.
• More than 1,500 agencies publish a Flock Transparency Portal showing their policy, retention period, sharing partners and search activity.

The ACLU's response, through senior policy counsel Chad Marlow, was that the changes "did little to address" its core objection, which is the collection of billions of scans a month from people who have done nothing wrong, and the nationwide sharing that remains available.

States have moved faster than at any point since the technology appeared, and the direction is consistent: short retention, enumerated uses, limits on who can be given the data.

Indiana, Nevada, Ohio, Utah and Virginia have signaled further review, and Pennsylvania held hearings in September 2026. If your state is not in the table, the controlling rules are your police department's own policy and its Flock settings, which is why the public records steps below matter.

ICE and federal access, carefully

This is the most charged part of the Flock story and the easiest to get wrong in either direction. The accurate statement as of October 2026 has several parts.

Flock's own position, published January 2026 and updated since: "ICE does not have direct access to Flock cameras, systems, or data, unless the agencies that control their data expressly and deliberately allow it." Flock says it has no contract with ICE. It acknowledges running pilots with federal agencies, including Customs and Border Protection and Homeland Security Investigations in 2025, and says it ended all federal pilots in August 2025 and removed federal agencies from its statewide and national lookup networks at the same time.

So the question "does ICE have access to Flock cameras" has different answers depending on the path:

• Direct access, meaning ICE as a Flock customer searching the network itself: no, per Flock, since August 2025.
• Agency-to-agency sharing, meaning a local department choosing to run a search for a federal agency or give it results: possible wherever state law and local policy allow it, and this is the path that audits keep finding. Mount Prospect, Illinois logged 262 immigration-related searches in a few months of 2025, and the Illinois Secretary of State's audit found the state's 2023 law had been violated.
• Federated or national lookup, meaning an outside agency searching your city's cameras because your city joined a network: this is how out-of-state agencies reached Bend's cameras in 2025, including 161 queries by other agencies acting on behalf of ICE, CBP and HSI, through a default setting the department had not meant to leave on.
• Local departments choosing to share: Dayton's 7,000-plus immigration-related searches were run by outside entities that its sharing settings permitted, against its own written policy, and nobody was checking until the city paid for an audit.
• Improper or unintended access: San Francisco's internal audit, released June 17, 2026, found 299 searches over a year by out-of-state and federal agencies, including the DEA, IRS, U.S. Marshals and Forest Service, routed through a regional intelligence center at night, in violation of California law. The audit specifically did not find ICE or DHS among them. A separate class action filed in February 2026 alleges far larger numbers; that is an allegation, not a finding.

Flock's CEO wrote in August 2025 that "some of our public statements inadvertently provided inaccurate information" about federal relationships, which is part of why cities now ask for audit logs rather than assurances. The defensible summary for a driver: there is no evidence that ICE can sit down and search the national Flock network today, and there is documented evidence that local data has reached federal and out-of-state agencies through sharing settings, intermediaries and misconfiguration. Whether that can happen with your city's cameras depends on your city's settings and your state's law, both of which are public.

What gig drivers should actually know

Being photographed is not being targeted. A Flock record is created for every car; a Flock search is an act by a named officer, logged with a reason, that most plates never experience. The things that turn a passive record into a problem are a hot list match on your plate, which rental and trip records resolve, or a human misusing the system, which the audits and prosecutions above are now catching.

The cameras read plates and describe cars. They do not identify drivers, they do not use facial recognition by Flock's account, and a plate traces to a registered owner, not to whoever was driving. In a rental, that owner is not you.

Your paperwork is your protection. Rental agreements with dates and times, a verified driver profile that records who you are and which platforms you work, platform trip exports and, for owners, a record of who had each car when, are what settle any question about a vehicle's history. Keep them for at least as long as your state's retention period, and longer if you can.

To find out whether your city uses plate readers and on what terms:

• Search for your city or county name with "Flock transparency portal". More than 1,500 agencies publish one, showing retention, sharing partners and search counts.
• Check the Electronic Frontier Foundation's Atlas of Surveillance, which catalogs agency contracts by technology.
• Read your police department's ALPR policy, which most states require to be written and public, and the council minutes from when the contract was approved or renewed.
• File a public records request for the search audit log, which is what reporters, Dayton and San Francisco used. The Lufkin case began with a records request.

If you drive in Virginia, Washington, Connecticut, Kentucky, New Mexico, California or Illinois, state law now limits retention, use or sharing. Everywhere else, the local policy is the rule.

Before your next shift

• Keep every rental agreement, with start and end times, and export your trip history regularly
• If you rent through a marketplace such as GigCarFinder's weekly rentals, keep the application and message thread; it dates who had the car
• Look up your city's Flock transparency portal or ALPR policy once, so you know the retention period and who it shares with
• Remember the difference: a plate photographed is routine; a plate searched is a logged act with a reason
• If you are ever stopped on a plate alert in a car you are renting, say it is a rental and name the owner; most alert errors are resolved by checking the plate against the car
• Owners: keep a dated log of which driver had which car, because the registration points to you

Sources

• Flock Safety: Data Privacy and Protection, for what the cameras capture and do not, the 7-day default and audit logging
• Flock Safety: privacy, accountability, security and transparency updates, August 13, 2026, and Police1's summary
• Flock Safety: Does Flock share data with ICE?, January 2026, for the company's position and the 2025 federal pilots
• Flock Safety FAQ, for hot lists, data ownership and search audit fields
• EFF Street-Level Surveillance: automated license plate readers, for how hot lists and historical searches work
• NBC News: police cameras track billions of plates a month, November 1, 2025, for the 20 billion scans, 5,000 agencies, 75% national sharing and private customer figures, and NBC News on the August 2026 oversight changes
• The Source: federal immigration officials made 279 queries into Bend's Flock data, for the default national lookup setting
• Fortune: Dayton covers Flock cameras after data-sharing violations, June 3, 2026
• Mission Local: feds improperly accessed San Francisco plate data, June 2026
• Illinois Secretary of State: audit finds Flock in violation of state law, August 25, 2025, and Chicago Sun-Times on Illinois suburbs halting Flock use, September 1, 2026
• Governing: Texas governor halts Flock camera funding, August 2026; Texas Tribune on Flock's growth in Texas, August 3, 2026; KWTX on Hewitt and Central Texas, October 2, 2026
• Washington Examiner: Florida orders unpermitted Flock cameras down, October 1, 2026
• KBTX: former Lufkin officer pleads to five years over Flock misuse, September 30, 2026
• WFYI: five Indianapolis officers charged for misusing Flock cameras, September 24, 2026, following the Washington Post's August 2026 investigation
• Institute for Justice: innocent motorists detained after plate camera errors, July 2026
• WHRO: federal judge rules Norfolk's Flock cameras constitutional, for now, February 2026, and NBC News on the Norfolk lawsuit's capture counts
• DeFlock cancellation tracker, an advocacy-maintained list, as of September 2026, and the ACLU's Get the Flock Out campaign for the civil liberties position
• Techdirt on the reported Flock and Nexar dashcam plan, August 2026; Flock says the partnership never launched
• MultiState: states restrict automatic license plate readers in 2026, September 23, 2026; Flock's summary of Connecticut SB 397; California Attorney General bulletin 2023-DLE-06 on SB 34
• 18 U.S.C. 2721, the Driver's Privacy Protection Act, for who may obtain motor vehicle records
• Uber: guidelines for U.S. law enforcement, for what trip records require a court order or warrant; Turo privacy policy on legal process; Hertz law enforcement requests
• Nothing on this page is legal advice. Rules on retention, sharing and what process an agency needs to obtain rental records vary by state and agency; the links above are the places to check your own.