The Four Privacy Torts Every Caller Should Know

If your business makes outbound calls, you are operating in a legal neighborhood most teams underestimate. Privacy torts have been quietly producing seven-figure verdicts for decades, and a fresh wave of class actions is now targeting AI-assisted calling tools specifically.

Invasion of privacy is an intentional tort, primarily controlled by state law and built through common law rather than statute. According to Cornell Law School's Wex, every recognized claim shares one thread: an unwelcome or unauthorized intrusion into a person's private life. Three independent legal authorities, Cornell, FindLaw, and the Student Press Law Center, name the same four torts.

• Intrusion on seclusion, Liability applies when the intrusion would be highly offensive to a reasonable person. A few unsolicited calls may not qualify, but FindLaw warns that repeated calls after being asked to stop would be invasive.
• Public disclosure of private facts, True information about medical conditions, sexual conduct, or educational records can create liability. Notably, truth is not a defense, unlike in defamation.
• False light, Publicizing information that is misleading rather than outright false. In Peoples Bank and Trust Co. v. Globe International Publishing, a 96-year-old woman received a $1.5 million verdict after her photo appeared beside a headline implying she was pregnant.
• Appropriation of name or likeness, Using someone's identity for commercial benefit without permission. For public figures this overlaps with the right of publicity.

State variation matters here. New York does not recognize common law privacy rights at all. Courts in North Carolina, Colorado, Florida, Texas, and Virginia have declined to treat false light as a distinct cause of action.

The most relevant risk for outbound calling is intrusion on seclusion, because the facts line up directly with phone contact. But the bigger near-term exposure is a newer wave. As of mid-2025, class actions have emerged targeting GenAI conversation-intelligence tools that transcribe and summarize calls in real time. Plaintiffs allege these tools eavesdrop in violation of wiretap statutes like the California Invasion of Privacy Act, even when callers are told the call may be recorded. The precedent case, Ambriz v. Google LLC, survived a motion to dismiss in February 2025, and several similar suits followed within weeks. More than a dozen comparable state wiretap laws exist nationwide.

Across all four torts, consent is the universal defense, and written consent is the easiest to prove. That single legal fact shapes how a managed calling operation should be built. A service that reviews list source and consent records before launch, honors STOP and REVOKE keywords immediately, carries opt-outs across every campaign, and discloses AI on every call is not just polite. It is documenting the defense that shuts down intrusion claims before they start.

Why Intrusion and Wiretap Claims Hit Call Centers Hardest

A few unsolicited calls rarely rise to the level of a legal claim. Repeated calls after someone asks you to stop are a different story, and that distinction sits at the center of how privacy law treats outbound calling.

FindLaw's overview of invasion of privacy notes that while a handful of unsolicited calls may not qualify as intrusion, repeated calls after being asked to stop would be invasive. That single sentence explains why intrusion of solitude is the first of the four torts that matters most for call centers. The second is the wiretap exposure now building around AI call tools.

In February 2025, Ambriz v. Google LLC survived a motion to dismiss, and a Holland & Knight litigation analysis reports that several similar class actions followed within months. Plaintiffs allege that GenAI conversation-intelligence tools eavesdrop on calls without consent, even when callers are told the call may be recorded. More than a dozen state wiretap laws exist nationwide, and the same analysis notes that investigations now reach beyond tool developers toward the organizations using those tools.

State law adds another layer of variation that outbound teams cannot ignore:

• New York does not recognize common law privacy rights, per FindLaw's state-by-state discussion.
• Five states reject false light as a distinct cause of action, according to Freedom Forum's analysis.
• More than a dozen state wiretap statutes create separate consent standards for recorded or monitored calls.

Consent is the defense that travels across all four torts. The Student Press Law Center explains that consent must come from someone with the legal right to give it, must be candid about how the information will be used, and is easiest to prove when it is in writing.

That is the standard My AI Call Center builds its campaigns around. Lists are checked for source and consent records before launch, bought lists without clear permission records get flagged or declined, opt-outs are logged and honored immediately, and AI disclosure runs on every call. If the list will not support the campaign, you hear it before you spend anything.

Run structured outbound campaigns against approved, permissioned lists, with consent records reviewed before any call goes out. Campaigns start at 9¢ per connected minute. Plan your campaign at https://myaicallcenter.app/campaigns.

Consent: The One Defense That Works Against All Four

If you've read this far, you might expect that defending against four different privacy torts requires four different strategies. It doesn't. There's one defense that works against all of them.

The Student Press Law Center puts it plainly: "with all four forms of invasion of privacy, consent is a valid defense." The consent must come from someone with the legal right to give it, and it must be candid about how the information will be used. Most importantly, SPLC notes that consent is easiest to prove in writing.

That last point matters more than most organizations realize. A verbal assurance from a contact, or a vague assumption that someone "signed up for updates," won't hold up when a dispute lands in front of a lawyer. A timestamped record showing what the person agreed to, and when, will.

Holland & Knight's 2025 analysis of the GenAI call center litigation wave reinforces this from the litigation side. Their guidance for organizations adopting AI calling tools comes down to four practical steps:

• Obtain and document express consent from users and customers before calls begin.
• Ensure privacy policies accurately reflect how data is actually collected and used.
• Disclose the technology on calls, since plaintiffs allege "eavesdropping" even where callers are told calls may be recorded.
• Consult outside defense counsel and review indemnification provisions before onboarding any tool.

The stakes are real. The precedent case in this wave, Ambriz v. Google LLC, was filed in late 2023 and survived a motion to dismiss in February 2025, and more than a dozen similar state wiretap laws exist nationwide. Prior technology waves produced hundreds of class actions.

This is why consent records are the hinge of any compliant calling program. My AI Call Center checks list source and consent records before any campaign launches, flags bought lists without clear permission records, and in most cases declines them outright. AI disclosure happens on every call, recording is optional and consent-based, and opt-outs are logged and honored immediately.

None of this is complicated. It's just discipline: document what you have permission to do, then do only that. As SPLC's guidance makes clear, documented consent is the one shield that stands up against intrusion, disclosure, false light, and appropriation alike. Campaign requirements still vary by location, industry, and technology, so get appropriate legal guidance before launch.

How My AI Call Center Builds These Defenses Into Every Campaign

The legal theory matters less than the defense. Across all four invasion of privacy torts, legal guidance is clear: consent is a valid defense, and written, documented consent is the easiest kind to prove. That single principle shapes how My AI Call Center builds every campaign.

The stakes are not theoretical. As of July 2025, class actions have begun targeting GenAI call center tools under state wiretap statutes like the California Invasion of Privacy Act, with plaintiffs alleging the tools "eavesdrop" on calls without consent, even when callers were told the call might be recorded. The precedent case, Ambriz v. Google LLC, survived a motion to dismiss in February 2025, and several similar suits followed within weeks. Attorneys at Holland & Knight advise organizations adopting these tools to obtain and document express consent and ensure privacy policies accurately reflect how data is used.

Here is how those defenses map to concrete practice, step by step:

• List and consent review before anything launches. Every campaign starts with a review of list source, consent records, and calling windows. Bought lists without clear permission records get flagged, and in most cases declined. You hear it plainly before you spend anything.
• AI disclosure on every call. Recipients can ask whether the call is AI-assisted, request a human, or opt out. This addresses the exact gap the current litigation wave is exploiting: consent obtained after or around the AI's involvement, rather than before it.
• Opt-outs honored immediately, with logs that follow the contact. FindLaw notes that a few unsolicited calls may not qualify as intrusion, but repeated calls after being asked to stop would be invasive. STOP and REVOKE keywords trigger immediate opt-out handling, and DNC requests are carried across all campaigns into client DNC records, so a contact who opted out of one campaign is not called in the next.
• Recording only with disclosure and consent. Recording is optional, never automatic, and never happens without the recipient knowing. Data is never shared or sold and is not used to train shared models.
• Nothing launches until you approve. The script, the disclosure language, the opt-out handling, and the escalation path all go through your review first. One clear goal per campaign, quoted before launch.

That last item matters more than it sounds. Intrusion claims turn on what a reasonable person would find highly offensive, and state law varies widely: New York does not recognize common law privacy rights, five states reject false light as a distinct claim, and more than a dozen state wiretap laws exist nationwide. What is compliant in one jurisdiction may not be in another, which is why the escalation path and calling windows are set per campaign, not per template.

One caveat worth stating plainly: campaign requirements vary by location, industry, contact type, consent status, and technology. Clients are responsible for obtaining appropriate legal guidance before launch. A managed service can build the defenses in, but the legal sign-off belongs with you and your counsel.

If you want structured outbound calls run against approved, permissioned lists, with consent records checked before the first dial, campaigns start at 9¢ per connected minute. Plan your campaign at myaicallcenter.app/campaigns.

A Pre-Launch Privacy Checklist You Can Run Today

You don't need a legal team to run a compliant outbound campaign. You need a specific, repeatable process.

The core defense against privacy torts is documented consent. As legal analysis from the Student Press Law Center notes, written consent is the easiest form to prove in court. If you cannot show how you obtained permission to call a specific number, you are exposed.

Start by auditing your list source. Verify that every contact has a clear, written record of prior express consent. If a list lacks these records, flag it immediately. Do not proceed with contacts where the permission trail is broken or ambiguous.

Next, check your calling windows against state quiet-hour rules. More than a dozen state wiretap laws exist nationwide, and they vary by jurisdiction. Ensure your dialing system respects local time zones and specific day restrictions. This prevents the "intrusion of solitude" claims that arise from repeated calls after being asked to stop.

You must also disclose AI and recording practices on every single call. Recent litigation targeting GenAI tools alleges that these systems "eavesdrop" without proper consent, even when recording is mentioned. To mitigate this risk, you must clearly state that the call is AI-assisted. Recording should only occur if you have explicit, documented consent.

Finally, honor opt-outs within the campaign itself. If a recipient uses a keyword like "STOP" or "REVOKE," the system must log the request and honor it immediately. Do not wait for the campaign to end. Log these opt-outs and carry them into your permanent DNC records to prevent future intrusion.

Here is the pre-launch checklist to run today:

• Verify list source and consent records for every contact.
• Check calling windows against state quiet-hour and day restrictions.
• Disclose AI usage and recording practices on the initial script.
• Configure immediate opt-out handling for STOP and REVOKE keywords.
• Document all consent and opt-out data in writing before launch.

My AI Call Center builds this discipline into every managed campaign. We review list sources and consent records before any call goes out. If a list cannot support the campaign legally, we tell you plainly before you spend anything. We handle the compliance heavy lifting so you can focus on the outcome.

Run structured outbound campaigns against approved, permissioned lists. Campaigns start at 9 cents per connected minute. Plan your campaign at myaicallcenter.app/campaigns.