ICE Deleted Its Palantir Paperwork in 41 Hours

Introduction

If a landlord has ever run a background check on you or a lender has pulled your identity records, LexisNexis Risk Solutions keeps a file on you. On August 10, ICE posted a procurement document requiring that database to connect by API to Palantir's platform, and adding two capabilities its 2020 predecessor never asked for: an AI-driven identification system built on device metadata and network signatures, and bulk facial recognition searches. 404 Media broke the story that same day. Forty-one hours after the document went up, ICE deleted it from SAM.gov.

Four months earlier, 33 members of Congress had asked DHS in writing which commercial datasets get fed into Palantir-developed systems for immigration enforcement, with a deadline of April 24. No answer came. On day 108, ICE published the requirement in the paperwork for its next LexisNexis contract.

Bridging LexisNexis Past August 31

ICE's current arrangement with the company, the Law Enforcement Investigative Database Subscription, expires August 31. The USAspending record for award 70CMSD21C00000001 shows a ceiling of $24,509,115 across five and a half years, of which $15,655,221.81 has actually been outlaid, about 64%. That contract was competed in the open, with six offers received. The no-bid part is what comes next.

The notice of intent ICE's Office of Acquisition Management posted that afternoon says the agency will award LexisNexis Risk Solutions Inc. an interim contract without competition, citing 41 U.S.C. § 3304(a)(1) and FAR 6.302-1, "Only One Responsible Source." Estimated value, $6.7 million, over a seven-month base plus five one-month options. Homeland Security Investigations "requires continued access to LexID and Accurint Virtual Crime Center," the notice says, and those capabilities "cannot be obtained from another source within the required timeframe."

FAR 6.302-1 is the ordinary authority for sole-sourcing proprietary commercial software, and the most-used sole-source justification in federal contracting, so the citation itself is routine. A contract with a known end date is running to expiration without a competed successor, and the fallback is a no-bid bridge justified partly by there being no time. Nothing has been awarded yet. ICE says it intends to.

What the Attachment Record Says

SAM.gov doesn't scrub deleted attachments from its API. It flags them. The resources record for this notice still returns a file named 1.2.1-PWS.pdf, posted August 10 at 20:01:50 UTC, carrying deletedFlag: 1 and an effectiveDeletedDate of 2026-08-12T13:35:05.637 UTC. That's 9:35:05 a.m. Eastern on August 12, and it matches the notice's own "modified" timestamp to the millisecond. The two versions of the notice text are byte-identical, which means pulling the attachment was the entire update.

The order of events: the performance work statement is internally dated July 22, went public August 10 at 4:01 p.m. Eastern, and came down on the morning of the 12th. 404 Media published the day it appeared and State of Surveillance followed on the 11th. Biometric Update ran its detailed read at 3:52 p.m. on the 12th, six hours after the file stopped being downloadable, because its reporter already had a copy.

The PDF is not recoverable: SAM.gov's download endpoints return HTTP 400 without an API token, and the Wayback Machine's index comes back empty for the opportunity page and the file path. What the record doesn't carry is a reason. Attachments get pulled for unremarkable reasons all the time, including a wrong version or markings that shouldn't have gone public.

The Palantir Line in the Deleted Document

While the file was live, reporters quoted it. The operative sentence, quoted by State of Surveillance, requires that the database "must be able to application programming interface (API) with ICE applications, such as but not limited to, Palantir platform, PenLink, and ICE Data Analytics."

Biometric Update's Anthony Kimery, working from a copy, reported the rest: up to 11,200 authorized users across HSI, Enforcement and Removal Operations, and the Office of Professional Responsibility, with 7,500 ERO users granted unlimited 24- and 72-hour booking-data searches. The document calls for a "system-to-system connection" supporting "live queries, batch requests and data imports," an "AI-driven identification system" combining behavioral indicators, device metadata, and network signatures, and "advanced AI-driven facial recognition platforms" for bulk image searches. It also, on paper, requires human oversight and bars AI output from being the sole evidence for an enforcement action.

That AI identification line is the one I keep going back to. Inferring identity from device metadata and network signatures is a guess about who you are from how your phone behaves, rather than a match against a name.

The pipe itself isn't new. ICE's 2020 LEIDS solicitation already required an interface with what it then called "FALCON/Raven Palantir systems," as Biometric Update notes. What changed is what sits on the receiving end: Palantir now works under a five-year, departmentwide DHS agreement with a $1 billion ordering ceiling, and has already drawn $86.27 million and $45.85 million task orders under it this spring.

Scope is the other open question. DHS's August 6 acquisition forecast pegged this requirement at $2 million to $5 million over a six-month base plus six monthly options; the August 10 notice says $6.7 million over seven months plus five; the performance work statement describes a base year plus four option years with no price schedule. Biometric Update flagged the mismatch, saying it's unclear whether the AI functions belong to the bridge, a later contract, or another product entirely. Which Palantir application receives the feed isn't in the public record either.

Congress Asked in April

On April 14, Rep. Dan Goldman, Sen. Ron Wyden, and Rep. Nydia Velázquez sent DHS and then-Acting ICE Director Todd Lyons a seven-page letter carrying 11 numbered demands and 33 signatures. Item three asked which government and commercial datasets are "implemented into Palantir-developed systems...utilized by DHS for the purpose of immigration enforcement." The letter set its own clock: answers "no later than Friday, April 24th, 2026."

It exists because of what ICE leadership had been telling Congress. On February 10, Lyons appeared before the House Homeland Security Committee, where Rep. Lou Correa asked about a viral clip of an ICE agent telling a woman she'd be added to a "nice little database." Lyons answered: "I can't speak for that individual. But I can assure you that there is no database that's tracking United States citizens." FedScoop reported the same exchange independently. Then-Secretary Noem told the House Judiciary Committee something separate on March 4, responding to a question about whether DHS was building a database of protesters: "we're not creating a database." Two different questions, and the letter itself keeps them apart.

Two days after the letter's date, Lyons announced his resignation, effective May 31, and left without answering it. He is now a senior vice president at the defense contractor Navigators Security and Defense, barred from engaging DHS for a year, per NPR's June reporting.

On May 7, at a rally outside Palantir's New York office, Goldman said DHS and ICE "have refused to provide transparency about how they are using these tools and what information they are collecting about American citizens." No response to the letter has surfaced since.

DHS has answered a narrower question elsewhere: Assistant Secretary for Public Affairs Tricia McLaughlin told FedScoop on the record that the department runs no database of domestic terrorists, a specific denial to a specific allegation, and not one of the letter's 11 items.

Who Benefits

LexisNexis Risk Solutions, and RELX plc above it, gets the obvious thing: an eight-figure federal revenue stream that continues past August 31 with nobody allowed to underbid it for the length of the bridge.

Palantir gets more than money, and the money is considerable. Its Q2 2026 Form 8-K, covered by CNBC on August 3, puts revenue at $1.94 billion, up 93% year over year, with U.S. government revenue at $809 million, up 90%. Per a shareholder filing corroborated by the Financial Times, it has signed more than $81 million in ICE contracts since January 2025, on top of that $1 billion DHS ceiling. Once the government's own procurement language names your platform as the thing every vendor's data must connect to, whoever wins the data contract builds to Palantir anyway, and that's worth more than the contract's face value.

None of that margin circles back to the public, either: Palantir paid $0 in U.S. federal corporate income tax in 2025, its third straight year at zero, on $1.66 billion of pretax profit, per a CICTAR report covered by Al Jazeera and a separate February finding from the Institute on Taxation and Economic Policy. CICTAR produced that report with a European public-services union federation.

ICE gets continuity and time. The agency keeps the pipeline running and widens what it asks of that pipeline, without answering the letter that asked about it. The deadline it's actually working against is a contract expiration date it controlled all along.

When a Subscription Does a Database's Job

There's a real defense here. Subscribing to a commercial product that thousands of other customers also buy isn't the same as the government building and keeping a database of its own citizens, and nothing in the notice says ICE builds or retains one. Palantir makes the architectural version of this argument in a January 27 post answering an EFF report: it is "not working on any master database project to unify databases across federal agencies," and each customer's instance of its software is "legally, technically, and operationally distinct."

Take all of that at face value and it still doesn't reach what's being bought. Persistent identity resolution across the 82 billion records LexisNexis markets (a company figure that, per Biometric Update, LexisNexis itself cautions may contain errors), a live API into a case-management platform used by up to 11,200 enforcement users, machine inference about identity from device and network behavior, and one-to-many face search across bulk images add up to a querying capability that does the work a tracking database does. Whose servers hold the bytes doesn't change what comes back from a query, and retention terms aren't in the public record at all.

Per the letter's own text, the February 12 Senate exchange it also quotes concerned a database of "any kind," including facial recognition, license plate and address data, not a government-hosted table.

The Bottom Line

The challenge window closes at 9 a.m. Eastern on August 14, the notice goes inactive August 29, and the old contract ends August 31. Somewhere in that stretch, ICE intends to sign.

Item three of the April letter asked DHS which commercial datasets get implemented into Palantir-developed systems for immigration enforcement. For 41 hours this month, part of the answer sat on a federal procurement website as a public PDF, and now it doesn't. The letter is still unanswered, the contract is still coming, and whether the next version of that paperwork ever goes up in public is a call made by the same office that took this one down.