<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Privacy on No Semicolons</title><link>https://nosemicolons.com/tags/code-privacy/</link><description>Recent content in Code Privacy on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2026 09:44:09 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/code-privacy/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Privacy Leak: How Your Generated Code Is Accidentally Exposing Sensitive Data (And 5 Prevention Patterns)</title><link>https://nosemicolons.com/posts/ai-code-generation-privacy-leak-prevention-patterns/</link><pubDate>Sun, 12 Jul 2026 09:44:09 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-privacy-leak-prevention-patterns/</guid><description>&lt;p>Ever copy-pasted AI-generated code only to realize later it contained a hardcoded API key that looked suspiciously real? You&amp;rsquo;re not alone, and it&amp;rsquo;s more common—and dangerous—than most of us realize.&lt;/p>
&lt;p>I learned this the hard way last month when reviewing a teammate&amp;rsquo;s pull request. Buried in what looked like perfectly innocent AI-generated database connection code was a MongoDB connection string with credentials that, while not ours, were clearly from someone&amp;rsquo;s actual development environment. The AI had essentially leaked another developer&amp;rsquo;s sensitive data through our code generation.&lt;/p></description></item></channel></rss>