“TRSS latest ICE contract is the first to include voter fraud that we are aware of, and we intend to press the company, alongside other investors, for clarity on this contract,” Emma Pullman wrote.
What the contract language says
The source material includes a passage that reads: “Due to ICE’s re-prioritized mission, there is need for this data to be readily accessible to support the presidential mandate of the identification of Voters Fraud, Immigration Fraud and National Security.” That phrasing appears in the materials discussed in the piece and frames why access to transactional datasets is being sought.
Emma Pullman’s comment—explicitly naming Thomas Reuters Special Services (TRSS) and ICE—frames investor scrutiny as already underway: Pullman said she and “other investors” intend to press TRSS “for clarity on this contract.” The source also states that TRSS “provides a lot of data to ICE,” while noting TRSS is not the only contractor supplying information.
ICE, TRSS, and “Data Brokers”
The article presents ICE’s access to credit-card and transactional records as routed through data brokers and commercial vendors. It highlights TRSS as a prominent supplier of data to ICE and signals that other, unnamed contractors also feed the agency. The reporting frames this procurement as part of a changed ICE mission tied to the quoted “presidential mandate” language.
Your town's IT department is one person. Maybe.
Ransomware crews target small municipalities because nobody's watching. Nubivance gives Maine and New Hampshire towns a security program sized to a town budget.
Protect the town office404 Media, web requirements, and personal data
The source draws attention beyond government procurement to the wider ecosystem that collects personal details. It asks directly about “404 Media” — the outlet that published the story — and “what it does with your personal details required to read the article.” The piece also flags “increasing numbers of Web Sites” that gather personal information as a consequential layer in the broader data-collection chain.
Client-side scanning, big tech names, and the Carrier IQ precedent
The source claims that Apple and Alphabet have built scanning capabilities “way down deep into your phone OS,” and that Microsoft is “forcing a unique ID on to just about everyone who uses Edge, the OS or more importantly the likes of Office etc as SaaS.” It also asserts these companies are “pushing in ‘Client Side Scanning’ into the ‘User Interface’ to ‘Phone Home’ with just about everything you type or see.”
The article situates those claims against a historical example: the Carrier IQ controversy of 2011. It quotes specifics: “On November 12, 2011, researcher Trevor Eckhart stated in a post on androidsecuritytest.com that Carrier IQ was logging information such as location without notifying users or allowing them to opt out, and that the information tracked included detailed keystroke logs, potentially violating US federal law.” It further notes that “On November 16, 2011, Carrier IQ sent Eckhart a cease and desist letter,” that Eckhart “sought and received the backing of user rights advocacy group Electronic Frontier Foundation (EFF),” and that Carrier IQ “continuously denied the claims and got taken over by AT&T in 2015.” The source states the result: “a fair amount of legal action against CarrierIQ was started.”
The piece uses that history to argue the persistence of the “Client Side Scanning” and “ET Phone Home” ideas in contemporary software and services.
What this means for technologists, policymakers, and the public
- Technologists and security teams: watch commercial contracts with TRSS and similar vendors, and evaluate claims about client-side scanning and telemetry being embedded “deep” in operating systems and UIs. The source ties procurement language to operational change at ICE, suggesting technical teams will see new data flows to government customers.
- Policymakers and investors: the source records explicit investor intent—Pullman and “other investors” plan to press TRSS for clarity—indicating governance and disclosure questions will be pursued outside normal procurement channels.
- End users and publishers: the article calls attention to site-level data collection (naming 404 Media) and to “increasing numbers of Web Sites” that require personal details to read content, underlining that publisher practices are part of the wider data pipeline the story describes.
The piece closes with broader reflections embedded in the source: a cautionary line about power accumulation—“The oldest and hardest security question: how do you manage societies of more than about 150 people without organs of power which just accumulate more and more power?”—and a set of rhetorical observations about markets, “Directing Minds,” and political incentives that, in the author’s view, help explain why data and surveillance capabilities become valuable and contested. Those reflections frame the procurement dispute not as an isolated contract line item but as part of a continuing tension over who controls data, why they want it, and how they obtain it.
