Vendor-hosted analytics

Evidence rule

This page is public-interest research. An argument grade is not a court finding. A watchdog page describes the device. It is not proof a Nevada agency bought it or turned a feature on. A product description is not a Nevada practice. Agencies are not merged: the City of Las Vegas Department of Public Safety, the Las Vegas Metropolitan Police Department, the Clark County School District, the City of Reno, and the Nevada Department of Public Safety stay separate. A hotlist hit is not a confirmed crime. Legal review of this page is unverified.

What it does

Vendor-hosted analytics is software a company runs for an agency: link charts, plate searches, or models, on the company’s servers. The agency uploads or connects its data. The vendor’s staff and the vendor’s other customers are the access question. The analytic itself may have its own card.

Privacy watchdog concerns

No watchdog page is attached.

Constitutional issues

Unresolved question

No constitutional provision is attached. The factual record is not sufficient.

Warrant practice not established for a Nevada agency

Vendor-hosted analytics: No Nevada analytics-hosting contract is documented beyond the systems already on their own cards. A vendor login is not a new constitutional holding.

No decision in this library decides vendor-hosted analytics as a class.

Statutes attached to read, not findings.

NRS Chapter 239. Nevada public-records law is the route to ask for contracts, policies, and logs. Citing it is not a finding that a surveillance practice is unlawful.

Nevada use

Not documented on this page.

Capability only. Named products stay on their own cards.

Next record

Vendor-hosted analytics: Do not merge Fog, Flock, or a face vendor into one hosting card.

All devices. A document workflow for this page is not built. The arrest correction form is not a surveillance-document inbox. Corrections and source documents for this page follow the corrections policy. Corrections policy.