Apple says DOJ safety claims drove its ICEBlock removal. Raskin wants a list

Apple told the House Judiciary Committee that it removed ICEBlock and similar apps from the App Store in early October 2025 after the US Department of Justice raised officer-safety concerns. On September 29, 2026, Rep. Jamie Raskin, the committee's ranking member, published a reply that disputes the reasoning and asks Apple for a list of every app it has pulled at the federal government's request.

After the DOJ raised concerns, Apple cited a content rule

Apple's explanation came in a July 22 letter to Raskin. His September 28 response summarizes it: the removal "was prompted by two factors," the September 24, 2025 attack on a Department of Homeland Security building in Dallas, and "representations the Department of Justice (DOJ) made to Apple after the Dallas incident."

Raskin's letter quotes Apple directly: "in the wake of the fatal Dallas shooting, the U.S. Department of Justice expressed serious concerns to Apple that ICEBlock posed a threat to the safety of federal officers." AppleInsider reports that Apple told Raskin the apps broke App Store policy by providing "precise location information about ICE officers."

The rule Apple used dates from the removal notice. According to The National, Apple told the developer the app "violates Guideline 1.1.1 because its purpose is to provide location information about law enforcement officers that can be used to harm such officers individually or as a group." 9to5Mac reports that Apple had approved ICEBlock in April 2025.

Guideline 1.1.1 in Apple's App Review Guidelines covers "defamatory, discriminatory, or mean-spirited content" about targeted groups, "particularly if the app is likely to humiliate, intimidate, or harm a targeted individual or group." Apple's removal notice echoes that last clause. The published text does not mention law enforcement.

Raskin says the Dallas link does not hold

Raskin writes that "there is no evidence" the Dallas shooter "may have used ICEBlock in the lead up to the attack," which he quotes as Apple's phrasing. He says the suspect "appears to have searched for" tracking apps in the App Store but "did not need a tracking app to locate the fixed position of a government building," and, according to the committee's release, reportedly found the address with an app that comes standard on Apple devices.

Apple's account and Raskin's account conflict on this point. Neither letter settles it.

Two requests, no deadline

First, Raskin asks Apple to "identify for the Committee the full list of apps that Apple has removed from the App Store after you received requests to do so from the federal government." Second, he asks for Apple's "own independent review" of those removals "to ascertain if they do, in fact, violate your terms of service," to start "as soon as practicable." Neither request has a fixed deadline.

The committee's release says the probe began in February 2026 with a letter to then-Attorney General Pam Bondi and widened to Apple and Google in June. The National reported in October 2025 that Google also removed similar apps from Google Play.

What Apple's transparency report counts

Apple does publish government takedown numbers. Its semiannual Transparency Report says App Store takedown requests go in a separate report "that includes data showing takedown demands by government entity and law cited."

The 2025 App Store Transparency Report lists 2,045 apps removed under government takedown demands. The US line reads 39. A footnote says those are "the 39 ByteDance apps" Apple withheld to comply with a US law on foreign-adversary-controlled apps, restored on February 13, 2025. It also lists 3,929 US appeals of app removals and 88 US restorations, noting most appealed removals involve illegality or fraud.

Why a build studio cares

Put those two documents side by side. The 39 US government takedowns are all ByteDance. ICEBlock, which Apple says it pulled after DOJ representations, went out as a guideline 1.1.1 violation, so on our reading of the published report it is not in the government column. The report does not say how Apple classified it. If that reading is right, it is the gap a full list from Apple would close: a government concern that arrives as a safety claim, gets enforced as a content rule, and does not appear in the government count.

For a product that ships only through the App Store, that is one point of removal with one appeal path and no public record of who asked. In the EU, where a court upheld Apple's gatekeeper status in July, the Digital Markets Act makes Apple allow rival app marketplaces, so a second route onto iPhones exists there. When we map vendor vanish-risk in a software audit, distribution sits next to domain and hosting control: who can remove this, on whose request, and what the fallback is.

Next step: read Raskin's September 28 letter next to Apple's 2025 App Store Transparency Report. If your product reaches users through a single app store and you want that dependency mapped, write to us at hello@gattyworks.com.