<?xml version="1.0" encoding="utf-8"?>
<oembed>
  <version>1</version>
  <type>rich</type>
  <provider_name>Libsyn</provider_name>
  <provider_url>https://www.libsyn.com</provider_url>
  <height>90</height>
  <width>600</width>
  <title>The AI Wrote Your App. The Lawsuit Names You.</title>
  <description>Attorney Mitch Jackson warns that the rising trend of &amp;quot;vibe coding&amp;quot;—using AI to generate software from plain English—is creating a massive&amp;amp;nbsp;legal and financial liability&amp;amp;nbsp;for developers. Although AI makes app creation accessible, it often produces&amp;amp;nbsp;insecure code&amp;amp;nbsp;that lacks essential&amp;amp;nbsp;privacy protections&amp;amp;nbsp;required by state and federal laws. Because the law holds the human creator responsible for&amp;amp;nbsp;data breaches&amp;amp;nbsp;and&amp;amp;nbsp;compliance failures, &amp;quot;vibe coders&amp;quot; face severe penalties regardless of their technical expertise. The source emphasizes that developers must establish&amp;amp;nbsp;formal business entities, like corporations and LLCs, to shield their&amp;amp;nbsp;personal assets&amp;amp;nbsp;from lawsuits. Ultimately, the text serves as a call to action for creators to prioritize&amp;amp;nbsp;manual security reviews&amp;amp;nbsp;and&amp;amp;nbsp;accurate privacy policies over development speed. Learn more in Mitch's new book, &amp;quot;Privacy In America&amp;quot; available on Amazon in paperback, hardcover, Kindle and audio. </description>
  <author_name>AI In Law Podcast</author_name>
  <author_url>https://mitch-jackson.com</author_url>
  <html>&lt;iframe title="Libsyn Player" style="border: none" src="//html5-player.libsyn.com/embed/episode/id/41416340/height/90/theme/custom/thumbnail/yes/direction/forward/render-playlist/no/custom-color/88AA3C/" height="90" width="600" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen&gt;&lt;/iframe&gt;</html>
  <thumbnail_url>https://assets.libsyn.com/secure/content/202286430</thumbnail_url>
</oembed>
