Secret Law – Page 5 – Papers, Please!

May 11 2020

Will courts finally make the TSA comply with FOIA?

The tenor of questioning by the judge in a Federal court hearing last week raises hope that the Transportation Security Administration (TSA) might soon be ordered to correct some of its longest standing and most systemic violations of the Freedom Of Information Act (FOIA).

It’s no exaggeration to say that, from its creation in November 2001, the TSA has acted with complete contempt for the FOIA law and the requirements that law imposes on the TSA and all other Federal agencies. Time after time, TSA failure to comply with FOIA has delayed, complicated, or completely frustrated our research and reporting on TSA policies and procedures, and has deprived the public of the opportunity for informed scrutiny and comment on what the TSA is doing, why, and with what effects on our rights.

One chronic problem is the way the TSA responds to FOIA requests for digital records.

Provisions of the FOIA statute that went into effect as part of the Electronic FOIA Amendments Act of 1996 — years before the TSA came into existence — require that:

5 USC § 552(a)(3)(B) — In making any record available to a person under this paragraph, an agency shall provide the record in any form or format requested by the person if the record is readily reproducible by the agency in that form or format. Each agency shall make reasonable efforts to maintain its records in forms or formats that are reproducible for purposes of this section.

When it set up its FOIA office and procured software for responding to FOIA requests, the TSA completely ignored this provision of FOIA. In a display of either gross incompetence or gross bad faith, the TSA and its parent the Department of Homeland Security (DHS) appear to have entirely omitted this legal requirement for production of records in any form and format in which they are readily reproducible from their procurement specifications and criteria for evaluation of proposals. Instead, the DHS and TSA standardized on the use of cloud-based FOIAXpress software that is designed to munge all records by converting them to rasterized images embedded in PDF files, regardless of the original file format.

There’s lots of other software that was, and is, capable of redacting files in native formats. But it’s impossible for any Federal agency to fulfill its FOIA obligations with respect to the form and format of production of records by using FOIAXpress. FOIAXpress should have been summarily eliminated from consideration for any Federal agency contracts as not capable of satisfying the EFOIA requirements. No Federal agency should ever have used it.

Dec 05 2019

DHS postpones plan for mug shots of innocent US citizen travelers

Press releases issued today by US Customs and Border Protection (CBP) and Sen. Edward Markey suggest that CBP and its parent agency, the Department of Homeland Security (DHS), have cancelled or postponed, at least for now, their plans to require mug shots of all US citizens leaving, or returning to, the US.

But rather than admit that it has partially backed down or postponed some of its most offensive and intrusive plans in the face of public and Congressional outrage, CBP has sent reporters a statement alleging that our report breaking the story and others that followed contained “incorrect claims” about CBP plans:

We stand by our story.

Until this Monday, when we called attention to the official DHS/CBP notice, the officially-approved and officially-stated intent of the DHS and CBP was to propose rules requiring U.S. citizens on international flights to be photographed.

If “there are no current plans” for mandating mug shots of US citizens, that’s becuuse DHS and CBP plans changed this week in response to public and Congressional outrage and the likelihood that pursuing these plans now would derail DHS and CBP hopes for approval of its current facial recognition programs by airport authorities such as the Seattle Port Commission, which will consider the issue next Tuesday (and which had been misleadingly told by the CBP official responsible for the planned rulemaking that facial recognition would not be mandatory for US citizens).

The official DHS/CBP notice of planned rulemaking meant what it said. It was issued through a formal process of agency review. It wasn’t a typo, a mistake, or issued by a “rogue” employee.

We vigorously contest the CBP assertion that our story contained any “incorrect claim”.

Such DHS and CBP allegations, in response to truthful reporting, only further discredit the DHS and CBP, and lower whatever little credibility they may have had.

Was this a trial balloon to find out whether the DHS had finally reached the limits of our willingness to be treated like criminals whenever we fly? And if so, has the DHS partially backed off, at least for now? Maybe.

Oct 22 2019

9th Circuit upholds “no-fly” procedures & criteria

A 3-judge panel of the 9th Circuit Court of Appeals has upheld the government’s procedures and criteria for issuing “no-fly” orders against a complaint that the criteria (which are essentially “pre-crime” criteria based on predictions of future bad actions) are too vague to provide fair notice of what actions might lead to a “no-fly” order, and that the procedures do not provide the degree of procedural due process (notice of the accusations, an opportunity to see the evidence and cross-examine witnesses, etc.) required by the Constitution.

While the 9th Circuit panel left open the possibility of a challenge to the substantive grounds for a specific no-fly order, it upheld the government’s effort, in mid-litigation, to change the procedures for no-fly orders to keep challenges to no-fly orders out of U.S. District Courts and preclude any trial or adversarial or judicial fact-finding in such cases.

The 9th Circuit panel found that no-fly orders issued by the TSA under the current revised procedures are excluded from the jurisdiction of U.S. District Courts. TSA no-fly orders can be “reviewed” by a Circuit Court of Appeals only on the basis of a self-serving “administrative record” created by the TSA, and on the basis of a deferential standard that presumes the validity of the TSA’s fact-finding. The 9th Circuit panel did not address the Constitutionality of the applicable jurisdiction-stripping law, 49 U.S.C. § 46110, which is currently being challenged in the 1st Circuit in Sai v. Pekoske (originally Sai v. Neffenger).

The decision announced yesterday in Kashem v. Barr may be the worst appellate court decision against freedom of travel since the 2006 decision by the 9th Circuit Court in Gilmore v. Gonzales.

Oct 02 2019

Do I need ID to ride a train?

We’ve been trying for years to find out what the real story is with respect to ID requirements for travel by train, especially on Amtrak.

Amtrak and Greyhound ID policies and practices are of paramount importance to the mobility of undocumented people and people who, whether or not they are eligible for or have chosen to obtain government-issued ID credentials, don’t want to show their papers to government agents as a condition of exercising their right to freedom of movement.

Amtrak and Greyhound policies and practices will become even more important if the government and/or airlines further restrict air travel by people who don’t have, or don’t show, ID credentials that comply with the REAL-ID Act.

The latest responses to our requests for Federal and state public records reveal more about passenger railroad policies and practices, but still don’t give a clear answer.

What we can say at this point, based on the records disclosed to us to date, is that:

There are substantial discrepancies and contradictions between what the TSA has told Amtrak to do, what Amtrak tells its own staff about what is required, what Amtrak tells travelers about what is required and the basis for those requirements, and what Amtrak staff actually do. Those variations make it impossible to determine unambiguously what “the rules” are for Amtrak travel, or what is “required”.
Some of Amtrak’s claims, including its claim that passengers are required by the TSA to have and to show ID to travel by Amtrak, are blatant lies.
TSA Security Directive RAILPAX-04-02, cited by Amtrak in its employee manual as the basis for demanding that passengers show ID, requires Amtrak to “request” (not demand) that passengers show ID, but does not purport to require passengers to respond to such requests and does not prescribe any sanctions on passengers for failure, refusal, or inabiity to show ID.
Amtrak has instructed its staff that “If the customer responds they are 18 or older and do not have valid identification, … the Amtrak police must be notified by the quickest available means away from the customer,” but also that, “Failure to possess the proper photo identification is not, by itself, sufficient reason to have the customer removed from the train.” Amtrak has not yet responded to our FOIA request for Amtrak Police policies and staff directives for what to do in such cases.
Although Amtrak is unquestionably an instrumentality of the Federal government, and transportation by Amtrak is unquestionably a Federal government activity, the list of ID credentials deemed acceptable by Amtrak does not correspond to the list of forms of ID deemed by the DHS to be acceptable for “Federal purposes” pursuant to the REAL-ID Act of 2005. Amtrak says it accepts several forms of ID that do not comply with the REAL-ID Act. None of Amtrak’s ID policies, procedures, or staff directives disclosed to date mention the REAL-ID Act or when or how it might be implemented by Amtrak, although records of such policies or of discussions related to them would be responsive to soem of our pending FOIA requests.

Where does this leave undocumented long-distance travelers, including those who turn to Amtrak as a government-operated common carrier of last resort?

Sep 04 2019

US government blacklisting system is unconstitutional

In an opinion issued late today in Alexandria, VA, US District Court Judge Anthony Trenga has upheld the complaint by 23 victims of US government blacklisting that the system pursuant to which the government has designated them as “suspected terrorists” on the basis of secret algorithms applied to secret datasets, without notice or an opportunity to contest any allegedly “derogatory” information, does not provide those who are stigmatized, and whose stigmatized status is broadcast to tens of thousands of law enforcement and other government agencies and private entities around the world, with the procedural due process required by the US Constitution.

This decision is one of the most fundamental victories for the rule of law since 9/11.

According to today’s opinion, it is undisputed that the DHS and FBI define anyone who has been arrested or charged with an offense related to terrorism as a “known” terrorist, even if they have been acquitted of that charge. In other words, the DHS and FBI think that what is “known” is what they believe, not what judges or juries have found the facts to be. That presumption that by definition their secret judgments are more reliable than judicial fact-finding pretty much sums up why this decision is correct, why it is so important, and why it should be upheld if, as seems a near certainty, the government appeals.

None of the plaintiffs have even been arrested, much less convicted, for any criminal offense, terrorist or otherwise. The plaintiffs include, among others, several infants whom the government has apparently blacklisted as “suspected terrorists”. But even though the government will neither confirm nor deny that anyone is or is not, or has or has not been, included in the “Terrorist Screening Database” (TSDB), the court found that the plaintiffs have demonstrated sufficient basis for their belief that they have been blacklisted.

The government calls this database and decsion-making system a “watchlist”, but it is really a blacklist intended and used to determine adverse consequences for individuals.

The “No-Fly List” is only a subset of the TSDB, and not being allowed to fly is only a subset of the consequences of blacklisting detailed in the plaintiffs’ submissions to the court and the government’s admissions during discovery and depositions. The TSDB is used as the basis for a plethora of decisions, as the plaintiffs have experienced, from whether to have them arrested at gunpoint when they try to cross land borders to whether to interrogate them for hours about their religious beliefs, seize their electronic devices for copying and forensic analysis of the data stored on them, deny them public or private-sector jobs, or close their bank accounts and deny them other fincial services.

The government’s use of secret criteria, secret datasets, and guilt by association as the basis for secret decisions — communicated to tens of thousands of other decision-makers, but not to those who have been blacklisted — resembles the worst of McCarthyism, just with “terrorist sympathizer” or (literal) “fellow traveler” substituted for “Communist sympathizer” or (ideological) “fellow traveler”.

Aug 05 2019

Questions about the REAL-ID Act

Fragmentary and jumbled records related to the REAL-ID Act of 2005 released by the US Department of Homeland Security in response to one of our Freedom Of Information Act (FOIA) requests don’t reveal much about DHS policy, but do provide a glimpse of DHS practices and plans.

The DHS has been threatening to harass, interfere with, or bar access to facilities or passage through checkpoints (including, but not limited to, those at airports) to people who don’t have, don’t carry, or don’t show ID; show ID that the DHS doesn’t deem compliant with the REAL-ID Act; or show ID issued by states or territories that the DHS deems insufficiently compliant with the REAl_ID Act.

These threats to deny equal rights to residents of noncompliant states and territories have been central to the DHS campaign to extort compliance from state and territorial officials reluctant to upload their residents’ data to an outsourced, privately-held national ID database.

But what sort of enforcement problem, at what scale, is this likely to pose for the DHS and those collaborators carrying out its REAL-ID directives? How many people will be affected, at what sorts of facilities and locations, in what circumstances? Inquiring minds want to know, including opponents of the REAL-ID Act like ourselves, but also including officials at DHS headquarters trying to devise a workable REAL-ID enforcement plan.

Jul 25 2019

Can you “opt out” of TSA groping or virtual strip-searches?

Two recent decisions — one an administrative decision by the TSA, and the other a judicial decision by the 11th Circuit Court of Appeals — have dealt with, but failed to resolve, the question of whether, in the face of unpredictable demands for more intrusive searches, an airline passenger can “opt out” if they decide they would rather abandon their attempt to board a flight than submit to whatever search TSA or contractor checkpoint staff demand.

The TSA has withdrawn its proposed administrative fine against Jonathan Cobb, a passenger who, when selected for a pat-down (manual groping of his body, including his genitals, by which he had previously been traumatized), chose to abandon his attempt to fly and left the airport. That’s good, but sets no legally binding precedent.

Meanwhile, the 11th Circuit Court of Appeals has dismissed a petition filed by Jonathan Corbett seeking judicial review of the TSA’s policy of requiring selected passengers to submit to imaging of their bodies by virtual strip-search machines. That’s bad, but at least the decision was based solely on whether Mr. Corbett could expect to be selected for this sort of search, and left undecided whether these searches are Constitutional.

These decisions leave the law unclear in practice — even if the Constitution seems clear — as to whether or when an airline passenger can opt out of which sorts of searches.

How far can the TSA and its contractors legally go? How can tell if they are going too far? And when, if ever, can you “opt out” or say no to an escalated search?

Mar 13 2019

US government blacklisting system is unconstitutional, victims say

The Terrorist Screening Database (TSDB) “fails to provide constitutionally sufficient procedural due process,” according to a motion for summary judgment filed this week in a lawsuit brought by people who have been placed on the TSDB blacklist.

We’ve been following this case, Elhady v. Kable, since it was filed in 2016. Discovery and depositions taken in the case, as well as leaks by whistleblowers while the case has been pending, have revealed an unprecedented level of detail about the operation of the blacklisting system, the inter-agency “Watchlisting Advisory Council” which overseas the blacklist, and the dissemination of blacklist information.

The TSDB is described euphemistically by the US government as a “watchlist”, but in reality it’s a blacklist. Individuals — including infants and children as well as adults, and US citizens and residents as well as non-residents — are subjected to adverse government and private action by having the government place them on the TSDB blacklist and disseminate this stigmatizing designation — with the intent that the designation will be used against listed individuals — to Federal, state, and local government agencies and private entities.

The government has refused to disclose the criteria for TSDB listings, but has conceded that being listed does not require suspicion of having committed or intending to commit any crime. Listings are determined through a secret, extrajudicial administrative process, without those being blacklisted being notified or having any opportunity, before or after the fact, to know whether or why they are being blacklisted, what the basis is for their blacklisting, or what the evidence against them is.

The case has survived multiple attempts by the government to have it dismissed on jurisdictional and procedural grounds and to avoid discovery and depositions. Now the plaintiffs’ motion for summary judgment that the TSDB is unconstitutional is scheduled for oral argument on April 4, 2019, before US District Court Judge Anthony Trenga in Alexandria, VA.

Jan 09 2019

How many times will the DHS cry wolf on REAL-ID?

The last time we checked in on the status of the seemingly endless game of “chicken” being played by the US Department of Homeland Security with its threats to start harassing air travelers who reside in states the DHS deems insufficiently “compliant”, every state and territory had been given another “extension” of time to demonstrate commitment to compliance until at least January 10, 2019.

Since then, the DHS, in its standardless administrative discretion, has announced further extensions until at least April Fools Day, 2019 (for the US Virgin Islands), for every state and territory except California and Guam.

But as of today, the DHS website says that, “California has an extension for REAL ID enforcement, allowing Federal agencies to accept driver’s licenses and identification cards from California at Federal facilities, nuclear power plants and federally regulated commercial aircraft until January 10, 2019.”

As of this morning, with the “deadline” less than 48 hours away, we got the following response to our questions about this from a spokesperson for the California DMV:

The State of California has been working for the better part of a year to be deemed compliant with the REAL ID act, unfortunately due to a lack of response on the part of the Federal Government with the ongoing shutdown there has been no final confirmation.

So was that a real deadline for REAL-ID in California?

Is the DHS really prepared to have TSA checkpoint staff — working for indefinitely deferred pay — start trying to carry out time-consuming “ID verification procedures” for everyone who shows up at an airport checkpoint with a California drivers’ license or ID, starting the day after tomorrow?

The answer turns out to be, “No.”

The DHS and TSA have blinked yet again in the face of insufficient state “compliance”.

We’ve just received the following updated statement from the DMV:

The California DMV has confirmed with the Department of Homeland Security (DHS) that they will be granting California an extension to April 1, 2019. Due to the furlough, the letter might not arrive until tomorrow and DHS will likely not be updating their website until the furlough ends. All driver licenses will remain valid and can continue to be used for federal purposes.

And this from a spokesperson for the TSA:

I recently learned from DHS that California’s extension has been extended through April 1, 2019…. Updates to their website are underway.

California doesn’t actually comply with the REAL-ID Act. That would require uploading data about all California drivers’ licenses and ID cards to the SPEXS national ID database, which California hasn’t done and which would probably violate multiple provisions of California’s state constitution. But DHS certifications and extensions are discretionary, and need not be based on any specific criteria or on actual compliance.

There’s still no public word about Guam, the extension for which is also scheduled to expire tomorrow.

“Phase 4b” of REAL-ID Act enforcement at airports supposedly started on January 22, 2018. Since then, the only state or territory where the DHS has let a REAL-ID extension lapse, even temporarily, has been American Samoa, for which another extension has now been granted until October 10, 2019. We’re still waiting for any response to our FOIA request for records of what happened to American Samoans who tried to fly during the period last year when the extension had lapsed.

Jan 04 2019

Issues for the revitalized Privacy and Civil Liberties Oversight Board

With its recent revival, the Federal government’s Privacy and Civil Liberties Oversight Board (PCLOB) has a chance to take a fresh look at how far the USA has gone since 9/11 in implementing a combination of “pre-crime” policing (à la Minority Report) and “social credit scoring” integrated with commercial service providers (à la China) as a means of control of what people can and cannot do, and where they can and cannot go.

The PCLOB didn’t have a quorum since early 2017, and was down to only one member. But three new members were confirmed in October 2018. An Executive Director – who may end up with longer-term influence than the members of the Board, especially given that the new members weren’t appointed and confirmed until just three months before one of their terms is scheduled to end – is currently being hired. Civil libertarians able to obtain a security clearance and willing to relocate to DC are encouraged to apply.

>What should the PCLOB focus on, with its limited time and resources? The PCLOB is an advisory committee with neither legislative nor prosecutorial authority. The best use it can make of its limited mandate is to ask hard questions and raise issues that Federal agencies won’t otherwise acknowledge or address.

The TSA and DHS were created in haste after 9/11 without consideration of the privacy and civil liberties implications of their new activities, many of which have never been explicitly approved by Congress. The reactivation of the PCLOB after the latest hiatus is a chance to take a fresh look at the big picture of what these agencies are doing, and what this means for privacy and civil liberties. It might be tempting to focus on “emerging” threats, but the first priority should be to assess the DHS surveillance and control systems that are already in place:

Conversion of state licensing of motor vehicle operators into a national ID system. More than a decade after Congress enacted the REAL-ID Act of 2005, we are entering the endgame of DHS efforts to pressure states into participating in an outsourced, privately-operated, national ID database created to enable compliance with the REAL-ID Act. SPEXS already includes records sourced from states about more than 50 million Americans, but is not subject to any direct government control and has never been the subject of any publicly-disclosed review of its implications for privacy and civil liberties.
Mass surveillance and permission-based predictive control of movement and travel. Congress has never debated whether air travelers should be required to identify themselves,whether the government should keep histories of innocent citizens’ movements (compiled from commercial airline reservations for common carrier travel, license plate readers for travel by private vehicle, and facial recognition for pedestrian movement), or whether existing judicial mechanisms for restricting the right to travel and movement through injunctions or restraining orders should be replaced with secret, extrajudicial administrative prior restraint and similar orders. How has travel been transformed from a right to a privilege exercised only by government permission? How does this implicate the 1st Amendment right to assemble and the right of freedom of movement recognized by international human rights treaties? How widely, and with what implications for privacy and civil liberties, has the precedent set by real-time “pre-crime” predictive control of travel expanded to other activities and transactions?
Suspicionless dragnet administrative searches. Today, the most common hands-on interaction between a Federal agent and a person not suspected of any crime is a TSA pat-down. But there’s never been any comprehensive review of the legality or the implications for privacy and security of the proliferation of suspicionless administrative searches since the creation of the DHS and TSA: security theater in airports, warrantless searches at internal checkpoints (domestic airports, CBP roadblocks on roads that don’t cross the US border, and attempts to claim the right to impose searches on the public in other forms of transportation.

There’s much more that we and others could say about each of these issues, if the PCLOB choses to consider them. But the first challenge for the PCLOB is whether it will tackle these big-picture issues.

Papers, Please!

The Identity Project