Back to Blog
Policy & Regulation April 19, 2026 5 min read

Congress Passes 10-Day FISA 702 Stopgap — Surveillance Powers Expire April 30

House Republicans failed twice to advance a long-term renewal of Section 702, forcing a 10-day extension that sets a hard April 30 deadline for U.S. surveillance powers. Cloud providers and telcos face immediate compliance uncertainty if talks collapse.

Congress Passes 10-Day FISA 702 Stopgap — Surveillance Powers Expire April 30

FISA Section 702 — the statute that authorizes NSA surveillance of foreign nationals’ electronic communications — came within hours of expiration on April 17, before Congress agreed to a 10-day stopgap. The new deadline is April 30.

The Senate passed the extension by unanimous voice vote Friday morning after the House failed, twice, to advance a longer-term renewal. A 5-year reauthorization bill and a shorter 18-month version backed by Trump both collapsed when approximately 20 far-right Republicans voted against the procedural motion after midnight Thursday.

What Section 702 Actually Does

Under 702, the NSA can collect electronic communications of non-U.S. persons located outside the country — without a warrant — if the target is reasonably believed to be a foreign intelligence source. The controversial part: Americans’ communications swept up in that collection can subsequently be queried by the FBI without a warrant. That “backdoor search” provision has been the central civil-liberties flashpoint blocking renewal for years.

The debate scrambles the usual partisan lines. Some conservative Republicans, allied with ACLU-adjacent libertarians, have pushed for a warrant requirement before the FBI can access incidentally collected American data. The intelligence community and mainstream Democrats argue the requirement would create dangerous delays during active threat investigations.

What Happens Next

Both chambers left Washington on recess immediately after passing the stopgap. Lawmakers must return, agree on language, and pass a bill — all before April 30. Given that the House couldn’t clear two procedural votes in a single night, a 10-day breakthrough seems unlikely.

The realistic scenarios: another short extension to buy more negotiating time, or a brief lapse while the standoff plays out. A lapse doesn’t immediately shut down 702 collection on active investigations — emergency procedures exist — but it restricts the NSA’s ability to initiate new collection and share foreign intelligence with allies.

The Tech Industry Angle

Cloud providers, telecommunications companies, and major platform operators are directly implicated in 702 compliance. Microsoft, Google, Apple, and Meta have all received 702 production orders under this statute. A lapse creates immediate legal uncertainty around compliance obligations — particularly for companies that handle EU-U.S. data flows already under international scrutiny following Schrems II.

A renewal that includes expanded warrant requirements would restructure how government data requests are processed, adding judicial review to a process currently handled administratively. For cloud providers building sovereign or government cloud tiers, the outcome of this negotiation directly shapes their legal architecture.

The EU-U.S. Data Privacy Framework, which underpins transatlantic data flows for thousands of U.S. and European companies, depends in part on demonstrated U.S. surveillance safeguards. A messy 702 expiration — or a renewal fight that reveals the depth of congressional disagreement — gives European regulators exactly the kind of ammunition they need to challenge the framework’s adequacy finding.

April 30 is not a soft deadline.

FISA surveillance regulation privacy congress cloud