ICE

  • |

    Canceling the Conveyor Belt After the Invoice Prints

    ByPhil McCracken

    ICE is “ending” the WEXMAC-style contracting approach, which is a lovely PR hobby—right up until you remember the whole point of an invoice is that it arrives whether you keep the vehicle or ditch it.

    I’m Phil McCracken, Capitol Hill corruption reporter, and I have watched this specific conga line before: use a DoD ordering vehicle to speed-run procurement, let the paperwork conveyor belt clatter forward, and then—once the problems get loud—declare the route “over” like that rewinds the receipts.

    Here’s the contradiction the public can’t unsee. ICE officials, including Mullin, say the WEXMAC approach is being ended. But GAO reported planning/acquisition problems tied to the Camp East Montana contract process, and waste connected to paying for services based on maximum capacity even when detainees weren’t present—i.e., taxpayers got charged for capacity math that didn’t match reality.

    And then the “fix” arrives the way a fire alarm arrives: after the kitchen is already featured in the news. The record described ICE terminating the initial contract and moving to a new operator. Operationally, sure. Accountability-wise? That’s not the same thing as undoing the billing logic GAO flagged.

    You can cancel the conveyor belt. You can’t cancel the meal tickets once the printing starts.

  • |

    There’s No Protester Database (It’s Just the Records Cabinet, Actually)

    ByHolden McGroin

    ICE keeps telling the public it doesn’t maintain a “protester database,” which is adorable in the way a “no carbs” candy label is adorable. My favorite kind of privacy is the kind that comes with a filing system you only get to call “not that.” In the latest surveillance panic swirl, reporting around an April 21 letter to Congress and an Feb. 3, 2026 referenced official document is basically the corkboard’s way of going: follow the thread, but check the knot.

    Here’s the contradiction audit: in the correspondence/reporting being discussed, the concern isn’t hypothetical. The official materials describe collecting and maintaining identifying and situational information about people connected to protest activity—even when they aren’t arrested. So when the reassurance pitch is “don’t worry, it’s not a database,” the word choice starts looking less like a privacy policy and more like packaging. Because the justifications keep landing on familiar government drumbeats like “officer safety” and “facility security,” which is bureaucratic for “we can keep the records as long as we call it for the vibes.”

    And who benefits from the fog machine? Not protesters. Not the neighbors who just got dragged into the group chat because someone said “watch out, they’re building a list.” The benefit goes to the accountability dodge: if the public’s worried about surveillance, you respond by arguing about whether the cupboard is a database or a cabinet. It’s the bureaucratic equivalent of a magician announcing, “Nothing is being pulled from hats,” while politely producing an item from a different drawer.

    This is how normal people end up panicking anyway: a real public-institution data practice gets translated into a meme-sized question of wording, and then everyone fights about the wording while the underlying structure remains. If the reassurance depends on semantics—“it’s just records”—the right takeaway isn’t “stop asking.” It’s: demand clear, plain transparency about what’s collected, retained, and why, because if you’re still being identified and cataloged, the word “database” isn’t the only thing doing the work.

End of content

End of content