<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[ClearVerse Insights]]></title><description><![CDATA[Inside the intersection of AI, music copyright, and tech. Analysis and insights from the team building legal intelligence for the AI-era music industry.]]></description><link>https://insights.clearverse.ai</link><image><url>https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png</url><title>ClearVerse Insights</title><link>https://insights.clearverse.ai</link></image><generator>Substack</generator><lastBuildDate>Thu, 30 Apr 2026 23:12:41 GMT</lastBuildDate><atom:link href="https://insights.clearverse.ai/feed" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><webMaster><![CDATA[clearverse@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[clearverse@substack.com]]></itunes:email><itunes:name><![CDATA[Christian Loarca]]></itunes:name></itunes:owner><itunes:author><![CDATA[Christian Loarca]]></itunes:author><googleplay:owner><![CDATA[clearverse@substack.com]]></googleplay:owner><googleplay:email><![CDATA[clearverse@substack.com]]></googleplay:email><googleplay:author><![CDATA[Christian Loarca]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Sony, UMG, and Warner Just Walked Away From $4.2 Billion in Lawsuits. The Pressure Has to Land Somewhere.]]></title><description><![CDATA[Cox v. Sony closed the labels' ISP playbook in March. On April 23, the three majors dismissed two of their biggest active cases inside 72 hours. The pressure isn't gone. It's redirecting.]]></description><link>https://insights.clearverse.ai/p/sony-umg-and-warner-just-walked-away</link><guid isPermaLink="false">https://insights.clearverse.ai/p/sony-umg-and-warner-just-walked-away</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 26 Apr 2026 23:58:37 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!Dtj0!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Dtj0!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Dtj0!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!Dtj0!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg" width="1456" height="1092" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1092,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:3206394,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.clearverse.ai/i/195574160?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!Dtj0!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Dtj0!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0ff12779-9d51-4369-b734-15d6064f431e_5355x4016.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>On April 23, attorneys for Sony Music Entertainment, Universal Music Group, and Warner filed joint stipulations of dismissal in two federal courts.</p><p>The Verizon case had been seeking $2.6 billion in damages. The Altice case had potential damages exceeding $1.6 billion. Both cases dismissed <a href="https://torrentfreak.com/record-labels-drop-piracy-lawsuits-against-altice-and-verizon-in-wake-of-cox-ruling/">with prejudice</a>, meaning they cannot be refiled. Each side bears its own costs and fees.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Combined damages walked away from inside 72 hours: more than $4.2 billion.</p><p>The legal reason is straightforward. On March 25, the Supreme Court ruled 9-0 in <a href="https://www.supremecourt.gov/opinions/25pdf/24-171_bq7d.pdf">Cox Communications v. Sony Music</a> that internet service providers cannot be held contributorily liable for their subscribers&#8217; copyright infringement absent specific intent to facilitate it. That ruling closed off the legal theory both lawsuits depended on.</p><p>The structural reason is what matters for the agencies and MCNs managing YouTube creators.</p><div><hr></div><h3>What the Cox ruling actually changed</h3><p>For two decades, the playbook was the same. Major label sues ISP. Argues the ISP knew users were pirating music and didn&#8217;t terminate accounts aggressively enough. Wins or settles for hundreds of millions. Repeats with the next ISP.</p><p>The 2019 Cox jury verdict was $1 billion. The Grande Communications verdict was $46.7 million. Sony, UMG, Warner, and ABKCO had filed against Verizon in 2024 seeking $2.6 billion, citing more than 500 subscribers who had each received over 100 infringement notices. The Altice complaint listed 6,700 sound recordings and 4,000 compositions allegedly infringed by Altice subscribers between 2020 and 2023.</p><p>In Cox v. Sony, all nine Supreme Court justices sided with the ISP. Justice Thomas, writing for the majority, drew the line: contributory liability requires proof that the provider intended its service to be used for infringement, demonstrated either through active inducement or by operating a service incapable of substantial non-infringing uses. Knowing that some subscribers infringe and continuing to serve them isn&#8217;t enough.</p><p>Justice Sotomayor, joined by Justice Jackson, concurred in the judgment but criticized the majority. Her concern was that the new rule lets ISPs sell connections to known infringers without facing meaningful liability, gutting the incentives Congress wrote into the DMCA&#8217;s safe harbor.</p><p>The fallout was immediate. The Supreme Court vacated the $46.7 million Grande verdict and remanded for reconsideration. X cited Cox in a court filing two days after the ruling, arguing music publishers&#8217; long-running case against the platform should be dismissed; that case was <a href="https://www.digitalmusicnews.com/2026/04/03/music-publishers-x-lawsuit-settlement/">paused indefinitely on April 3</a>. Meta invoked Cox in its summary judgment filing against Epidemic Sound. RCN cited Cox in pushing back against active label claims. Then on April 23, the labels jointly dismissed Verizon and Altice.</p><p>Inside 30 days, more than $5 billion in active label-versus-ISP litigation either evaporated, paused, or got vacated. That&#8217;s the most significant retreat the music industry has made from off-platform copyright enforcement in two decades.</p><div><hr></div><h3>The legislative move that&#8217;s already underway</h3><p>Within ten days of the Cox ruling, Senator Thom Tillis (R-NC) and Representative Zoe Lofgren (D-CA) reportedly began merging their separate site-blocking proposals into one bicameral bill. The unified version would require ISPs and large DNS providers (think Cloudflare, Google&#8217;s public DNS) to block foreign piracy sites under court order. Tillis isn&#8217;t running for reelection. The deadline for getting the bill through Congress runs out in January 2027.</p><p>Site-blocking legislation hasn&#8217;t had this kind of bipartisan traction since SOPA derailed in 2012. Whether it actually passes is uncertain. Even if it does, it would create a court-ordered blocking mechanism for foreign piracy sites. That&#8217;s a different problem than holding ISPs liable for subscriber piracy. It doesn&#8217;t restore the playbook the labels just lost.</p><p>The labels&#8217; off-platform enforcement budget is going to be looking for a new home for the next twelve to eighteen months minimum, regardless of what Congress does.</p><div><hr></div><h3>Where the budget actually goes</h3><p>Litigation budgets don&#8217;t go back to shareholders when the cases get dismissed. They reallocate to whatever vehicles are still producing recoverable revenue.</p><p>The vehicle that has been scaling in parallel for fifteen years is Content ID. YouTube processed 2.2 billion Content ID claims in 2024 alone. The system has paid out $12 billion to rightsholders since launch. It doesn&#8217;t require a verdict, a settlement, or a deposition. A claim placed on a video starts capturing revenue immediately, and the burden of disputing it falls on the creator.</p><p>If you&#8217;re a label rights operations team and the litigation pipeline you&#8217;ve been building toward for a decade just lost its target, the rational move is to expand the mechanism that&#8217;s already working. That means more aggressive reference filing for catalog you weren&#8217;t actively monetizing before. More claim volume against marginal cases that previously weren&#8217;t worth the operational cost. Tighter enforcement of catalog you&#8217;d been deprioritizing for years.</p><p>This won&#8217;t happen with an announcement. There is no press release titled &#8220;Universal Pivots Enforcement Strategy.&#8221; It happens quietly, through procurement. A label rights ops team gets a budget reallocation. They expand their catalog reference work with a third-party service, or use their internal CMS more aggressively. Six months later, claim volume on creator videos has gone up 15-25%, and nobody has connected it to the Cox ruling.</p><p>Roster operators are the ones who&#8217;ll feel that shift first, in claim volume, before anyone connects the dots back to a Supreme Court decision six months prior.</p><div><hr></div><h3>What this looks like at agency scale</h3><p>If you run an agency managing 30 channels averaging three uploads per week, you&#8217;re processing roughly 90 uploads per week. Even at a conservative 10% Content ID match rate, that&#8217;s 9 new claim decisions per week, each running on its own 5-day clock for revenue recovery.</p><p>Now apply a 15-20% increase in claim volume across the back half of 2026. You&#8217;re looking at 11-12 new claim decisions weekly instead of 9. That&#8217;s another two to three claims per week, or roughly 100 to 150 additional claims over a year.</p><p>Most of those will be legitimate. Most won&#8217;t materially threaten your operation. The marginal claims, the ones in the gray zone where the answer requires research, are the ones that consume agency time. Each one demands the same workflow. Look up the claimant. Check the licensing chain. Decide whether to dispute. File before the 5-day window closes. Track the response. Each cycle takes hours of operational time.</p><p>Multiply that by 100-150 incremental cases over a year and you&#8217;re not talking about a copyright problem. You&#8217;re talking about a staffing problem you didn&#8217;t budget for.</p><p>The agencies I talk to are mostly running this manually. Someone on ops handles claims as they come in. There is no internal claimant database. No pattern recognition across the roster. No way to surface that a particular claimant has filed against three other channels in the network and disputes are succeeding 80% of the time.</p><p>That gap has been a problem for a while. The Cox ruling compresses the timeline on when it becomes urgent.</p><div><hr></div><h3>What to do in the next 90 days</h3><p>Pull twelve weeks of historical Content ID claim data across your roster. Track the weekly claim rate, the median time to resolution, and the concentration by claimant. The point is to establish a baseline now, before any shift starts. If claim volume goes up 18% in October, you&#8217;ll only know if you can compare it to April. Without a baseline, that movement is invisible until it&#8217;s already painful.</p><p>Audit your dispute decision workflow before you change it. When a claim lands on a creator&#8217;s video Tuesday at 2pm, who reviews it, who decides whether to dispute, and what&#8217;s the maximum elapsed time before a decision is made? If the honest answer is &#8220;depends who&#8217;s around,&#8221; that&#8217;s a process gap, and it&#8217;ll get expensive when claim volume rises. Document the workflow even if you don&#8217;t redesign it. You can&#8217;t fix what you haven&#8217;t written down.</p><p>Build a claimant reference list. The major labels (UMG, Sony, Warner, BMG, Concord) account for the largest legitimate volume. Below them are the rights management companies (HAAWK/Identifyy, AdRev, Audiam, and others) that handle catalog on behalf of multiple rightsholders. Then there is the long tail of independent claimants. When a claim comes in from a name you don&#8217;t recognize, the first question should be &#8220;have we seen this name before, and how did the disputes resolve.&#8221; Without an internal record, every claim is a cold start.</p><p>None of this is sophisticated. All of it can be done in a spreadsheet by an ops associate over two weeks. The agencies that do it before claim volume rises will be the ones that handle the next twelve months without scrambling.</p><div><hr></div><p>This is the work ClearVerse is built to make easier. Claimant histories instead of cold lookups. Legal precedent on similar disputes instead of guesswork on whether to fight. Portfolio-level visibility for agencies running rosters of 20, 50, 100+ channels.</p><p>YouTube tells you a claim was filed. ClearVerse tells you what to do about it.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.clearverse.ai/book-demo&quot;,&quot;text&quot;:&quot;See how it works!&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.clearverse.ai/book-demo"><span>See how it works!</span></a></p><div><hr></div><p>If you run a roster, what&#8217;s your weekly Content ID claim volume right now? Is it different from where it was 90 days ago? And do you have a way to actually know if it changes, or are you running on feel? Hit reply. I read all of them.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; The Cox ruling closed one front. The follow-on effects haven&#8217;t shown up in your dashboard yet, which is exactly when there&#8217;s still time to prepare for them. Forward this to anyone managing YouTube creators who needs to be paying attention to where this goes next.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Every Copyright Claim Comes With a 5-Day Clock. Most Creators Don't Know It's Running.]]></title><description><![CDATA[Say a video goes up on a Tuesday. The creator gets the notification Wednesday morning: a copyright claim has been placed on the video.]]></description><link>https://insights.clearverse.ai/p/every-copyright-claim-comes-with</link><guid isPermaLink="false">https://insights.clearverse.ai/p/every-copyright-claim-comes-with</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Mon, 20 Apr 2026 02:18:07 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Thirty seconds of background music: a track they licensed, or thought they licensed, or pulled from a platform with a disputed catalog. They open YouTube Studio, look at the claim, and aren&#8217;t immediately sure what to do. They check with their editor. They try to track down the licensing documentation. They Google the claimant&#8217;s name. By Friday, they&#8217;ve decided the claim looks wrong and they want to fight it.</p><p>The 5-day window closed on Sunday. They lost four days of recoverable revenue. Permanently.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This is not fine print. It is a documented mechanic in YouTube&#8217;s Content ID system that most creators and agencies either don&#8217;t know exists or don&#8217;t understand precisely enough to act on in time. And because YouTube videos earn at their highest rate in the first several days after upload, the window always closes at the worst possible moment.</p><div><hr></div><h2>How the mechanic actually works</h2><p>When Content ID places a claim on your video, YouTube begins holding the revenue your video generates. That held revenue does not sit there indefinitely. What happens to it, and whether you can recover any of it, depends entirely on what you do and when you do it.</p><p>YouTube states this plainly in their own Help Center documentation:</p><p>If you dispute a claim within five days of when it was placed, YouTube holds all revenue from Day 1 forward while the dispute is pending. Win the dispute, and you get everything back to the original claim date.</p><p>If you dispute after five days, YouTube only holds revenue going forward from the date you file. Everything your video earned between Day 1 and the day you finally decided to act is gone. The claimant keeps it, regardless of how the dispute ultimately resolves.</p><p>If you do nothing within five days, the held revenue is released directly to the claimant.</p><p>Not still processing. Not waiting for review. Released. To the claimant.</p><p>There is a second window worth understanding too. Once you file a dispute, the claimant has 30 days to respond. They can release the claim, reinstate it, or escalate to a formal copyright removal request. If they reinstate and you want to appeal, that window tightens to 7 days. For videos that are blocked outright, YouTube does allow creators to skip the initial dispute and go straight to appeal, which gets you a response in 7 days instead of 30. But none of those downstream windows matter if the first 5 days have already passed without a decision.</p><div><hr></div><h2>Why this lands when it hurts the most</h2><p>Content ID does not wait for a video to find its audience before scanning it. YouTube processes uploads for copyright matches within minutes of a video going live, often before the first subscriber notification has hit anyone&#8217;s feed. A claim can appear on a new video before it has earned its first dollar.</p><p>For most channels, view velocity is highest in the first 24 to 72 hours after upload. That is when subscriber notifications push content to existing audiences, when the algorithm surfaces it to new viewers, when social sharing builds. After that initial window, views typically plateau unless the video catches a second wave through search or recommendations.</p><p>Which means a copyright claim placed on a new video arrives at precisely the moment the video is making the most money, and the 5-day decision window closes right in the middle of that peak earning period.</p><p>A creator who misses the window by 48 hours is not just losing two days of revenue. Depending on the video, they may be losing a meaningful percentage of everything that video will ever earn.</p><div><hr></div><h2>The numbers that make this a systemic problem</h2><p>YouTube processed 2.2 billion Content ID claims in 2024, a new record. Over 99% were placed automatically, without a human reviewing them before they went out.</p><p>Less than 0.5% of those claims were disputed.</p><p>That number deserves a closer look. It does not mean that 99.5% of claims are valid and creators are correctly accepting them. The evidence points in a different direction. Of the claims that were actually disputed, approximately 60 to 65% resolved in favor of the uploader, according to YouTube&#8217;s own transparency reports. The majority of the time, when a creator fights a claim, they win.</p><p>What that combination tells you is that most creators are not accepting claims because the claims are correct. They are accepting them because they do not know how to dispute effectively, do not know whether the dispute will hold up, or did not act within the window before the decision calculus changed.</p><p>Meanwhile, rightsholders collected on claims that were never challenged. YouTube has paid out $12 billion total to rightsholders through Content ID since the system launched. That $12 billion includes revenue from disputed claims that resolved in the rightsholder&#8217;s favor, but it also includes revenue from claims that were never disputed at all, including claims that would have been released had the creator filed on time.</p><div><hr></div><h2>What this looks like at agency scale</h2><p>For an individual creator, missing the 5-day window on one video is painful but contained. For an agency managing 20 or 30 channels with multiple uploads per week, the math compounds quickly.</p><p>Take an agency running 25 channels averaging two uploads each per week. That is 50 uploads per week. If only 10% of those uploads receive a Content ID claim in the first week (a conservative number for channels that regularly use licensed music), the agency is managing five new claim decisions every week, each with its own 5-day clock, each arriving during or immediately after the video&#8217;s highest-earning window.</p><p>That is not a copyright problem. That is a workflow problem. And most agencies do not have a structured workflow for it. They have someone who handles copyright when it comes up, which means handling it reactively, which means windows sometimes close on weekends, during high-volume upload periods, or simply while everyone is focused on the next piece of content.</p><p>Missing the window on a video with strong early performance can mean losing hundreds or thousands of dollars per video that cannot be recovered regardless of how the dispute eventually resolves. Across a full roster over a year, that is a number worth paying attention to.</p><div><hr></div><h2>What to actually do when a claim lands</h2><p>Treat the claim date as Day 1, not the day you notice it. YouTube timestamps the claim, and that is the clock that matters. Notifications can lag. Go directly to YouTube Studio to check the timestamp rather than relying on email.</p><p>Before doing anything else, look up who filed the claim. YouTube shows you the claimant&#8217;s name in Studio. Some claimants are major labels or publishers with well-documented catalogs. Others are third-party rights management companies whose catalogs include public domain content they have registered with varying degrees of legitimacy. The claimant&#8217;s identity is the first signal about whether a dispute is worth pursuing and how strong your position is.</p><p>Understand the claim type before you act. A monetization claim redirects your revenue while the video stays live. A block claim takes the video down in some or all countries. The dispute paths and the risk profiles are different for each. For block claims, YouTube allows creators to escalate directly to appeal, bypassing the initial 30-day dispute period. That shortens resolution to 7 days. But if the appeal is rejected, the claimant can escalate to a formal copyright removal request, which can result in a copyright strike on your channel. Faster is not always safer.</p><p>Prepare your documentation before you file, not after. License agreements, purchase receipts, timestamps showing when you acquired the audio, confirmation emails from the platform you licensed through. If you licensed a track from a third-party service, that paper trail is the foundation of your dispute. Filing without it often results in reinstatement, which limits your options going forward.</p><p>Understand what fair use actually protects before you invoke it. YouTube cannot evaluate fair use claims; only a court can make that determination. Disputing on fair use grounds when the case is weak can result in reinstatement and leave you with fewer options than if you had approached it differently from the start. Fair use is a real defense, but it requires a real argument.</p><div><hr></div><p>The pattern I hear consistently from agencies and creators who have dealt with this is the same. A claim comes in. The decision of what to do feels uncertain. Someone puts it on the list to handle. Two days pass. Three days. By the time there is clarity on whether the claim is legitimate and what the right move is, the window has narrowed or closed.</p><p>YouTube flags the claim. The 5-day clock starts immediately. Whether you recover the revenue from those first critical days depends entirely on a decision that has to be made before most people even fully understand the situation.</p><p>That is the gap. Not the dispute process itself, which is navigable once you know it. The gap is the time between &#8220;a claim just appeared on my video&#8221; and &#8220;I know what to do about it and I am doing it.&#8221;</p><p>If you are managing a creator roster, I would like to know how you handle this right now. When a claim lands, is there a process in place, or does it get handled case by case? And how often does a claim arrive in the first 48 hours after a video goes live?</p><p>Hit reply. I read all of them.</p><p>&#8212; Christian</p><p><em>P.S. ClearVerse is building the decision layer for exactly this moment, helping agencies understand which claims to fight, which to fix, and what the legal precedent looks like before the window closes. If you are managing a roster and want to see what that looks like, sign up for early access at clearverse.ai. If this is useful to someone running a creator agency or a monetized channel, pass it along.</em></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.clearverse.ai/book-demo&quot;,&quot;text&quot;:&quot;See how ClearVerse works!&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.clearverse.ai/book-demo"><span>See how ClearVerse works!</span></a></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Copyright Ambulance Chasers Are Coming for Your Revenue]]></title><description><![CDATA[YouTube processes 6 million copyright claims every day.]]></description><link>https://insights.clearverse.ai/p/the-copyright-ambulance-chasers-are</link><guid isPermaLink="false">https://insights.clearverse.ai/p/the-copyright-ambulance-chasers-are</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 12 Apr 2026 21:26:18 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!mTAv!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!mTAv!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!mTAv!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!mTAv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png" width="1456" height="971" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:971,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2313017,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.clearverse.ai/i/194005211?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!mTAv!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 424w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 848w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 1272w, https://substackcdn.com/image/fetch/$s_!mTAv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb6667e6c-c2b4-4488-a1b9-d681419fd27d_1536x1024.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Most of them are legitimate. A creator uses a song without a license, Content ID matches it, the rightsholder monetizes the video. That&#8217;s the system working as intended.</p><p>But a growing percentage of those claims are not legitimate. They&#8217;re filed by companies and individuals who don&#8217;t own the content they&#8217;re claiming. They file anyway because the economics work in their favor: if nobody disputes, they get paid. If someone does dispute, they lose nothing.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>WatchMojo, one of the largest YouTube channels with over 20 million subscribers, spent a decade tracking this problem. Their estimate: rightsholders unlawfully claimed over $2 billion between 2014 and 2019.</p><p>And that was before Content ID volume exploded. YouTube processed 2.2 billion claims in 2024 alone. Even if only a fraction of a percent are fraudulent, that&#8217;s millions of claims siphoning revenue from creators who did nothing wrong.</p><div><hr></div><h2>How Fraudulent Claims Work</h2><p>Content ID is an automated system. YouTube scans uploaded videos against a database of reference files provided by verified rightsholders. If the system detects a match, it files a claim automatically. No human reviews it before the claim goes live.</p><p>The rightsholder then has options: block the video, track viewership, or monetize it. Over 90% choose to monetize. The video stays up. Ads run. Revenue flows to whoever filed the claim.</p><p>Creators can dispute. But most don&#8217;t. According to YouTube&#8217;s own transparency data, 99.5% of Content ID claims go undisputed. That&#8217;s partly because creators assume the claim must be valid. It&#8217;s also because disputing takes time, requires understanding the process, and carries risk if you&#8217;re wrong.</p><p>For anyone willing to file bad-faith claims, this creates an asymmetric opportunity. File thousands of claims. Most go undisputed. The ones that do get disputed, you release without consequence. Meanwhile, revenue accumulates from every undisputed claim.</p><p>The claimant gets 30 days to respond to a dispute. If they do nothing, the claim eventually expires. If the creator doesn&#8217;t dispute within 5 days of the claim landing, any revenue generated before the dispute is filed goes to the claimant permanently. That first week of monetization? Gone.</p><p>And here&#8217;s what makes it worse: 65% of disputed claims resolve in the creator&#8217;s favor. That means the majority of creators who fight back were right all along. But by the time they win, the video&#8217;s peak earning window has passed.</p><div><hr></div><h2>The MediaMuv Case</h2><p>This isn&#8217;t theoretical. The largest documented Content ID fraud resulted in federal prison sentences.</p><p>Between 2017 and 2021, two men ran a company called MediaMuv. They convinced a YouTube partner that they owned the rights to over 50,000 songs. They didn&#8217;t own any of them. The songs were primarily Latin American music that hadn&#8217;t yet been monetized on YouTube. MediaMuv uploaded reference files, claimed the content, and collected the royalties.</p><p>For four years, the scheme generated over $23 million. The artists who actually created the music received nothing.</p><p>By 2019, MediaMuv was branching out. They started claiming soundtracks from video games, including music from Doki Doki Literature Club. YouTubers who made gameplay videos or used the game&#8217;s music in their content suddenly found their videos claimed by a company they&#8217;d never heard of.</p><p>A Twitter account called @fuckmediamuv started tracking the scheme in 2018, warning other creators. The account posted photos of the defendants with graphics of cartoon burglars, calling them &#8220;ladrones de contenido en YouTube.&#8221; YouTube content thieves.</p><p>It took until November 2021 for federal authorities to arrest them. A grand jury indicted both men on 30 felony counts including wire fraud, money laundering, and aggravated identity theft. In 2023, Jose Teran was sentenced to 70 months in prison. Webster Batista Fernandez received 46 months. Teran forfeited a house in Phoenix, a Tesla, a BMW i8, and bank accounts containing over a million dollars.</p><p>The Department of Justice called it &#8220;one of the largest music-royalty frauds ever perpetrated.&#8221;</p><p>But here&#8217;s the part that should concern every creator and agency: MediaMuv operated for four years before anyone stopped them. Four years of claims. Four years of revenue flowing to the wrong people. And that was just one operation that got caught.</p><div><hr></div><h2>Why Agencies Are Exposed</h2><p>If you&#8217;re managing YouTube creators, this is your problem at two points in the workflow.</p><p><strong>During post-production:</strong> The editor finishes a cut. Before export, you have no system to analyze the audio and flag potential issues. YouTube will scan it after upload, but by then the video is supposed to go live. If it gets flagged, someone has to go back to the editor (often in a different time zone), re-edit, re-export, re-upload to Google Drive, re-download, re-upload to YouTube, re-add thumbnails and titles. That loop burns hours and delays launch.</p><p><strong>After a claim lands:</strong> A creator gets hit with a claim from a company you&#8217;ve never heard of. They come to you asking what happened. Is it real? Should they dispute? What&#8217;s the process? What happens if they&#8217;re wrong?</p><p>Most of the time, you don&#8217;t have good answers.</p><p>You can look up the claimant, but that doesn&#8217;t tell you whether they actually own the content. You can tell the creator to dispute, but neither of you knows whether the claim will hold up. You can wait 30 days to see if the claimant releases, but by then the video&#8217;s first week of revenue is already gone.</p><p>And if you&#8217;re managing 30 or 50 creators, this happens more than once. A claim lands on Monday. Another on Thursday. A third the following week. Each one triggers the same workflow: figure out if it&#8217;s real, decide whether to fight, file the dispute, wait, follow up.</p><p>That&#8217;s time your ops team spends playing defense instead of driving growth.</p><p>The larger issue is that you have no system for knowing which claims are worth fighting. Content ID tells you a claim was filed. It tells you who filed it. It doesn&#8217;t tell you whether that company has a history of bad-faith claims. It doesn&#8217;t tell you whether other creators have successfully disputed similar claims. It doesn&#8217;t give you any legal context for whether the claim is likely to hold up.</p><div><hr></div><h2>The Real Issue</h2><p>YouTube tells you a match exists. It doesn&#8217;t tell you what it means.</p><p>When a claim lands, YouTube&#8217;s interface shows you the claimant, the content matched, and the timestamp. It gives you four options: do nothing, erase the audio, replace it with YouTube&#8217;s library, or dispute.</p><p>What it doesn&#8217;t give you: any intelligence about whether this claim is legitimate. Any history of this claimant&#8217;s dispute rate. Any legal precedent suggesting whether the claimed content is actually protected or whether you have a fair use defense. Any data point that would help you make an informed decision.</p><p>The same gap exists during editing. YouTube will scan your video after you upload it. But what if you could scan it during post-production, before the file ever touches YouTube, and get deeper analysis than YouTube provides? Not just &#8220;this matches Track X&#8221; but &#8220;this segment has high similarity to a track with an aggressive claimant history, courts have ruled against similar usage in 3 out of 4 comparable cases, here&#8217;s your risk level and here&#8217;s the recommended action.&#8221; Your editor could fix it in the timeline before export, not after upload.</p><p>Creators are expected to navigate this alone. Agencies are expected to figure it out across dozens of channels with no tools designed for the job.</p><p>This is why fraudulent claimants get away with it. The system assumes every claim is valid until proven otherwise. The burden of proof falls on the creator. And most creators don&#8217;t have the time, knowledge, or resources to fight back.</p><p>The 65% win rate on disputes tells you something important: the majority of creators who fight are right. But the 99.5% of claims that go undisputed tells you something else: most creators never try.</p><p>That gap is where money disappears.</p><div><hr></div><h2>What We&#8217;re Building</h2><p>This is why ClearVerse exists.</p><p>We&#8217;re building copyright intelligence that YouTube doesn&#8217;t provide, whether your team catches an issue during editing or after upload.</p><p>During post-production: Analyze content before it&#8217;s exported and uploaded. Give editors and content teams deeper analysis than YouTube will ever provide. Not just &#8220;this matches Track X&#8221; but defensibility assessment, claimant reputation, and recommended action. Fix it in the timeline, not after the video was supposed to go live.</p><p>After a claim lands: Decision intelligence. Should you fight or fix? What does this claimant&#8217;s history look like? What have courts ruled in similar cases? AI-generated dispute responses backed by legal precedent.</p><p>For agencies managing creator rosters: Portfolio-level visibility into claims across your entire operation. Identify which claimants file bad-faith claims so you can respond with evidence, not hope. Standardized workflows so your ops team isn&#8217;t reinventing the process every time a claim lands.</p><p>YouTube detects matches. ClearVerse analyzes risk. There&#8217;s a difference.</p><div><hr></div><p><strong>Managing YouTube creators and seeing claims you don&#8217;t know how to evaluate? I&#8217;d like to show you what copyright intelligence looks like, before and after upload.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.clearverse.ai/book-demo&quot;,&quot;text&quot;:&quot;See how ClearVerse works!&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.clearverse.ai/book-demo"><span>See how ClearVerse works!</span></a></p><div><hr></div><p><em>Have you dealt with a claim that felt fraudulent? How did you handle it? I&#8217;m curious what&#8217;s working and where you&#8217;re seeing gaps.</em></p><p>&#8212; Christian</p><p>P.S. The MediaMuv defendants are in prison, but the incentive structure that made their scheme possible hasn&#8217;t changed. As long as undisputed claims pay out and bad-faith claimants face no consequences until someone sues, this problem will keep growing. Forward this to anyone managing creator portfolios who should be paying attention.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Suno's Copyright Filters Just Got Exposed. If Your Creators Use AI Music, This Is Your Problem.]]></title><description><![CDATA[Suno tells users its filters prevent copyright infringement.]]></description><link>https://insights.clearverse.ai/p/sunos-copyright-filters-just-got</link><guid isPermaLink="false">https://insights.clearverse.ai/p/sunos-copyright-filters-just-got</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 05 Apr 2026 21:56:31 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!6Rxl!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!6Rxl!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!6Rxl!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 424w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 848w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 1272w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!6Rxl!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png" width="1456" height="702" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/d30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:702,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:3219834,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.clearverse.ai/i/193291055?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!6Rxl!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 424w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 848w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 1272w, https://substackcdn.com/image/fetch/$s_!6Rxl!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd30cc1fd-0fc8-459e-8847-991b457e3d97_2152x1038.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>This week, users demonstrated how easy those filters are to bypass. Upload a YouTube cover version of a copyrighted song instead of the original recording and Suno&#8217;s detection doesn&#8217;t flag it. Change a few words to homophones and the lyric filter lets it through. One tester bypassed the system on Beyonc&#233;&#8217;s &#8220;Freedom&#8221; by changing &#8220;rain on this bitter love&#8221; to &#8220;reign on.&#8221; Beyond the first verse and chorus, they didn&#8217;t need to make any changes at all.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>For a company facing up to $150,000 in statutory damages per infringed work in federal court, that&#8217;s a problem.</p><p>But here&#8217;s what caught my attention: when those filters fail, Suno faces a lawsuit. Your creator faces a Content ID claim. And you face the lost revenue, the ops headache, and the conversation about why you didn&#8217;t catch it before upload.</p><p>The filters protect Suno. They don&#8217;t protect your creators.</p><div><hr></div><h2>What&#8217;s Actually Happening</h2><p>The bypass methods aren&#8217;t sophisticated. They&#8217;re embarrassingly simple.</p><p>Suno scans for copyrighted material in two places: uploaded audio and typed lyrics. The audio filter checks uploads against known recordings. The lyric filter matches text against protected song words.</p><p>Both have gaps.</p><p>The audio filter only recognizes original recordings. A YouTube cover of a song doesn&#8217;t trigger it. The AI then uses that cover as a style reference and produces output that sounds like the copyrighted original without technically matching it. Users have been sharing this workaround openly. Upload a cover, get the vibe, bypass the filter.</p><p>The lyric filter relies on exact text matching. Homophones work. Phonetic spelling works. Small changes defeat it. Swap &#8220;sweet&#8221; for &#8220;suite&#8221; and you&#8217;re through. The filter scans for the copyrighted text string; if it doesn&#8217;t match exactly, it passes.</p><p>Independent artists testing Suno&#8217;s v5 model found their own songs cleared the copyright filter with zero modifications. Tracks by smaller artists, self-distributed through Bandcamp or DistroKid, slipped through without any changes at all. The protection appears strongest for major-label catalogs and weakest for everyone else.</p><p>That asymmetry matters. If you&#8217;re managing creators who use AI music, the tracks most likely to trigger Content ID claims might be the ones Suno&#8217;s filters are least likely to catch.</p><div><hr></div><h2>The Legal Context</h2><p>Suno isn&#8217;t operating in a vacuum. It&#8217;s in the middle of active litigation.</p><p>The RIAA filed suit on June 24, 2024, in the US District Court for the District of Massachusetts on behalf of Universal, Sony, and Warner. The complaint alleges mass infringement, accusing Suno of training its AI on copyrighted recordings without permission. It seeks up to $150,000 per infringed work, plus $2,500 for each act of circumventing encryption protections.</p><p>In its August 2024 answer, Suno argued fair use. In the same filing, Suno acknowledged that its training data &#8220;presumably included recordings whose rights are owned by the Plaintiffs.&#8221; The company declined to disclose what was actually in that data, calling it &#8220;confidential business information.&#8221;</p><p>That fair use argument took a hit in May 2025. The US Copyright Office released its Part 3 report on generative AI training and concluded that using copyrighted expressive works to generate competing content goes &#8220;beyond established fair use boundaries.&#8221; The report emphasized this is especially true when the AI produces outputs that substitute for the originals in the market.</p><p>Warner Music Group subsequently settled and formed a licensing partnership with Suno. The deal announced in November 2025 includes new &#8220;licensed models&#8221; rolling out in 2026, download restrictions for free users, and monthly download caps for paid subscribers. Financial terms weren&#8217;t disclosed.</p><p>But Universal and Sony remain in active litigation. And a separate class action by independent artists is also pending in the same Massachusetts court, with an amended complaint filed September 22, 2025. That filing tripled the original complaint&#8217;s length and added stream-ripping allegations, claiming Suno bypassed YouTube&#8217;s encryption to harvest training data.</p><p>Internationally, GEMA &#8212; Germany&#8217;s version of ASCAP or BMI, representing over 95,000 composers and songwriters &#8212; became the first music rights organization worldwide to sue an AI music generator when it filed against Suno in January 2025. Their tests allegedly produced AI outputs for songs including &#8220;Daddy Cool,&#8221; &#8220;Mambo No. 5,&#8221; &#8220;Forever Young,&#8221; and &#8220;Atemlos&#8221; that matched the originals in melody, harmony, and rhythm without specifying those elements in the prompt. A ruling is scheduled for June 12, 2026.</p><p>The legal landscape is moving. But none of that helps your creator when a claim lands tomorrow.</p><div><hr></div><h2>Why This Is an Agency Problem</h2><p>Suno&#8217;s legal exposure is Suno&#8217;s problem. Your operational exposure is yours.</p><p>When a creator uses AI-generated music in a YouTube video and that music triggers a Content ID match, YouTube doesn&#8217;t care whether Suno&#8217;s filters should have caught it. Content ID scans the final audio. If it matches a reference file in YouTube&#8217;s database, a claim gets filed. Revenue redirects to the claimant. The yellow icon appears. And your creator wants to know what happened.</p><p>You can&#8217;t see it coming. AI music platforms don&#8217;t tell creators &#8220;this track might trigger a claim.&#8221; They tell creators the filters are working. Your ops team has no visibility into whether a creator&#8217;s AI-generated track shares enough characteristics with protected content to trigger a match.</p><p>Content ID doesn&#8217;t care about source. It uses acoustic fingerprinting. It doesn&#8217;t distinguish between music created in a DAW, pulled from a library, or generated by an AI that trained on copyrighted material. If the output sounds similar enough to a reference file, you get a claim. The fact that Suno said it was safe doesn&#8217;t matter.</p><p>And if you&#8217;re managing 30 creators across your roster who are using various AI tools with varying filter quality, that&#8217;s cumulative risk you can&#8217;t currently track. One creator experimenting with Suno is a curiosity. A dozen creators generating tracks with tools whose filters have documented gaps is a portfolio-level exposure you have no system to manage.</p><p>There&#8217;s also the ownership question, which most agencies aren&#8217;t thinking about yet. Under current Copyright Office guidance, music generated entirely by AI without meaningful human authorship may not be copyrightable. That means creators using raw AI output might not even own what they&#8217;re uploading. If a dispute arises over rights to the track, the answer might be: nobody owns it.</p><p>The time cost adds up too. Every claim triggers a workflow. Someone on your team notices the claim, assesses whether it&#8217;s legitimate, decides whether to dispute, files the dispute, monitors it for 30 days, follows up if it gets rejected. Multiply that by six or eight claims per month across your roster and you&#8217;ve burned hours your ops team could have spent on growth, creator support, or closing brand deals.</p><p>And every claim erodes trust. Creators see the yellow icon. They watch their AdSense estimate drop. They ask what happened, why you didn&#8217;t catch it, what you&#8217;re doing to prevent it next time. You don&#8217;t have a good answer because there&#8217;s no tool that catches it before upload. The agencies that retain their best talent will be the ones who can say: &#8220;We checked it before you uploaded. It&#8217;s clean.&#8221;</p><div><hr></div><h2>The Real Issue</h2><p>The filter bypass story exposes something that was already true.</p><p>AI music platforms position their filters as protection for creators. That&#8217;s not quite right. The filters protect the platform from the most obvious liability. They reduce the chance that Suno generates something that sounds exactly like &#8220;Bohemian Rhapsody&#8221; and triggers immediate legal action. They don&#8217;t protect creators from Content ID claims. They don&#8217;t guarantee the output is safe to monetize. They don&#8217;t mean you won&#8217;t get a claim.</p><p>Suno&#8217;s Terms of Service make this explicit if you read them. The platform grants users certain rights but disclaims any guarantee that content is free of third-party claims. The legal risk of using the output sits with the user, not the platform.</p><p>For agencies, relying on platform filters isn&#8217;t a risk management strategy. It&#8217;s hope dressed up as process.</p><div><hr></div><h2>What We&#8217;re Building</h2><p>This is why ClearVerse exists.</p><p>We analyze audio before it goes live. Not after a claim lands. Before your creator hits publish. Our system scans against known Content ID reference patterns and scores risk based on legal precedent, not just acoustic similarity. If a track is likely to trigger a claim, you know before you lose the first 48 hours of revenue.</p><p>The platforms protect themselves. We help you protect your creators.</p><div><hr></div><p><strong>Managing YouTube creators who use AI-generated music? I&#8217;d like to show you what pre-publish protection looks like.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.clearverse.ai/book-demo&quot;,&quot;text&quot;:&quot;See how ClearVerse works!&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.clearverse.ai/book-demo"><span>See how ClearVerse works!</span></a></p><div><hr></div><p><em>Are your creators using AI music tools? What&#8217;s your current process for checking whether those tracks are safe? I&#8217;m curious what&#8217;s working and what gaps you&#8217;re seeing.</em></p><p>&#8212; Christian</p><p>P.S. Suno&#8217;s filters might improve. The lawsuits will eventually resolve. But the fundamental problem remains: platform filters protect platforms, not creators. Forward this to anyone managing creator portfolios who should be thinking about this.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Hidden Cost of One Copyright Claim: What Creator Agencies Are Actually Losing ]]></title><description><![CDATA[If you're running a creator agency, you already know the feeling.]]></description><link>https://insights.clearverse.ai/p/the-hidden-cost-of-one-copyright</link><guid isPermaLink="false">https://insights.clearverse.ai/p/the-hidden-cost-of-one-copyright</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 22 Mar 2026 15:24:14 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!wgc1!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!wgc1!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!wgc1!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 424w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 848w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 1272w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!wgc1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png" width="1456" height="702" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:702,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:3668259,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.clearverse.ai/i/191771227?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!wgc1!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 424w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 848w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 1272w, https://substackcdn.com/image/fetch/$s_!wgc1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd0615c1-961b-4edb-a17b-252598fa48ec_3194x1540.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>You check your dashboard. One of your creators published yesterday. The video is performing. Views are climbing. And then you see it: a copyright claim landed six hours after upload. The monetization icon is yellow. The revenue from the video&#8217;s best 48 hours is already redirected to whoever filed the claim.</p><p>You didn&#8217;t see it coming. Neither did your creator. And now you&#8217;re in reactive mode.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This is happening across the industry at massive scale. YouTube processed 2.2 billion Content ID claims in 2024. That&#8217;s 6 million claims per day, over 4,000 per minute. In more than 90% of cases, rightsholders chose to monetize the claimed content rather than block it.</p><p>The videos stay up. The views keep coming. The ads run. But the revenue flows to the claimant, not to your creator, and not to you.</p><div><hr></div><h2>Why the First 48 Hours Matter to Your Business</h2><p>YouTube&#8217;s algorithm tests new content aggressively in the first 24 to 48 hours. Strong early performance triggers broader distribution. This is also when ad revenue concentrates. A video that reaches 100,000 views in its first week will often generate the majority of those views in the first two days.</p><p>For agencies, this creates a timing problem. A claim that lands on day one captures the revenue from the video&#8217;s highest-earning window. Even if the claim is eventually released or disputed successfully, that window is already closed.</p><p>YouTube gives claimants 30 days to respond to disputes. If your team doesn&#8217;t file within 5 days of the claim, any revenue generated before the dispute is filed goes to the claimant permanently. By the time any dispute resolves, the algorithm has already moved on.</p><p>Here&#8217;s the part that should concern you: over 65% of disputed claims eventually resolve in the uploader&#8217;s favor. The claimant either releases the claim or doesn&#8217;t respond. That means the majority of disputes involve claims that shouldn&#8217;t have stuck, but the revenue from the video&#8217;s peak performance window is still gone.</p><div><hr></div><h2>The Real Cost to Your Agency</h2><p>The direct revenue hit is straightforward to calculate. Take a creator on your roster in a finance or tech vertical. One video hits 100,000 views in its first week. At a $10 CPM, that&#8217;s $1,000 gross. YouTube takes 45%, leaving $550 for the creator. Your 20% management fee on that is $110. A single claim wipes out both numbers.</p><p>Multiply that across your roster. If you&#8217;re managing 30 creators publishing weekly, that&#8217;s 120+ uploads per month flowing through your portfolio. Even a small claim rate means thousands in lost revenue per month, revenue your creators expected and revenue your agency counted on.</p><p>But the revenue loss is only the most visible cost.</p><p><strong>Ops burden.</strong> Every claim triggers work for your team. Someone has to monitor for claims across your roster, assess each one, decide whether to dispute, file the dispute, track it for 30 days, and follow up if it&#8217;s rejected. At scale, this becomes a significant time sink. Hours your team spends on claim management are hours they&#8217;re not spending on growth, brand partnerships, or creator support.</p><p><strong>Creator trust.</strong> When a creator sees their AdSense estimate drop to zero, they notice immediately. The next message you get is some version of: &#8220;What happened? Why didn&#8217;t you catch this? What are you doing to prevent it next time?&#8221; Every claim is a conversation that erodes confidence. Creators with options will eventually move to agencies that can protect their revenue.</p><p><strong>Portfolio drag.</strong> Creators who get burned by claims often become conservative. They avoid music that would make their content more engaging. They stop experimenting with formats that might trigger claims. Over time, this shows up as slower growth across your roster, less competitive content, and creators who underperform their potential.</p><div><hr></div><h2>The Visibility Gap</h2><p>The core problem isn&#8217;t that claims happen. It&#8217;s that you have no way to see them coming and no system to manage the risk across your portfolio.</p><p>Content ID is reactive. It scans content after upload. By the time a claim appears in YouTube Studio, the video is already live, the algorithm is already testing it, and the first 48 hours have already started.</p><p>There&#8217;s no portfolio-level view of copyright risk before content goes out. No system that flags which uploads are likely to trigger claims. No way to know whether the background track a creator is using will be safe or not.</p><p>Most agencies handle this in one of two ways. Some mandate royalty-free music libraries and build that into creator contracts. That solves the claim problem but limits what your creators can produce. Others take a reactive approach: deal with claims when they happen, dispute when possible, and accept the losses.</p><p>Neither scales well. The first constrains your creators. The second burns money and ops time you never recover.</p><p>The agencies that retain top talent and protect their margins will be the ones that can tell creators, before they hit publish: &#8220;We checked it. It&#8217;s clean.&#8221;</p><div><hr></div><h2>What Leading Agencies Are Building</h2><p>The agencies getting ahead of this are building process, but most of what they&#8217;re doing is manual.</p><p>Some require creators to submit audio for review before upload. That works when you&#8217;re managing 10 creators. It breaks at 50+. The review backlog becomes its own bottleneck.</p><p>Others build internal documentation: wikis of &#8220;safe&#8221; tracks, lists of music to avoid, playbooks for handling claims. This works until the person who built it leaves. Then the institutional knowledge walks out the door.</p><p>The most sophisticated agencies layer licensed music platforms, internal training, and dedicated ops capacity for claim management. But even this is patchwork. None of it gives you real-time, portfolio-wide visibility into risk before content goes live.</p><p>That&#8217;s the gap ClearVerse is built to fill.</p><div><hr></div><h2>What Portfolio-Level Copyright Protection Looks Like</h2><p>ClearVerse gives your agency a single dashboard for copyright risk across your entire roster.</p><p>Before content goes live, your team can scan audio against known Content ID reference patterns. We score risk based on legal precedent, not just acoustic similarity. You see which uploads are likely to trigger claims before they publish.</p><p>When something flags, you have options. Swap the track. Clear the license. Or make an informed decision that the risk is acceptable. Either way, you&#8217;re not finding out after the damage is done.</p><p>For your ops team, this means fewer surprise claims, fewer disputes to manage, and fewer difficult conversations with creators. For your business, it means protecting the revenue your roster generates and the margin your agency depends on.</p><div><hr></div><p><strong>If you&#8217;re running a creator agency and want to see what portfolio-level copyright protection looks like, I&#8217;d like to show you.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.clearverse.ai/book-demo&quot;,&quot;text&quot;:&quot;See how ClearVerse works!&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.clearverse.ai/book-demo"><span>See how ClearVerse works!</span></a></p><div><hr></div><p><em>How does your agency handle copyright risk across your roster today? I&#8217;m curious what&#8217;s working, what&#8217;s not, and what you wish you had. Reply or drop a comment below.</em></p><p>&#8212; Christian</p><p>P.S. If this was useful, forward it to another agency founder or ops lead. The more agency operators understand what reactive claim management actually costs, the faster this space moves toward something better.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Google Just Got Sued for AI Music. This One's Different.]]></title><description><![CDATA[On March 6, a group of indie artists sued Google over Lyria 3, its new AI music generator.]]></description><link>https://insights.clearverse.ai/p/google-just-got-sued-for-ai-music</link><guid isPermaLink="false">https://insights.clearverse.ai/p/google-just-got-sued-for-ai-music</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 15 Mar 2026 20:15:49 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!9fVY!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!9fVY!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!9fVY!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 424w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 848w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!9fVY!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg" width="612" height="408" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:408,&quot;width&quot;:612,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:64603,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://insights.clearverse.ai/i/191059278?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!9fVY!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 424w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 848w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!9fVY!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d2e7354-752f-47dc-8b6f-60ac34447db2_612x408.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>If you&#8217;ve been following the AI music space, another lawsuit might not feel like news. Suno and Udio have been fighting the major labels for over a year. The same indie artists suing Google already have pending cases against both platforms.</p><p>But this case is structurally different. The legal claims are similar: copyright infringement, unlicensed training data, the usual. What&#8217;s different is who Google is and what Google controls.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The plaintiffs&#8217; core argument, laid out in the opening pages of their 118-page complaint:</p><blockquote><p>&#8220;Google owns the platform where independent musicians distribute their music. Google runs the system that identifies who owns it. And then Google used both to train a product that competes with the very artists who trusted it with their work.&#8221;</p></blockquote><p>That&#8217;s not a startup scraping the web. According to the lawsuit, it&#8217;s the owner of YouTube using the same infrastructure artists depend on to build something that competes with them.</p><p>Whether that argument holds up legally is an open question. But it&#8217;s worth understanding what&#8217;s being alleged and why it matters for creators.</p><div><hr></div><h2>What Happened</h2><p>Google launched Lyria 3 on February 18 through its Gemini app. The tool generates 30-second tracks with vocals and lyrics from text prompts or images. It&#8217;s now available to more than 750 million monthly active Gemini users worldwide.</p><p>In its launch announcement, Google said it developed the technology &#8220;responsibly in collaboration with the music community&#8221; and has &#8220;been very mindful of copyright and partner agreements.&#8221;</p><p>The plaintiffs dispute that framing.</p><p>Their complaint points to Google&#8217;s own published research, specifically peer-reviewed papers authored by Google researchers, that describe the training data in detail.</p><p>A 2022 paper describes collecting approximately 50 million internet music videos, extracting 30-second clips from each, and retaining roughly 44 million clips totaling nearly 370,000 hours of recorded music.</p><p>A 2023 paper describes training on 5 million clips totaling 280,000 hours of audio.</p><p>According to the lawsuit: &#8220;Both papers were published in peer-reviewed venues under the names of Google researchers. Neither mentions a license. Neither discusses a consent mechanism. Neither identifies a single rights holder whose permission was sought.&#8221;</p><p>The plaintiffs argue Google &#8220;has not named any agreement. It has not specified a single license covering training data.&#8221;</p><p>Google hasn&#8217;t publicly responded to the lawsuit yet.</p><div><hr></div><h2>Why the Plaintiffs Say This Case Is Different</h2><p>When Suno and Udio got sued, the lawsuits targeted startups that allegedly scraped music from the internet. Both companies have argued fair use. The labels argued mass infringement. Courts are still deciding.</p><p>The plaintiffs argue Google&#8217;s situation is different because of what Google already controls.</p><p>Google owns YouTube, one of the largest repositories of recorded music in the world. Artists upload their work to YouTube for distribution, discovery, and monetization.</p><p>Google also runs Content ID, the automated rights management system that scans uploads and matches them against reference files. The system reportedly contains more than 50 million reference files submitted by rights holders.</p><p>The lawsuit argues this gave Google unique access. It didn&#8217;t need to scrape the web because it already had the music. It didn&#8217;t need to guess who owned what because Content ID already tracked ownership.</p><p>As the complaint puts it, Google had &#8220;every opportunity to develop this product legally. It has the technical infrastructure, financial resources, and industry connections to clear rights before training.&#8221;</p><p>The plaintiffs allege Google &#8220;chose not to do so, not because licensing was impossible, but because copying was faster and cheaper.&#8221;</p><p>That&#8217;s their argument. Whether courts agree is a different question.</p><div><hr></div><h2>The DeepMind Connection</h2><p>One detail worth noting: Udio, the AI music platform that settled with Universal and Warner last year, was founded by former Google DeepMind researchers.</p><p>The four co-founders who built Udio&#8217;s core technology previously worked on generative music at Google. According to the lawsuit, &#8220;Within months, all four left Google DeepMind, formed a new company, and publicly launched Udio, another AI music-generation service trained on copyrighted recordings without authorization.&#8221;</p><p>Google launched Lyria 3 after Udio&#8217;s settlements were announced.</p><p>Days after that launch, Google acquired ProducerAI, the AI music platform formerly known as Riffusion, bringing the team into Google Labs.</p><p>The plaintiffs see a pattern. Whether it&#8217;s legally relevant is something courts will determine.</p><div><hr></div><h2>What the Lawsuit Alleges</h2><p>The complaint lists 16 alleged violations under federal and state law:</p><p><strong>Copyright infringement</strong> on both sound recordings and musical compositions. This is the core claim: that Google copied millions of works without permission.</p><p><strong>Removal of copyright management information.</strong> The lawsuit alleges Google stripped identifying metadata during the training process.</p><p><strong>False endorsement under the Lanham Act.</strong> When users create with Lyria 3, Google identifies them as the &#8220;creator.&#8221; The plaintiffs argue this generates false attribution for works allegedly derived from unlicensed material.</p><p><strong>Illinois BIPA violations.</strong> Google&#8217;s privacy notice for ProducerAI mentions that it &#8220;may involve the extraction of a biometric voiceprint.&#8221; The plaintiffs argue this could violate Illinois biometric privacy law if done without consent.</p><p>The case is structured as a proposed class action. The named plaintiffs, indie artists from New York, Los Angeles, Atlanta, and Chicago, are seeking to represent all independent artists whose work may have been used.</p><div><hr></div><h2>What Google Has Said</h2><p>Google hasn&#8217;t formally responded to the lawsuit.</p><p>At the Lyria 3 launch, the company said it trains on music it has &#8220;a right to use under our terms of service, partner agreements, and applicable law.&#8221;</p><p>The plaintiffs argue that language is vague. Being &#8220;mindful&#8221; of copyright isn&#8217;t the same as having licenses. &#8220;Partner agreements&#8221; could mean formal licensing deals or standard terms-of-service language.</p><p>If Google has specific licensing agreements covering the training data, it hasn&#8217;t publicly disclosed them.</p><div><hr></div><h2>What This Means for Creators</h2><p>If you&#8217;re using AI music tools or releasing music on streaming platforms, a few things are worth noting:</p><p><strong>The scale is significant.</strong> Gemini has 750 million monthly active users. Compare that to Suno&#8217;s roughly 100 million total users or Udio&#8217;s smaller base. If Lyria 3 becomes a go-to tool for casual music creation, the volume of AI-generated content entering the ecosystem will grow substantially.</p><p><strong>The platform relationship question is sharpening.</strong> This lawsuit forces a question that&#8217;s been in the background: what do platforms owe the creators who use them? Artists upload to YouTube expecting distribution, not training data extraction. Whether that expectation is legally enforceable is what courts will decide.</p><p><strong>Legal uncertainty remains.</strong> Google is being sued under similar theories to the Suno and Udio cases. But those cases haven&#8217;t been decided on fair use. The Copyright Office is still developing guidance. If you&#8217;re releasing AI-assisted music, the rules aren&#8217;t fully clear yet.</p><div><hr></div><h2>What to Watch</h2><p><strong>Whether Google settles or fights.</strong> The major labels have been settling with AI platforms rather than going to trial. Google has far more resources than any AI music startup. It could fight through trial and potentially establish precedent, or it could settle quietly.</p><p><strong>Class certification.</strong> This is a proposed class action. If the class gets certified, the potential damages grow significantly. If it doesn&#8217;t, this remains a smaller case.</p><p><strong>Whether the major labels file their own suit.</strong> Right now, this is an indie artist lawsuit. The RIAA hasn&#8217;t filed against Google. If they do, the dynamics change; Google has existing relationships with all three majors through YouTube licensing and Content ID.</p><div><hr></div><h2>The Larger Question</h2><p>This lawsuit sits at an interesting intersection.</p><p>YouTube has been controversial in the music industry for years. Artists have debated the royalty rates, the value gap, and platform power. But YouTube remained essential for reach and discovery.</p><p>This case asks whether the calculation changes when the platform you depend on is also training AI that could compete with you.</p><p>That&#8217;s not a legal question with a clear answer. It&#8217;s a relationship question that creators and platforms will navigate over the coming years, regardless of how this lawsuit resolves.</p><div><hr></div><h2>What We&#8217;re Building</h2><p>At ClearVerse, we&#8217;re building tools to help creators understand copyright exposure before release, not after a claim arrives.</p><p>Cases like this add complexity to an already complicated landscape. Understanding where your music goes, who might be using it, and what rights you actually have is becoming more important, not less.</p><p>If that resonates, you can sign up for early access at <a href="https://clearverse.ai">clearverse.ai</a>.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics.</p><div><hr></div><p><strong>What&#8217;s your read on this lawsuit? Does it change how you think about uploading to platforms?</strong> I&#8217;d like to hear your perspective in the comments.</p><div><hr></div><p><em>P.S. If this helped clarify what&#8217;s happening with AI music and copyright, send it to a creator friend. These issues affect everyone making music right now.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Supreme Court Just Answered the AI Copyright Question. Here's What It Means for Your Music.]]></title><description><![CDATA[On March 2, 2026, the U.S. Supreme Court declined to hear Thaler v. Perlmutter; quietly ending a decade-long legal battle over whether AI can be recognized as an author under U.S. copyright law.]]></description><link>https://insights.clearverse.ai/p/the-supreme-court-just-answered-the</link><guid isPermaLink="false">https://insights.clearverse.ai/p/the-supreme-court-just-answered-the</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 08 Mar 2026 14:49:38 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The answer, at least for now: No.</p><p>This wasn&#8217;t a dramatic ruling. The Court simply refused to take up the case, leaving lower court decisions intact. But that procedural silence carries enormous weight for anyone creating music with AI tools.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>If you use Suno, Udio, or any other AI music generator, this decision directly affects the legal foundation of your work. Let&#8217;s break down what actually happened, what it means, and what you need to do about it.</p><div><hr></div><h2>The Case That Finally Reached (and Was Rejected by) the Highest Court</h2><p>Dr. Stephen Thaler is a computer scientist from St. Charles, Missouri, and founder of Imagination Engines Incorporated. In 2012, his AI system DABUS (also called the &#8220;Creativity Machine&#8221;) generated a visual artwork titled &#8220;A Recent Entrance to Paradise.&#8221;</p><p>In November 2018, Thaler filed for copyright registration; but with an unusual twist. He listed DABUS, the AI, as the author, describing the work as &#8220;created autonomously by machine.&#8221; He sought to own the copyright as a &#8220;work-for-hire to the owner of the Creativity Machine.&#8221;</p><p>The Copyright Office rejected his application in August 2019, stating: &#8220;We cannot register this work because it lacks the human authorship necessary to support a copyright claim.&#8221;</p><p>Thaler didn&#8217;t give up. He filed reconsideration requests in September 2019, May 2020, and February 2022. Each was rejected for the same reason.</p><p>In June 2022, he sued the Copyright Office. In August 2023, Judge Beryl A. Howell of the U.S. District Court for D.C. ruled against him, writing what has become the defining phrase of this legal era:</p><p><strong>&#8220;Human authorship is a bedrock requirement of copyright.&#8221;</strong></p><p>Thaler appealed. On March 18, 2025, the D.C. Circuit Court of Appeals unanimously affirmed the district court&#8217;s decision. Judge Patricia Millett&#8217;s opinion was unambiguous: the Copyright Act of 1976 &#8220;requires all eligible work to be authored in the first instance by a human being.&#8221;</p><p>The court even offered an analogy: AI should be understood as a sophisticated tool, &#8220;akin to a laboratory instrument.&#8221; The tool might help create something, but it cannot be the author.</p><p>Thaler petitioned the Supreme Court in October 2025, arguing the case was of &#8220;paramount importance&#8221; given the rapid rise of generative AI. On January 23, 2026, the Trump administration&#8217;s Department of Justice filed a brief urging the Court to decline the case, noting: &#8220;Although the Copyright Act does not define the term &#8216;author,&#8217; multiple provisions of the act make clear that the term refers to a human rather than a machine.&#8221;</p><p>On March 2, 2026, the Supreme Court denied certiorari without comment.</p><p>Thaler&#8217;s attorneys responded: The decision risks &#8220;irreversibly and negatively impacting AI development and use in the creative industry during critically important years.&#8221;</p><p>Maybe. But the law is now settled; at least until Congress acts.</p><div><hr></div><h2>What This Actually Means (And What It Doesn&#8217;t)</h2><p>Let&#8217;s be precise about what this decision does and doesn&#8217;t do.</p><p><strong>What it confirms:</strong></p><p>Works created <em>entirely</em> by AI, without meaningful human creative contribution, cannot be copyrighted under U.S. law. If you type a prompt into Suno and release the output unchanged, that track likely has no copyright protection. Anyone could copy it, and you&#8217;d have limited legal recourse.</p><p><strong>What it does NOT do:</strong></p><p>This ruling doesn&#8217;t ban AI-assisted music creation. The D.C. Circuit explicitly stated that &#8220;the human authorship requirement does not prohibit copyrighting work made by or with the assistance of artificial intelligence.&#8221;</p><p>It doesn&#8217;t affect your Suno or Udio subscription. Those platforms grant you <em>commercial use rights</em> through their terms of service; a contractual license, not a copyright transfer. You can still monetize AI-generated tracks on YouTube, Spotify, or elsewhere.</p><p>It doesn&#8217;t address the ongoing lawsuits over AI training data. Whether companies like Suno can legally train on copyrighted music is a separate legal question (fair use) from whether their outputs are copyrightable.</p><div><hr></div><h2>The Copyright Office Already Told Us This Was Coming</h2><p>If you&#8217;ve been following this space, the Supreme Court&#8217;s decision shouldn&#8217;t surprise you. The Copyright Office has been consistent for years.</p><p>On January 29, 2025, the Office released Part 2 of its Copyright and Artificial Intelligence Report, which stated clearly:</p><p><strong>&#8220;Given current generally available technology, prompts alone do not provide sufficient human control to make users of an AI system the authors of the output.&#8221;</strong></p><p>The report drew a crucial distinction: AI can be used &#8220;to assist&#8221; human creativity, but not as a &#8220;stand in&#8221; for it. Using AI to help brainstorm, clean up audio, or generate reference ideas? That&#8217;s fine. Typing a prompt and releasing the raw output as your creative work? That likely won&#8217;t qualify for copyright protection.</p><p>Register of Copyrights Shira Perlmutter put it plainly: &#8220;Where human creativity is expressed through the use of AI systems, it continues to enjoy protection. Extending protection to material whose expressive elements are determined by a machine, however, would undermine rather than further the constitutional goals of copyright.&#8221;</p><div><hr></div><h2>What This Means for You as a Creator</h2><p>Here&#8217;s the practical reality for anyone using AI music tools in 2026:</p><p><strong>1. Raw AI output = legally vulnerable</strong></p><p>If you generate a track in Suno and release it unchanged, you have commercial use rights through your subscription; but likely no copyright. If someone copies your track, your legal standing to enforce is weak.</p><p>This is why Suno&#8217;s own terms of service include this disclaimer: &#8220;Due to the nature of machine learning, Suno makes no representation or warranty to you that any copyright will vest in any Output.&#8221;</p><p>They&#8217;re telling you this directly.</p><p><strong>2. Human contribution strengthens your position</strong></p><p>The more you add, the stronger your claim. According to the Copyright Office&#8217;s guidance, copyright can attach to:</p><ul><li><p>Human-authored lyrics (even if set to AI-generated music)</p></li><li><p>Substantial modifications to AI output</p></li><li><p>Creative arrangement or selection of AI-generated elements</p></li><li><p>Original vocals, instruments, or production you layer on top</p></li></ul><p>If you&#8217;re treating AI as raw material and putting your creative stamp on it, you&#8217;re in a much better position than someone just hitting &#8220;generate&#8221; and &#8220;export.&#8221;</p><p><strong>3. Documentation matters</strong></p><p>As AI becomes more embedded in creative workflows, you may need to demonstrate what you contributed. Save your drafts. Keep notes on your process. Document which elements are yours versus AI-generated.</p><p>This isn&#8217;t paranoia; it&#8217;s prudent practice in a landscape where the legal status of your work may be challenged.</p><p><strong>4. Platform disclosure requirements are here</strong></p><p>Spotify, Apple Music, and YouTube are implementing or expanding disclosure requirements for AI-generated content. Spotify&#8217;s DDEX standard requires labels and distributors to indicate where AI was used; in vocals, instruments, or production. YouTube treats &#8220;raw&#8221; AI audio with minimal human input as low-value content, potentially ineligible for monetization.</p><p>Bandcamp went further in January 2026, banning AI-generated music entirely. Their stated goal: ensuring &#8220;fans have confidence that the music they find on Bandcamp was created by humans.&#8221;</p><p>If you&#8217;re distributing AI-assisted music, disclosure isn&#8217;t optional anymore. And non-disclosure could cost you.</p><div><hr></div><h2>The Bigger Picture</h2><p>The Supreme Court&#8217;s refusal to hear Thaler&#8217;s case doesn&#8217;t mean AI is incompatible with copyright. It means AI cannot <em>replace</em> human authorship.</p><p>This is an important distinction. Courts and the Copyright Office aren&#8217;t hostile to creators who use AI tools; they&#8217;re drawing a line around works that have no meaningful human creative input.</p><p>For YouTube creators using AI music in their videos, the practical impact is limited. Your videos are your creative work. Background music, whether licensed, AI-generated, or from the YouTube Audio Library, is just one element.</p><p>But if you&#8217;re building a music-focused brand, releasing tracks on streaming platforms, or otherwise treating AI-generated music as a primary creative output, you need to think carefully about:</p><ul><li><p>What human contribution are you making?</p></li><li><p>Can you document that contribution?</p></li><li><p>Are you disclosing AI use where required?</p></li><li><p>Do you understand the difference between commercial use rights and copyright ownership?</p></li></ul><div><hr></div><h2>Where This Goes From Here</h2><p>The D.C. Circuit acknowledged that AI technology will continue to evolve. Judge Millett&#8217;s opinion even referenced Star Trek&#8217;s Data as an example of a future AI that might respond to economic incentives; noting that &#8220;if the human authorship requirement stymied the creation of original work,&#8221; Congress could address it.</p><p>That door isn&#8217;t closed forever. But for now, Congress hasn&#8217;t acted, and courts have spoken: if you want copyright protection, there must be a human in the creative process.</p><p>For creators, this creates both risk and opportunity. The risk is obvious: raw AI output is legally thin. The opportunity is that human creativity still matters; and the law says so.</p><div><hr></div><h2>Before You Hit Publish</h2><p>If you&#8217;re using AI music tools, ask yourself:</p><ol><li><p>What am I actually contributing to this track?</p></li><li><p>Is my contribution substantial enough to demonstrate authorship?</p></li><li><p>Have I disclosed AI use where my distribution platform requires it?</p></li><li><p>Do I understand what my platform license does and doesn&#8217;t give me?</p></li></ol><p>These aren&#8217;t just legal questions; they&#8217;re questions about the kind of creator you want to be.</p><p>AI can be an incredible tool for music creation. But tools don&#8217;t create alone. The law just confirmed what many of us already believed: the human behind the machine still matters.</p><div><hr></div><p><em>ClearVerse is building technology to help creators understand the legal exposure in their music before they release it &#8212; so you can create with confidence, not confusion.<br></em><br><strong>Signups are open.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics.</p><div><hr></div><p><strong>What&#8217;s your take on the Supreme Court&#8217;s decision? Does this change how you think about AI music tools?</strong> I&#8217;d love to hear your perspective in the comments.<br><strong><br>P.S.</strong> If this helped clarify the copyright landscape, forward it to a creator friend who uses AI tools. The more we understand the rules, the better we can work within them.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[You Own It. Actually, You Don't. Wait, You Do? What Suno's Ownership Flip-Flop Means for Creators]]></title><description><![CDATA[You Own It. Actually, You Don't. Wait, You Do? What Suno's Ownership Flip-Flop Means for Creators]]></description><link>https://insights.clearverse.ai/p/you-own-it-actually-you-dont-wait</link><guid isPermaLink="false">https://insights.clearverse.ai/p/you-own-it-actually-you-dont-wait</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Wed, 04 Mar 2026 15:44:16 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>For a brief window in late December, Suno&#8217;s FAQ said something very different about whether you own the songs you create. Then creators noticed. Then Suno clarified. Then everything went back to normal.</p><p>Except it didn&#8217;t; because the episode revealed something important that every creator using AI music tools needs to understand.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><h2>What Actually Happened</h2><p>Let me walk you through the timeline, because the details matter.</p><p><strong>November 2025:</strong> Suno&#8217;s Help Center was clear. If you paid for Pro or Premier, &#8220;you own the songs&#8221; and &#8220;you are granted a commercial use license to monetize those songs.&#8221; Simple.</p><p><strong>November 25, 2025:</strong> Suno announced a landmark settlement with Warner Music Group, ending the label&#8217;s copyright lawsuit and launching a licensing partnership. The deal promised &#8220;more advanced and licensed models&#8221; coming in 2026.</p><p><strong>Late December 2025:</strong> Creators started noticing that Suno&#8217;s FAQ language had quietly changed. The new version read differently: &#8220;Even with granted commercial use rights, you generally are not considered the owner of the songs, since the output was generated by Suno.&#8221;</p><p>Another page went further: &#8220;The answer (as to whether Suno owns outputs) is a bit complicated, but generally, yes. Suno is ultimately responsible for the output itself, though you help guide it.&#8221;</p><p>That&#8217;s a meaningful shift from &#8220;you own the songs&#8221; to &#8220;you&#8217;re not considered the owner.&#8221;</p><p><strong>January 7, 2026:</strong> After creator feedback spread across Reddit, Discord, and social media, Suno posted a clarification on X: &#8220;We recently made an update to our Knowledge Base (FAQ) and it didn&#8217;t clearly describe ownership on our platform... you do own the Output you make in the Pro and Premier plans and you are granted commercial rights to use those Outputs.&#8221;</p><p>Suno reverted the FAQ to its previous version. The company emphasized that the Terms of Service, the actual legal document, hadn&#8217;t changed since November 6, 2025.</p><div><hr></div><h2>Why This Matters More Than It Seems</h2><p>Here&#8217;s what most coverage of this story missed: even with the clarification, there&#8217;s a critical distinction buried in Suno&#8217;s Terms of Service that every creator should understand.</p><p>The Terms say Suno &#8220;assigns to you all of its right, title and interest&#8221; in outputs you create while subscribed to a paid plan. That sounds like ownership. And according to Suno, it is.</p><p>But the very next sentence adds: &#8220;However, due to the nature of machine learning, Suno makes no representation or warranty to you that any copyright will vest in any Output.&#8221;</p><p>Read that again. You own the output. But that output might not be copyrightable.</p><p>This isn&#8217;t Suno being sneaky. It&#8217;s Suno being honest about a genuinely unsettled area of law.</p><div><hr></div><h2>The Difference Between Ownership and Copyright</h2><p>This is where most creators get confused; and it&#8217;s the most important thing to understand if you&#8217;re using AI tools to create music.</p><p><strong>Ownership</strong> is about your relationship with the platform. Suno says paid subscribers own their outputs. That means Suno won&#8217;t claim your songs, won&#8217;t take a cut of your revenue, and won&#8217;t stop you from distributing them.</p><p><strong>Copyright</strong> is about your relationship with the law. Under current U.S. Copyright Office guidance, works created entirely by AI, without sufficient human creative input, generally aren&#8217;t eligible for copyright protection.</p><p>You can own something that isn&#8217;t copyrightable. You just can&#8217;t stop someone else from copying it.</p><p>Here&#8217;s what that looks like in practice:</p><ul><li><p>You create a song with Suno while subscribed to Pro</p></li><li><p>You own that song (per Suno&#8217;s terms)</p></li><li><p>You upload it to Spotify through DistroKid</p></li><li><p>You earn royalties from streams</p></li><li><p>Someone else downloads your song and re-uploads it as their own</p></li><li><p>You have limited legal recourse because the song may not be copyrightable</p></li></ul><p>This isn&#8217;t a Suno problem. It&#8217;s an AI music problem. Udio&#8217;s terms have similar disclaimers. So will every AI music platform until the law catches up.</p><div><hr></div><h2>What the December Confusion Actually Revealed</h2><p>The brief language change, and the speed of the backlash, tells us something important about where AI music is heading.</p><p>Suno now has 2 million paid subscribers and $300 million in annual recurring revenue. Users generate roughly 7 million tracks per day on the platform. That&#8217;s more music every two weeks than Spotify&#8217;s entire catalog.</p><p>When you have that many creators depending on your platform, words matter. The difference between &#8220;you own the songs&#8221; and &#8220;you&#8217;re granted commercial use rights&#8221; might seem like lawyer-speak, but creators immediately understood the implications.</p><p>The episode also landed at a sensitive moment. Suno had just settled with Warner Music. New &#8220;licensed models&#8221; were coming. Download caps were announced. Creators were already watching for signs that the platform might become more restrictive.</p><p>Suno moved quickly to clarify, and I think that&#8217;s worth acknowledging. Once the confusion surfaced publicly, they posted a clear statement within days and reverted the FAQ. Compare that to platforms that let ambiguity linger for months.</p><p>But the underlying tension isn&#8217;t going away. AI music platforms are caught between two forces: creators who want simple, clear ownership, and a legal landscape that can&#8217;t provide it yet.</p><div><hr></div><h2>What This Means If You&#8217;re a YouTube Creator</h2><p>If you&#8217;re using Suno (or Udio, or any AI music tool) to create background music, intros, or full tracks for your content, here&#8217;s what you should actually do:</p><p><strong>1. Understand that &#8220;ownership&#8221; has limits</strong></p><p>You can monetize AI-generated music on YouTube, Spotify, and other platforms. But you may not be able to enforce copyright claims against others who copy it. Plan accordingly.</p><p><strong>2. Add human creativity where it matters</strong></p><p>The Copyright Office has indicated that human creative input can make AI-assisted works copyrightable. If you write original lyrics, perform vocals, or substantially modify the AI output, you strengthen your legal position.</p><p><strong>3. Read the terms; especially the disclaimers</strong></p><p>Every AI platform has language about copyright uncertainty. This isn&#8217;t fine print designed to trick you. It&#8217;s an accurate description of the current legal landscape.</p><p><strong>4. Keep records</strong></p><p>Document when you created tracks, what plan you were on, and what inputs you provided. If ownership questions arise later, you&#8217;ll want receipts.</p><p><strong>5. Stay informed</strong></p><p>The rules are changing. The Copyright Office is still developing guidance. Courts are still deciding cases. What&#8217;s true today might shift in six months.</p><div><hr></div><h2>The Bigger Picture</h2><p>Suno isn&#8217;t the villain in this story. Neither are the creators who raised concerns. Everyone is navigating genuinely uncharted territory.</p><p>AI music tools are giving millions of people the ability to create songs who never could before. That&#8217;s remarkable. It&#8217;s also creating legal and business questions that don&#8217;t have clean answers yet.</p><p>The platforms are trying to build sustainable businesses while lawsuits are still pending. Creators are trying to monetize their work while copyright rules remain unclear. Labels are trying to protect their catalogs while also exploring licensing deals.</p><p>All of this is happening simultaneously, in public, at scale.</p><p>The December confusion at Suno was a small window into how fragile the current equilibrium is. A few sentences in an FAQ created genuine anxiety among creators who depend on the platform. That anxiety was reasonable; because the underlying uncertainty is real.</p><div><hr></div><h2>What We&#8217;re Building at ClearVerse</h2><p>This is exactly why I started ClearVerse.</p><p>When I talk to creators using AI music tools, the same questions come up over and over: Can I monetize this? Will I get a copyright claim? What if my song sounds similar to something else? Am I actually protected?</p><p>The answers aren&#8217;t simple. They depend on how you created the music, what inputs you used, what the output sounds like, and which platform you&#8217;re releasing on.</p><p>We&#8217;re building a tool that helps you understand your risk before you release; not after you get a claim or a takedown notice. Think of it as a pre-flight check for your music.</p><p>Because the best time to understand your legal exposure isn&#8217;t when something goes wrong. It&#8217;s before you hit publish.</p><p><strong>Signups are open.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics.</p><div><hr></div><p><strong>Have you been following the Suno ownership situation? Have questions about your rights when using AI music tools? Drop a comment &#8212; I read all of them.</strong></p><p><em>P.S. If this was helpful, forward it to a creator friend who uses AI music. These questions affect everyone in the space, and most people don&#8217;t know what they don&#8217;t know.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[97% of People Can't Tell AI Music from Human Music. That's Not the Problem.]]></title><description><![CDATA[Last November, Deezer and Ipsos ran a study across eight countries with 9,000 participants. They played people three songs and asked them to identify which ones were AI-generated. 97% got it wrong.]]></description><link>https://insights.clearverse.ai/p/97-of-people-cant-tell-ai-music-from</link><guid isPermaLink="false">https://insights.clearverse.ai/p/97-of-people-cant-tell-ai-music-from</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Mon, 23 Feb 2026 04:07:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The headlines wrote themselves. &#8220;AI Fools Listeners.&#8221; &#8220;Humans Can&#8217;t Tell the Difference.&#8221; The implication was clear: AI music has won. It&#8217;s indistinguishable. Game over for human musicians.</p><p>But here&#8217;s what those headlines missed: the inability to detect AI music isn&#8217;t the crisis. The crisis is what happens after the music gets uploaded.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><h2>The Real Story Behind the 97%</h2><p>Let&#8217;s be clear about what the Deezer study actually found.</p><p>Yes, 97% of people failed a blind listening test. But dig into the details and you see something more interesting: 52% of those people felt uncomfortable when they learned they couldn&#8217;t tell the difference. 71% were surprised. 80% said AI-generated music should be clearly labeled.</p><p>In other words, people don&#8217;t want to be fooled. They want to know what they&#8217;re listening to.</p><p>And when you look at what&#8217;s actually happening on streaming platforms, you start to understand why.</p><div><hr></div><h2>60,000 Tracks Per Day</h2><p>Deezer is the only streaming platform that publicly reports how much AI content it receives. In January 2025, they counted 10,000 fully AI-generated tracks uploaded daily. By September, it was 30,000. By November, 50,000. By January 2026, it hit 60,000.</p><p>That&#8217;s 39% of all music delivered to the platform. Every single day.</p><p>But here&#8217;s the number that matters most: up to 85% of the streams on those AI tracks are fraudulent.</p><p>Not &#8220;some.&#8221; Not &#8220;a concerning percentage.&#8221; Eighty-five percent.</p><p>The fraud works like this: someone uses an AI tool to generate thousands of tracks. They upload them under fake artist names. Then they use bots, manipulated playlists, and click farms to rack up streams. The streaming platform&#8217;s royalty pool pays out based on streams, so money flows from legitimate artists to scammers running automation scripts.</p><p>Deezer caught this because they built detection systems. They tag AI music, exclude it from algorithmic recommendations, and demonetize fraudulent streams. Across their entire catalog, fraud accounts for about 8% of streams. But within AI-generated content specifically? It&#8217;s 85%.</p><p>The problem isn&#8217;t that AI music sounds real. The problem is that AI music is primarily being used to steal.</p><div><hr></div><h2>What the Other Platforms Are Dealing With</h2><p>Deezer is relatively small compared to Spotify and Apple Music. But they&#8217;re the only ones publishing detailed AI upload data.</p><p>What we know about the larger platforms:</p><p>Apple Music&#8217;s VP Oliver Schusser revealed in early February that they identified and demonetized 2 billion fraudulent streams in 2025. Two billion. He called it a &#8220;zero-sum game&#8221; and announced they&#8217;re doubling their fraud penalties from a maximum of 25% to 50% of would-be royalties.</p><p>Spotify removed over 75 million &#8220;spammy&#8221; tracks in 2025 alone, acknowledging that AI has made it &#8220;easier than ever for bad actors to mass upload content.&#8221; They&#8217;ve rolled out new spam filters and banned unauthorized AI voice clones.</p><p>These aren&#8217;t hypothetical concerns. In September 2024, Michael Smith was charged with wire fraud for using AI to generate hundreds of thousands of songs, then using bot accounts to stream them. At his peak, prosecutors said he was generating 661,440 fake streams per day across Spotify and Apple Music.</p><p>The streaming economy is being gamed at scale, and AI is the tool that makes it possible.</p><div><hr></div><h2>Why Detection Isn&#8217;t the Answer</h2><p>Here&#8217;s where it gets complicated.</p><p>Deezer&#8217;s detection system can identify 100% AI-generated tracks from tools like Suno and Udio with 99.8% accuracy. They&#8217;ve applied for patents. They&#8217;re licensing it to other companies.</p><p>But detection only solves part of the problem. It tells you what something is. It doesn&#8217;t tell you whether it&#8217;s legal, ethical, or worth paying for.</p><p>Consider the edge cases:</p><p>A poet uses Suno to set her lyrics to music. She writes every word, but the instrumentation is AI-generated. Xania Monet, created this way, became the first AI artist to chart on Billboard and signed a multimillion-dollar record deal.</p><p>A band called The Velvet Sundown racked up 500,000 monthly Spotify listeners before anyone realized they weren&#8217;t human. The creator later admitted it was a &#8220;hoax&#8221; to see how far AI music could go.</p><p>An AI-generated country track called &#8220;Walk My Walk&#8221; hit number one on the Billboard chart in November 2025.</p><p>Some of this is creative experimentation. Some is outright fraud. The technology to detect AI doesn&#8217;t help you distinguish between the two.</p><div><hr></div><h2>What Actually Matters</h2><p>The 97% headline makes for good panic. But here&#8217;s what the Deezer study actually tells us about what people care about:</p><p>80% want AI music clearly labeled.</p><p>73% of streaming users want to know if their platform is recommending AI content.</p><p>69% think payouts for AI music should be lower than for human music.</p><p>65% say it shouldn&#8217;t be allowed to use copyrighted material to train AI models.</p><p>70% believe AI music threatens musicians&#8217; livelihoods.</p><p>People aren&#8217;t asking &#8220;can I tell the difference?&#8221; They&#8217;re asking &#8220;is this fair?&#8221;</p><p>And that&#8217;s a much harder question to answer.</p><div><hr></div><h2>The Platform Response</h2><p>Right now, the platforms are responding to AI music in three ways:</p><p><strong>Detection and labeling.</strong> Deezer tags AI content and excludes it from recommendations. This is the most aggressive approach, but it requires building and maintaining sophisticated detection systems.</p><p><strong>Fraud enforcement.</strong> Apple Music and Spotify are demonetizing fake streams and penalizing distributors. This targets the symptom (fraud) rather than the cause (AI music), but it&#8217;s easier to implement.</p><p><strong>Policy updates.</strong> Spotify now requires distributors to disclose AI use and has banned unauthorized voice clones. These policies are new and still evolving.</p><p>What none of them are doing yet: fundamentally rethinking how streaming royalties work when anyone can generate unlimited content.</p><p>The current system pays based on streams. If you can generate 1,000 tracks in an hour and use bots to stream them, you can siphon money from artists who spent months on a single album. The detection systems help, but they&#8217;re playing defense against an offense that keeps getting more sophisticated.</p><div><hr></div><h2>What This Means for You</h2><p>If you&#8217;re a creator using AI tools, the landscape is shifting fast.</p><p>The platforms are building detection systems. Your AI-assisted music may get flagged, even if you&#8217;re using it legitimately. The line between &#8220;AI-assisted&#8221; and &#8220;fully AI-generated&#8221; matters for how platforms treat your content.</p><p>The royalty pool is being diluted. Even with fraud detection, the sheer volume of AI content affects how money flows. More tracks competing for the same pool means less per stream for everyone.</p><p>The legal questions aren&#8217;t settled. Who owns AI-generated music? Can it be copyrighted? The Copyright Office says fully AI-generated works don&#8217;t get protection. Courts haven&#8217;t fully weighed in. Labels are still suing Suno and Udio.</p><p>The stigma is real. 40% of streaming users say they&#8217;d skip AI music without listening if they knew it was AI. 45% want the option to filter it out entirely. That&#8217;s not a majority, but it&#8217;s not nothing.</p><div><hr></div><h2>The Bigger Picture</h2><p>The music industry has always adapted to new technology. Every format change, every distribution shift, every new tool has been met with predictions of doom followed by eventual adaptation.</p><p>AI is different in one crucial way: it doesn&#8217;t just change how music is made or distributed. It changes who can make it and how much can be created.</p><p>When 60,000 AI tracks hit a single platform every day, when 85% of those streams are fraudulent, when 2 billion fake streams get demonetized in a single year, we&#8217;re not talking about a creative tool. We&#8217;re talking about an industrial-scale challenge to the economics of music.</p><p>The 97% who couldn&#8217;t tell the difference in a listening test? They&#8217;re not the story.</p><p>The story is what we do about a system where anyone can create unlimited content, upload it instantly, and compete for the same royalty pool as artists who spend their lives making music.</p><p>That&#8217;s the conversation we should be having.</p><div><hr></div><h2>What to Watch</h2><p><strong>Detection technology licensing.</strong> Deezer is now selling their AI detection tool to other companies. If Spotify and Apple Music adopt similar systems, AI content will be flagged across all major platforms.</p><p><strong>Royalty model changes.</strong> Deezer has already moved to an &#8220;artist-centric&#8221; payment model. Others may follow, shifting away from pure stream counts.</p><p><strong>Legal developments.</strong> Sony is still suing Suno and Udio. The UK is debating copyright changes for AI training. The Copyright Office continues to clarify what can and can&#8217;t be protected.</p><p><strong>Platform policies.</strong> Watch for changes in how distributors handle AI content, whether platforms require disclosure, and how recommendation algorithms treat synthetic music.</p><div><hr></div><p>This is exactly the kind of complexity I&#8217;m tracking at ClearVerse. We&#8217;re building tools to help creators understand not just whether something sounds similar, but whether it creates actual legal risk. Because in a world where AI can make anything sound real, understanding the legal and economic reality becomes even more important.</p><p>If you&#8217;re navigating this, I&#8217;d love to hear what questions you have. What&#8217;s confusing? What&#8217;s worrying you? What do you wish the platforms would do?</p><p>Hit reply and tell me what you&#8217;re seeing.</p><p><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; Know someone trying to make sense of AI music? Send this their way.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Walled Gardens vs. Open Studios: The Fight That Will Decide the Future of AI Music]]></title><description><![CDATA[Two weeks ago, during Grammy Week, Suno's Chief Music Officer Paul Sinclair posted a LinkedIn memo that landed like a grenade in the music industry.]]></description><link>https://insights.clearverse.ai/p/walled-gardens-vs-open-studios-the</link><guid isPermaLink="false">https://insights.clearverse.ai/p/walled-gardens-vs-open-studios-the</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 15 Feb 2026 16:55:38 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The title: &#8220;Open Studios, not walled gardens.&#8221;</p><p>Sinclair, a former Warner Music executive who joined Suno last July, was taking direct aim at Universal Music Group&#8217;s approach to AI licensing. His argument: locking AI-generated music inside closed platforms will stifle creativity and repeat the mistakes the industry made fighting the internet in the early 2000s.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Universal&#8217;s response came through Michael Nash, the company&#8217;s Chief Digital Officer, who called Suno&#8217;s open approach &#8220;an unsustainable status quo&#8221; that risks &#8220;direct cannibalisation&#8221; of artists.</p><p>This isn&#8217;t corporate posturing. This is a fundamental disagreement about how AI music should work. And whichever side wins will shape what you can and can&#8217;t do with AI music tools for years to come.</p><div><hr></div><h2>What&#8217;s Actually Being Debated</h2><p>The fight comes down to one question: what happens after you create something with AI?</p><p><strong>The walled garden model</strong> (Universal&#8217;s position): AI-generated music stays on the platform where it was created. You can stream it, share it within the app, maybe remix it further. But you can&#8217;t download it. You can&#8217;t put it on Spotify. You can&#8217;t use it in a YouTube video. The music exists only inside the walls.</p><p><strong>The open studio model</strong> (Suno&#8217;s position): You can create music with AI and then take it wherever you want. Download it. Distribute it. Monetize it. The platform is a tool, not a container.</p><p>These aren&#8217;t theoretical positions. They&#8217;re already being implemented.</p><div><hr></div><h2>What Happened to Udio</h2><p>When Universal settled its lawsuit with Udio in October 2025, the &#8220;walled garden&#8221; concept went from idea to reality overnight.</p><p>The day the deal was announced, Udio disabled all downloads. No warning. Users who had paid for subscriptions, who had spent months building libraries of AI-generated tracks, suddenly couldn&#8217;t access their own creations.</p><p>The backlash was immediate. Reddit threads filled with users threatening legal action. Some called it fraud. One user wrote: &#8220;I&#8217;ve spent hundreds of dollars and countless hours building tracks with this tool. No one warned us that one day, we wouldn&#8217;t even be able to access our own music.&#8221;</p><p>Udio offered a 48-hour window for users to download their existing tracks. After that, the walls went up permanently.</p><p>The new Udio platform launching later this year will operate entirely as a walled garden. You&#8217;ll be able to stream your creations within the app. You won&#8217;t be able to take them anywhere else.</p><div><hr></div><h2>Why Suno Got a Different Deal</h2><p>A month after Udio&#8217;s settlement, Warner Music struck a deal with Suno. But the terms were notably different.</p><p>Suno users can still create songs. They can still download them. They can still distribute them to streaming services.</p><p>The main changes: Suno will launch new models trained on licensed music in 2026. Free users won&#8217;t be able to download (only stream and share). Paid users will have monthly download caps instead of unlimited access.</p><p>It&#8217;s a restriction, but it&#8217;s not a prison.</p><p>Why did Warner give Suno more freedom than Universal gave Udio? Industry observers point to a few factors.</p><p>First, Suno is bigger. With nearly 100 million users and a recent $250 million funding round valuing the company at $2.45 billion, Suno had more leverage.</p><p>Second, there&#8217;s the China question. Multiple analysts have noted that if Western AI music platforms become too restrictive, users will migrate to unregulated alternatives. Reddit threads following the settlements were full of comments warning: &#8220;Soon there will be a model from China to fill the gap.&#8221;</p><p>Third, Warner may simply have a different philosophy. CEO Robert Kyncl has been more publicly open to AI innovation than his counterparts at Universal and Sony.</p><div><hr></div><h2>The Arguments on Each Side</h2><p><strong>Universal&#8217;s case for walled gardens:</strong></p><p>The labels argue that open distribution of AI-generated music will flood streaming platforms with low-quality content, dilute royalty pools, and directly compete with human artists. If anyone can generate a song and upload it to Spotify, the value of human-created music decreases.</p><p>They also point to fraud. Deezer reported in November 2025 that up to 70% of streams on AI-generated tracks are fraudulent, driven by bot farms gaming the royalty system. Walled gardens, they argue, prevent AI music from escaping into environments where it can be weaponized against artists.</p><p>Michael Nash put it bluntly: letting AI music flow freely is &#8220;direct cannibalisation&#8221; of artists&#8217; work.</p><p><strong>Suno&#8217;s case for open studios:</strong></p><p>Sinclair argues that excessive restrictions will kill the creative potential of AI tools. In his LinkedIn post, he wrote: &#8220;If we had tried to lock music into closed systems over the last 25 years, we wouldn&#8217;t have streaming as we know it &#8212; the world music library, available in your pocket.&#8221;</p><p>His point: user-generated content and open platforms enabled the rise of global genres and viral discovery. SoundCloud launched careers. YouTube made music accessible to billions. Restricting AI music to walled gardens treats every user as a potential bad actor rather than a potential creator.</p><p>Sinclair also argues that openness is compatible with licensing. Suno&#8217;s Warner deal proves you can have licensed models and still let users export their creations.</p><div><hr></div><h2>What This Means for You</h2><p>If you&#8217;re using AI music tools today, here&#8217;s the practical impact:</p><p><strong>If you&#8217;re on Udio:</strong> Your options are shrinking. Once the new platform launches, you&#8217;ll be able to create music within the app, but you won&#8217;t be able to take it anywhere. If your goal is to distribute AI-generated music on streaming platforms, Udio is no longer the tool for that.</p><p><strong>If you&#8217;re on Suno:</strong> You&#8217;ll still be able to create and download, but with limits. Free tier users will lose download access when the new models launch in 2026. Paid users will have caps. The open studio model survives, but it&#8217;s less open than before.</p><p><strong>If you&#8217;re waiting to see who wins:</strong> Watch the Sony settlements. Sony hasn&#8217;t settled with either Suno or Udio. They&#8217;re still actively litigating. How Sony&#8217;s lawsuits resolve will signal whether the industry is moving toward walled gardens as the standard or accepting some version of open distribution.</p><div><hr></div><h2>The Bigger Picture</h2><p>This debate isn&#8217;t just about AI music platforms. It&#8217;s about the future of AI-assisted creativity across every medium.</p><p>The walled garden model is a bet that control is more valuable than distribution. It prioritizes protecting existing revenue streams over enabling new ones. It assumes that if you give people tools to create and distribute freely, they&#8217;ll mostly use those tools to harm artists.</p><p>The open studio model is a bet that creativity flourishes when you remove friction. It prioritizes reach and accessibility over control. It assumes that most people using AI tools are genuine creators, not fraudsters, and that treating them like criminals will just push them to unregulated alternatives.</p><p>Both sides claim to be protecting artists. But they have fundamentally different ideas about what protection means.</p><div><hr></div><h2>What I&#8217;m Watching</h2><p>Three things will determine how this plays out:</p><p><strong>1. The quality gap.</strong> If the new licensed models from Suno and Udio sound noticeably worse than the current &#8220;trained on everything&#8221; versions, users will revolt or migrate to unregulated alternatives. The labels are betting that licensed training data can still produce compelling music. We&#8217;ll see.</p><p><strong>2. International competition.</strong> If Chinese or other international AI music platforms offer unrestricted creation and distribution, users who care about flexibility will leave. The walled garden only works if there&#8217;s nowhere else to go.</p><p><strong>3. Creator backlash or adoption.</strong> Will professional musicians embrace these tools as creative aids, or reject them as threats? Right now, the music industry is mostly fighting AI. But if major artists start publicly using AI-assisted creation, the dynamic shifts.</p><div><hr></div><h2>What I&#8217;m Building</h2><p>I&#8217;ve spent the last six months building tools to help creators navigate the legal complexity of AI music. ClearVerse focuses on copyright risk assessment: understanding whether your music might trigger infringement claims before you publish.</p><p>But the walled garden debate adds a new layer. It&#8217;s not just about whether your music might infringe on someone else&#8217;s rights. It&#8217;s about whether you&#8217;ll have any rights at all to music you create using these tools.</p><p><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics.</p><div><hr></div><h2>One Last Thing</h2><p>The music industry has a long history of fighting new technology, then adapting, then profiting from it.</p><p>They fought cassette tapes. They fought Napster. They fought YouTube. Each time, the initial response was restriction and litigation. Each time, the eventual outcome was licensing deals that created new revenue streams.</p><p>AI music might follow the same pattern. The question is whether the industry learned from those fights or is doomed to repeat them.</p><p>What do you think? Are walled gardens necessary protection or counterproductive overreach?</p><p>Hit reply and let me know. I read every response.</p><p>Talk soon.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; If you know someone trying to figure out what these platform changes mean for their music, forward this their way.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Someone Can Clone Your Voice With AI. In Most States, That's Perfectly Legal.]]></title><description><![CDATA[In April 2023, an anonymous producer called Ghostwriter dropped a track on TikTok. It featured Drake and The Weeknd trading verses about Selena Gomez. The song racked up 11 million views and hundreds]]></description><link>https://insights.clearverse.ai/p/someone-can-clone-your-voice-with</link><guid isPermaLink="false">https://insights.clearverse.ai/p/someone-can-clone-your-voice-with</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 08 Feb 2026 14:17:59 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>One problem: Drake and The Weeknd had nothing to do with it.</p><p>Ghostwriter had used AI to clone their voices. The track was so convincing that listeners couldn&#8217;t tell the difference. Universal Music Group scrambled to get it taken down, and eventually succeeded. But the takedown wasn&#8217;t based on a clear legal right to the artists&#8217; voices. It was a copyright claim over a producer tag buried in the track.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>That workaround worked for Drake. But what about everyone else?</p><p>If you&#8217;re a musician, voice actor, podcaster, or anyone whose voice has value, here&#8217;s the uncomfortable truth: in most of the United States, someone can clone your voice with AI and there&#8217;s not much you can do about it.</p><div><hr></div><h2>The Patchwork Problem</h2><p>The right to control how your voice and likeness are used commercially is called the &#8220;right of publicity.&#8221; It&#8217;s the legal principle that says you, not someone else, get to decide if your face appears on a billboard or your voice sells a product.</p><p>The problem is that right of publicity laws vary wildly from state to state. Some states have strong protections. Some have weak ones. And most of them were written long before anyone imagined you could generate a convincing vocal clone from a few minutes of audio samples.</p><p>Here&#8217;s what the landscape looks like:</p><p><strong>Strong protection (explicit AI coverage):</strong> Tennessee passed the ELVIS Act in March 2024, which explicitly protects against AI voice cloning. It&#8217;s the first law in the country specifically designed for this. Violations can result in civil lawsuits and criminal prosecution as a Class A misdemeanor.</p><p><strong>Moderate protection (voice included, but no AI-specific language):</strong> California has protected voice as part of publicity rights since the 1980s, thanks to cases like Bette Midler v. Ford Motor Company. But the law wasn&#8217;t written with AI in mind, so there&#8217;s uncertainty about how it applies.</p><p><strong>Weak or no protection:</strong> Many states don&#8217;t explicitly include voice in their publicity rights at all. And even in states that do, most laws require the unauthorized use to be &#8220;commercial&#8221; in a traditional sense. AI-generated content doesn&#8217;t always fit neatly into that box.</p><p>The result is a patchwork where your rights depend entirely on where you live and where the person cloning your voice operates. If someone in a state with no voice protection clones your vocals and uploads the result, your legal options might be limited to nothing.</p><div><hr></div><h2>What Tennessee&#8217;s ELVIS Act Actually Does</h2><p>Tennessee&#8217;s Ensuring Likeness Voice and Image Security Act (yes, named after Elvis) took effect on July 1, 2024. It&#8217;s worth understanding because it&#8217;s likely the template for future legislation elsewhere.</p><p>The ELVIS Act does a few key things:</p><p><strong>Explicitly includes voice as a property right.</strong> The law defines &#8220;voice&#8221; broadly to include both an individual&#8217;s actual voice and any simulation of it. If it&#8217;s &#8220;readily identifiable and attributable&#8221; to you, it&#8217;s protected.</p><p><strong>Covers AI-generated replicas specifically.</strong> The law targets &#8220;personalized generative AI cloning models and services that enable human impersonation.&#8221;</p><p><strong>Creates liability for the tools, not just the content.</strong> You can sue not only the person who publishes an unauthorized voice clone, but also anyone who &#8220;makes available an algorithm, software, tool, or other technology&#8221; whose primary purpose is creating unauthorized voice replicas.</p><p><strong>Carries real penalties.</strong> Civil lawsuits can seek injunctions, actual damages, and profits. Criminal violations are Class A misdemeanors, carrying up to 11 months and 29 days in jail and fines up to $2,500.</p><p><strong>Has exemptions for legitimate use.</strong> News coverage, commentary, criticism, satire, and parody are protected. So is representing yourself as yourself in an audiovisual work, unless the work is designed to create a false impression that it&#8217;s authentic.</p><p>The music industry lobbied hard for this law. Luke Bryan, Chris Janson, Lindsay Ell, and other Nashville artists showed up at the signing ceremony. The bill passed the Tennessee legislature unanimously.</p><p>But Tennessee is just one state. And the AI tools that can clone your voice don&#8217;t respect state lines.</p><div><hr></div><h2>The Federal Void</h2><p>There&#8217;s no federal right of publicity in the United States. That&#8217;s why you end up with 50 different state laws (and some states with no law at all).</p><p>Congress is trying to change that. The NO FAKES Act (Nurture Originals, Foster Art, and Keep Entertainment Safe) was first introduced as a draft in 2023, formally introduced in 2024, and reintroduced in April 2025. It would create a federal intellectual property right to your voice and likeness for the first time.</p><p>The bill has bipartisan support and backing from an unusual coalition: the music industry (UMG, Warner, RIAA, SAG-AFTRA) and the tech industry (YouTube, OpenAI, Google, Amazon, IBM) are both on board. That kind of alignment is rare.</p><p>What the NO FAKES Act would do:</p><ul><li><p>Establish that every individual has a federal property right in their voice and visual likeness</p></li><li><p>Allow individuals (or their heirs, for 70 years after death) to control the use of digital replicas</p></li><li><p>Create liability for creating, distributing, or profiting from unauthorized AI-generated replicas</p></li><li><p>Set up a notice-and-takedown process similar to the DMCA for copyright</p></li><li><p>Include exemptions for news, commentary, parody, satire, and other First Amendment-protected speech</p></li></ul><p>If passed, it would replace the state-by-state patchwork with a uniform national standard.</p><p>But the bill hasn&#8217;t passed yet. It failed to advance in 2024. It was reintroduced in April 2025 with more industry support, but as of now, there&#8217;s still no federal protection. And even if it does pass, the takedown mechanisms and enforcement details will matter a lot for how effective it actually is.</p><div><hr></div><h2>What This Means for Different Creators</h2><p><strong>If you&#8217;re a professional musician or voice actor:</strong></p><p>Your voice is your primary asset. Until federal law catches up, your protection depends heavily on where you&#8217;re based. If you&#8217;re in Tennessee, you have explicit protection against AI cloning. If you&#8217;re in California, you have some protection, but it wasn&#8217;t written for AI. If you&#8217;re elsewhere, check your state&#8217;s publicity rights laws carefully.</p><p>Consider whether your contracts with labels, publishers, or platforms address AI voice cloning. Many older contracts don&#8217;t. Newer ones increasingly do, often with opt-in provisions for AI training or likeness licensing.</p><p><strong>If you&#8217;re an independent creator building an audience:</strong></p><p>You&#8217;re probably not thinking about voice cloning as a threat yet. But as your profile grows, so does the value of your voice. Someone could theoretically train an AI on your podcast episodes, YouTube videos, or social content and create synthetic versions of you.</p><p>Documentation matters. Keep records of your original content. If you ever need to prove that your voice was cloned without permission, having timestamps and originals helps.</p><p><strong>If you&#8217;re using AI voice tools:</strong></p><p>Be careful whose voice you&#8217;re cloning. Using AI to generate content that sounds like a real, identifiable person without their permission could expose you to liability, especially if you&#8217;re in Tennessee or if the cloned artist is.</p><p>The &#8220;Heart on My Sleeve&#8221; case showed how fast platforms will act when major labels are involved. But smaller artists have less leverage. That doesn&#8217;t mean the legal risk is zero.</p><div><hr></div><h2>The Practical Playbook</h2><p>Until federal law provides clear protection, here&#8217;s what you can do:</p><p><strong>1. Know your state&#8217;s law</strong></p><p>Look up whether your state has a right of publicity statute, whether it includes voice, and whether it applies to AI-generated content. Tennessee&#8217;s ELVIS Act is the gold standard. California offers moderate protection. Many states offer very little.</p><p><strong>2. Document your voice</strong></p><p>Keep records of your original vocal work with timestamps. If you ever need to prove your voice was cloned, this documentation will matter.</p><p><strong>3. Review your contracts</strong></p><p>If you&#8217;re signing with labels, publishers, or platforms, look for clauses about AI, voice likeness, and digital replicas. Some newer deals include opt-in provisions for AI training. Understand what you&#8217;re agreeing to.</p><p><strong>4. Monitor for unauthorized use</strong></p><p>This is harder than it sounds. Unlike visual content, there&#8217;s no reverse-image search for voice. But keeping an eye on social media, YouTube, and streaming platforms for content falsely attributed to you is increasingly important.</p><p><strong>5. Support federal legislation</strong></p><p>The NO FAKES Act would solve a lot of these problems. If it matters to you, let your representatives know.</p><div><hr></div><h2>What I&#8217;m Building</h2><p>I&#8217;ve spent the last six months deep in copyright and AI law for music. The voice cloning issue sits right at the intersection of what ClearVerse is about: helping creators understand their legal exposure before it becomes a problem.</p><p>Right now, ClearVerse is focused on copyright risk assessment. But the broader question is the same: what are your actual rights, and how do you protect them in a landscape that&#8217;s changing faster than the law can keep up?<br><br><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics. </p><div><hr></div><h2>One Last Thing</h2><p>The Ghostwriter incident was a wake-up call. But it won&#8217;t be the last time someone clones a famous voice and goes viral. The tools are getting better. The barrier to entry is getting lower. And the legal framework still has massive gaps.</p><p>I want to hear from you: <strong>Has anyone ever used your voice or likeness without permission? Would you even know if they did?</strong></p><p>Hit reply and let me know. I read every response.</p><p>Talk soon.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; If you know a creator who hasn&#8217;t thought about voice cloning, send this their way. This is one of those things where the first time you learn about it shouldn&#8217;t be when it happens to you.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[You Might Not Own What You Create: The AI Music Copyright Problem Nobody's Talking About ]]></title><description><![CDATA[Two weeks ago, the Department of Justice told the Supreme Court to reject a case that could have changed everything about AI-generated art.]]></description><link>https://insights.clearverse.ai/p/you-might-not-own-what-you-create</link><guid isPermaLink="false">https://insights.clearverse.ai/p/you-might-not-own-what-you-create</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Thu, 05 Feb 2026 17:49:21 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The case was simple: a computer scientist named Stephen Thaler wanted to copyright an image his AI system created. He listed the AI as the sole author. The Copyright Office said no. The courts agreed. And now the government is urging the Supreme Court not to even hear the appeal.</p><p>The message is clear: if a machine made it, you don&#8217;t own it.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This might sound like an abstract legal debate. It&#8217;s not. If you&#8217;re using Suno, Udio, or any AI tool to make music, this affects you directly. Because that track you spent an hour prompting and tweaking? It might belong to everyone. And anyone can copy it, remix it, or upload it as their own.</p><p>Here&#8217;s what&#8217;s actually going on.</p><div><hr></div><h2>The Rule: Human Authorship Required</h2><p>In January 2025, the U.S. Copyright Office released its official guidance on AI-generated works. The core finding: copyright protection requires human authorship. If an AI determines the expressive elements of a work, that work isn&#8217;t copyrightable.</p><p>The key phrase is &#8220;meaningful human authorship.&#8221; The Copyright Office was explicit: prompts alone don&#8217;t count.</p><p>Here&#8217;s how they put it: &#8220;Given current generally available technology, prompts alone do not provide sufficient human control to make users of an AI system the authors of the output.&#8221;</p><p>So if you type &#8220;make me a lo-fi hip hop beat with jazzy piano samples&#8221; into Suno and download the result, you don&#8217;t own it. Not legally. That track enters the public domain the moment it&#8217;s created.</p><p>This isn&#8217;t a technicality. It&#8217;s the foundation of copyright law. And courts are enforcing it.</p><div><hr></div><h2>What This Means in Practice</h2><p>Let&#8217;s say you create a song with Suno. You love it. You upload it to Spotify. It starts getting streams.</p><p>Then someone else downloads your track, uploads it under their name, and starts collecting your royalties.</p><p>What can you do about it?</p><p>If your track was purely AI-generated, the answer might be: nothing.</p><p>Copyright gives you the legal right to control who copies, distributes, and profits from your work. But that right only exists if you own the copyright in the first place. If your work isn&#8217;t copyrightable because it lacks human authorship, you have no legal claim. Anyone can use it however they want.</p><p>This isn&#8217;t hypothetical. Streaming platforms are already flooded with AI-generated content. Deezer reported receiving over 50,000 AI-generated tracks per day in late 2025. As this flood continues, disputes over who &#8220;owns&#8221; AI-generated music will only increase.</p><p>And if you can&#8217;t prove meaningful human authorship, you&#8217;ll lose those disputes before they even start.</p><div><hr></div><h2>What Counts as &#8220;Meaningful Human Authorship&#8221;?</h2><p>This is where it gets complicated. The Copyright Office evaluates authorship on a case-by-case basis. But their guidance gives us some clear signals about what does and doesn&#8217;t count.</p><p><strong>What probably doesn&#8217;t count:</strong></p><ul><li><p>Typing a text prompt into an AI generator</p></li><li><p>Selecting from multiple AI-generated outputs</p></li><li><p>Making minor tweaks to AI-generated content</p></li><li><p>Choosing parameters like tempo, genre, or mood before generation</p></li></ul><p><strong>What probably does count:</strong></p><ul><li><p>Writing original lyrics that you then have AI set to music</p></li><li><p>Composing a melody yourself and using AI for arrangement or production</p></li><li><p>Substantially editing, rearranging, or modifying AI-generated output</p></li><li><p>Playing instruments over AI-generated stems</p></li><li><p>Creating a &#8220;selection and arrangement&#8221; of AI elements that reflects your creative vision</p></li></ul><p>The distinction the Copyright Office keeps making: are you using AI as a tool to assist your creativity, or is AI standing in for human creativity entirely?</p><p>If you&#8217;re a songwriter who uses AI to generate backing tracks for your original lyrics and melodies, you probably have a stronger copyright claim than someone who prompts an AI to create an entire song from scratch.</p><div><hr></div><h2>The Spectrum of Ownership</h2><p>Think of AI music creation on a spectrum:</p><p><strong>Fully AI-generated (no copyright):</strong> You prompt Suno with &#8220;upbeat pop song about summer love&#8221; and download the result without modification. The AI determined the melody, harmony, rhythm, lyrics, and arrangement. You contributed a concept. That&#8217;s not enough.</p><p><strong>AI-assisted with minimal human input (probably no copyright):</strong> You generate 10 versions and pick your favorite. You trim the intro and adjust the volume. You added selection and minor editing, but the expressive elements were still determined by the AI.</p><p><strong>AI-assisted with substantial human input (probably copyrightable):</strong> You write original lyrics. You hum a melody into the AI and have it develop the arrangement. You export the stems and re-record the bass line yourself. You make significant creative decisions that shape the final work. The human authorship is demonstrable.</p><p><strong>Human-created with AI assistance (copyrightable):</strong> You compose the song yourself, play the instruments, write the lyrics. You use AI for mixing assistance or to clean up a vocal take. The AI is a tool, like Auto-Tune or a drum machine. The creative expression is yours.</p><p>The further right you are on this spectrum, the stronger your copyright claim.</p><div><hr></div><h2>Why the Thaler Case Matters</h2><p>Stephen Thaler has been fighting this battle for years. He created an AI system called the &#8220;Creativity Machine&#8221; and tried to register a work it generated as copyrighted. He listed the AI as the author and himself as the owner.</p><p>The Copyright Office rejected him. A federal district court upheld that rejection. The D.C. Circuit Court of Appeals affirmed it in March 2025. And in May 2025, the court declined to rehear the case.</p><p>Now Thaler has petitioned the Supreme Court. His argument: the Copyright Act doesn&#8217;t explicitly require human authorship, and the Copyright Office is adding words to the statute that Congress never wrote.</p><p>On January 23, 2026, the Department of Justice filed its response urging the Court not to take the case. Their position: the lower courts got it right, and this case doesn&#8217;t raise any new legal questions that need Supreme Court resolution.</p><p>If the Supreme Court declines to hear the case (which seems likely), the human authorship requirement stays in place. And every creator using AI tools needs to understand what that means for their work.</p><div><hr></div><h2>The Practical Problem: Documentation</h2><p>Even if you do add meaningful human authorship to your AI-assisted work, you might have trouble proving it.</p><p>The Copyright Office requires applicants to disclose AI-generated content and describe their human contributions. If you can&#8217;t articulate what you contributed, your registration could be rejected or challenged later.</p><p>This creates a documentation problem. Most creators aren&#8217;t thinking about copyright when they&#8217;re in the middle of making music. They&#8217;re not logging which elements they wrote versus which the AI generated. They&#8217;re not saving drafts that show their creative process.</p><p>But if ownership ever becomes disputed, that documentation could be the difference between keeping your rights and losing them.</p><div><hr></div><h2>What To Do About This</h2><p>If you&#8217;re using AI to make music and you want to actually own what you create, here&#8217;s the practical playbook:</p><p><strong>1. Add substantial human creativity</strong></p><p>Don&#8217;t just prompt and download. Write your own lyrics. Compose your own melodies. Re-record elements. Make creative decisions that shape the final work in demonstrable ways.</p><p><strong>2. Document your process</strong></p><p>Keep records of what you contributed versus what the AI generated. Save intermediate drafts. Note which elements you wrote, performed, or substantially modified. This documentation could matter if you ever need to prove authorship.</p><p><strong>3. Understand your platform&#8217;s terms</strong></p><p>Suno and Udio both have terms of service that grant you certain rights to your creations. But platform terms don&#8217;t override copyright law. If your work isn&#8217;t copyrightable, the platform can&#8217;t make it copyrightable. Read the fine print and understand what you&#8217;re actually getting.</p><p><strong>4. Consider your use case</strong></p><p>If you&#8217;re making music for fun and don&#8217;t care about ownership, none of this matters. Generate away. But if you&#8217;re planning to monetize, license, or commercially exploit your AI-assisted music, the copyright question becomes critical.</p><p><strong>5. Stay informed</strong></p><p>This area of law is evolving rapidly. The Copyright Office is still developing its guidance. Courts are still deciding cases. What&#8217;s true today might shift as the legal landscape develops.</p><div><hr></div><h2>The Bigger Picture</h2><p>The Copyright Office&#8217;s position isn&#8217;t anti-AI. They&#8217;ve explicitly said that using AI as a tool doesn&#8217;t disqualify your work from copyright protection. The question is whether you&#8217;re the author or the AI is.</p><p>This distinction actually makes sense. Copyright exists to incentivize human creativity. It gives creators exclusive rights to their work so they can benefit from it. If machines can generate unlimited content without human creative input, extending copyright to that content doesn&#8217;t serve the original purpose.</p><p>But the practical implications for creators are real. If you&#8217;re building a catalog of AI-generated music, you need to understand that catalog might not be legally yours to protect.</p><div><hr></div><h2>What I&#8217;m Building</h2><p>I&#8217;ve spent the last six months deep in copyright law and AI music. The more I learn, the more I see how much confusion exists between what platforms do, what the law says, and what creators assume.</p><p>ClearVerse is building tools to help creators navigate this landscape. Right now, we&#8217;re focused on copyright risk assessment: helping you understand whether your music might trigger infringement claims before you publish. But the ownership question is just as important. If you can&#8217;t own your work, protecting it becomes a different problem entirely.</p><p><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics. </p><div><hr></div><h2><strong>One Last Thing</strong></h2><p>The AI copyright question isn&#8217;t going away. The Thaler case could get resolved this year. The Copyright Office is still releasing guidance. And millions of creators are generating music without understanding who actually owns it.</p><p>I want to hear from you: <strong>Have you thought about this before? Does it change how you&#8217;ll use AI tools?</strong></p><p>Hit reply and let me know. I read every response.</p><p>Talk soon.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; If you know someone making music with AI who hasn&#8217;t thought about ownership, send this their way.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[What the Suno and Udio Settlements Actually Mean for Creators]]></title><description><![CDATA[Two months ago, the major labels were suing Suno and Udio for copyright infringement. Now two of the three are partnering with them.]]></description><link>https://insights.clearverse.ai/p/what-the-suno-and-udio-settlements</link><guid isPermaLink="false">https://insights.clearverse.ai/p/what-the-suno-and-udio-settlements</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 25 Jan 2026 23:18:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>If that whiplash confused you, you&#8217;re not alone.</p><p>The headlines say &#8220;landmark deals&#8221; and &#8220;victory for the creative community.&#8221; But when you read the actual details, the picture gets complicated. Some things changed. Some things didn&#8217;t. And some questions that actually matter to creators using these tools are still unanswered.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Here&#8217;s what&#8217;s really going on.</p><div><hr></div><h2>What Actually Happened</h2><p>In June 2024, all three major labels (Universal, Sony, Warner) sued both Suno and Udio for copyright infringement. The allegation: these companies trained their AI models on millions of copyrighted songs without permission.</p><p>Then, starting in late October 2025, the settlements started rolling in:</p><p><strong>UMG + Udio</strong> (October 29): Settlement plus licensing deal for a new &#8220;walled garden&#8221; platform launching in 2026.</p><p><strong>WMG + Udio</strong> (November 19): Similar deal. Opt-in licensing for artists.</p><p><strong>WMG + Suno</strong> (November 25): Settlement plus partnership. Suno also acquired Songkick from Warner as part of the deal.</p><p><strong>Still fighting:</strong> Sony hasn&#8217;t settled with either company. UMG&#8217;s lawsuit against Suno is still active. As of late December, Sony filed documents confirming it plans to keep litigating against Udio.</p><p>So the scorecard looks like this:</p><p><strong>Universal:</strong> Settled with Udio &#10003; | Still suing Suno <br><strong>Warner:</strong> Settled with both &#10003; <br><strong>Sony:</strong> Still suing both</p><p>The lawsuits aren&#8217;t over. The legal questions aren&#8217;t answered. Two out of three majors found it cheaper to make deals than to keep fighting. Sony apparently disagrees.</p><div><hr></div><h2>What Changes for Suno and Udio Users</h2><p>Both platforms announced changes coming in 2026. Here&#8217;s what we know:</p><p><strong>Suno (under the Warner deal):</strong></p><ul><li><p>New &#8220;licensed models&#8221; trained only on authorized music (launching later in 2026)</p></li><li><p>Current models will be phased out when new ones launch</p></li><li><p>Free tier users will no longer be able to download audio (only stream and share)</p></li><li><p>Paid users will get download caps with option to pay for more</p></li><li><p>Artists can opt-in to allow their voice, name, likeness in AI generations</p></li></ul><p><strong>Udio (under the UMG and Warner deals):</strong></p><ul><li><p>Pivoting from open generation to a &#8220;fan engagement&#8221; platform</p></li><li><p>New platform launching in 2026, trained on licensed music</p></li><li><p>Becomes a &#8220;walled garden&#8221; where creations can&#8217;t leave the platform</p></li><li><p>Focus shifts to remixing, mashing up, and interacting with licensed music</p></li></ul><p>The key difference: Suno gets to keep doing what it does (generate new music from prompts) but with licensed training data. Udio has to fundamentally change its product into something closer to an interactive streaming service.</p><p>Industry observers are calling Suno&#8217;s deal significantly better. Udio essentially agreed to stop competing in the generative music space.</p><div><hr></div><h2>What Doesn&#8217;t Change</h2><p><strong>The fair use question is still unresolved.</strong> No court has ruled on whether training AI on copyrighted music constitutes fair use. The settlements specifically avoided setting legal precedent. Sony&#8217;s ongoing lawsuits could still produce a ruling, but we&#8217;re likely looking at 2026 or later.</p><p><strong>Your old creations are still in legal limbo.</strong> The settlements cover future models trained on licensed content. They don&#8217;t retroactively bless everything created on current models. If you made something on Suno or Udio in 2024 or 2025 that sounds suspiciously like a copyrighted song, that liability hasn&#8217;t disappeared.</p><p><strong>Indie artists aren&#8217;t covered.</strong> These deals are between the major labels and the AI companies. Independent musicians whose work was allegedly used in training? They&#8217;re still suing. Class action lawsuits were filed in October 2025, and more arrived in December. The indie artist cases are separate from the major label settlements.</p><p><strong>Your AI-generated outputs might still be uncopyrightable.</strong> Remember: the Copyright Office ruled in January 2025 that purely AI-generated works can&#8217;t be copyrighted. These licensing deals don&#8217;t change that. If you prompt Suno and download the result without meaningful human modification, you still don&#8217;t own it.</p><div><hr></div><h2>What This Means for Different Types of Creators</h2><p><strong>If you&#8217;re using Suno to make finished songs:</strong></p><p>You can keep doing this, but the terms are changing. Once the new licensed models launch later in 2026, free tier users won&#8217;t be able to download at all (only stream and share), and paid users will face download caps. Until then, the current models are still operating during the transition period. Your future creations will be trained on licensed music, which reduces (but doesn&#8217;t eliminate) infringement risk. But you still probably can&#8217;t copyright the output unless you add substantial human input.</p><p><strong>If you&#8217;re using Udio:</strong></p><p>The product is changing fundamentally. By 2026, Udio becomes a fan engagement platform, not a generative tool. You won&#8217;t be creating new songs from scratch. You&#8217;ll be interacting with licensed music in a controlled environment. If that&#8217;s not what you signed up for, look elsewhere.</p><p><strong>If you&#8217;re an independent artist worried about your music being used:</strong></p><p>The major label settlements don&#8217;t help you. Your best options are (1) join or follow the indie class action lawsuits, (2) opt-out of AI training through services like Spawning.ai, or (3) document your catalog meticulously in case you need to prove infringement later.</p><p><strong>If you&#8217;re monetizing AI-generated music:</strong></p><p>Be careful. Download restrictions and walled gardens suggest the labels want to control where this content ends up. Deezer estimates <a href="https://musically.com/2025/11/12/50000-ai-music-tracks-are-now-uploaded-to-deezer-every-day/">50,000 AI-generated songs hit streaming services daily</a>. The majors are clearly trying to stop that flood. Expect distribution platforms to tighten their policies.</p><div><hr></div><h2>The Uncomfortable Questions Nobody&#8217;s Answering</h2><p><strong>Where does the money go?</strong></p><p>The deals promise &#8220;compensation&#8221; for artists and songwriters, but nobody&#8217;s disclosed the actual terms. Irving Azoff, legendary artist manager and founder of the Music Artists Coalition, <a href="https://www.musicartistscoalition.com/news/mac-umg-udio-partnership">called it out immediately</a>: &#8220;We&#8217;ve seen this before &#8212; everyone talks about &#8216;partnership,&#8217; but artists end up on the sidelines with scraps.&#8221;</p><p>The announcements emphasize opt-in. But opt-in to what, exactly? What&#8217;s the royalty rate? How is usage tracked? How do you even know if your work is being used? None of this has been disclosed.</p><p><strong>What about the music already created?</strong></p><p>Suno has over 100 million users. Millions of songs have been generated. The settlements say current models will be &#8220;deprecated&#8221; in 2026. But those creations don&#8217;t disappear. What&#8217;s their legal status? The settlements are silent.</p><p><strong>Why did Warner and Universal settle but Sony didn&#8217;t?</strong></p><p>Sony filed documents in December 2025 confirming it&#8217;s continuing litigation against both companies. That&#8217;s interesting. Either Sony thinks it can get a better deal, or it genuinely wants a court ruling on fair use. If Sony wins, it could reshape the entire AI music landscape. If it loses, the labels who settled early might look smart.</p><p><strong>Are these deals actually enforceable?</strong></p><p>Training AI on &#8220;only licensed music&#8221; sounds clean. But how do you verify it? The original lawsuits alleged Suno and Udio scraped songs from YouTube using stream-ripping techniques. How do the labels know the 2026 models won&#8217;t still have that data baked in? Fingerprinting and filtering were mentioned. Whether that&#8217;s sufficient remains to be seen.</p><div><hr></div><h2>What I Think Is Really Happening</h2><p>Reading between the lines, here&#8217;s my take:</p><p>The major labels realized litigation was expensive and uncertain. Fair use cases are unpredictable. Meanwhile, Suno just <a href="https://techcrunch.com/2025/11/25/warner-music-signs-deal-with-ai-music-startup-suno-settles-lawsuit/">raised $250 million at a $2.45 billion valuation</a>. These AI companies aren&#8217;t going away.</p><p>So the labels did what labels do: they found a way to get paid. Licensing deals mean revenue. Partnerships mean influence over how the platforms develop. Walled gardens mean the output doesn&#8217;t compete directly with their catalogs on Spotify.</p><p>Is this good for artists? Maybe. The opt-in model gives creators some control. But the financial terms are opaque, and history suggests the middlemen (labels, platforms) capture most of the value.</p><p>Is this good for users? Mixed. Suno keeps working. Udio becomes something different. Both get more expensive and more restricted.</p><p>Is this good for the broader legal question of AI and copyright? No. These settlements kicked the can down the road. We still don&#8217;t know if training on copyrighted music is fair use. We still don&#8217;t know how courts will handle AI-generated outputs that resemble copyrighted works. The only way we get answers is if Sony pushes its cases to a ruling, or if the indie artist class actions succeed.</p><div><hr></div><h2>What to Watch in 2026</h2><p>Here&#8217;s what I&#8217;m tracking:</p><p><strong>Sony&#8217;s litigation.</strong> If they push to a ruling, we finally get legal clarity. If they settle too, the fair use question stays open indefinitely.</p><p><strong>The indie artist class actions.</strong> These cases are specifically about whether AI-generated music creates &#8220;competitive, radio-quality substitutes&#8221; that harm the market for human-made music. That&#8217;s a different argument than the major label cases, and it could produce different results.</p><p><strong>How opt-in actually works.</strong> When Warner and Universal artists start seeing (or not seeing) AI-related payments on their statements, we&#8217;ll know whether &#8220;compensation&#8221; is real or marketing.</p><p><strong>Distribution platform policies.</strong> Spotify, Apple Music, and others will have to decide whether to accept music made on these platforms. Expect tightening.</p><p><strong>The Copyright Office.</strong> Part 3 of their AI report came out in May 2025 and questioned whether AI training on music qualifies as fair use. More guidance could be coming.</p><div><hr></div><h2>What I&#8217;m Building</h2><p>This is exactly why ClearVerse exists.</p><p>The settlements don&#8217;t solve the fundamental problem: creators have no way to assess their actual legal risk. Not the platform&#8217;s risk. Not the label&#8217;s risk. Yours.</p><p>You need to know: Does this track I made sound enough like a copyrighted song to get me sued? Not flagged by Content ID. Sued.</p><p>That&#8217;s the gap we&#8217;re filling. Technology that scores copyright risk based on how courts actually rule, not just how similar something sounds.</p><p><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics. </p><div><hr></div><h2>One Last Thing</h2><p>If you&#8217;re using Suno or Udio, I want to hear from you.</p><p>Are you worried about these changes? Do you understand what you can and can&#8217;t do with your creations? Are you getting any clarity from the platforms themselves?</p><p>Hit reply and tell me: <strong>What&#8217;s your biggest question about AI music right now?</strong></p><p>I read every response. Next week I&#8217;m planning to tackle whatever comes up most.</p><p>Talk soon.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; If this was useful, forward it to someone else trying to figure out what these deals actually mean.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The 5 Music Copyright Myths AI Just Made Worse]]></title><description><![CDATA[AI didn't create music copyright confusion. It amplified it.]]></description><link>https://insights.clearverse.ai/p/the-5-music-copyright-myths-ai-just</link><guid isPermaLink="false">https://insights.clearverse.ai/p/the-5-music-copyright-myths-ai-just</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Sun, 18 Jan 2026 19:10:26 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>YouTube processed 2.2 billion copyright claims in 2024. That&#8217;s roughly 70 claims per second, running around the clock.</p><p>Behind every one of those claims is a creator staring at a notification, trying to figure out: <em>Am I in legal trouble? Should I dispute this? What actually happened?</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Most of them will never get a straight answer. The systems designed to &#8220;protect&#8221; copyright don&#8217;t explain copyright. They just enforce policies that have almost nothing to do with the law.</p><p>I&#8217;ve spent the last six months deep in the weeds of music copyright, building technology that translates similarity detection into actual legal risk. The deeper I&#8217;ve gotten, the more I&#8217;ve realized that most of what creators believe about copyright is just... wrong. And AI is making it worse.</p><p>Here are the five myths I keep running into.</p><div><hr></div><h2><strong>Myth #1: &#8220;Similar&#8221; Means &#8220;Stolen&#8221;</strong></h2><p>When Content ID flags your video, it&#8217;s not saying you committed copyright infringement. It&#8217;s saying something in your upload (audio, video, or even a melody) matches something in their database. That&#8217;s it.</p><p>Content ID doesn&#8217;t check whether you have a license. It doesn&#8217;t evaluate fair use. It doesn&#8217;t ask whether the similar portion is legally &#8220;substantial&#8221; or whether an average listener would even recognize the similarity.</p><p>Courts look at all of that. Platforms look at none of it.</p><p>Here&#8217;s a situation I see constantly: You license a drum loop from Splice. You use it legally. But 500 other creators also licensed that same loop. Content ID flags all of you against each other, because it can&#8217;t tell the difference between &#8220;this sounds similar&#8221; and &#8220;this is infringement.&#8221;</p><p>You get a claim on content you have every legal right to use. The platform treats you like an infringer. And you&#8217;re left wondering if you did something wrong.</p><p>You didn&#8217;t. The system just can&#8217;t tell the difference.</p><div><hr></div><h2><strong>Myth #2: &#8220;Under 50% Similarity Is Safe&#8221;</strong></h2><p>I hear this one all the time. &#8220;I&#8217;m only at 30% similarity, so I should be fine.&#8221;</p><p>There is no percentage threshold in copyright law. Not 50%. Not 30%. Not 10%.</p><p>The &#8220;70-30 rule&#8221; and &#8220;6-second rule&#8221; you&#8217;ve heard about? Those are platform policies. Internal guidelines that YouTube, TikTok, and Instagram use to manage their systems. They have nothing to do with what would happen in a courtroom.</p><p>Courts care about different questions entirely.</p><p>Did you copy the &#8220;heart&#8221; of the work? Two seconds of a hook that everyone recognizes can be more legally significant than two minutes of generic background music. Would an average listener recognize your track as coming from the original? Did you copy something that&#8217;s actually protectable, or just common musical elements that nobody owns?</p><p>An AI tool can tell you &#8220;this is 47% similar.&#8221; It cannot tell you whether that 47% includes the one melodic phrase that would get you sued.</p><p>Here&#8217;s where AI makes this worse: generative music tools can create infinite variations that hover right around similarity thresholds. But &#8220;similar enough to avoid detection&#8221; is not the same as &#8220;legally safe.&#8221; You can have zero Content ID claims and massive legal exposure if you copied the wrong four bars.</p><div><hr></div><h2><strong>Myth #3: &#8220;If I Can&#8217;t Hear It, It&#8217;s Not Infringement&#8221;</strong></h2><p>Your ears are not a legal instrument.</p><p>In the <em>Blurred Lines</em> case, the jury found infringement even though the songs don&#8217;t share a single identical melody line. The similarity was in the &#8220;feel,&#8221; the groove, the combination of elements that created a recognizable vibe. I&#8217;m still not entirely sure I agree with that verdict. A lot of people in the industry don&#8217;t. But it&#8217;s the precedent we&#8217;re working with.</p><p>The <em>Dark Horse</em> case went the other direction. A jury initially found that Katy Perry&#8217;s song infringed a Christian rap track based on an 8-note repeating pattern. But an appeals court overturned it, ruling the pattern was too common to be copyrightable. Same type of claim, opposite outcome.</p><p>What these cases show is that copyright analysis is multidimensional. Courts look at melody, harmony, rhythm, structure, timbre, lyrics. They don&#8217;t weight these equally. Melody is generally more protected than rhythm. A match in one dimension can be legally significant even if everything else is completely different.</p><p>You might listen to your track and think &#8220;this sounds nothing like the original.&#8221; But if you inadvertently copied a melodic contour or a harmonic progression, you might have legal exposure you literally can&#8217;t hear.</p><p>That&#8217;s not paranoia. It&#8217;s just how the law works. And no detection tool on the market explains which dimensions matter in your specific case.</p><div><hr></div><h2><strong>Myth #4: &#8220;AI-Generated Music Is Safe to Use&#8221;</strong></h2><p>This one&#8217;s for creators using AI music tools, and it&#8217;s more complicated than most people realize.</p><p><strong>The training question is still unresolved.</strong> In 2024, the major labels sued Suno and Udio for copyright infringement, alleging that training on copyrighted music without permission was itself illegal. Since then, some cases have settled. Warner Music Group is now partnering with Suno. Universal settled with Udio. But Sony&#8217;s case against both companies is still active, and no court has definitively ruled on whether training AI on copyrighted music constitutes fair use. The settlements avoided setting precedent. The legal question remains open.</p><p><strong>But here&#8217;s what most creators don&#8217;t realize:</strong> Even if AI training is eventually ruled legal, your AI-generated output might not be copyrightable at all.</p><p>In January 2025, the U.S. Copyright Office ruled that purely AI-generated works cannot receive copyright protection. A federal appeals court affirmed this in March. The logic: copyright exists to protect human creativity, and works generated entirely by AI lack the required human authorship.</p><p>What does this mean practically? Music you create by typing a prompt into Suno or Udio and hitting generate? That&#8217;s public domain. Anyone can use it, remix it, or monetize it. You have no legal protection.</p><p>The only way to own what you create is to add meaningful human involvement. Edit the melodies. Write your own lyrics. Add live instrumentation. Layer your own production. The Copyright Office has said AI-<em>assisted</em> works can qualify for protection if the human contribution is substantial enough, but you&#8217;ll need to document your creative process if you ever want to register or defend it.</p><p>So when creators assume that because an AI tool exists, the output must be legal to use and theirs to own, that&#8217;s not how any of this works.</p><p>Pay attention to how these cases develop. Don&#8217;t assume &#8220;AI-generated&#8221; means &#8220;copyright-free.&#8221; And if you want to actually own your music, make sure you&#8217;re doing more than prompting.</p><div><hr></div><h2><strong>Myth #5: &#8220;Copyright Detection Tools Know the Law&#8221;</strong></h2><p>This is the myth that made me start building ClearVerse.</p><p>Every major detection company (Audible Magic, Pex, YouTube&#8217;s Content ID) does the same thing: measure similarity. They compare audio fingerprints, identify matches, and return a number.</p><p>That number tells you nothing about legal risk.</p><p>This one surprised me when I found it: 65% of Content ID disputes succeed. Most creators don&#8217;t dispute because they&#8217;re scared of getting a strike. But the majority of claims, when actually challenged, get resolved in the creator&#8217;s favor.</p><p>Why? Because detection and law are measuring different things.</p><p>Detection asks: <em>Does this sound similar?</em></p><p>Law asks: <em>Is this similarity the kind that matters?</em></p><p>A detection tool can&#8217;t tell you whether the similar portion is legally &#8220;substantial.&#8221; It can&#8217;t evaluate fair use. It can&#8217;t tell you if the element you matched is even copyrightable, or what a court would actually do with your case.</p><p>What creators need isn&#8217;t just detection. It&#8217;s interpretation. Not just &#8220;47% similar,&#8221; but &#8220;here&#8217;s what that similarity means given how courts have ruled on cases like this.&#8221;</p><p>That gap is why I started building what I&#8217;m building.</p><div><hr></div><h2><strong>What This All Means</strong></h2><p>The copyright system wasn&#8217;t designed for a world where anyone can generate infinite musical variations with AI, where platforms process billions of claims automatically, where detection technology is completely divorced from legal analysis, and where creators bear all the risk without any tools to assess it.</p><p>The result is a system that optimizes for one thing: don&#8217;t get the platform sued.</p><p>That&#8217;s rational from YouTube&#8217;s perspective. It&#8217;s terrible for creators.</p><p>You&#8217;re navigating a minefield where claims don&#8217;t mean you broke the law, similarity scores don&#8217;t predict legal outcomes, platforms have no incentive to explain the difference, and the only people who really understand the nuances charge hundreds of dollars an hour.</p><div><hr></div><h2><strong>What I&#8217;m Building</strong></h2><p>I started ClearVerse because I kept seeing the same pattern: sophisticated detection, zero legal context.</p><p>We&#8217;re building something different. Technology that scores copyright risk based on how courts actually rule, not just how similar something sounds.</p><p>And yes, ClearVerse uses AI. But there&#8217;s a difference between AI that generates content without understanding legal risk and AI that helps you understand risk before you create. The same technology that&#8217;s flooding the market with potential copyright landmines is also the only thing capable of analyzing legal patterns at scale. It comes down to what you point it at.</p><p>We&#8217;re using AI to do what humans can&#8217;t do fast enough: cross-reference your content against how courts have actually ruled on similarity, weigh which musical elements carry legal weight, and translate that into a risk score you can act on.</p><p>The goal is to give creators the intelligence they need to make informed decisions <em>before</em> they upload, not after a claim hits their channel.</p><p><strong>We&#8217;re opening early access soon.</strong> Sign up at clearverse.ai to be first in line.</p><p><strong>Want a walkthrough? </strong>If you&#8217;re a label, agency, or high-volume creator, I&#8217;d love to show you what we&#8217;re building. Just reply to this email or DM me on LinkedIn.</p><p><strong>Or just subscribe.</strong> I&#8217;ll be writing more about AI, copyright, and creator economics. Next week I&#8217;m looking at what the Suno and Udio settlements actually mean for creators, and what&#8217;s still unresolved.</p><div><hr></div><h2><strong>One Last Thing</strong></h2><p>If you&#8217;ve gotten this far, you probably have opinions. Maybe you&#8217;ve dealt with bogus claims. Maybe you&#8217;ve lost revenue to Content ID. Maybe you think I got something wrong.</p><p>I want to hear it.</p><p>Hit reply and tell me: <strong>What&#8217;s your biggest copyright frustration right now?</strong></p><p>I read every response. Some of the best article ideas come from questions I hadn&#8217;t thought to ask.</p><p>Talk soon.</p><p>&#8212; Christian</p><p><em>P.S. &#8212; Know a creator dealing with copyright headaches? Send this their way.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ClearVerse Insights! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Coming soon]]></title><description><![CDATA[This is ClearVerse Insights.]]></description><link>https://insights.clearverse.ai/p/coming-soon</link><guid isPermaLink="false">https://insights.clearverse.ai/p/coming-soon</guid><dc:creator><![CDATA[Christian Loarca]]></dc:creator><pubDate>Thu, 15 Jan 2026 01:57:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!7oO6!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa661256d-96b2-457f-b2e4-151fb950b74d_1024x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>This is ClearVerse Insights.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://insights.clearverse.ai/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://insights.clearverse.ai/subscribe?"><span>Subscribe now</span></a></p>]]></content:encoded></item></channel></rss>