Blog

Analysis. Updates. The case for owner-controlled vehicle data.

Why "Right to Encrypt" — Not "Right to Privacy"

Privacy arguments have been losing for two decades. Property rights arguments win. The Right to Encrypt is a positive right — you own the keys to data produced by property you own. That's not a request. It's a statement of existing constitutional principle applied to a new category.

290 Lines of Code: What It Actually Takes

Every connected vehicle already has AES for secure boot and TLS for cellular. The encryption module for owner-controlled telematics is ~290 lines of firmware. The crypto primitives exist. The secure elements exist. The only thing missing is the requirement.

The Secret Service Problem: National Security and Cleartext Vehicle Data

The government banned Chinese components from vehicle data streams because of the intelligence risk. American OEM clouds hold the same data under no equivalent protection. One data breach from GM exposes presidential motorcade patterns. The architecture that created this risk is the same one every American driver operates under.

These Are the First Robots: Why the Vehicle Precedent Matters for Everything

Connected vehicles are mass-deployed robots. The data sovereignty rules we write for them will govern autonomous vehicles, delivery drones, household robots, surgical systems, and agricultural machines. We have one chance to set this right.

The Massachusetts Trilogy: Repair (2012) → Access (2020) → Encrypt (Next)

Massachusetts Chapter 93J carved out telematics in 2012. Question 1 gave access in 2020. Neither gave control. The Right to Encrypt is Act III — the completion of a 14-year legislative arc.

The EPA Doesn't Require This: Debunking the Regulatory Necessity Argument

OEMs claim continuous telemetry is required for regulatory compliance. It is not. The EPA requires on-board monitoring and periodic inspection. The continuous cellular data stream is a $750 billion business decision disguised as a regulatory mandate.