The Capitol LedgerEvery move in Congress, on the record
HomeBillsRecordsLedger AI

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

AboutFAQFeedbackTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

The projectAboutFAQFeedback
LegalTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

All bills
H.R. 9679·119th Congress·Introduced Jul 14, 2026

REDACT Act

IntroducedCrime and Law EnforcementSubstantive
View bill text
Sponsor
Rep. Jayapal, Pramila [D-WA-7]
Committees
Judiciary Committee (primary)
Last action
Jul 14, 2026

Bottom line

This bill creates a new legal pathway for victims to sue the U.S. government for significant damages if their private information is negligently disclosed during the release of documents under the Epstein Files Transparency Act.

What it actually does

This bill, known as the REDACT Act, amends the existing Epstein Files Transparency Act to establish a private cause of action against the United States government. It allows individuals whose personally identifiable information or sensitive personal/medical files are improperly disclosed by federal officers, employees, or agents under the Epstein Files Transparency Act to sue for damages. The bill waives sovereign immunity and sets statutory damages at $50,000 per instance of violation or the amount of compensatory damages, whichever is greater.

Proponents argue

Supporters argue that this bill provides essential accountability and a robust remedy for victims whose privacy is violated during the release of sensitive government documents. They contend it ensures the government takes its redaction responsibilities seriously, acting as a strong deterrent against negligence and offering meaningful recourse for re-victimization through disclosure.

Opponents contend

Critics might argue that while privacy protection is important, the statutory damages of $50,000 per instance are excessive and could lead to substantial financial liability for the government, potentially chilling the release of documents or creating an overly litigious environment. They may also raise concerns about the interpretation of 'instance' and the potential for multiple claims from a single disclosure event.

The bill is very short and easy to read, allowing ample time for thorough evaluation.

Section 2, subsection (d)

Establishes Private Cause of Action for Privacy Violations under Epstein Files Transparency Act

prominently featuredstraightforward

This provision amends the existing Epstein Files Transparency Act to allow individuals whose personally identifiable information, personal files, or medical files are improperly disclosed by the U.S. government under that Act to sue the government. It defines what constitutes a violation and sets out the types of relief available, including statutory damages of $50,000 per instance or actual compensatory damages, attorney's fees, and injunctive relief. The bill explicitly waives sovereign immunity for these actions and sets a 5-year statute of limitations.

GroupImpactMechanismScale
GroupVictims whose PII or sensitive files are disclosed under the Epstein Files Transparency ActImpactEmpowers them to seek legal redress and financial compensation for privacy violations.MechanismCreates a new civil cause of action against the U.S. government with specific damages and remedies.ScalePotentially significant for individuals, providing a direct legal avenue for compensation and accountability.
GroupU.S. Government (federal departments/agencies and their employees)ImpactIncreased legal and financial liability; heightened pressure to ensure meticulous redaction of sensitive information.MechanismWaiver of sovereign immunity and establishment of statutory damages for privacy breaches.ScalePotentially significant financial exposure depending on the number of violations and instances, and increased administrative burden for legal defense.

Supporters argue

Supporters argue this provision is essential for protecting the privacy and dignity of victims, ensuring that the government is held fully accountable for any failures in redacting sensitive information. The statutory damages provide a strong incentive for compliance and offer meaningful recourse to those harmed, preventing re-victimization.

Critics contend

Critics might contend that while privacy protection is important, the $50,000 per instance statutory damage could lead to excessive payouts, potentially making the government overly cautious in releasing documents or creating a significant financial burden on taxpayers. They may also argue that existing administrative remedies are sufficient.

Tradeoffs

The bill balances the public's right to transparency regarding the Epstein files with the victims' right to privacy. It aims to prevent re-victimization through disclosure, but potentially at the cost of increased government liability and administrative burden, which could impact the speed or scope of future document releases.

FOUND

Defines 'instance' as 'each discrete act constituting a violation' and 'violation of this section' as a failure to withhold or redact personally identifiable information or sensitive files that would constitute a 'clearly unwarranted invasion of personal privacy' under the Epstein Files Transparency Act.

Section 2, subsection (d)(1)(A) and (B)

Why it matters:It is standard legislative practice to define terms within a bill. However, the specific wording of 'each discrete act' could be subject to broad interpretation, significantly impacting the financial implications.

Case for: Proponents would argue these definitions provide necessary clarity for courts to apply the law consistently and ensure that every distinct privacy breach is actionable, not just a single overall disclosure event, thereby maximizing victim protection.

Case against: Critics might argue that the definition of 'instance' is vague enough to allow for multiple claims from a single document release, potentially inflating liability for the government. The 'clearly unwarranted invasion of personal privacy' standard is also subject to judicial interpretation, which could lead to inconsistent application.

Estimated impact: Could significantly multiply the financial liability for the government if a single document release contains multiple distinct privacy breaches for one or more individuals, potentially leading to much higher total damages than a single per-document or per-victim claim.

FOUND

States that the new private cause of action applies to any violation occurring on or after November 19, 2025.

Section 2, subsection (d)(6)

Why it matters:Setting an effective date is standard legislative practice. This specific date provides a prospective application for the new cause of action.

Case for: Proponents would argue this provides a clear start date for the new legal protections, allowing federal agencies time to adjust their procedures and ensure compliance if the bill passes well in advance of this date.

Case against: Critics might argue that if the bill passes significantly after this date, it could create retroactive liability, or if it passes before, it delays crucial protections for victims who might suffer violations between the bill's enactment and the specified date.

Estimated impact: Determines the window of time for which violations are actionable, potentially limiting immediate claims if the bill passes before the specified date, or creating retroactive liability if it passes after.

About this analysis. AI-Generated from the official bill text and available committee reports. Gaps in available data are noted explicitly. Verify important details with the official Congress.gov record.

On this page

  • Executive summary
  • Key provisions
  • Buried treasure
  • Follow the money
  • Critical analysis
  • Questions to ask
Ask Ledger AI about this