Codify — Article

SAFE Act (S.3893) tightens Section 702 queries, boosts oversight and limits data-broker buys

A broad FISA rewrite: mandatory FBI query audits and approvals, new court and reporting checks, criminal penalties, and tight limits on intelligence and law‑enforcement purchases of U.S.-person data.

The Brief

The SAFE Act (S.3893) repackages a sweeping set of reforms to the Foreign Intelligence Surveillance Act focused on Section 702 query practices, transparency, and limits on acquisition of U.S.-person data. It forces mandatory, regular audits of FBI queries, requires training and higher‑level approval for sensitive queries (including queries that may touch Members of Congress, judges, or batch jobs), imposes stricter documentation and notification duties, and restricts warrantless access to content of U.S. persons with narrow exceptions.

Beyond query rules, the bill changes institutional oversight: it expands FISC review tools (random sample review of targeting decisions and expanded amicus authority), mandates broader declassification review of certain court opinions, creates statutory accuracy and disclosure duties in FISA applications with new criminal penalties for false statements or omissions, and curtails government purchases of personal data from data brokers absent court authorization or narrow exceptions. The Act bundles these procedural and transparency steps to make many classified collection activities auditable and subject to judicial or congressional review.

At a Glance

What It Does

The bill requires DOJ audits of every FBI ‘covered query’ in rolling 180‑day windows and compels agencies to keep query logs, written justifications, and training records; it limits when Section 702‑derived content touching U.S. persons can be accessed and documents exceptions. It also narrows the ability of intelligence and law‑enforcement bodies to buy or query commercially held personal data about U.S. persons without court authorization or specific exceptions.

Who It Affects

Directly affects the FBI’s query systems and all intelligence community users of Section 702 material, online service providers and ‘covered’ data brokers, the Foreign Intelligence Surveillance Court and its counsel, congressional intelligence and judiciary committees, and providers that host or route communications (intermediaries). Agencies that rely on commercial datasets for targeting or investigations will need new clearance, minimization, and deletion workflows.

Why It Matters

This is a coordinated operational, judicial, and transparency package: compliance and disciplinary regimes shift the internal governance of queries; new reporting and declassification demands expose program details to oversight; and the data‑broker and service‑provider rules close a loophole that allowed bulk, warrant‑free downstream use of commercially obtained U.S.‑person data.

More articles like this one.

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

Unsubscribe anytime.

What This Bill Actually Does

Title I zeroes in on Section 702 query practice. DOJ must audit every “covered query” performed by the FBI in rolling 180‑day windows and deliver unredacted results to specified congressional committees.

The statute sets new operational guardrails for the FBI: queriers must be trained, certain sensitive queries require pre‑approval by an FBI attorney (examples include terms likely to identify Members of Congress, judges, or batch queries), and each covered query requires a written factual justification retained in an auditable record. Systems that combine 702 content with other holdings must force an affirmative election before including 702 content in a search.

The bill also erects a tighter firewall around accessing content of U.S. persons and persons located in the United States. It bars warrantless access to such content returned by covered queries except in narrowly delineated cases: simultaneous lawful authorizations (or prompt post‑hoc applications and reporting for emergency authorizations), user consent, specific defensive cybersecurity uses, or exigent life‑safety circumstances.

Access under those exceptions must be documented electronically and, for certain kinds of uses, reported to the FISC and Congress.Title II and related provisions recalibrate the filing and verification duties for FISA applications. Applicants must disclose material information and exculpatory facts, describe accuracy procedures, and certify that supporting documentation has been reviewed.

The bill bars relying solely on media‑sourced or campaign‑gathered content unless the application discloses it and explains corroboration; false statements or material omissions in filings are criminalized. Agencies must implement compliance procedures and internal discipline regimes; the FBI must establish centralized tracking and escalating personnel consequences for query violations.The Act reshapes judicial oversight and transparency.

It expands the FISC’s amicus role, gives amici access to previously withheld materials (including decisions and supporting documents), and authorizes amici to seek certification of legal questions for higher‑court review. The DNI and Attorney General must complete specified declassification reviews and, in some cases, provide summary descriptions to the FISC and congressional committees before or shortly after serving directives on certain providers.

An Inspector General audit cycle is mandated and DNI reporting requirements are enlarged to include disaggregated counts of queries, directives, and when U.S.‑person identities are disseminated.Title V and related sections limit how the government acquires commercial personal data about U.S. persons: the intelligence community may not acquire ‘covered data’ about persons reasonably believed to be in the U.S. or U.S. persons absent a court order or narrow exceptions (employment vetting, emergencies, consent, compliance functions, and non‑segregable datasets subject to strict minimization). Law enforcement faces a similar bar on buying data from data brokers, subject to exceptions.

Statutory definitions of “derived from” and anti‑parallel‑construction guidance seek to prevent circumvention of disclosure and legal‑process requirements.

The Five Things You Need to Know

1

DOJ must audit every FBI ‘covered query’ on a rolling 180‑day basis and deliver completed, unredacted audit results to the congressional intelligence committees and the Judiciary Committees within strict deadlines.

2

FBI personnel must complete pre‑query training; certain queries (those likely to identify Members of Congress, judges, batch jobs, or prominent U.S. organizations) require prior attorney approval and a written factual justification logged with the query record.

3

The bill bars warrantless access to Section 702 content for U.S. persons and persons in the U.S. except for tightly defined exceptions (concurrent lawful orders, exigent life‑safety, consent, or narrowly tailored cybersecurity uses) and requires electronic records documenting the legal basis for any access.

4

The DNI/AG must expand public and classified reporting: disaggregate covered‑query counts by agency, report how often U.S.‑person content was accessed or disseminated, track cross‑agency queries performed on behalf of agencies without 702 access, and publish a declassified portion annually.

5

The intelligence community and law enforcement are generally prohibited from buying or acquiring ‘covered data’ about U.S. persons from data brokers without a court order; limited exceptions (employment vetting, emergencies, consent, compliance) are narrowly prescribed and any nonsegregable dataset must be minimized.

Section-by-Section Breakdown

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

Sec. 101

Query procedure reform and FBI query controls

This section prescribes mandatory DOJ audits of FBI covered queries every 180 days, with completion and reporting deadlines and a requirement to repeal any overlapping statutory audit obligations. It also augments Section 702(f) to require FBI‑specific querying procedures: pre‑query training, prior attorney approvals for categories of sensitive searches, prior written justifications for each covered query, explicit recordkeeping (term, operator, date, factual basis), and an affirmative UI control forcing operators to choose whether to include unminimized 702 content in searches. Practically, systems, logs, and internal workflows will require redesign and retention policies to survive oversight.

Sec. 101 (cont.)

Prohibition on warrantless access and exception architecture

The bill inserts a categorical prohibition on warrantless access to U.S.‑person communications and information obtained under Section 702 unless a defined exception applies. Exceptions include concurrent court authorizations or prompt post‑hoc FISC applications for emergency access, narrowly constrained defensive cybersecurity queries, consent, and specified exigent circumstances. Each access must produce an electronic record showing the applicable legal basis, and agencies must institute systems to preserve those records and report compliance to Congress.

Sec. 102–103

Reporting and FBI accountability regime

AG/DNI reporting obligations expand: annual DN I/AG reports must break down covered queries, counts of U.S.‑person content accesses, frequency of asserted exceptions, use of batch queries, and cross‑agency query activity. Separately, the FBI must implement centralized tracking of query compliance incidents and escalating personnel consequences—suspensions, access revocations, reassignments, and referral for inspection—plus annual unclassified reporting (with classified annexes) on disciplinary actions.

4 more sections
Sec. 104–105

Reverse‑targeting ban and FISC sampling oversight

The SAFE Act tightens targeting limits to prevent acquisitions intended to ‘reverse‑target’ United States persons or persons in the U.S. It requires FISC submission of a random sample of targeting decisions and written justifications from the prior year for court review. That expands the court’s substantive oversight role from program certifications to ex post review of particular targeting decisions and their supporting facts, increasing judicial scrutiny and creating a record for subsequent audits or appeals.

Title II (Secs. 201–206)

Disclosure, accuracy, and anti‑circumvention measures

New statutory duties require applicants seeking FISC orders to provide all material information—including exculpatory or potentially reliability‑undermining facts—and to describe internal ‘accuracy procedures.’ Applications must include certifications that supporting documentation was collected and reviewed. The bill adds criminal penalties for intentional false statements or material omissions in filings, narrows permissible reliance on media or campaign‑sourced information, prohibits parallel construction designed to avoid disclosure obligations, and clarifies the meaning of ‘derived from’ to prevent attenuated workarounds.

Title III (Secs. 301–303)

FISC process and amicus expansion; declassification deadlines

The Act broadens the court’s amicus program: the FISC must appoint amicus curiae for novel, sensitive, or programmatic matters (and prioritize privacy/civil‑liberties expertise), grant those amici access to applications and supporting materials (including underlying accuracy files on motion), and permit amici to seek certification of legal questions for appellate review. The DNI and AG must complete declassification review of certain previously secret FISC opinions and publish summaries of the types of providers and services at issue; courts get deadlines for handling such submissions.

Title V

Limits on acquisition and purchase of U.S.‑person data

This title defines ‘covered data’ and bars the intelligence community from acquiring covered data tied to U.S. persons or persons in the U.S. absent a FISA or judicial order or narrow, enumerated exceptions (employment‑related vetting, compliance testing, exigent life‑safety, consent, or limited nonsegregable datasets with strict minimization). It likewise caps law‑enforcement purchase of personal data from data brokers unless covered by statutory exceptions (consent, background checks, reimbursed compulsory legal process, whistleblower programs). The bill also requires public notices and reports when large datasets containing U.S.‑person data are expected.

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

  • United States persons and residents: gain statutory guardrails against warrantless queries and downstream use of commercial data, more notice to Congress when high‑level persons are queried, and extra reporting that could expose misuse.
  • Members of Congress and judges: receive statutory notification rights and additional procedural protections when queries use their names or identifying terms, reducing stealth surveillance risks.
  • Privacy and civil liberties advocates and the public: obtain expanded declassification review, more granular annual reporting, and an empowered amicus program that can surface novel legal issues to higher courts.
  • Foreign Intelligence Surveillance Court and appellate defenders: receive structured access to targeting samples and supporting accuracy files, enabling more effective judicial review and development of precedents.

Who Bears the Cost

  • Federal Bureau of Investigation: faces immediate compliance costs—new training, pre‑approval workflows, query logging systems, centralized tracking of violations, and personnel discipline infrastructure.
  • Intelligence community programs that rely on commercially acquired datasets: will face limits, extra minimization burdens, and potential suspension of acquisitions pending court orders or technical segregation.
  • Data brokers and some commercial aggregators: lose a portion of revenue from selling datasets about U.S. persons to government buyers and will face new legal process and disclosure standards.
  • Online service and intermediary providers: may see increased legal process demands, new directive review and declassification interactions, and operational burdens responding to FISC‑notified directives and quarterly reporting.
  • Courts and oversight committees: FISC and congressional oversight bodies must handle additional documents, declassification reviews, and potentially large volumes of audit materials, increasing workload and resource needs.

Key Issues

The Core Tension

The central dilemma: the SAFE Act forces a trade‑off between two legitimate aims—protecting national security by preserving rapid, wide‑ranging collection and operational flexibility, and protecting constitutional privacy and civil liberties through independent review, narrow access, and transparency. Measures that increase judicial and congressional oversight and restrict downstream use of data will improve accountability but risk slowing or complicating urgent intelligence and law‑enforcement actions; implementation choices (how exceptions are defined and how technical minimization is conducted) will determine whether the balance tips toward security or privacy.

The SAFE Act stitches together many different levers—operational rules, judicial process changes, reporting mandates, and criminal penalties—so implementation will require significant cross‑agency coordination. The practical effect depends on how agencies draft procedures (e.g., what qualifies as a ‘covered query’ or ‘reasonable belief’), how vigorously the FISC exercises its new review tools, and how the DNI/AG balance declassification against protecting sources and methods.

Tight deadlines for audits, reporting, and FISC review will strain agency IT, personnel, and legal teams and raise the risk that incomplete systems delay investigations or force temporary suspensions.

The bill’s restrictions on acquiring commercially held U.S.‑person data close an important avenue for warrantless downstream access, but they also create operational gaps for legitimate national‑security and public‑safety uses (employment vetting, time‑sensitive cyber‑defense, compliance testing). Agencies will rely on narrowly defined exceptions and the nonsegregable‑dataset path, which in practice may require complex, possibly contested technical determinations about whether covered records are segregable or ‘derived from’ covered acquisitions.

The criminal penalties for misleading filings increase accountability but may discourage candid intra‑agency discussion unless well‑scoped accuracy‑procedures guidance and whistleblower protections are in place.

Try it yourself.

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