Project ideas from Hacker News discussions.

Data collected by cars and sold to third parties

📝 Discussion Summary (Click to expand)

1. Pervasive data collection in modern vehicles
Many commenters note that cars constantly harvest and transmit telemetry—location, speed, diagnostics, even microphone/audio data—to manufacturers, insurers, and third‑party brokers.
- “All European car manufacturers pull a crazy amount of telemetry data from your car… Either via permanent 4G/5G link or during service intervals.” – BlackRabbit1
- “Your mileage went from VW → telematics vendor → broker → carfax… the owner is the only one without the record.” – samsullivan
- “EU was about privacy… nowadays it did a complete U‑turn and legislates mandatory anti‑privacy union‑wide laws every year.” – Yizahi (listing Chat Control, eIDAS, ADDW, etc.)

2. Technical work‑arounds to stop the spying
Users discuss hardware‑level fixes—pulling fuses, disconnecting antennas, using 50 Ω terminators, or Faraday cages—as the only reliable way to prevent data leakage.
- “Pulling the telematics module fuse… is a much lighter touch.” – willis936
- “The most reliable way to permanently silence the cellular modem is to pull the relevant fuse.” – drnick1
- “Best to use a termination, to avoid the power… reflecting back into the output driver transistors.” – femto
- “You could wrap the comms in a Faraday cage.” – tomrod

3. Regulatory and legal landscape (or lack thereof)
The thread contrasts weak U.S. state laws (CCPA, proposed CA bills) with increasingly invasive EU legislation, highlighting a gap between privacy rhetoric and actual enforcement.
- “You can invoke CCPA… to get a report of and/or delete your data.” – derwiki
- “The CA assembly has passed AB‑1542… making the sale and sharing of ‘sensitive’ personal information illegal.” – jboggan
- “EU… legislates mandatory anti‑privacy union‑wide laws every year… Chat Control law, now all messaging must be intercepted and monitored.” – Yizahi

4. Convenience vs. privacy: consumer behavior and the appeal of older cars
Many acknowledge that most drivers choose convenience (remote start, OTA updates, infotainment) over privacy, while a minority prefer older, “dumb” vehicles to avoid surveillance altogether.
- “When given the choice between privacy and convenience, the great majority of consumers choose convenience over and over again.” – pnw
- “Another reason to use a car from 90's or 2000's… they won’t burn oil like a modern car + more durable and repairable metal parts.” – everyone
- “I really wanted a modern car because of the fancy automation stuff… but it never is economical or more environmental friendly.” – herbst
- “I’d rather have my data hoarded by a crazy right‑winger Elon, than by Stellantis or VW… being sold to each other.” – Yizahi

These four themes capture the core of the discussion: ubiquitous vehicle data collection, the technical means to thwart it, the evolving (and often inadequate) legal framework, and the tension between convenience‑driven adoption and privacy‑conscious resistance.


🚀 Project Ideas

Telematics Kill Switch (TKS)

Summary

  • A plug‑and‑play OBD‑II dongle that physically disconnects the car’s cellular/GPS antenna when activated, stopping all covert telemetry while preserving local functions like diagnostics and infotainment.
  • Core value proposition: gives owners a reliable, reversible hardware kill switch for data‑spying without sacrificing essential car features.

Details

Key Value
Target Audience Privacy‑conscious car owners, especially those with modern vehicles that have embedded telematics modules
Core Feature Mechanical relay that cuts power/coax to the telematics antenna; LED status indicator; optional manual toggle switch
Tech Stack PCB with relay, OBD‑II connector, MOSFET driver, STM32 microcontroller for status logging, optional Bluetooth low‑energy for phone app
Difficulty Medium
Monetization Revenue-ready: $29.99 per unit (hardware) + optional $4.99/mo app for usage stats

Notes

  • HN users repeatedly asked for a sure way to disable the modem: “pull the fuse… but that also kills maps/emergency services” (willis936, kevin_thibedeau). A dedicated kill switch solves this cleanly.
  • Provides a tangible discussion point for right‑to‑repair and hardware‑based privacy mods, likely to spark threads on iFixit‑style teardowns.

CarTelemetry Monitor (CTM)

Summary

  • Open‑source software that runs on a Raspberry Pi or Android device connected via OBD‑II to sniff, log, and telemeter the car’s outbound cellular/GPS packets, showing users exactly what data is being sent and to whom.
  • Core value proposition: transparency into car data flows, enabling informed decisions about blocking or consenting.

Details

Key Value
Target Audience Developers, privacy researchers, and technically inclined car owners who want to audit what their vehicle is transmitting
Core Feature Real‑time packet capture, decryption of common OBD‑II protocols (UDS, ISO‑TP), dashboard showing destination IPs, data types (GPS, speed, VIN), and ability to generate block‑lists
Tech Stack Python 3, Scapy, pysocketcan, optional Android UI with Kotlin, Docker container for easy deployment
Difficulty High
Monetization Hobby

Notes

  • Commenters lamented the opacity of data flows: “Your mileage went from VW->telematics vendor->broker->carfax” (samsullivan). CTM makes that chain visible.
  • Enables community‑driven block‑list sharing (like ad‑block lists), fostering collaborative privacy defenses and discussion on HN about reverse‑engineering OEM telematics.

DataBroker Opt‑Out Service (DBOO)

Summary

  • Automated service that submits CCPA/GDPR right‑to‑know and deletion requests to data brokers, car manufacturers, and telematics aggregators on behalf of the user, tracking responses and providing proof of compliance.
  • Core value proposition: saves users the tedious, often futile manual process of exercising their legal data rights.

Details

Key Value
Target Audience Consumers in jurisdictions with data‑access laws (CCPA, GDPR, emerging state laws) who want to erase or limit their vehicle‑derived data profiles
Core Feature Pre‑filled request templates per company, authenticated submission via email/API, response tracking dashboard, optional legal‑escalation workflow
Tech Stack Node.js backend, React frontend, encrypted storage for user credentials, integration with services like Mailgun for outbound requests
Difficulty Medium
Monetization Revenue-ready: $9.99/mo subscription (tiered for number of requests)

Notes

  • Users expressed frustration with the difficulty of opting out: “You can invoke CCPA… but most companies will find ways to deny you” (jboggan). DBOO automates the follow‑up and escalation.
  • Provides a concrete tool for privacy advocates to discuss on HN, potentially spawning data‑broker transparency reports.

Faraday OBD Adapter (FOA)

Summary

  • A compact Faraday‑cage enclosure that fits over the OBD‑II port’s internal telematics antenna connector, attenuating cellular/GPS signals while still allowing wired diagnostics (e.g., for mechanics) via shielded pass‑through.
  • Core value proposition: easy, reversible RF shielding for the telematics module without needing to pull fuses or modify wiring.

Details

Key Value
Target Audience Car owners who want a non‑invasive way to block telematics but still retain OBD‑II access for service and diagnostics
Core Feature Magnetic snap‑on shield with 30 dB attenuation at 700 MHz‑2.7 GHz, built‑in SMA pass‑through for diagnostic cables, LED indicator when shield is seated
Tech Stack Mu‑metal or nickel‑zinc ferrite sheet, 3D‑printed ABS housing, spring‑loaded pogo pins for OBD‑II contacts
Difficulty Low
Monetization Revenue-ready: $19.99 per adapter

Notes

  • Several commenters tried pulling fuses or antennas but feared side effects: “pulling the fuse… also disables maps, contacting emergency services” (brookst). FOA offers a targeted RF block that leaves other circuits untouched.
  • Invites discussion on effectiveness of DIY shielding vs. hardware kills, likely to generate practical test‑result threads on HN.

Read Later