Codify — Article

Government Surveillance Transparency Act of 2026 (S.3918) — limits sealing, mandates public dockets, and expands notice

Creates a new chapter in Title 18 that restricts indefinite sealing of surveillance orders, requires inventories and notice to targets/providers, and publishes machine‑readable docket data.

The Brief

The Government Surveillance Transparency Act inserts a new Chapter 206A into Title 18 to curb indefinite secrecy around criminal surveillance. It generally forbids sealing surveillance orders after execution and establishes a default maximum sealing interval (initial 180 days with narrowly circumscribed extensions).

The bill also requires courts to publish standardized, machine‑readable docket metadata for surveillance cases and to implement automatic unsealing mechanisms.

The bill reaches beyond federal practice: it conditions certain interstate authorities and prosecutorial tools on state and tribal courts’ compliance, creates reporting obligations for judges and agencies, tightens the contents of inventory returns (to flag any provider disclosures or government overcollection), and phases implementation with targeted grant funding. For compliance officers, defense counsel, providers, and court administrators, the measure reshapes notice, recordkeeping, and technical requirements tied to warrants, subpoenas, pen registers, and other surveillance processes.

At a Glance

What It Does

The bill creates Chapter 206A defining “criminal surveillance orders,” limits how long courts may keep such orders sealed (initial seal up to 180 days with a narrow extension regime), requires machine‑readable public docket metadata and unique case numbers per target, and mandates inventories that disclose unauthorized provider disclosures or government overcollection. It also tightens notice obligations to customers/targets and constrains the use of nondisclosure and delayed‑notice orders.

Who It Affects

Federal, State, and Tribal courts and their clerks (electronic docketing and unsealing systems); law enforcement and prosecutors (new certification and reporting burdens, limits on secrecy); communications and cloud providers (inventory disclosures, 7‑day notice rules for voluntary disclosures); and targets, defense attorneys, researchers, and transparency organizations who gain structured access to surveillance records and metadata.

Why It Matters

This bill shifts the default from secrecy toward post‑fact transparency—creating formal pathways for notice, audit, and public reporting. It introduces technical and procedural standards (machine‑readable dockets, automated unsealing) that change how courts, agencies, and providers document, retain, and disclose surveillance activity.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill creates a standalone statutory framework for criminal surveillance orders (wiretaps, pen registers, cell‑site warrants, orders for third‑party assistance, delayed‑notice orders, search warrants, and comparable state and tribal instruments). It defines covered documents (applications, orders, inventories) and then places strict constraints on sealing: courts may not keep those materials sealed beyond execution or the end of authorized surveillance except under a limited sealing regime.

The initial sealing window is up to 180 days; a single 180‑day extension is allowed on certification that disclosure would cause enumerated adverse results; further extensions require a particularized showing and specific factual detail (including suspected crimes and named targets) and trigger an obligation for courts to consider redactions rather than continued full sealing.

To ensure transparency without publishing sensitive content wholesale, the bill requires courts to publish a minimum set of docket metadata for each criminal surveillance matter as an open government data asset. That metadata includes filing and return timestamps, statutory authority, investigating agency, duration, whether sealing or nondisclosure was requested, disposition, a unique case number assigned per identified target (phone, device, address, account), and the date the seal expires.

The statute allows narrow withholding of particular metadata items if the applicant shows those items would produce the enumerated adverse results.The bill also revises discovery and inventory practice: inventories and Rule 41 filings must affirmatively state whether a provider disclosed data beyond what the order authorized and whether the government searched or accessed materials or signaling information beyond the court’s authorization; if so, the inventory must describe the overcollection in detail. Parallel amendments force providers who voluntarily disclose customer communications or records to notify affected subscribers within seven days unless a court delays notice under the statutory gatekeeping procedure.Finally, the Act builds an implementation architecture: it phases the effective date (most federal changes in two years, with a four‑year window for some state and tribal courts lacking electronic dockets), authorizes $1 million for the Administrative Office of the U.S. Courts to implement standards, and caps grants for State/Tribal court compliance at $25 million.

It also ties certain federal authorities (e.g., state‑based wiretap cooperation, full‑faith‑and‑credit recognition) to whether the issuing state or tribal court certifies compliance with the new Chapter 206A requirements.

The Five Things You Need to Know

1

The bill forbids indefinite sealing and sets a presumption against secrecy: initial seals may last no more than 180 days; one 180‑day extension is permitted, and any further extension requires a particularized factual showing naming the target, suspected crimes, and why redactions won’t suffice.

2

Courts must publish open, machine‑readable docket metadata for each criminal surveillance matter (including statutory authority, investigating agency, surveillance duration, whether nondisclosure was sought, disposition, and seal‑expiry date) and assign unique case numbers for each identified target (phone number, device, account, address, etc.).

3

Inventories (and amended Rule 41 returns) must disclose whether a provider supplied data not authorized by the court or whether the government searched or obtained information beyond the authorization, and must provide detailed information when overcollection occurred.

4

The bill narrows the use of delayed‑notice and nondisclosure: notice to subscribers/customers is required prior to surveillance where feasible (or within 7 days after contact info is obtained), and courts may only delay or preclude notice for sealed matters while the sealing order remains in effect under the statutory standards.

5

Implementation is phased and funded but limited: most provisions take effect 2 years after enactment, some state/tribal applicability is delayed to 4 years for courts lacking e‑docketing, the Administrative Office gets $1M to operationalize requirements, and a $25M grant pool is available to help State and Tribal courts comply.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 2 / Chapter 206A (new)

Definitions and scope of ‘criminal surveillance orders’

This section creates the statutory home for the Act’s rules and gives a broad definition of ‘‘criminal surveillance order,’’ covering federal and ‘‘equivalent’’ state orders: wiretaps (chapter 119), pen registers/trap‑and‑trace (chapter 206), mobile tracking warrants, 2705 delayed‑notice orders, many kinds of search warrants, court‑martial orders, orders for third‑party assistance, and orders enforcing assistance statutes. Practically, that breadth pulls common surveillance authorities under a unified transparency regime so the same sealing, docketing, inventory, and notice rules apply across instrument types.

Section 3132(a)

Limitations on sealing and standards for extensions

This provision makes sealing the exception, not the norm. It sets an initial sealing ceiling (up to 180 days post‑execution or end of surveillance) and allows a single 180‑day extension on a government certification that disclosure would cause enumerated harms (danger to life, flight, destruction of evidence, witness intimidation, or serious jeopardy to the investigation). Any extension beyond that triggers a heightened judicial review: the government must make a particularized showing, identify the investigation, suspected crimes, and the target, and explain why redaction won’t mitigate harm. The court may require factual support and must consider redactions as a less‑restrictive alternative.

Section 3132(b)

Public docketing, unique case numbers, and automated unsealing

Courts must publish a public docket record for each surveillance matter as open government data—text searchable, machine‑readable, and accessible in bulk. The docket must include timestamps, statutory authority, agency, surveillance duration, whether secrecy was requested, disposition, an index of related filings, the unique target‑specific case number, and the seal expiration date. The court may withhold only specific items that would cause the enumerated adverse results. Importantly, clerks must implement a technical mechanism that automatically unseals at expiration (and provide the investigating agency a 10‑business‑day pre‑unsealing notice). The rule aims to standardize transparency while allowing surgical withholding when disclosure would actively harm investigations.

4 more sections
Section 3132(c) & 3133

Filing and challenge processes for unsealing or redaction

All applications and inventories must be filed electronically (subject to the phased delays for courts without e‑filing). The statute gives any person standing to move to unseal or challenge a redaction either in the original case or as a separate, stand‑alone petition; challenges can encompass multiple related sealed applications. The availability of a stand‑alone path is designed to let transparency groups, news organizations, and defense counsel coordinate strategic challenges without joining underlying criminal proceedings.

Sections 3–4 (2702, 2703, Rule 41 changes)

Inventories, provider disclosures, and notice to subscribers/targets

The bill strengthens inventories and provider obligations: Rule 41 inventories and court orders must report whether the provider supplied any data beyond what the court authorized and whether the government accessed or searched material in an unauthorized way (including dialing/routing data). Providers that voluntarily disclose customer content or records at a government request must notify subscribers within seven days unless a court delays notice under the newly tightened 2705 standards. The practical effect is a statutory feedback loop: overcollection becomes a reportable, docketed fact that can trigger litigation over legality and notice claims.

Section 5 (2705)

Requlating delay and preclusion of notice

The bill narrows the scope and duration of delayed‑notice orders. Courts can only delay notice for warrants/orders that are sealed under Chapter 206A, and initial delay periods for subpoenas or emergency requests are tied to the 180‑day standard with a similar single extension and heightened standard for subsequent extensions. The court must enter or revoke delay orders consistent with the sealing record and will be notified promptly by the government once the risk of adverse result ends. The statute also requires judges to report annually on such orders to the Administrative Office.

Sections 6–9 (incentives, reporting, grants, effective dates)

Incentives for State/Tribal compliance, reporting regime, and funding

The Act conditions certain cooperative authorities (state wiretap cooperation, pen register recognition, and full faith and credit) on whether the state or tribal courts require compliance with Chapter 206A, creating an incentive for local courts to adopt e‑docketing and the Act’s transparency rules. It imposes machine‑readable annual reporting duties on judges for delayed‑notice orders and surveillance orders, authorizes the AOUSC to publish forms and adopt rules (funded at $1M), and creates a time‑limited $25M grants program to help State and Tribal courts implement electronic docketing and reporting. The effective dates are phased: most federal provisions in two years, with a four‑year window for courts lacking e‑docketing and opportunities for 1‑year security certification delays.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Privacy across all five countries.

Explore Privacy in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Targets and defendants — gain a statutory right to eventual notice and a clearer path to challenge sealed orders and redactions, allowing post‑investigation review of legality and more timely defense preparation when warrants are disclosed.
  • Civil‑society organizations, journalists, and researchers — receive standardized, machine‑readable docket metadata and a stand‑alone mechanism to petition courts to unseal or challenge redactions, enabling oversight and empirical research into surveillance use and patterns.
  • Defense counsel and discovery teams — inventories and amended Rule 41 returns are required to flag overcollection and unauthorized disclosures, improving the ability to litigate Fourth Amendment violations and preserve remedies.
  • Court administrators and clerks — receive federal grants and a statutory framework for standardizing docket metadata and automated unsealing, which can simplify case management once systems are implemented.
  • State and Tribal courts committed to transparency — benefit from conditional access to interstate cooperation and federal tools when they certify compliance with Chapter 206A, and from grant funding to build electronic dockets.

Who Bears the Cost

  • Law enforcement and prosecutors — face new procedural steps, documentation and certification burdens, constraints on secrecy windows, and the need to justify continued sealing with detailed facts; investigative workflows will require adaptation to shorter default sealing periods.
  • Court systems and clerks — must implement or upgrade e‑filing, automated unsealing, machine‑readable publication, and reporting systems; even with grants, local budgets and IT teams will bear implementation and maintenance costs.
  • Communications and cloud providers — must produce more detailed inventories, identify unauthorized disclosures, and, for voluntary disclosures, facilitate 7‑day notice to subscribers; providers may need additional compliance teams and logging capabilities.
  • Defense and civil litigants (costs of challenges) — increased access to unsealing and redaction challenges will create additional litigation, discovery fights, and potential expense for both courts and governments, including payment of fees if challengers substantially prevail.
  • Federal agencies and the Department of Justice — must adjust to tighter sealing standards, additional reporting, and potential operational limits on longstanding investigative techniques; they may also need to fund additional compliance infrastructure.

Key Issues

The Core Tension

The central dilemma is between two legitimate public goods that pull in opposite directions: transparency and accountability (notice to targets, public dockets, inventories revealing overcollection) versus the need for operational secrecy to protect lives, preserve evidence, and sustain effective investigations. The bill narrows secrecy but expects courts to use redaction and targeted withholding—placing heavy weight on judicial fact‑finding and on underfunded court IT systems to reconcile the competing objectives.

The bill’s principal trade‑off is procedural visibility versus operational secrecy. By defaulting to unsealing and by publishing standardized metadata, the statute increases public accountability and post‑fact litigation risk for overcollection or unlawful surveillance.

But greater transparency also risks revealing investigative techniques or patterns through metadata (for example, persistent filings against particular identifiers can signal an ongoing operation even when order contents are redacted). The statute attempts surgical remedial tools—heightened judicial review for continued sealing, redaction procedures, and a narrow list of adverse results—but those carve‑outs rely heavily on judges’ willingness and capacity to conduct in‑camera fact review and to craft precise redactions instead of blanket secrecy.

Implementation will test the law’s aspirations. The requirement for electronic filing and automated unsealing presumes robust, secure e‑courts infrastructure; the Act permits limited delays if systems are insecure, but the certification and phased timelines shift significant technical work onto courts already stretched thin.

The Act also conditions interstate cooperation on State/Tribal adoption, a leverage point that could speed compliance but may also create uneven cross‑jurisdictional effects: investigators may encounter variation in sealing and notice rules that complicates multistate investigations and may drive some functions to venues with weaker transparency rules. Finally, the grant cap ($25M) and $1M AOUSC appropriation are modest relative to the nationwide technical modernization likely required, raising questions about whether resource constraints will hinder uniform compliance and whether smaller courts or tribes will lag behind in practice.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.