TL;DR

Surveillance gear your city buys leaves a paper trail, and much of it is public. Start with the legislative file: the item that reaches the council names the vendor, the price and the scope. Then pull the executed contract, because the real retention period and the data-sharing terms live there, not on the vendor's website. When the papers stop, request the procurement file under your state's public records law. The catch: this gets you the paperwork, not a camera map.

Most people find out about a new camera from a photo somebody posted. The slower route is the useful one. A city that buys this gear has to run a procurement, and procurement leaves documents: a proposal, a bid or a reason for skipping the bid, a contract, a budget line, sometimes a policy.

Step 1: Work out who is doing the buying

Gear is bought by a department, approved by a government, and the government keeps the papers. Start by identifying the body that owns your police department: a city council, a county board, a state agency or a regional authority. Each has its own clerk and agenda portal. In Seattle, a Council Bill can be "an appropriation of public money", and the City Clerk publishes each bill in a weekly Introduction and Referral Calendar.[1] In Chicago, once a department identifies a need, "it is brought to DPS to procure the needed goods or services", where DPS is the city Department of Procurement Services.[2]

Step 2: Read the agenda and the legislative file

The clerk's portal is where the purchase first becomes visible. Seattle's City Clerk says you can "Access published meeting agendas in the City Clerk's Legislative Information Center", and it offers subscriptions to council agendas, action summaries and the referral calendar.[3] Subscribe: it puts the agenda in your inbox before the meeting.

Seattle also publishes how the file moves: the clerk assigns a bill number, the council adopts the weekly referral calendar, the item goes to a committee, and bills voted out of committee land on the full council agenda, where "each committee reports its recommendations as to whether the Bill should be passed or not passed."[1] Public comment is where you can still change the outcome: "Public hearings are a formal opportunity for members of the public to comment".[1]

Run the vendor's name and the product words, because a clerk writes the item title: "license plate reader", "ALPR", "camera", "gunshot detection", "drone". Add "agreement", "sole source", "bid", "RFP". Search the whole archive, not just this year.

Step 3: Get the contract, not just the agenda

The agenda tells you a purchase happened. The contract tells you what it does. Chicago is unusually open: its procurement page says "To search for and view scanned copies of awarded contracts (2003 to date), please search the Contract Award & Vendor Database", and it also publishes bid tabulations, a vendor, contract and payment search, and its sole-source procurements.[2] Those are the categories to look for in your own city procurement office.

Read the contract for five things: term and price, how many units and what they collect, the retention schedule, the data-sharing terms, and whether the purchase rides on a framework agreement. If there is no bid tabulation, the trail is not over. Chicago's page explains that under the Illinois Municipal Purchasing Act, which it cites as "Contracts Not Requiring Competitive Bids", non-competitive procurement "is used for the procurement of goods and services which by their nature are not adapted to award by competitive bidding".[2] When a purchase skips the competition, the written justification is a document, and that document is usually the interesting one.

Step 4: Read the budget line

The budget is public before the contract is. Seattle's City Clerk notes that the budget is two documents, a budget ordinance giving departments "the authority to spend City funds" and a Capital Improvement Program covering "infrastructure and systems", and that copies of proposed and adopted budgets are available at the City Budget Office, the City Clerk's Office and the public library.[4] Look for a new or expanded police or public safety line: a new line item with a vendor name beside it is often the first public trace of a purchase.

Step 5: Read the retention number in the contract, not on the vendor's website

This is where readers get the wrong number, because the vendor's public page and your contract are not the same document. Flock Safety's License Plate Reader Policy, last updated 30 June 2026, says "LPR data is hard deleted on a rolling 7-day basis by default", and that the schedule changes "if a different schedule is required by a customer's law or policy."[5] Flock's FAQ says the same thing more plainly: "The customer sets its own data retention period, based on its own policy and applicable law. Flock recommends a 7-day default."[6] Your city is the customer, and the City of Boulder publishes 14 days, "after which it is automatically deleted from the system".[7] Fourteen days, not seven, because Boulder set it.

The same documents tell you who owns the data. Flock's policy says LPR data "is owned by the customer" and that customers "choose whether to share LPR data with other customers in accordance with their laws and policies."[5] Boulder adds that "All requests to share access to our data must be approved by a supervisor, logged, and tracked through strict audit trails", and that as of June 2025 it deactivated the national lookup feature.[7] Whether your contract names a sharing partner, or your city barred one, is the difference between a local tool and a networked one.

Step 6: Ask the agency for the procurement file

When the public trail runs out, request the rest. The request goes to a named office, not to the police chief. Seattle's public records page gives a mailing address, an email address and a Public Records Request Center.[8] Its rules page lists the Washington Public Records Act in chapter 42.56 RCW and the city's own disclosure policy.[9] Put your own state's references in the letter; they set the deadline.

In Washington the clock starts fast: within five business days an agency must respond in one of five ways, including "Providing the record", acknowledging the request with a reasonable estimate, asking you to clarify, or "Denying the public record request."[10] Money is not the obstacle people expect. Seattle's fee schedule says the city "does not charge for inspecting public records", and for large requests it may "Require a deposit of up to 10 percent of the estimated cost before making copies."[11] Put a dollar limit in the letter anyway.

Ask for documents, not answers. Name the vendor, the product and the date range, then request the solicitation and every bid, the bid tabulation, the sole-source justification, the executed contract and its exhibits, the funding source, the use policy, any data-sharing agreement, and the query logs. Federal money means a separate request under FOIA: the request "must be in writing and reasonably describe the records you seek", there is no initial fee, and there is usually no charge "for the first two hours of search time or for the first 100 pages of duplication."[12] Agencies get 20 working days to decide, extendable by ten more working days for "unusual circumstances" if they give you written notice.[13]

Step 7: When the answer is no

Denial is a step, not an ending. Under Washington's law, when an agency decides a record is exempt, "the person may request the attorney general to review the matter", and the attorney general "shall provide the person with his or her written opinion on whether the record is exempt."[14] Federal denials work the same way: FOIA.gov says an appeal is a letter or email to the agency's designated appeal authority, and it costs nothing.[12] Make the agency name the exemption, then narrow and refile.

What this trail will not tell you

A contract tells you what was bought, not where the units went or how many are live; a camera location list is a separate record to ask for. The paper trail starts when the paper starts: pilots and memoranda of understanding that never reached an agenda leave no legislative file, because the clerk publishes what reaches the council.[1] Non-competitive and emergency purchases never produce a bid tabulation either.[2] And records can be legally off limits: Washington's law exempts investigative and law enforcement records,[15] and personal information,[16] and FOIA carries nine exemptions of its own.[12]

None of this tells you what the equipment does in practice. That is a use-policy and audit-log question, and Flock's policy notes that queries are logged for auditing, with a username, date, time and the stated purpose of the search.[5] Ask for those logs.

Related Reading

Sources

  1. City of Seattle, City Clerk: How a Bill Becomes a Law (Office of the City Clerk, legislative process overview).
  2. City of Chicago, Department of Procurement Services: Contract Administration (awarded contracts, bid tabulations, and purchases made without competitive bidding).
  3. City of Seattle, City Clerk: City Council Agendas (Office of the City Clerk, published meeting agendas and subscriptions).
  4. City of Seattle, City Clerk: City Budget Process (Office of the City Clerk, budget ordinance and Capital Improvement Program).
  5. Flock Safety: License Plate Reader Policy (vendor policy page, last updated 30 June 2026).
  6. Flock Safety: Frequently Asked Questions (vendor FAQ, data retention and what the cameras capture).
  7. City of Boulder: Flock Safety Cameras and Boulder Police Department (police department page published by the city).
  8. City of Seattle: Public Records (where to send a public records request).
  9. City of Seattle: Public Records Rules and Resources (the state statute, the advisory model rules, and the city policy that governs the answer).
  10. Washington State Legislature: RCW 42.56.520, Prompt responses required (primary statute).
  11. City of Seattle: Public Record Fee Schedule (no charge for inspecting records, and the fee schedule for copies).
  12. FOIA.gov: Freedom of Information Act Frequently Asked Questions (U.S. Department of Justice, Office of Information Policy).
  13. FOIA.gov: Freedom of Information Act Statute (5 U.S.C. 552, as published by the Department of Justice).
  14. Washington State Legislature: RCW 42.56.530, Review of agency denial (primary statute, appeal to the Attorney General).
  15. Washington State Legislature: RCW 42.56.240, Investigative, law enforcement, and crime victims (primary statute, exemptions).
  16. Washington State Legislature: RCW 42.56.230, Personal information (primary statute, personal information exemptions).