Twelve states had moved on synthetic content and AI-generated likeness before the federal government produced a viable bill. The NO FAKES Act changed that calculus on or around June 18, 2026, when the Senate Judiciary Committee reportedly advanced it unanimously, according to a statement from the Recording Industry Association of America. One floor vote now separates the patchwork from a potential national standard. The Senate Judiciary Committee’s official record hasn’t been confirmed independently; the RIAA’s statement is the sourced basis for this report’s procedural facts.
This piece answers a different question than the committee vote itself. The daily brief covers what happened procedurally. This covers what it means for compliance teams that have already spent real resources building state-specific consent frameworks, and whether that work holds, scales, or needs to be redesigned.
Section 1: What Unanimous Committee Advancement Actually Means
A unanimous committee vote is not enactment. The distinction matters.
Committee advancement means the bill clears its first substantive legislative hurdle – a vote by the Senate Judiciary Committee’s members to send it to the Senate floor. No recorded opposition at this stage is notable for legislation that touches both the entertainment industry and the technology sector, which often have competing interests. It suggests the bill’s sponsors resolved enough internal committee concerns to avoid a fractured vote. It doesn’t mean the full Senate agrees.
The bill’s next step is a full Senate floor vote. No date has been confirmed in this reporting cycle. Floor scheduling is controlled by the Senate majority leader and depends on competing legislative priorities, appropriations, nominations, and other floor business can delay even widely supported bills for weeks or months. Don’t expect a confirmed floor date to emerge quickly.
The realistic timeline framing: committee passage is a necessary condition for enactment, not a sufficient one. The bill’s bipartisan structure, documented in prior pipeline coverage of the safe harbor stakeholder fight, reduces the risk of a floor amendment fight on political lines. But the click-wrap concern flagged by Public Knowledge could surface as a floor amendment, which would send the bill back through a conference process before it reaches the president’s desk.
Section 2: The Federal-State Stack, What’s Already Active
The compliance layer that exists before NO FAKES passes isn’t theoretical.
New York’s Synthetic Performers law became active on June 9, 2026. It covers digital replicas of performers, voice, likeness, and visual image, and requires explicit written consent before a digital replica can be created or used commercially. Enforcement sits with the New York Attorney General. For companies with New York users or New York operations, this is current law, not pending legislation.
Connecticut’s CART Act established parallel consent requirements with its own enforcement architecture. State attorney general activity in this space has accelerated over the past 90 days, based on prior hub coverage of the state AG enforcement wave. The emerging pattern: states aren’t waiting for federal preemption. They’re building enforcement infrastructure on the assumption that federal action, if it comes, will define a floor, not a ceiling.
The compliance reality for AI voice and likeness product teams right now:
- New York requires written consent before digital replica creation, active June 9
- Connecticut CART Act establishes parallel consent requirements
- State AG enforcement actions are creating case law that will shape interpretation regardless of federal action
- The EU’s Article 50 transparency requirements for synthetic content take effect August 2, 2026, adding an international layer for any product reaching EU users
That’s the stack before NO FAKES adds a federal layer.
Synthetic Content Compliance Stack, Active and Pending (June 2026)
| Jurisdiction | Law | Status | Effective Date | Scope |
|---|---|---|---|---|
| New York | Synthetic Performers Act | Active | June 9, 2026 | Digital replicas, voice, likeness, visual image |
| Connecticut | CART Act | Active | 2026 | AI-generated synthetic content consent |
| United States (Federal) | NO FAKES Act | Pending Senate floor vote | TBD | Federal IP right, voice and visual likeness |
| EU | AI Act Article 50 | Effective | August 2, 2026 | Synthetic content disclosure / transparency |
Pre-Enactment Compliance Preparation Checklist
- Review click-wrap and ToS consent language for voice/likeness acquisition scope and duration
- Map current state law exposure (NY, CT, and pending state legislation) against your user base
- Confirm EU Article 50 compliance path for EU-facing products, deadline August 2, 2026
- Set up Senate floor schedule monitoring (Senate Judiciary Committee official press record)
- Engage legal counsel for bill text review upon Senate floor passage
| Jurisdiction | Law / Requirement | Status | Scope |
|---|---|---|---|
| New York | Synthetic Performers Act | Active (June 9, 2026) | Digital replicas of voice, likeness, visual image |
| Connecticut | CART Act | Active | AI-generated synthetic content consent |
| United States (Federal) | NO FAKES Act | Pending floor vote | Federal IP right, voice and visual likeness |
| EU | Article 50, EU AI Act | Effective August 2, 2026 | Synthetic content disclosure / transparency |
Sources: Prior hub coverage (NY Synthetic Performers, Connecticut CART Act, EU AI Act Article 50 deadline briefs). EU Article 50 deadline confirmed in prior TJS EU AI Act compliance calendar brief.
Section 3: Where the NO FAKES Act Changes the Calculus
Federal law does things state law can’t.
A federal right of publicity creates a national cause of action, meaning a rights holder can sue in federal court regardless of which state the violation occurred in or where the defendant is incorporated. State laws require plaintiffs to establish jurisdiction and navigate different statutory standards across different courts. Federal law removes that friction.
Federal preemption is the more consequential possibility. If the NO FAKES Act includes preemption language, meaning it explicitly supersedes conflicting state laws, it could replace the multi-state compliance architecture companies have been building with a single federal standard. That’s not necessarily simpler. If the federal standard is lower than New York’s or Connecticut’s requirements, companies that built to the stricter state standard would need to re-evaluate whether to maintain the higher bar (for reputational or risk management reasons) or simplify to the federal floor. If the federal standard is higher, companies that built to state minimums will need to upgrade.
The prior hub brief on the federal-vs.-state AI showdown documented the preemption debate in detail. The NO FAKES Act’s preemption scope hasn’t been confirmed in this package, that’s a legal detail that requires bill text review. What can be said with confidence: federal enactment changes the litigation landscape immediately, regardless of preemption scope, because it creates a parallel federal claim alongside state claims.
Section 4: The Click-Wrap Problem and the Safe Harbor Fight
This is where the bill’s internal tension lives.
Public Knowledge warns the bill as advanced may lack sufficient protections against “click-wrap” contracts, the standard terms of service agreements that users accept when downloading apps. According to Public Knowledge’s analysis, the bill as written could allow software developers to acquire rights over a user’s voice or likeness for up to 10 years through those standard app agreements. This is Public Knowledge’s advocacy position and characterization of the bill’s language; the 10-year figure hasn’t been verified against bill text.
The concern is structural. Click-wrap consent is how most AI voice products currently obtain user permission to record and process voice samples. If the bill permits that mechanism to satisfy its consent requirements, the protection it offers is only as strong as the user’s ability to read and understand 50-page app terms of service, which Public Knowledge argues is not meaningful consent.
The prior hub brief on the NO FAKES Act safe harbor debate documented the broader stakeholder fracture between platform companies (who want a robust safe harbor for user-generated content) and individual creators (who want narrower liability shields that protect their likeness rights against larger platforms). The click-wrap concern sits within that broader fight: it’s the user-versus-developer dimension of the same structural tension.
Any resolution to the click-wrap gap now requires a floor amendment or post-enactment regulatory guidance, procedurally harder and slower than a committee markup fix.
Unanswered Questions
- Does the NO FAKES Act include preemption language that supersedes state synthetic content laws, or does it establish a federal floor alongside state requirements?
- Does the bill's consent mechanism specifically address click-wrap agreements, or does the Public Knowledge gap require a floor amendment to close?
- What audit trail or documentation standard does the federal right of publicity create for companies claiming user consent?
What to Watch
Section 5: What Compliance Teams Must Do Now
The bill isn’t law yet. Action taken now is risk preparation, not legal compliance. Organizations should consult legal counsel before making changes to contract language or consent workflows based on bill language that has not yet been enacted.
That said, preparation isn’t premature.
Review existing click-wrap and ToS consent language for AI voice and likeness products. Public Knowledge’s analysis, however it’s ultimately validated against bill text, identifies the specific mechanism most likely to face challenge: standard app download consent for voice/likeness acquisition. If your current ToS relies on click-wrap for this consent, understanding its terms and duration is useful regardless of how the federal law resolves.
Map your current state exposure before the federal layer arrives. Which state consent requirements apply to your user base? New York and Connecticut are active. Other states have pending legislation in similar territory. Knowing your current exposure tells you what the federal law would change, and what it wouldn’t, in states with stronger protections.
Track the Senate floor schedule through the Senate majority leader’s office and the Senate Judiciary Committee’s official press record. The vote date isn’t confirmed; floor scheduling can shift on short notice. Compliance teams should have a monitoring mechanism rather than a fixed calendar entry.
Assess EU Article 50 obligations separately. If your AI voice or likeness product reaches EU users, Article 50 disclosure requirements take effect August 2, 2026 – well before any US federal enactment could follow. The EU and federal tracks don’t synchronize; both require independent compliance analysis.
The real question is whether the legal team reviewing this bill post-enactment finds it to be a floor, a ceiling, or a different standard than the state frameworks they’ve already built around. The answer to that question will determine whether the compliance work from the first half of 2026 ports cleanly to a federal standard or requires a rebuild. Companies that understand their current state stack before the floor vote will be positioned to answer that question quickly when enactment happens, or when it doesn’t.