<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Privacy Engineering on The Coders Blog</title><link>https://thecodersblog.com/tag/privacy-engineering/</link><description>Recent content in Privacy Engineering on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 07:52:17 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/privacy-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Vehicle Telemetry: The Illusion of Opt-Out in Modern Cars (2026)</title><link>https://thecodersblog.com/the-illusion-of-opt-out-modern-vehicles-and-unavoidable-data-collection-2026/</link><pubDate>Fri, 01 May 2026 07:52:17 +0000</pubDate><guid>https://thecodersblog.com/the-illusion-of-opt-out-modern-vehicles-and-unavoidable-data-collection-2026/</guid><description>&lt;p&gt;You&amp;rsquo;re building the future of mobility, but are you also unwittingly designing its most sophisticated surveillance system? In 2026, the &lt;strong&gt;&amp;lsquo;opt-out&amp;rsquo; button&lt;/strong&gt; in our vehicles is often just a placebo, masking an intricate web of unavoidable vehicle data collection. This is not hyperbole; it is the fundamental reality of connected cars today, a reality that every architect and privacy engineer must confront.&lt;/p&gt;
&lt;h3 id="the-unseen-costs-why-opt-out-is-an-illusion-not-a-feature"&gt;The Unseen Costs: Why &amp;lsquo;Opt-Out&amp;rsquo; is an Illusion, Not a Feature&lt;/h3&gt;
&lt;p&gt;The narrative around vehicle data often centers on &amp;ldquo;connected services&amp;rdquo; and &amp;ldquo;safety enhancements.&amp;rdquo; Beneath this veneer lies a far more cynical truth: &lt;strong&gt;manufacturers&amp;rsquo; drive for data monetization&lt;/strong&gt; is the primary force behind pervasive collection. Our vehicles are rolling data mines, generating streams of valuable insights that can be packaged and sold.&lt;/p&gt;</description></item><item><title>Maryland's Ban on Surveillance Pricing: The Technical Imperative for Ethical Data Design in 2026</title><link>https://thecodersblog.com/maryland-becomes-first-state-to-ban-surveillance-pricing-in-grocery-stores-2026/</link><pubDate>Wed, 29 Apr 2026 21:32:27 +0000</pubDate><guid>https://thecodersblog.com/maryland-becomes-first-state-to-ban-surveillance-pricing-in-grocery-stores-2026/</guid><description>&lt;p&gt;Maryland&amp;rsquo;s new &amp;lsquo;Protection From Predatory Pricing Act&amp;rsquo; isn&amp;rsquo;t just another compliance checkbox; it&amp;rsquo;s a technical earthquake demanding a complete re-evaluation of how your data pipelines manage pricing models, right now.&lt;/p&gt;
&lt;h2 id="the-shifting-sands-of-pricing-ethics-marylands-gauntlet"&gt;The Shifting Sands of Pricing Ethics: Maryland&amp;rsquo;s Gauntlet&lt;/h2&gt;
&lt;p&gt;Maryland&amp;rsquo;s &lt;strong&gt;HB 895&lt;/strong&gt;, effective &lt;strong&gt;October 1, 2026&lt;/strong&gt;, isn&amp;rsquo;t a distant future problem. For senior engineers and architects, this date marks an immediate architectural imperative. The law outright bans using an individual&amp;rsquo;s personal data to set higher prices for groceries and delivery services. This isn&amp;rsquo;t a subtle nudge; it&amp;rsquo;s a legislative sledgehammer for any system relying on individualized dynamic pricing.&lt;/p&gt;</description></item></channel></rss>