Know what’s on your site before a plaintiff’s firm does
A free privacy audit shows which cookies, pixels and trackers are running — and which ones commonly appear in privacy claims.
Intrusion upon seclusion is the common-law privacy tort people have in mind when they say someone “spied” on them. It does not require a publication, and it does not come with a built-in statutory damages chart. What it does require is an intentional intrusion into a private place or matter that would be highly offensive to a reasonable person. A recent Meta Pixel demand letter, like others sent to e-commerce and website operators, lists that tort as claim (c) and treats a page-view event sent to Meta as if it were a hidden camera. Sometimes the comparison is worth taking seriously. Often it is a stretch.
TL;DR
- California follows the traditional intrusion test: an intentional intrusion into solitude or a private affair that would be highly offensive to a reasonable person.
- The Ninth Circuit applied that test, together with California’s constitutional privacy right, in In re Facebook, Inc. Internet Tracking Litigation, a case about Facebook compiling logged-out users’ browsing histories.
- Demand letters use intrusion both as a standalone claim and as a tortious purpose for the ECPA crime-tort exception. Ordinary, disclosed advertising events are harder to call “highly offensive” than hidden collection of sensitive browsing trails.
What the tort actually requires
The Restatement (Second) of Torts § 652B describes intrusion upon seclusion as an intentional intrusion, physically or otherwise, upon the solitude or seclusion of another or his private affairs or concerns, if the intrusion would be highly offensive to a reasonable person. California courts have long used that formulation. The plaintiff must show both that the matter was private and that the intrusion crossed a line a reasonable person would find highly offensive, not merely annoying or unexpected.
Offensiveness is judged by more than the plaintiff’s irritation. Courts look at the degree of intrusion, the context, the perpetrator’s motives and objectives, and the setting in which the plaintiff was when it happened. Opening someone’s mail is not analyzed the same way as standing in a public square. Collecting a confidential medical questionnaire is not analyzed the same way as recording that a person loaded a public homepage.
In In re Facebook, Inc. Internet Tracking Litigation, 956 F.3d 589 (9th Cir. 2020), the Ninth Circuit considered intrusion together with California’s constitutional privacy claim. Plaintiffs alleged that Facebook continued to track them after they logged out and compiled their browsing histories across other websites. The court held they had alleged a concrete privacy injury and that the claims could proceed. The opinion is now a staple citation in tracking complaints. It matters, and it has limits. The alleged intrusion was a platform’s hidden, cross-site profile of a user’s web activity, carried out after the user had taken a step (logging out) that made an expectation of privacy more plausible.
How letters turn a pixel into an intrusion
In Meta Pixel demand letters built around ECPA procurement, the intrusion theory is usually spare. The business embedded JavaScript. The visitor’s browser sent Meta a URL, a timestamp, and identifiers. The visitor did not know, or could not have consented in the milliseconds before the banner appeared. Therefore, the letter says, the business intentionally intruded on a private communication with the website, and the intrusion was highly offensive because it was secret and because the data was used for advertising.
Two pieces of evidence show up repeatedly. One is an export of activity off Meta technologies, which may list a page-view event attributed to the business. The other is a HAR file showing the request leaving the browser. Counsel then describe the categories of data a pixel can collect in broad terms, sometimes implying that every available field was sent even when the log shows a basic page view.
The “highly offensive” label does a lot of work in that story. Letters treat secrecy and commercial motive as enough. California law asks a more particular question. Did the plaintiff have a reasonable expectation that this information would remain between the visitor and the site? Would a reasonable person consider the specific intrusion highly offensive? A hidden relay of a fertility-clinic appointment page is a different allegation from a hidden relay of a publicly advertised product page. Demand letters often write as if the legal test cannot tell the difference.
Where the claim is stronger, and where it thins out
The Facebook tracking decision shows that electronic surveillance can be an intrusion when the collection is broad, unexpected, and at odds with the user’s steps to protect privacy. Healthcare pixel cases have a similar emotional and legal gravity because medical information is the classic private matter. A letter that can point to form fields, search terms, account pages, or URLs that reveal a condition has more to work with than a letter that can point only to “PageView.”
On an ordinary commercial site, several defenses are apparent even before anyone argues about damages. Visitors chose to load a public website. Browser tools have shown third-party requests for years. Privacy policies commonly describe advertising partners. The information at issue may be a URL the business itself published. None of those facts is an automatic win, especially if the pixel also collected hashed emails or other identifiers the visitor did not expect to share with Meta. They do make it harder to call the event highly offensive as a matter of law.
There is also the double-use problem. Letters offer intrusion as a standalone tort and as the tortious purpose that defeats ECPA consent. Courts applying the crime-tort exception have required an independent purpose, not a restatement of the interception. If the only “intrusion” is the interception itself, the exception may not do what the letter wants. That is one reason recipients should read intrusion next to, not instead of, the federal theory.
Practical responses
- Inventory the events, not just the vendor name. PageView, ViewContent, Search, Lead, and Purchase are not the same intrusion story. Search and lead events deserve extra scrutiny because they can include user-entered text.
- Read the URLs the pixel would have sent on the dates alleged. If folder names or query strings reveal something intimate, change the information architecture or stop sending those URLs.
- Do not rely on “everyone uses pixels” as the entire answer. Widespread use can undermine offensiveness, but a specific broken promise or a sensitive data type can cut the other way.
- Stop pre-consent firing. The letter’s offensiveness narrative depends on secrecy and lack of choice. A pixel that waits for a recorded decision is a different fact. That is also the core advice in our overview of how businesses are responding to Meta Pixel lawsuits.
How Captain Compliance helps on the facts, not on the jury instruction
No consent tool can promise that a judge will find an alleged intrusion inoffensive. Captain Compliance can make the underlying conduct harder to describe as secret. The consent manager can block the Meta Pixel until a choice is recorded and can honor Global Privacy Control. The scanner can show whether a “reject” or an opt-out signal actually stops the tag. Consent receipts and current privacy notices give counsel something concrete to put next to the HAR file. If the business uses the platform as intended, Compliance Shield may cover qualifying claims connected to consent and disclosure. The tort still has to be evaluated by a lawyer on its elements.
Frequently asked questions
Is a page view a “private affair”?
It can be, depending on what the page reveals and what the visitor was told. A public product page is a weaker privacy interest than a page whose URL discloses a medical, financial, or similarly intimate matter. Letters often assume the answer is always yes.
If I am offended, is that enough?
No. The standard is whether a reasonable person would find the intrusion highly offensive, considering context and degree. Personal upset is not the test.
Do we need to prove the visitor saw our privacy policy to defeat this claim?
Not necessarily, and “buried in a policy” is not a complete strategy. Notices still matter because they affect reasonable expectations. The cleaner operational answer is to stop sending the data until there is a documented choice and to make the disclosure match the tags that remain.
Offense is an element, not an adjective
Intrusion upon seclusion gives demand letters a familiar moral vocabulary: secrecy, dignity, someone watching. The law behind that vocabulary is more precise. It asks what was private, how far the defendant went, and whether a reasonable person would call that step highly offensive. For some pixel implementations, especially those that capture user-entered or sensitive information without any real choice, the tort is not imaginary. For a basic, disclosed advertising event, claim (c) is often there to lengthen the stack and to give the crime-tort exception another name to recite. Measure it against the facts on your site, not against the tone of the letter.
This article is for educational purposes and is not legal advice.
Put this into practice
Turn privacy guidance into working controls.
Captain Compliance helps teams discover tracking technologies, enforce consent, manage privacy requests and document the evidence behind every decision.
