Texas Public Records and Retention for Robot-Collected Data
Published
Law checked through .
Robot-generated information can be public information when it meets Chapter 552's conditions, including some vendor-held records. Disclosure, confidentiality, law-enforcement exceptions, trade secrets, retention, and litigation preservation are separate questions. A vendor's label does not automatically authorize withholding, and a public-information request does not permit destruction of other required records. Texas agencies should secure usable access and apply the actual record-specific law. [1; 2; 3]
Public information and vendor possession
Section 552.002 defines public information through the statutory relationships and circumstances. Physical possession is not the only relevant fact. A vendor storing agency footage or telemetry can hold information within the definition even where the agency accesses it through a dashboard. [1]
The contract should identify agency access, search, export, metadata, documentation, assistance, costs, and continued availability after termination. The entity should know whether it can obtain the underlying records or only a selected report. Public duties can be difficult to perform if those rights are considered only after a request arrives.
Classify the record and applicable restrictions
Video, audio, maps, commands, mission logs, purchase records, and maintenance data can raise different exceptions. Section 552.101 addresses information confidential by law; § 552.108 addresses specified law-enforcement information; § 552.110 addresses particular trade-secret and commercial-information conditions. Each requires the actual provision and facts. [1]
A vendor's confidential stamp or general agreement is not automatically a statutory exception. Conversely, public-information status does not override a separate confidentiality statute. The agency should identify the precise information and legal basis rather than withhold an entire robotic program's records under one broad label.
Drone imagery has a separate rule
Chapter 423 includes restrictions concerning specified illegally or incidentally captured images, including evidence, disclosure, and compelled release, subject to its exception. Section 423.005 should be examined before assuming every government drone image is releasable under the ordinary Chapter 552 analysis. [4]
Law-enforcement drone-use reporting under § 423.008 is another distinct duty. The report's publication requirement does not necessarily require publication of every underlying image, and a public-information request is not a substitute for the statutory use report. [4]
Requests, decisions, and deadlines
Chapter 552 establishes procedures and timing for responding and obtaining Attorney General decisions where required. Section 552.301 and related provisions must be applied to the actual request and claimed exception, including any applicable prior determination or other rule. The agency should not assume that a vendor's review process automatically extends the statutory time. [1]
The response process should identify custodians and systems, preserve responsive information, obtain vendor assistance, and separate releasable and protected material as required. Redaction and technical export should be planned before the program generates large volumes of sensor records.
Retention and lawful disposition
State records and local-government records have different retention frameworks. Government Code Chapter 441 and Local Government Code records provisions should be applied with the actual approved schedules and record series. The robot's storage capacity or a vendor's default deletion period does not itself determine the lawful retention period. [2; 3]
Local Government Code Chapter 202 addresses destruction and alienation, including conditions and restrictions. A pending request, litigation, audit, or other applicable duty can affect disposition under the actual law. No universal rule requiring all robot data to be kept forever should be invented, but neither should ordinary deletion proceed without checking the relevant holds. [3]
Security and confidential data
The program should identify access, authentication, logs, vendor personnel, transfers, and secure disposition. Information about individuals, sensitive facilities, or confidential technology may require particular protections. Retention and security should be coordinated so that required evidence remains usable without unnecessary exposure.
An AI feature can add processing and disclosure questions under TRAIGA, while a public-entity exemption under one privacy statute does not remove every records or confidentiality duty. The actual information and authority remain the basis for the decision. [5]
Hypothetical vendor exit
A city ends a robot subscription while a records request and injury investigation are pending. The agency should identify responsive and preserved information, secure usable exports and metadata, maintain applicable restrictions, and suspend deletion where required. Terminating the commercial account does not itself authorize destruction or discharge the city's obligations.
Sources
- Texas Government Code Chapter 552, especially §§ 552.002, 552.101, 552.108, 552.110, and 552.301 with related procedures.
- Tex. Gov't Code ch. 441
- Tex. Loc. Gov't Code ch. 202
- Texas Government Code §§ 423.005 and 423.008.
- HB 149 enrolled text
