# Freedom To Fix Act

**Status:** Draft. Targeted for introduction early in the next Congress, alongside the 2027 §1201 triennial cycle.

**Summary.** The Freedom To Fix Act amends 17 U.S.C. §1201 by adding a new subsection (l) that creates a permanent statutory exemption for *diagnosis, maintenance, cybersecurity research, or repair* of "digital electronic equipment" — broadly defined as any product dependent on attached or embedded digital electronics to function. The exemption covers all three of §1201's prohibitions: the access-circumvention ban (§1201(a)(1)(A)), the trafficking-in-access-tools ban (§1201(a)(2)), and the trafficking-in-copy-tools ban (§1201(b)(1)).

**Relationship to the Register's 2017 recommendation.** The bill implements the substance of the U.S. Copyright Office's 2017 recommendation to Congress for a permanent §1201(a) repair exemption (see `1201/Policy Studies/Section-1201-of-Title-17-2017/Full-Report.txt` at PDF pp. 88–96; synthesis in `1201/Claude Reports/2026-05-24__Office-Policy-Reports-and-2027-Plan-Implications.md`). Two notable differences from the Register's proposal:

- **Scope.** The Register suggested anchoring the definition of "maintenance" and "repair" in 17 U.S.C. §117(d) (servicing or restoring a machine "in accordance with its original specifications"). The Freedom To Fix Act instead defines the covered population by *equipment* — any product with embedded digital electronics — and leaves "diagnosis, maintenance, cybersecurity research, [and] repair" undefined for case-by-case application. The Register's preferred device-agnostic framing (2017 Study at p. 94: "recommends against limiting an exemption to specific technologies or devices") aligns with the bill's broad equipment definition.
- **Cybersecurity research.** The Register recommended targeted reform of §1201(j) but did not fold cybersecurity research into the proposed repair exemption. The bill combines them — circumvention for cybersecurity research is permitted alongside repair under the same subsection.

**Relationship to the 2027 triennial filings.** If enacted, the Freedom To Fix Act would render the 2027 multi-class filings (see `2027-repair-proposals.html`) substantively unnecessary: the bill's permanent exemption would cover every repair use case those filings target. Until enactment, the triennial rulemaking is the only available avenue — and every triennial win builds the political record for the bill's passage.

---

## Bill text (draft)

> **Note (editorial):** The text below resolves two clerical issues in the source draft — (a) SECTION 1's short title now reads "Freedom To Fix Act" to match the act's preamble; (b) Section 2's heading now reads "CYBERSECURITY RESEARCH" to match the body of subsection (l), which throughout refers to "cybersecurity research" rather than "cybersecurity" alone. Substantive provisions are unchanged.

To amend title 17, United States Code, to provide for the diagnosis, maintenance, cybersecurity, and repair of certain digital electronic equipment.

### IN THE HOUSE OF REPRESENTATIVES

`TKTK`, 2026

`____` introduced the following bill; which was referred to the Committee on the Judiciary

---

### A BILL

To amend title 17, United States Code, to provide for the diagnosis, maintenance, cybersecurity, and repair of certain digital electronic equipment.

*Be it enacted by the Senate and House of Representatives of the United States of America in Congress assembled,*

#### SECTION 1. SHORT TITLE.

This Act may be cited as the "**Freedom To Fix Act**".

#### SEC. 2. DIAGNOSIS, MAINTENANCE, CYBERSECURITY RESEARCH, AND REPAIR OF CERTAIN DIGITAL ELECTRONIC EQUIPMENT.

Section 1201 of title 17, United States Code, is amended by adding at the end the following new subsection:

> "(l) **Diagnosis, Maintenance, Cybersecurity Research, And Repair Of Digital Electronic Equipment.**—
>
> "(1) Notwithstanding the provisions of subsection (a)(1)(A), it is not a violation of that subsection for a person, for the purpose of the diagnosis, maintenance, cybersecurity research, or repair of digital electronic equipment, to circumvent a technological measure that effectively controls access to a work protected under this title.
>
> "(2) Notwithstanding the provisions of subsection (a)(2), it is not a violation of that subsection for a person, for the purpose of the diagnosis, maintenance, cybersecurity research, or repair of digital electronic equipment, to manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof described in that subsection.
>
> "(3) Notwithstanding the provisions of subsection (b)(1), it is not a violation of that subsection for a person, for the purpose of the diagnosis, maintenance, cybersecurity research, or repair of digital electronic equipment, to manufacture, import, offer to the public, provide, or otherwise traffic in any technology, product, service, device, component, or part thereof described in that subsection.
>
> "(4) For the purposes of this subsection, the term '**digital electronic equipment**' means any product dependent, in whole or in part, upon attached or embedded digital electronics to function."

---

## Open items in this draft

The following items remain to be filled in before introduction:

- **Introduction date** — placeholder `TKTK, 2026` in the "IN THE HOUSE OF REPRESENTATIVES" line.
- **Lead sponsor** — placeholder `____` in the "introduced the following bill" line.
- **Cosponsors** — to be added as a separate line below the lead sponsor.
- **Committee referral** — currently "Committee on the Judiciary," correct for House. A Senate companion would refer to the Committee on the Judiciary as well.
- **Effective date** — the bill is silent on effective date; default is enactment date. May want to consider whether to specify (e.g., "shall take effect on the date that is 30 days after the date of enactment").
- **Conforming amendments** — none currently included. Worth checking with counsel whether §1201's table of contents or related cross-references need updating.

## Issues that may surface during markup

These are predictable lines of attack from the historical §1201 record (see `1201/Policy Studies/Section-1201-of-Title-17-2017/Comments/` for the public-comment archive). Sponsors / coalition should be ready:

- **"Repair" vs. "modification" line-drawing.** The 2017 Register's Study supported a permanent exemption for repair / maintenance / diagnosis but expressly *did not* recommend extending it to "modification" or "tinkering" (PDF p. 89). Some opponents will argue the bill enables modification under cover of "repair." Counter: the bill is structured around the *purpose* test ("for the purpose of … repair") and does not authorize modifications that change the device's specifications. The §117(d) "original specifications" framing the Register endorsed could be incorporated as a clarifying definition if the markup demands it.
- **Anti-trafficking provisions ((a)(2) and (b)(1)).** Including these — as the bill does — is broader than the Register's 2017 recommendation, which focused on the access prohibition in (a)(1)(A). Rightsholders will argue that allowing trafficking in circumvention tools creates piracy risk. Counter: the bill ties trafficking to *purpose* (repair), and a tool sold "for the purpose of … repair" is distinguishable from a general-purpose anti-piracy tool. Coalition counsel should have ready language on how the purpose-test would apply in litigation.
- **Cybersecurity research scope.** The bill folds cybersecurity research into the same exemption rather than separately reforming §1201(j) as the Register recommended. Security-research advocates (EFF, Rapid7, Bugcrowd, HackerOne, ACM, CDT) are natural allies; rightsholders may argue the unification creates ambiguity. Counter: a unified purpose-test is cleaner than §1201(j)'s multi-factor test, which the Register itself criticized as confusing (2017 Study at pp. 76–78).
- **"Any product dependent … upon attached or embedded digital electronics" definition.** Broad — intentionally so, aligning with the Register's "recommends against limiting an exemption to specific technologies or devices" position (2017 Study at p. 94). DVD-player and game-console makers will argue this sweeps in their authentication systems and creates piracy risk. Counter: those systems gate *access to copyrighted works*; the purpose-test ("for the purpose of … repair") cabins the exemption to non-piracy use cases.
- **Safety regulation.** Opponents in the building / energy / automotive space will argue the exemption enables unsafe modifications. Counter: the 2017 Register's Study expressly directed safety arguments away from copyright law (PDF p. 94: "the Office believes these matters are better addressed through laws or regulations outside of the Copyright Act"). UL, IEEE, EPA, DOE, FAA, FDA, and AHJ inspection regimes — not §1201 — regulate safety.

## Not legal advice

This is draft legislative text not yet introduced. Final language is subject to Congressional drafting conventions, House Office of Legislative Counsel input, and coalition-counsel review. This file documents the draft for the archive; nothing here is a legal conclusion.
