Amidst a major auto industry shift to electric vehicles (EVs) and software-driven mobility, a new survey shows that almost all drivers want to have ownership over their own vehicle data—though consumer awareness on data privacy and ownership are still lacking.
As part of a survey of over 1,300 adults who lease or own vehicles that they drive at least once a week, car insurance app Jerry reported last month that 96 percent of respondents said they should be able to own any data generated by their vehicles. Similarly, 78 percent of those surveyed reported that they were either uncomfortable or extremely uncomfortable with having their data collected by automakers already.
You can see a few insights from the survey below, or check out the full report here.
Credit: Jerry Credit: Jerry Credit: Jerry
“People were nearly unanimous” in “thinking that they should own the data that is generated by their cars,” said Henry Hoenig, Jerry data journalist, in a statement to Automotive News.
The results come as many companies plan to use vehicle data as a consistent revenue stream, including manufacturers, insurance providers, and data brokers. On the consumer side, many may not be fully aware of how their vehicles are being connected to the internet, nor how their data is being used.
Data Collection in Modern Cars and Consumer Awareness
Teslarati spoke with Andy Chatham, co-founder of the connected vehicle platform Digital Infrastructure for Moving Objects (DIMO), about vehicle data ownership and privacy. He notes that modern cars include substantial amounts of data collection, such as Tesla’s 360-degree camera view around the cars as just one example. However, he also says that consumers are less likely to be aware of their vehicles’ data collection practices than they are with their cell phones.
“Generally, your vehicle is the most expensive or the second most expensive asset that you own, and traditionally people are very aware that their phones and their computers are connected to the internet,” Chatham said. “But especially with modern cars, it’s not always obvious that the car is also connected to the internet.”
Chatham says that most automakers aren’t generally following best practices surrounding cybersecurity, noting that many let third-party sub-contractors make those decisions for them, alongside other companies in the supply chain.
-
“Generally, [automakers are] not following best practices when it comes to how the vehicles are networked and how cybersecurity practices are implemented,” Chatham adds.
“I see a pretty big transition from the world of buying a phone and understanding that this is a device that has a lot of data collection going on, and buying a car and maybe acknowledging that once at the beginning, but never really understanding what that actually means.”
Chatham also says companies should open up their APIs for other developers to create applications using that data, and let vehicle owners access their own vehicle data and toggle permissions directly from their cars—not unlike what Tesla is currently doing.
However, even Tesla’s approach to vehicle data may leave a few things to be desired, and the company is one of many automakers to have faced legal action over the matter. Still, the DIMO co-founder estimates that Tesla is roughly three to five years ahead of the industry, perhaps except for Rivian.
Chatham also notes that as applications for car data improve more and more, and perhaps even offer certain data monetization options for consumers, owners will become more aware of vehicle connectedness. Still, the transition to this new public paradigm could be tricky for both consumers and developers.
“In order for that to even exist in the first place, there’s a chicken and egg problem, because developers don’t want to go cut separate deals with 10 different OEMs and get them to like agree to certain terms and use different APIs. They just won’t,” Chatham adds. “They just want to build to one thing, which is what they’re used to with both. It’s honestly a big enough pain in the ass to get developers to build an iOS and Android app and deal with two separate terms of service.”
“In the car world, Toyota is the biggest automaker and they’re, what, like 15 percent of cars? So it’s not the same dynamic, and then choice is the biggest thing that allows people to protect their own privacy because a lot of consumers don’t care.”
-
Automakers and the Use of Vehicle Data
Earlier this year, General Motors (GM) reported ceasing a partnership with one data broker, after discovering that the company had been selling customer data to insurance companies without gaining their consent. Public backlash ensued, and affected consumers said they witnessed inexplicable increases for their monthly insurance premiums, which were ultimately traced back to the telemetry program that had shared their data.
Ford and Progressive Insurance were involved in a similar case that brought data ownership and privacy to light in 2022. Last year, Mozilla said that all 25 car companies it examined as part of a study on privacy collected more personal data than necessary, even calling them “privacy nightmares.”
Unlike some companies, Tesla doesn’t sell or rent consumer data to third-party companies, though it does collect driver information on a fleet scale for its own purposes, as the company explains on its website.
“We’re committed to protecting you anytime you get behind the wheel of a Tesla vehicle. That commitment extends to your data privacy,” Tesla writes on its web page dedicated to the topic of privacy. “Our privacy protections aim to go beyond industry standards, ensuring your personal data is never sold, tracked or shared without your permission or knowledge.”
Tesla Insurance data has driven changes to vehicle design: Elon Musk
What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send us tips at tips@teslarati.com.
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
-
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
-
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
-✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
