Start with the text. Here is the whole Fourth Amendment:
The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized.
Fifty-four words. Read the list of what’s protected: persons, houses, papers, and effects. Two of those are doing quiet work that matters enormously for everything this blog is about.
“Effects” is the catch-all — your tangible personal property, the things you own. A phone is an effect. A laptop is an effect. “Papers” are also, technically, a kind of personal property; the Framers could have let “effects” swallow them and lost nothing in logic. They didn’t. They gave papers their own line. And they did it for a reason that turns out to be the single most important thing the Fourth Amendment has to say about digital evidence: the harm the government does to your papers is not mainly about the paper. It’s about what’s written on it. The Fourth Amendment protects the physical document, yes — but far more importantly, it protects the content the document carries.
That distinction — the object versus the content it holds — is baked into the constitutional text itself. And it is exactly the distinction we need to make sense of digital property.
It helps to remember why “papers” was on the Framers’ minds at all. The Fourth Amendment was written by people with specific, recent grievances, and a striking number of them were about documents. British authorities used general warrants and writs of assistance — open-ended authorizations to search wherever and seize whatever — to rummage through homes and papers hunting for evidence of sedition or smuggling. James Otis’s 1761 argument against the writs of assistance in Boston was one of the sparks John Adams later credited with igniting the Revolution. In England, in Entick v. Carrington (1765), the King’s messengers broke into John Entick’s house and carried off his private papers under a general warrant; Lord Camden’s opinion striking that down became one of the taproots of our own Fourth Amendment. The evil those cases named was rummaging — the government pawing through everything a person had written in search of something it could use. “Papers” is in the amendment because reading a person’s documents wholesale was understood as a distinct and graver intrusion, worse in kind than carting off a chair.
Hold onto that word, rummaging. It is about to describe something very modern.
This is also why definitions are not the boring part. The federal wiretap law opens, at 18 U.S.C. § 2510, with definitions, and those definitions decide almost everything that follows — whether a communication is covered turns on what “electronic communication” and “intercept” mean, and if what the government did wasn’t an “interception,” the statute simply does not apply. Definitions aren’t throat-clearing. They’re the fence line: everything inside is regulated, everything outside is free. So when I say the model act I’m drafting this year has to begin, like the wiretap law and the amendment itself, by naming what it protects, I don’t mean it as a formality. The definitions are the first and most important fight.
Now put a seized laptop on the table and ask where it falls in “persons, houses, papers, and effects.” It’s closest to two of them at once, and keeping those two apart is the whole game. Because “digital property” is not one thing. When the government executes a warrant on that laptop, at least three distinct objects are in play, and most of the confusion in this field comes from treating them as one.
There’s the device — the physical laptop. This is an effect, plainly: ordinary tangible property. We’ve known how to think about seizing objects since the Founding.
There’s the data — the files, the messages, the photographs, the years of accumulated life. This is the modern equivalent of papers. It is content. And if the Framers were right that papers earned their own line because content is what matters, then the data is the part the Fourth Amendment should care about most — not the aluminum shell it happens to live in. Some of it sits on the device; some sits in a cloud account a third party holds for you.
And there’s the copy — the forensic image, a bit-for-bit clone of the entire storage medium that the government makes and keeps. This one has no clean 1791 analog, and it’s the one that should worry you most. The image didn’t exist before the government created it. It’s a new artifact, produced by the act of investigation, and it contains everything: the handful of files the warrant named, and the overwhelming remainder it didn’t.
Look hard at that forensic image and you will see the ghost of the writ of assistance. A complete clone of your drive, retained and searchable at will, is the most literal form of rummaging the modern state can perform — a general search of all your papers to find the few the warrant actually authorized. The word the Framers wrote into the amendment to stop that practice describes, almost perfectly, the thing our forensic tools now do by default.
There is a second constitutional text worth setting beside “papers,” because it names the same thing and supplies the one dimension the Fourth Amendment leaves implicit. Article I empowers Congress to secure “to Authors … the exclusive Right to their respective Writings.” The Copyright Clause’s Writings are the Fourth Amendment’s papers by another name — authored content — and what that clause treats as worth securing is specifically the right to control the copying of it. Let me be careful, because a sharp reader should not be able to catch me overstating: I am not claiming copyright law restrains a forensic examiner. It doesn’t, and the clause is a grant of power to Congress, not a limit on searches. But the resonance is not decorative. The Fourth Amendment protects your papers from being seen and taken; the premise behind the Copyright Clause is that your writings are yours to copy. Digital forensics does both at once — it reads your content and it manufactures a perfect, permanent reproduction of it — and ordinary search-and-seizure analysis really only captures the first half. Making the copy is a distinct act from searching, and a Constitution that elsewhere thought the exclusive right to copy one’s writings was worth naming should not wave that act through in silence. That is why “copy” has to be its own defined object here, and why copying earns its own section later in this project rather than riding along inside “search.”
A statute that says “digital property” without saying which of these it means will fail on contact, because the three behave differently. You can return a device. You cannot “return” a copy — you can only delete it, and deletion is a choice someone has to be affirmatively required to make. Hold that thought; it’s the whole subject of a later section.
The same precision problem shows up inside the data itself. A warrant describes what the government may seize — call that the responsive data. The forensic image sweeps in everything else — the non-responsive remainder. And almost every retention dispute in this area is really a fight about that remainder: the government’s working assumption that once a drive has been lawfully imaged, the entire clone is its property to keep and to re-search, indefinitely. You cannot regulate that fight if your statute has no word for the thing being fought over. So “non-responsive data” has to be a defined term with its own rules, not an afterthought buried in a retention clause.
Even the verbs are definitions. Collection, analysis, copying, use, disposition — I’m going to treat each as a defined operation, because the protection a person receives should depend on what the government is doing to their content, not on which gadget it happened to use. And notice that the constitutional text pushes in exactly this direction. If the thing being protected is papers-as-content, then the protection travels with the information — a letter, an email, a file, a message on a server — regardless of the medium carrying it. The “effects” reading, the one fixated on the physical object, is the reading that keeps breaking as technology changes, because the object keeps changing. The “papers” reading — protect the content — is stable. Define by function, not by device, isn’t just tidy drafting; it’s what taking the word “papers” seriously actually requires.
That is the argument of this post, and it has a track record worth spelling out. Definitions in this area should be functional, not technological. The wiretap law’s deepest weakness is that it was written around the telephone, and every new medium — email, text, cloud storage — forced Congress or the courts to decide whether the old words stretched to cover it. The Stored Communications Act still runs on distinctions that made sense for 1986 server architecture and make almost none today. Technology-specific definitions rot. Function-specific ones don’t. “Collection” is collection whether the data comes off a seized phone, a compelled cloud production, or a quiet purchase from a data broker.
The Supreme Court has been feeling its way toward the same instinct. In Riley v. California, it refused to treat a smartphone like any other object found in a pocket, recognizing that the sheer quantity and kind of data changed the constitutional stakes. In Carpenter v. United States, it held that some digital records held by a third party still receive Fourth Amendment protection, cracking the old rule that anything you hand to a company is fair game. Both decisions are, at bottom, definitional: the Court noticing that the inherited categories no longer describe the thing in front of it — that the papers have moved, and the protection has to follow. A model statute should learn that lesson on purpose, instead of waiting a decade for litigation to force it one case at a time.
Now the counterargument, because a definition that can’t survive it isn’t worth proposing.
Define things functionally and broadly, and you risk sweeping in ordinary, legitimate government computing. If “collection” means any acquisition of digital data, does routine network administration count? Does a lawful, warranted search become a statutory violation because the forensic tool necessarily reads bytes outside the warrant’s scope in order to locate the ones inside it? Overbroad definitions can turn unavoidable technical steps into violations and hand defendants suppression arguments that have nothing to do with any real invasion of privacy. The government’s version of this objection is not frivolous. Forensics is not a scalpel, and a law that pretends it is will either be ignored in practice or will spring guilty people on technicalities.
The answer is not to narrow the definition of the object. It’s to put the limits in the operative sections, not the definitional ones. Define “collection,” “copy,” and “non-responsive data” broadly and accurately, so the statute actually sees everything the government does — then decide, section by section, what is permitted. The tool that reads a whole drive to find responsive files is doing “analysis” and “copying” as defined, and the analysis section can expressly permit the technically necessary read while forbidding the government from using what it incidentally saw. That’s a cleaner design than pretending the incidental read never happened. Honest definitions plus calibrated permissions beat dishonest definitions every time.
One tension I’ll flag now and wrestle with later, because a sharp reader is already there: the “protect the content” intuition is strongest for papers you keep yourself. Once your papers sit with a third party — the cloud provider, the phone carrier — the old third-party doctrine says you surrendered your expectation of privacy by sharing them at all. That collision, between papers-as-content and the third-party rule, is exactly what Carpenter began to renegotiate and what the Court is still working out. It’s also where Thursday’s post is headed. Hold the thought.
So the first section of the model act does three things. It separates the device (an effect) from the data (the modern papers) from the copy (the artifact the government itself creates), and refuses to conflate them. It makes “responsive” and “non-responsive data” defined terms, so the retention fight finally has vocabulary. And it defines the five lifecycle operations by function, so the statute’s protection follows the content instead of chasing next year’s hardware.
It reads like bookkeeping. It’s actually the argument the Framers already made in four words — persons, houses, papers, and effects — updated for a world where your papers number in the millions and live on a machine the government can copy in an afternoon. Write the definitions loosely and every hard question migrates into a gap. Write them well and every operative section that follows has something solid to bite on.
Next Tuesday: the baseline prohibition — why a statute like this has to start by saying no. And Thursday, we go to the far end of the timeline, to a place I once stood myself — what happens when the Supreme Court redefines a “search” out from under the people doing the searching.
(Actual model statutory text for these definitions comes in Pass 2, later this fall. This post is the why; the drafting is next.)
DigitalCrimPro 
Leave a comment