Technology · Data retention
Every record needs
an ending.
Operational software earns trust by explaining not only what it collects, but why that record remains useful tomorrow and what causes it to disappear. Different data deserves different answers.
The discipline
Retention is a schedule attached to a purpose.
Keeping everything forever feels safe until old records become an access burden, a privacy risk, and a dataset nobody can explain. Deleting everything quickly can also erase information needed for an active claim or a legitimate accounting duty.
The responsible question is record by record: what job does this serve, who may use it, which rule sets the minimum or maximum period, and what event starts the clock?
The inventory
Four records, four retention questions
Do not hide behind one global number
Plate
Recognition record
Is the plate needed only to match an active session, or is it entering a searchable history? Those are materially different systems.
Photo
Condition capture
Does the image support an open vehicle session, a claims window, or both? Preserve the original and define the review boundary.
Location
Operational event
A location fact may validate a curb event without justifying a continuous movement history.
Message
Guest communication
Delivery, consent, and support records can have different purposes from the message body itself.
California's ALPR law requires careful reading
The statute defines an ALPR operator as a person operating an ALPR system, and 'person' includes private entities. That does not create one universal retention number.
Operators
Broader than police
California Civil Code 1798.90.5 defines a person broadly, so private organizations can fall within the operator framework.
Policy
State the retention period
Covered operators and end-users must publish a usage and privacy policy that says how long ALPR information is retained and how destruction is decided.
60 days
Proposed, not current law
SB 274 would have imposed a 60-day limit on certain public-agency ALPR data. The governor vetoed it in 2025, and the veto was sustained in 2026.
→Primary sources: current California Civil Code 1798.90.5 through 1798.90.55, the governor's 2025 SB 274 veto announcement, and the official SB 274 bill status recording that the veto was sustained on March 2, 2026, reviewed August 23, 2026. This is operational guidance, not legal advice.
Build a retention decision that can be audited
→A policy without an executable deletion path is an aspiration. A deletion job without a documented policy is an unexplained risk.
The buyer's review
Ask for the table, not the slogan.
A useful vendor answer lists each record type, purpose, default period, available configuration, access scope, legal-hold behavior, deletion mechanism, and backup treatment. Local counsel should assess the jurisdictions and contracts that apply to the specific operation.
The takeaway: trust comes from making the life of data finite, explainable, and enforceable.
