DHS Ousted Three Career Privacy Officers Who Said the New Orders Were Illegal.
On January 20, 2025, Roman Jankowski was sworn in as DHS Chief Privacy Officer — Heritage Foundation's Oversight Project senior counsel, Day One appointee. Within the year, his office had issued directives ordering career compliance staff to do three things federal lawyers say have no legal basis: mark all future Privacy Threshold Analyses FOIA-exempt, treat routine compliance forms as legally privileged, and relabel completed, signed compliance documents as “drafts” so they could not be released under the Freedom of Information Act.
Three career CBP privacy officers objected in writing. They said the orders were illegal. They were reassigned — not fired, because the civil service termination process is slow and documentable, and reassignment is faster and harder to challenge. The trigger for all of it was a single lawful FOIA release: a career officer had released a Privacy Threshold Analysis to 404 Media documenting that DHS's Mobile Fortify facial recognition app — used more than 100,000 times since launch, including at public protests — had been deployed without completing the Privacy Impact Assessment its own compliance document said was legally required.
That document was the only public record that Mobile Fortify existed. The new directives were designed to make sure no document like it ever reached the public again. That is the story — not a bureaucratic personnel dispute, but a systematic effort to hide a surveillance program that career officials inside DHS had already flagged as operating without its required legal foundation.
- 100,000+Mobile Fortify deployments since launchCBP/ICE facial recognition app used more than 100,000 times — including at public protests — without completing the required Privacy Impact Assessment or System of Records Notice. Per Wired/EPIC, Biometric Update, and NBC News reporting.
- 3Career CBP privacy officers reassignedThree career officials objected in writing to orders they described as illegal. All three were reassigned rather than terminated — the standard civil-service retaliation workaround that avoids the procedural record created by formal termination.
- Dec. 2025Date of the Jankowski directivesDHS Chief Privacy Officer Roman Jankowski issued orders to relabel completed compliance documents as 'drafts,' categorically exempt all Privacy Threshold Analyses from FOIA, and treat routine compliance forms as legally privileged. Per Wired/EPIC.
- 42,695Times IRS shared taxpayer data with DHS illegallyFederal Judge Amit Mehta (D.D.C.) ruled in February 2026 that the IRS violated federal law 42,695 times by sharing taxpayer data with DHS — a concurrent data-sharing pattern judges and privacy experts placed in the same constitutional frame as the Mobile Fortify deployments.
- 1 weekFrom Warner-Kaine letter to DHS IG audit launchSenators Warner (D-VA) and Kaine (D-VA) wrote DHS demanding a surveillance audit on January 29, 2026. DHS IG Joseph Cuffari launched the formal biometric audit on February 6, 2026.
- Jan. 20, 2025Day Roman Jankowski was sworn inHeritage Foundation Oversight Project senior counsel sworn in as DHS Chief Privacy Officer and Chief FOIA Officer on inauguration day. The December 2025 directives that triggered the reassignments came within his first year.
Mobile Fortify is a facial recognition app deployed by CBP and ICE. It runs queries against biometric databases — matching faces captured on agents' phones against enrolled records and watch lists. It has been used more than 100,000 times since launch, including, per NBC News, against individuals photographed at public protests who had no enforcement contact with immigration officers.
Under the E-Government Act of 2002 and the Privacy Act, any federal system that collects, uses, or disseminates personally identifiable information must complete two documents before going live: a Privacy Impact Assessment (PIA) and a System of Records Notice (SORN). Mobile Fortify completed neither. Its own internal Privacy Threshold Analysis — the first-stage compliance document that triggers the PIA requirement — said a full PIA was legally required. That PIA was never completed. The app was deployed anyway.
The existence of Mobile Fortify was unknown to the public until a career FOIA officer lawfully released that PTA — the internal document acknowledging the missing compliance work — to 404 Media. That release was the correct and legal response to a valid FOIA request. It was also the event that triggered Jankowski's December 2025 directives.
ICE and CBP deployed the Mobile Fortify facial recognition app more than 100,000 times since launch — including at public protests — without completing the Privacy Impact Assessment their own Privacy Threshold Analysis said was legally required.
“This policy change is illegal. There is nothing in the FOIA statute — or any other statute — that allows the agency to categorically withhold Privacy Threshold Analyses.”
Attorney Ginger Quintero-McCall — WIRED reporting / EPIC mirror
Jankowski's December 2025 directives required three things. The first: all future Privacy Threshold Analyses were to be marked FOIA-exempt from the moment of creation. FOIA exemptions are defined by statute — 5 U.S.C. § 552 lists nine of them. None of them permits a blanket agency declaration that an entire category of compliance documents is exempt from disclosure. The directive had no legal citation because no applicable legal citation exists.
The second: routine compliance forms — the bureaucratic paperwork that documents an agency's adherence to its own privacy policies — were to be treated as legally privileged. Attorney-client privilege and deliberative-process privilege are the two FOIA exemptions most commonly invoked for agency documents. Neither covers routine compliance forms that are not legal advice and do not reflect pre-decisional agency deliberation in any sense recognized by case law.
The third is the one that crosses from aggressive legal interpretation into something records management lawyers call records falsification: completed, signed compliance documents — forms that had gone through the compliance workflow and bore the signatures of the officials who approved them — were to be relabeled as “drafts.” Draft documents are routinely withheld under the deliberative-process exemption. A completed signed document is, by definition, not a draft. Relabeling it as one is not a legal interpretation — it is altering a federal record.
1. Categorical FOIA exemption for all Privacy Threshold Analyses. No legal basis in 5 U.S.C. § 552 or any other statute. PTAs are compliance documents, not deliberative pre-decisional materials. The directive had no legal citation.
2. Routine compliance forms treated as legally privileged. Attorney-client and deliberative-process privilege do not cover routine compliance paperwork. No applicable case law supports the categorical designation. Same problem: no legal citation.
3. Completed, signed compliance documents relabeled as “drafts.” This is not a FOIA interpretation. This is altering an existing federal record. The documents had been completed, approved, and signed. Relabeling them “draft” after the fact to trigger a withholding exemption is what privacy attorneys quoted by Wired described as the most legally indefensible of the three directives.
The trigger event: A career CBP FOIA officer had lawfully released a Mobile Fortify Privacy Threshold Analysis to 404 Media. That release exposed, for the first time publicly, that Mobile Fortify had been deployed at scale without completing its required Privacy Impact Assessment. The December 2025 directives were issued within weeks of that release.
Roman Jankowski, who came from the Heritage Foundation's Oversight Project, was sworn in as DHS Chief Privacy Officer on January 20, 2025. Within months, his office issued directives to relabel completed compliance documents as “drafts” to prevent FOIA disclosure.
On January 20th, 2025, Roman Jankowski was officially sworn in as the Chief Privacy Officer and Chief FOIA Officer. We look forward to the leadership and expertise he will bring to these critical roles.
Three career CBP privacy officers objected in writing to the directives. They were not fired. Federal civil-service employment protections make terminating a career officer for raising a legal objection procedurally slow, documentable in a Merit Systems Protection Board record, and frequently reversed on appeal. Reassignment — moving an officer to a different position, often one with diminished responsibilities, access, and influence — is the standard workaround.
Reassignment is harder to challenge because it does not technically end employment, does not trigger the formal adverse-action procedures that protect against retaliatory termination, and in the short term removes the objecting officer from the unit — which is the immediate operational goal. The GAO investigation requested by Rep. Bennie Thompson and Sen. Gary Peters is specifically examining whether these reassignments constitute whistleblower retaliation under the Whistleblower Protection Act and DHS-specific whistleblower statutes.
The same pattern appeared across two agencies in the same month. DOJ Civil Rights Division Chief FOIA Officer Kilian Kagle resigned in April 2026 rather than comply with orders to share voter-roll data with DHS. Where the CBP officers were reassigned, Kagle resigned — but the mechanics were identical: legal objection, agency pressure, removal of the objector.
Senators Mark Warner (D-VA) and Tim Kaine (D-VA)wrote DHS on January 29, 2026 demanding a full audit of the department's surveillance technology use. The letter named Mobile Fortify explicitly, cited the absence of a completed Privacy Impact Assessment and System of Records Notice, and demanded a response within 30 days.
One week later — February 6, 2026 — DHS Inspector General Joseph Cuffari announced a formal audit of DHS biometric data collection and use. The audit scope covers Mobile Fortify specifically and the completeness of required privacy compliance documentation across DHS biometric programs.
Separately, Rep. Dan Goldman (D-NY), Sen. Ron Wyden (D-OR), and Rep. Nydia Velázquez (D-NY) demanded answers on ICE's use of Palantir-developed technologies used in coordination with Mobile Fortify deployments. Former DHS Secretary Kristi Noem (R) — fired by Trump on March 5, 2026 — held her position during the period when both the Mobile Fortify deployments and the Jankowski directives were issued.
NBC News reported the use of Mobile Fortify at protest locations. The footage below is the most detailed public documentation of how the app is used in the field — and why the absence of a Privacy Impact Assessment matters for anyone who has attended a demonstration, rally, or public gathering within range of an ICE or CBP agent.
Roman Jankowski— DHS Chief Privacy Officer and Chief FOIA Officer. Sworn in January 20, 2025. Prior position: Senior Counsel, Heritage Foundation's Oversight Project. Issued the December 2025 directives that triggered the officer reassignments.
Kristi Noem (R) — Former DHS Secretary. Fired by Trump on March 5, 2026. Held the position during both the Mobile Fortify deployments and the Jankowski directives. Has not addressed either publicly.
Joseph Cuffari — DHS Inspector General. Launched the formal biometric-surveillance audit on February 6, 2026 following the Warner-Kaine letter.
Kilian Kagle — DOJ Civil Rights Division Chief FOIA Officer. Resigned April 2026 rather than comply with orders to share voter-roll data with DHS. Same pattern, different agency: legal objection followed by removal.
Sen. Mark Warner (D-VA) and Sen. Tim Kaine (D-VA) — Wrote the January 29, 2026 letter demanding a DHS surveillance technology audit; their letter directly preceded the IG audit launch.
Rep. Bennie Thompson (D-MS) (House Homeland Security Ranking Member) and Sen. Gary Peters (D-MI) (Senate Homeland Security Ranking Member) — Requested the GAO investigation into DHS whistleblower retaliation.
This policy change is illegal. There is nothing in the FOIA statute — or any other statute — that allows the agency to categorically withhold Privacy Threshold Analyses.
ICE and CBP are doing a fantastic job protecting our border and our country. The fake news media doesn't want you to know it, but our law enforcement officers are using every available tool to keep criminals and illegal aliens out. We will NEVER apologize for keeping Americans safe. That is what we were elected to do!
Paraphrased commentary · not a verbatim post
Paraphrased composite of Trump's recurring immigration-enforcement Truth Social posts. Trump has not specifically addressed the Mobile Fortify PIA compliance gap or the privacy officer reassignments. The broader enforcement posture is documented via the @realDonaldTrump feed.
Three CBP privacy officers were reassigned after objecting to what they characterized as orders to falsify government records. The reassignment — rather than termination — is the standard civil service retaliation workaround that is harder to challenge legally.
- WIRED / EPIC mirror (primary — Mobile Fortify + privacy officer reassignments)Wired/EPIC reporting confirmed three career CBP privacy officers were reassigned after objecting to DHS Chief Privacy Officer Roman Jankowski's December 2025 directives: (1) categorically mark all future Privacy Threshold Analyses FOIA-exempt, (2) treat routine compliance forms as legally privileged, (3) relabel completed, signed compliance documents as 'drafts' to prevent disclosure. The trigger: a career FOIA officer had lawfully released a Mobile Fortify PTA to 404 Media — the only public record of the app's existence.https://epic.org/wired-dhs-ousts-cbp-privacy-officers-who-questioned-illegal-orders/
- NPR — DOJ Kilian Kagle resignation (voter data / DHS sharing)Kilian Kagle, DOJ Civil Rights Division Chief FOIA Officer, resigned in April 2026 rather than comply with orders to share voter-roll data with DHS. His resignation followed the same pattern as the CBP privacy officers: internal refusal on legal grounds, followed by removal rather than engagement with the legal objection.https://www.npr.org/2026/04/03/nx-s1-5768455/privacy-doj-dhs-voter-data
- Warner / Kaine Senate letter (Jan. 29, 2026)Senators Mark Warner (D-VA) and Tim Kaine (D-VA) wrote DHS demanding a full audit of its surveillance technology use, including Mobile Fortify. Letter cited the deployment of facial-recognition tools at protests and public gatherings without completed Privacy Impact Assessments or System of Records Notices as required under the E-Government Act of 2002 and the Privacy Act.https://www.warner.senate.gov/public/index.cfm/2026/1/warner-kaine-demand-investigation-into-dhs-use-of-surveillance-technology
- DHS IG audit launch — Kaine press release (Feb. 6, 2026)DHS Inspector General Joseph Cuffari launched a formal biometric-surveillance audit on February 6, 2026 — one week after the Warner-Kaine letter. The audit covers DHS biometric data collection, retention, and use, including Mobile Fortify deployments and the completeness of required Privacy Impact Assessments.https://www.kaine.senate.gov/press-releases/following-warner-kaine-pressure-dhs-inspector-general-launches-audit-of-dhs-data-privacy-abuses
- Biometric Update — Mobile Fortify oversight gaps (December 2025)Biometric Update documented in December 2025 that ICE and CBP's Mobile Fortify facial recognition app was built on a 'paper-thin' oversight foundation: no completed Privacy Impact Assessment, no System of Records Notice, and an internal Privacy Threshold Analysis that had not been finalized through the required compliance chain before the app was deployed at scale.https://www.biometricupdate.com/202512/ices-use-of-cbp-biometric-surveillance-app-built-on-paper-thin-oversight
- NBC News — Mobile Fortify protest deploymentNBC News reporting confirmed ICE agents deployed Mobile Fortify to run facial recognition on individuals photographed at public protests, including at demonstrations where attendees had no immigration enforcement contact. The app ran 100,000+ queries since launch without the required Privacy Impact Assessment being completed.https://www.nbcnews.com/tech/security/ice-agent-facial-recognition-video-protest-movile-fortify-photo-rcna257331
- Goldman / Wyden / Velázquez letter — Palantir / ICE surveillanceRep. Dan Goldman (D-NY), Sen. Ron Wyden (D-OR), and Rep. Nydia Velázquez (D-NY) demanded answers on ICE's use of Palantir-developed technologies used in coordination with Mobile Fortify deployments, including the absence of required Privacy Impact Assessments across the surveillance stack.https://goldman.house.gov/media/press-releases/goldman-wyden-velazquez-demand-answers-ice-use-palantir-developed-technologies
- POGO — GAO whistleblower retaliation probeThe Project on Government Oversight confirmed the Government Accountability Office launched an investigation into DHS's treatment of whistleblowers, including the three CBP privacy officers reassigned after objecting to Jankowski's directives. The GAO investigation was requested by House Homeland Security Ranking Member Rep. Bennie Thompson and Senate Homeland Security Ranking Member Sen. Gary Peters.https://www.pogo.org/investigates/dhs-treatment-of-whistleblowers-under-investigation-by-gao
- DHS — Roman Jankowski profileOfficial DHS biography confirms Roman Jankowski was sworn in as DHS Chief Privacy Officer and Chief FOIA Officer on January 20, 2025. His prior position was Senior Counsel at the Heritage Foundation's Oversight Project, which coordinates FOIA litigation strategy and government transparency litigation.https://www.dhs.gov/person/roman-jankowski
- 404 Media — Mobile Fortify PTA (the document that triggered the cover-up)404 Media was the recipient of the lawful FOIA release that triggered the Jankowski directives. The released Privacy Threshold Analysis was the first and only public document confirming Mobile Fortify's existence and noting that a full Privacy Impact Assessment was required but had not been completed. DHS subsequently moved to prevent future similar releases.https://www.404media.co/mobile-fortify-cbp-facial-recognition-privacy/
- Federal Judge Mehta — IRS / DHS taxpayer data ruling (Feb. 2026)In a February 2026 ruling, U.S. District Judge Amit Mehta (D.D.C.) found that the IRS had violated federal law 42,695 times by sharing taxpayer data with DHS. The ruling formed part of the broader constitutional challenge to DHS surveillance and data-collection practices.https://www.courtlistener.com/docket/dhs-irs-taxpayer-data-sharing/

