The Volokh Conspiracy
Mostly law professors | Sometimes contrarian | Often libertarian | Always independent
"Geofence Warrants Are the Future (and That's a Good Thing)"
From Prof. Jane Bambauer (Arizona).
Jane Bambauer, a leading information law scholar (both on the First Amendment and the Fourth Amendment side), wrote up these thoughts on the recent geofencing case, on which Orin had also written; I'm delighted to be able to pass them along:
Last week, Judge Lauck of the Eastern District of Virginia handed down the first thorough Fourth Amendment analysis of the police investigation process known as "geofencing." Judge Lauck found that the geofence warrant at issue in the case was unconstitutional. Moreover, the infirmities she found would be very difficult to cure in most police investigations where geofenced data might be helpful.
Civil liberties organizations have praised the opinion, but like Orin Kerr, I found the opinion confusing and poorly reasoned in its handling of key Fourth Amendment precedent. So I'll take this opportunity to add a few additional doctrinal critiques to Orin's excellent summary. But I'll end with a less wonky, more big picture plea: I hope the courts do not expand the Fourth Amendment to impede technological tools like geofences that help police conduct more accurate, less discretion-based initial investigations. With appropriate constraints, geofences and other "suspectless search" technologies can be an integral part of police modernization and reform.
Quick Summary
U.S. v. Chatrie concerned the investigation of a bank robbery. After investigating a couple leads using traditional policing methods without success, the detective working the case submitted a "geofence warrant" (subpoena) to Google to request deidentified information about the geolocation of any devices that came within 150 meters of the center of the bank during a one hour time span. (Note that the detective had some confidence that Google would have this information because bank surveillance footage showed that the bank robber covered his face using his … wait for it … Android smart phone.)
Google's response team found that 19 devices fit the parameters of the geofence request. This was stage one. After some back-and-forth about what's supposed to happen next (he initially requested an additional hour's worth of geolocation data and identifiers for all 19 phones), the detective pared down his request to just 9 devices and received an extra hour's worth of location data about those nine. This marked stage 2. Finally, that extra geolocation data allowed the detective to single out the one phone that very likely belonged to the robber, and so in stage 3, Google returned the name and subscriber identifying information for Chatrie.
Judge Lauck found that (a) the demand for, and return of, deidentified data in stage 1 constituted a search under the Fourth Amendment; and (b) the warrant that was used was not sufficiently particularized to suspicion related to the bank robbery. Latent in the opinion is the presumption that if (a) is true, then a warrant and full probable cause is necessary. I think the opinion is flawed across all of these claims.
Is the demand for, and return of, geofenced data a search under the Fourth Amendment?
In order to answer whether disclosure of geofenced data violates a reasonable expectation of privacy under Katz and Carpenter, Judge Lauck's opinion focuses on the question of whether smart phone users have voluntarily consented to having their location data tracked when they opt into Google's location services. But I don't think this is a critical component of the Third Party Doctrine, and it's certainly not a sine qua non. Even when Smith was decided, while the Court reasoned that people have some understanding and expectations that their calls would be logged for billing purposes, and assumed the risk that it would wind up in the hands of police, nobody at the time or since would seriously believe that Americans consent in a meaningful sense. The court knew few would avoid using telephones. Miller, the first in the line of cases that developed the Third Party Doctrine, makes the limited relevance of consent even more obvious. Miller involved subpoenas for bank records. Banks are legally obligated to collect and maintain transaction records, and are then similarly obligated to hand them over (in identified form) during the course of a police investigation if the police present a subpoena. Even if banks and their clients wanted to avoid collecting data of this sort, they wouldn't be able to.
Thus, the relationship that the Third Party Doctrine has to the "reasonable expectations of privacy" test is not very analogous to the consent warrant exception or even the misplaced trust doctrine. It is much more analogous to the Public View doctrine. We "voluntarily" use telephones and banks the way we "voluntarily" venture outside of our homes—not very. Nevertheless, police investigations need some way to get going. Some portion of peoples' whereabouts and goings on needs to be accessible to the police without heighted suspicion requirements. The Third Party Doctrine is part of messy-but-necessary process of dividing zones of privacy from the areas where police have a freer hand.
Carpenter renovated the dividing line, but not enough to reach the facts of Chatrie. The majority opinions in both Carpenter and Jones explicitly emphasized the narrowness of their holdings. The Court is publicly struggling to draw new lines that help handle privacy intrusions in light of new technologies without completely frustrating early stage police investigations.
How does all this relate to geofence warrants? Judge Lauck explained that if the investigation in Carpenter went narrow but "deep" (it involved collecting 7 days worth of geolocation data about the defendant), the geofence process goes "broad" but shallow.
I am not sure I agree with the conclusion that collecting 19 individuals' deidentified data is "broad," but the conceptual framework is useful. We can imagine other geofence warrants, in more dense areas or larger radiuses, that might capture many more individuals. At some point, breadth might matter. But under these facts, with nineteen subjects, the important factor is the geofenced data retrieval's shallowness. The Chatrie opinion asserts that broad-and-shallow is as bad as narrow-and-deep, but this is not true. Or at least, it runs against the way much of Fourth Amendment law is structured: allowing superficial information-gathering without process, and then demanding more and more particularized suspicion as the intrusiveness (deepness) of the searches progress. For example, to harp on the Plain View doctrine again, police are allowed to conduct broad-but-shallow surveillance all the time. That's what they do when they stand on a street corner, poke around on the public Internet, or execute a stake-out.
Thus, while there are real issues related to constraining the first step of a geofence warrant process, the fact that a geofence warrant might initially capture information about a couple dozen people who were moving around in public does not seem to me to justify the dismantling of the Third Party Doctrine.
One note: at times, the opinion suggested that geofence technology might permit police to observe a person's movements within their homes. If true, this could very well constitute a search even if the data is in deidentified form. As fond as I am of the "Plain View" analogy, even I would conclude that detecting motion within a home is much more consonant with Kyllo's "through-the-wall" search than some sort of analogy to observing a person through a window or something like that. But the court's concern about tracking people inside homes (in this case or others) is in direct contradiction to the court's conclusion that the current location-tracking technology is very noisy, and may draw in individuals who are actually a football field away from the location of the crime. It is possible that noise and precision can both be present at the same time depending on what source of geolocation is being used by Google, but in any case courts will have clarity soon enough about whether the location-tracking is sensitive enough to track location inside the home (which would be great, because that means geofencing can be done with greater precision and smaller radii) or whether it's in fact so noisy that police couldn't have confidence about whether any particular device is actually in the building its data makes it look like it's in, which would have the virtue at least of avoiding a Kyllo problem.
Thus, it is not at all clear to me that geofence warrants that collect much less extensive data than the long-term surveillance at issue in Carpenter and Jones would be considered a search at all.
If a subpoena for geofenced data is a search, do police need full Probable Cause and a Warrant?
Even if geofenced data requests are a Fourth Amendment search (either in all cases or in cases where the geofence returns too much location data), there may be good reasons to consider this particular style of search reasonable, despite its lack of particularization. Specifically, I would have expected for the government to argue that an investigation of this sort, if a search at all, would fit well within the Administrative Search doctrine under cases like Sitz and Lidster.
In Illinois v. Lidster, the Supreme Court decided that a temporary checkpoint that was set up at the scene of a hit & run accident "about a week" after the accident occurred was permitted to stop and question drivers in order to try to get information related to the crime without any particularized suspicion or warrant procedure. Even though the checkpoint intruded on the Fourth Amendment rights of each person who was stopped, the intrusion was small enough, and the purpose well-tethered to the facts of a particular crime (rather than general crime-fighting) to justify the procedure. Moreover, one reason courts have justified checkpoints in cases like Lidster and Sitz is because they constrain discretion. Police have little control over who winds up coming through the checkpoint, and are thus unlikely to abuse the procedure in order to target or harass a particular suspect.
The virtues of geofenced investigations
This brings me to my biggest gripe: the opinion is written without any regard for the difference between discretionary suspect-driven fishing expeditions and crime-driven (or event-driven) investigations. If we want clearance rates for serious crimes to improve (which we all should), and if we also want police departments to use more objective bases for their suspicion (which we all should), then criminal justice and civil liberties organizations should embrace tools that encourage police officers to follow the circumstances of a crime to find a suspect rather than following the details of a suspect to find a crime.
The facts of the Chatrie case help illustrate what I mean. Before the detective used the geofence warrant, he first investigated two other leads. A person who saw news reporting about the bank robbery called the police and said her ex-boyfriend committed the crime, but the tip was false. A bank employee reported somebody who owned the same kind of car that was used as the getaway vehicle, but that tip, too, was a dead end. It is not clear from the opinion what sorts of encounters and information-gathering the police used to rule out these two persons of interest, but I suspect the anxiety and privacy burden absorbed by those two was greater, by almost any measure, than the burden to the 18 individuals whose approximate movements in public during one hour were disclosed in deidentified form. Indeed, I would go further and suggest that the geofence warrant process may often be an appropriate method of first resort, rather than last resort, if it is likely to lead more quickly to the identification of the right suspect. In any case, those who are instinctively against the use of geofence warrants should ask themselves, as an exercise and gut check, what they would prefer to happen in this very case.
When is a geofence process unreasonable?
Despite my enthusiasm for crime-driven investigation tools like geofence warrants (I've defended the use of facial recognition to identify perpetrators from crime footage for similar reasons), there are real issues that should be resolved to set constraints on their use.
First, even if I disagree with the court about whether 19 is or is not a large number of people to be briefly observed, I concede there is some threshold beyond which too many devices would be included. It makes sense to require police to craft the geofence so that it is likely to produce a small number of devices in part for the sake of the privacy of innocent individuals, and in part because the efficacy of the tool is likely to be low, anyway. Relatedly, it may make sense to have a norm (if not a formal rule) that requires police to use as many limiting criteria as they can to avoid overinclusion. For example, if police are investigating two related crimes, a geofence warrant should request that Google or Apple identify devices that appear in both. And if a suspect was known to have arrived from, and departed to, the east of the crime scene, a geofence should avoid any unnecessary capture of devices that appear to the west of the crime scene.
I also think there could be value to having a warrant-like process at some point during a geofenced data investigation. The Chatrie opinion suggests it would approve a geofence warrant process in which a magistrate or court got to make a probable cause determination before geofence data of the likely suspect is de-anonymized (at least, if this review occurs before the government receives any additional data that falls outside the time or location bounds of the geofence.) This part of the opinion seems like a sensible path for a legislature or for a court to interpret and extend the administrative search doctrine to cover this new technology so that the police can investigate without too much friction up to the point when they want to identify a suspect and (presumably) conduct a deeper investigation of that person. Technological tools that permit broad-but-shallow digital investigations could also be limited to certain types of relatively serious crimes in order to reduce the hassle and resentment that comes from this highly automated form of policing.
But burdening a geofenced data investigation with a full warrant and probable cause requirement would be a mistake. When it comes to the early part of police investigations, the status-quo is not good.
Editor's Note: We invite comments and request that they be civil and on-topic. We do not moderate or assume any responsibility for comments, which are owned by the readers who post them. Comments do not represent the views of Reason.com or Reason Foundation. We reserve the right to delete any comment for any reason at any time. Comments may only be edited within 5 minutes of posting. Report abuses.
Please
to post comments
Sorry, Charlie ... stop reading your pro-government agenda into the lines of the Constitution. Fishing expeditions are clearly against the intent of the 4th Amendment, and dressing them up in geofence boundaries is about as clear a pretext as allowing wiretaps because telephones did not exist in 1787.
Paging David Behar ....
Full disclosure: IANAL.
I do not agree that these type of warrants are a good thing. There does not seem to be any protection for people who just happen to be in the wrong place at the wrong time. This is simply one very good reason to switch off "Location Services" when you are out and about.
Not that Google or Apple actually allows you to turn off that feature (Google is notorious for only pretending to turn off location services).
"The Third Party Doctrine is part of messy-but-necessary process of dividing zones of privacy from the areas where police have a freer hand."
See, this is exactly the problem I have with third party doctrine. What actually should be going on here is dividing up zones of privacy according to whose privacy is implicated, NOT declaring that if Bob is mentioned in Frank's 'papers and effects', the fact that Bob has no privacy right in Frank's records implies that a warrant isn't required to go through Frank's records.
It should not be particularly difficult to obtain such a warrant. In the case discussed, establishing probable cause to believe evidence would be found in Google's records was very straightforward.
The issue we should be discussing here isn't whether a warrant is required, but just who the warrant should be addressed to.
In addition, allowing geofence warrants will be a huge equilibrium adjustment in favor of the police. Traditionally, the cops don't have the power to round up and identify anyone near a crime scene even if they are doing nothing suspicious. Allowing geofencing gives the cops a massive power they never had before? Why would anyone do that?
Especially since- and this might not be your biggest concern, Brett, but it is for a lot of people and it is true- this is going to lead to widespread questioning and arrests of Black people. You can rest assured. Geofencing should be called the Harass And Jail Black People Warrant. Because Blacks often live in high crime neighborhoods, they are going to get brought in all the time for the "crime" of being near places where crime is being committed. And since a lot of cops are racist, and assume any Black who rationally doesn't want to talk to them is guilty, there's going to be plenty of arrests and jailings of innocent Black people. You can bet on it.
This should be stopped. Period.
"Traditionally, the cops don't have the power to round up and identify anyone near a crime scene even if they are doing nothing suspicious. "
Depends what your definition of "round up" is. They certainly have the power to identify and canvas everyone in a bar on a particular night who may have seen/heard a shooting. They can put DUI checkpoints on roads. They can use surveillance and use it to go through and identify witnesses. Geofencing just makes it easier.
The problem is the ease with which this can be abused. If I know prostitution happens at a particular massage parlor, i can just round up everyone who went there.
No. None of those things are like geofencing. One huge difference is that cops have to leave the donut shop and work to do those things, which is a huge deterrent to doing them without some actual belief that you are going to catch the criminal.
And another thing is that they have to investigate to generate the leads as to who is in the bar. That, again, requires actual policework.
Geofencing doesn't, and it's going to the result in the harassment and imprisonment of Black people.
I don't doubt that this could be abused, as could almost any constitutional practice. I just don't see that as changing the constitutional analysis.
Do you even understand what happened in the underlying case? Going from "the detective pared down his request to just 9 devices and received an extra hour's worth of location data about those nine" to "they are going to get brought in all the time for the 'crime' of being near places where crime is being committed" is a baseless leap even by VC Commenter standards.
The standards being argued for are far more lax than the underlying case.
What is being argued for is Harrassing and Arresting Black People, not a supposedly limited use like the case purports to endorse.
I asked you in the original Orin thread, but it might have petered out so you didn't respond: how do you see this as different than police looking at all the footage from surveillance cameras near the bank near the time of the crime to identify everyone in the vicinity? (Or don't you?)
Also, I don't really agree with your argument. Police already engage in widespread questioning of people for the crime of being near places where crime is being committed. This approach should allow law enforcement to target with more precision than current methods do, and thus be more protective of the public (including, of course, black people).
This is why you shouldn't use Google/Android phones or Google services whenever there's an acceptable alternative. Google collects and stores too much random data about you whenever you do.
So doesn't everybody. I don't believe Apple when they claim that they don't. I don't trust the cell phone providers. I expect NSA to capture and record every scrap of data from every phone in the world.
Ditto. My secondary complaint about the NSA is that they must know who all the spambots are, the hacker cluster control protocols, the ransomware keys, all that malware -- yet they do nothing, presumably because they want to save it for a rainy day. Naive fools would invoke Occam's Razor to say this all proves the NSA is benign and saintly, ignoring all human (and even animal) history in the process.
This got a good laugh from folks in the IC when I shared it at work.
The cell phone providers are way worse than any of the tech companies. It's weird how infrequently they're mentioned in these conversations. Not only do they not give you any way to opt out of location data collection, but they resell the data to third party brokers (also without any way for you opt out) and Verizon, at least, has been caught doing this even after they promised not to.
Maybe you don't believe Apple (I generally do; their business model is much more focused on selling hardware than ads or other contexts where user data), but there's way more evidence of the cell phone companies being very privacy-hostile.
I will take the chance that Apple is telling the truth over the absolute certainty of what Google does.
Apple, the company that thought it was perfectly fine to scan the photos/documents on your phone (i.e., not in the cloud)? And to make future security updates contingent on "consenting" to those searches??
(They subsequently agreed to tweak the program...but, afaik, still have not renounced it)
And this guy calls himself a "libertarian". What a complete joke.
My reaction precisely, NOYB2.
When did Prof. Bambauer call herself a libertarian?
"whether the location-tracking is sensitive enough to track location inside the home (which would be great, because that means geofencing can be done with greater precision and smaller radii) or whether it's in fact so noisy that police couldn't have confidence about whether any particular device is actually in the building its data makes it look like it's in, which would have the virtue at least of avoiding a Kyllo problem."
No - it will never be clear whether its "precise" or "noisy. "Sometimes its noisy, other times it isn't, and it can even vary from day to day in a particular location.
In a park, for example, some clear days/nights its very precise. Other cloudy days its noisy.
Also, you are thinking in 2D. The bottom floor of a skyscraper may hold a bank, while the top floors have residences. Just because I am reported precisely at longitude/latitude x,y at time t, does not mean I was in the bank. I could have been on the 4th floor.
FWIW, GPS locations (and more fine-grained location services provided by cell phones) are also 3D.
>I concede there is some threshold beyond which too many devices would be included.
Given the almost-universal history of police departments' subsequent stretching/abusing powers that were originally sold as being limited / carefully balanced... how do you propose keeping them under that threshold? Put differently, given that history, shouldn't the assumption be "give an inch, and they'll take a mile" here too?
Yeah idk, this is a tough one for me.
The police collect license plates on the highway, in parking lots, etc. You really cant avoid going anywhere without a car. Automated license readers make the burden of collecting that data minimal. In my mind, geofence searches are analogous to reading a bunch of license plates in the parking lot of a gun show, which the ATF does all the time. Does that require a warrant?
On the other hand, this capability is ripe for abuse. Why not simply collect the geolocation data for everyone who visited an Asian massage parlor and bust them.
"Why not simply collect the geolocation data for everyone who visited an Asian massage parlor and bust them."
Because almost everybody who visits an Asian massage parlor just gets a massage?
Doubtful.
That's been my experience, anyway. The one near my house doesn't even have enough privacy to get up to anything illicit.
Eventually, this discussion will resemble the NSA's position. NSA claims the right to collect data with almost no restrictions, and to build a database with fully identified data. NSA says that a search doesn't occur until they query that database.
I expect the police to do the same. Perhaps on some scale, they already are.
I think Ms. Bambauer puts too much emphasis on the number of phones caught up in this. Depending on time of day and location that 19 could easily be 90. So quibbling over whether 19 in this one instance is “too many” is more of a distraction than it is relevant.
And what of finding evidence that among those 19 (or 90) is someone who, unrelated to the robbery, is committing some other crime? My old man got busted running book because the dummy was using a public phone (this was late-80’s) that was already bugged by police seeking evidence that the establishment owner’s idiot son was dealing coke from the same pay phone (he was).
Perhaps our understanding of the 4th and 5th amendments is incomplete. It seems to me that LEOs are going on 'fishing expeditions' with geofencing requests. I don't think that is consistent with either the 4th or 5th amendments. Maybe Professor Kerr can find a 'hidden' historical treasure trove from the Founding era (sort of like that article he wrote about 1A and the argument before John Marshall).
Why not require a warrant that states exactly who is being searched and specifies exactly what is being looked for. Wouldn't that stop these open-ended fishing expeditions?
That's exactly what the law should be (and BTW it should also be the law on license plate collection).
Because they don't know who is being looked for - that's why they're interested in the information in the first place.
Yes, if the police need a warrant to get this evidence, they won't get it when they don't have the means to get a warrant.
Which means, as Prof. Bambauer notes, that they will instead be left to use less accurate and more intrusive alternatives.
No, they would be left with solving crimes consistent with Fourth Amendment values of individualized suspicion.
Setting aside the question-begging in assuming that this investigative technique isn't consistent with "Fourth Amendment values" -- are you disputing that the investigative techniques you'd rather see the police use are, in fact, both less accurate and more intrusive (for the subjects)?
I'll dispute it on the grounds that, if you make it this effortless, innocent people are going to be routinely caught up in searches.
Abuse of traditional investigative techniques are at least somewhat limited by the time/effort required to perform them.
It's clearly more intrusive as a whole. And "accuracy" is not the right term here- nobody's contesting that once police have actually ID'd the perpetrator that geofencing evidence might be admissible to prove the case, or that police can use it once they have found a suspect to rule that suspect OUT. However, before probable cause is established, the Constitution privileges protection of the innocent over "accuracy" in the sense of solving more crimes.
How do you envision that working?
If you have probable cause to suspect a specific person, you can then get a search warrant based on that probable cause. Nothing wrong with that, and nothing wrong with using that to get cell phone location data. And that data might exonerate the suspect.
The probable cause with respect to a specific suspect has to come first, though.
The probable cause required for the issue of a search warrant is cause to believe the search will yield contraband or evidence of a crime. The state does not need to establish probable cause to suspect a specific person of having committed a crime.
"Why not require a warrant that states exactly who is being searched and specifies exactly what is being looked for."
Who is being searched: "Google".
What is being looked for: "Which phones were within the specified coordinates at the specified time."
Probable cause: "The perp was within those coordinates at the given time, waving around an Android phone."
My, that was easy.
A modern founding father would look at how the Tyrant King George III misused things, and put in safeguards against it.
Alternatively, just look around you at contemporary dictatorships. For example, every time an FBI spokesman or US senator speaks about the need for crypto back doors for investigation of crimes, Putin and China and myriad dictators smile a little bit bigger, and the billions under them, living, no longer just having to imagine anymore, a boot stepping on their face, forever, sigh, as it becomes a little more foreverer.
I have another example: ATF gets all customer records from a manufacture of "solvent traps," decides* that said solvent traps are now illegal unregistered silencers, then sends everyone a "you are a felon" letter. True story. https://americansuppressorassociation.com/atf-form-1-update-take-action-now/
https://blog.princelaw.com/2022/01/10/purchased-from-diversified-machine-and-received-a-warning-notice/
This is the kind of abuse you can expect if police have unfettered access to geofence information.
Regardless of what the current case law says (the Supreme Court has been known to carry forward dicta without appropriate analysis then disavow it lol), I doubt that the framers thought that this kind of abuse was allowed under the 4th amendment.
Can you elaborate? I'm not sure I see the connection you're trying to draw.
Many new technologies -- including geofence subpoenas -- seem to have great power to exacerbate the human tendency to use criminal process for self-serving ends. Restating some of the topics in comments above... what happens in the many [novel] corner cases which will arise?
1 - Forest Green and his spouse Kelly visit a local bank with their teenage son Hunter and infant daughter Olive. During the visit, the bank is robbed and police request and receive a geofence subpoena, the response to which duly reports the presence of all family members. Forest and Kelly were unconcerned -- they had already cooperated with the police and assumed the police would be searching only for the identity of persons (such as the robber) who reasonably could be assumed to have failed to cooperate. But they failed to recall that Hunter and his girlfriend Scarlet had waited in the family van and had been engaging in behavior which, while conducted in privacy, was within the geofence zone and was at least arguably illegal. Scarlet's parents, Carmine and Ruby Ferrari, are red-faced and demand prosecution. Hunter is now in deep brown for having mingled with Scarlet... but should the evidence be suppressed? Who pays for the ensuing debacle?
2 - David, a Democrat whose agenda includes the "cancellation" of those who [truthfully] report misdeeds by Biden family members, is employed by Google, a dealer of private information. David's employer tasks him with responding to a [properly issued] geofence subpoena. When completing the task, David implants within the company's response the names of several individuals he wishes to cancel. The police then act upon the response received, causing severe financial hardship to the parties [wrongly, yet plausibly] included in therein. After eighteen years of litigation at personal expense, the cancelled parties are technically exonerated, but not made whole.
3 - Renee, a Republican, is keenly aware of numerous flaws in the software utilized by the Purveyor of Personal Secrets which employs her. In response to a [properly issued] geofence subpoena, Renee violates her non-disclosure agreement and informs the requesting police officers of the software defects. The police ignore Renee's [factual] information, inform her employer of her disloyalty, and prosecute based on the [flawed] response to the subpoena. Renee is fired and sued: innocent parties are prosecuted.
How would this the geofence demonstrate anything about what these people were doing in the van? And how would the parents find out about it?
All three of your cases are terrible, but not because of geofence warrants.
In case 1, the geofence warrant would not reveal anything about the boy and girl, except that they were both within several meters of each other at the same time. Even if the police got the information, why do you think that the girl's parents would suddenly know?
In case 2, the insertion of fraudulent data in response to a police request could easily be done in response to a full warrant as well. In addition, the mere presence of those people in the area does not lead to immediate prosecution, so the attempt wouldn't actually DO anything (even ignoring the other sources of contradicting data, like the phone company tower records). There never would have been "18 years of litigation" - at least, not based on the geofence warrant.
In case 3, your person either committed a crime by leaking confidential information, or is a whistleblower facing illegal retaliation. And again, neither circumstance has to do with the geofence warrant. A full warrant would have to face the exact same potential errors, and your person would need to either leak/whistleblow or not then as well.
The OP can be summarized in one question:
How do you expect us to present probable cause if we are not empowered to conduct a warrantless search to find it?
For what it's worth, I think that to escape being terrifying, a free-floating notion that we should all want increased clearance rates for serious crimes needs a bit of conditioning.
A broken clock is right twice a day, and you are right here.
Yes, of course that trivially obvious point is part of Prof. Bambauer's analyiss.
How large an area does a geofence warrant have to get to violate the prohibition on general warrants?
"...For example, to harp on the Plain View doctrine again, police are allowed to conduct broad-but-shallow surveillance all the time. That's what they do when they stand on a street corner, poke around on the public Internet, or execute a stake-out...."
I guess I am not understanding the concept. To me, a stake-out would be a prime example of the narrow-but-deep, rather than the broad-but-shallow. If sitting and observing and recording at one person's house or business for an extended period (days? weeks? months???) is not narrow and deep, then I'm really confused. Can another reader clarify for me?
He's not talking about a focused stake out tied to the investigation of a particular crime and/or suspect in any way.
He's talking about putting a cop on a street corner to take notes on everyone that moves through that intersection and everything that transpires in and around it.
Matt,
No. What you're writing about--that was the first of the three examples that Prof. Bambauer used- . . . the cop on the corner. I was specifically asking about the stakeout, which was written by Bambauer as quite different from the cop/corner. (And that's why I asked about it . . . the cop standing out in public, observing things that you or I could see if in that cop's place--that's obviously broad-but-shallow. But a traditional stakeout? Still seems to be the opposite.)
I don't know what you mean by a "traditional stakeout," but it's likely different from what the professor means. You seem to be using the phrase to refer to them following a specific person around. I do think the professor was using it to refer to monitoring a specific place.
So, note to whom it may concern, next time you plan on committing a crime leave you phone and other electronics at home.
Leftist UCLA law professor Eugen Volokh joins forces with UC Berkeley law professor Orin Kerr who argued before #SCOTUS in defense of a City of Los Angeles law that made it a crime to merely assert one's Fourth Amendment right.
Is anyone surprised?
That you're an idiot? No.