Research, policy & council record
Separate official statements, campus reporting, vendor material and community map data. The APD portal and current City Council roster were checked October 7, 2026.
The APD-described data model.
APD’s July 23, 2026 statement describes what its Flock system captures and what it says the system does not do. This is APD’s description of its own deployment.
APD says its system does not:
Check APD’s current policy links.
The new City portal page links APD operating procedures, general policy and an ALPR policy. Current retention settings and sharing details were not independently extracted in this review. Consult those live disclosures before relying on the older D-34 document.
The March 2022 procedure is retained only as historical background. Its five-year provision is not presented here as the current fixed-Flock setting.
Open current APD policy links30 days, with preservation exceptions
ACU’s published rule permits scans to be kept beyond 30 days for a criminal investigation, case or other legitimate law-enforcement purpose. It requires authorized access, documented search reasons and audit review. These are ACU’s stated safeguards, not an independent compliance finding.
Read ACU policyA lack of continuous GPS tracking does not mean sightings cannot be searched across time and locations. Camera observations and continuous GPS are different data sources.
Who voted for the existing 13-camera deployment?
That individual roll call has not been established in the records reviewed for this build. The site does not assign a yes/no vote without a specific agenda, minutes, resolution, contract approval, or purchasing record.
September 24 meeting: the City agenda listed a Flock presentation and public hearing. APD subsequently announced its portal on September 29. Separately, local reporting describes approval of the Axon equipment package. These records do not establish who originally authorized the existing Flock deployment.
City Council
Council roster checked against the City’s directory on October 1, 2026.
Official Council pageFind the authorization trail
Request the earliest Flock quote, contract, purchase order, invoice, signature page, cooperative-purchasing document, delegated authority, agenda item, minutes, resolution, and roll call connected to the current system.
Use the prepared requestPrimary records first. Community mapping second.
Every major factual claim should carry a source and date. Community mapping is useful evidence but is not a substitute for contracts, inventories, policies, or agency records.
Current APD policy entry point
The City links operating procedures, general policy and ALPR policy. The older March 2022 D-34 is historical, not a verified current configuration.
Read sourceCommunity location snapshot
28 coordinate records retrieved October 1 from Flock Camera, attributed to OpenStreetMap / DeFlock community mapping. This is not a complete or verified camera census.
Read sourceSeptember 25 · Axon reporting
KTAB/KRBC report: 28 Outpost units within the wider equipment package; locations not identified in that report.
Read sourceLocation confidence
Confirmed location: device-level primary evidence checked against geography; a group count does not qualify. Community-reported: a third-party claim, even if its publisher uses a verification badge. Disputed: conflicting evidence; withheld from verified listings. Reported: credible but not independently established. Unknown: insufficient evidence.
Owner confidence
Tracked separately from location. A camera may be physically verified while its purchaser, operator, property owner, or data-access partners remain unresolved.
Corrections
Preserve the old claim, record the correction source, add a date, and update the confidence label rather than silently rewriting the history.
September 29 · Portal launch
Official APD announcement and direct portal destination.
Read source · Open portalHardware references
Product capabilities should not be generalized between vendors or models.
Axon Outpost · Flock LPRReview limits · October 1
Portal launch verified; live dashboard values and linked policy PDFs not independently extracted. No new field inspections. Disputed entries remain excluded. Map refreshes can change the dataset.