Cloud-Managed Video in Texas: LPR, Loitering Analytics & Compliance - Avenger Security

Texas Network Video Licensing: Chapter 1702 Basics

Texas licensing rules for network video systems are broader than a simple distinction between “storage-only” cameras and “active” video analytics. A project's licensing requirements can depend on who sells, installs, services, monitors, or responds to the system—not just whether the software uses license plate recognition or loitering detection.

The Texas Department of Public Safety has specifically stated that a company selling and installing cameras that transmit or store images over a computer network fits within Chapter 1702's treatment of alarm systems and alarm systems companies. Customers and integrators should verify the current law, exemptions, company license, individual registrations, and exact scope before work begins.

This article is general information, not legal advice. Texas laws and agency interpretations can change. Confirm the current requirements with Texas DPS Regulatory Services, qualified counsel, and the authority responsible for the project.

The licensing question starts with the service being provided

Texas Occupations Code Chapter 1702 addresses companies that sell, install, service, monitor, or respond to alarm systems. Texas DPS also publishes guidance specifically addressing network video systems. That means an integrator should not assume that ordinary recording, cloud storage, or the absence of AI analytics automatically removes the work from the licensing framework.

An exemption may apply to a business that sells qualifying equipment exclusively through e-commerce, over-the-counter transactions, or mail order. Selling equipment is different from installing, configuring, servicing, or monitoring it. The exact facts matter.

Questions customers should ask a video provider

  • What Texas company license applies to the proposed work?
  • Are the individuals installing or servicing the system properly registered for their work?
  • Is the provider only selling equipment, or also installing, configuring, maintaining, monitoring, or responding?
  • Who owns and administers the cloud account?
  • Which party reviews alerts, video clips, license plates, or exported evidence?
  • Will any third party receive direct access to live or recorded video?
  • What retention, access, export, deletion, and incident-response policies are included?

Analytics add privacy and operational questions

License plate recognition, loitering rules, person or vehicle classification, facial-analysis features, and other analytics can create additional privacy, cybersecurity, policy, and contractual concerns. They do not create a universal licensing shortcut, and they should not be enabled without a clear operational purpose.

  • Define the purpose: Identify the risk or workflow the analytic is intended to address.
  • Limit access: Use individual accounts, least-privilege roles, and multi-factor authentication where supported.
  • Set retention intentionally: Match recording and event retention to the organization's documented needs.
  • Control sharing: Establish who may view, export, or disclose video and how requests are documented.
  • Test performance: Adjust detection zones and schedules for lighting, weather, traffic, and site conditions.
  • Review agreements: Identify recurring cloud fees, monitoring responsibilities, data ownership, cancellation terms, and support limits.

Cloud storage is not the same as live video response

A cloud-managed video platform may provide recording, remote viewing, device-health alerts, analytics, or multi-site administration. Remote video guard monitoring is a separate service that can involve event review, scheduled tours, audio talk-down, customer notification, or other response steps under a written plan.

Do not describe every cloud camera as continuously monitored. The proposal should identify which cameras and events are reviewed, during what hours, by whom, and what happens after an event.

Official Texas resources

Get the scope and credentials in writing

A customer should receive a written proposal identifying the cameras, recorder or cloud platform, storage period, analytics, network responsibilities, licenses, installation labor, monitoring or review services, recurring fees, and exclusions. Avenger Security can plan licensed network-video deployments for Austin and Central Texas properties.

For system design and pricing considerations, see our cloud-managed video surveillance guide, remote video guard monitoring guide, and IP camera cybersecurity guide.

Back to blog