Skip down to the research record

Minnesota aggrieved person and contents: 2 wiretap terms

Quota Forecast Editorial Team · Published · 11 min read

Minnesota defines an aggrieved person as a party to an intercepted communication or a person it was directed against. The two terms work as a pair: one names who, the other names what.

Key takeaways

  • Aggrieved person: a party to the intercepted communication, or a person against whom the interception was directed
  • Contents: any information about the substance, purport, or meaning of the communication — audio, transcripts, notes, or CRM summaries can qualify when they carry that information
  • Both definitions live in the same statute, Section 626A.01 of the Minnesota Statutes
  • The definitions answer standing and scope only — they do not settle consent, liability, or remedy
  • The backup carve-out covers storage by an electronic communication service, not your team's own archive of calls

Why these two definitions matter for your case

When a recorded call goes wrong, everything starts with two questions. Who counts as the person harmed? And what counts as the captured material? Minnesota answers both in one definitions section of its wiretap statute. If your revenue team records calls, these two terms tell you who could bring a claim and what they could point at.

The first term is aggrieved person. Minnesota defines this as a person who was a party to the intercepted communication or a person against whom the interception was directed. That definition comes from Section 626A.01 of the Minnesota Statutes. Two doors open there: the person on the call, and the person the call was aimed at.

The second term is contents. Minnesota says this covers any information about the substance, purport, or meaning of the communication. The same statute sets that out. That is a broad reach. Tone, numbers, names, commitments — if it reveals what the call meant, it sits inside the term.

Together, these two definitions decide the shape of any dispute. A revenue leader who knows them can tell, before counsel is even billable, whether a recorded conversation puts a Minnesota party at risk and what material could be in play.

What a party means under Minnesota law

The aggrieved-person definition splits into two prongs. The first prong is straightforward: you were on the call. If a prospect in Minneapolis was speaking when a rep recorded, that person was a party. The statute names this plainly.

The second prong is where deals get complicated. A person against whom the interception was directed can also claim the status. Think of a call where a rep screenshares a spreadsheet. The person listed in that sheet never said a word. Capture alone does not satisfy the second prong. The question is whether the interception was directed against that person, which is a fact question for counsel.

For a revenue team, the practical read is this. Recording a call with a Minnesota counterpart puts that counterpart inside the definition automatically. Recording a call that incidentally surfaces a third party's data does not by itself make that person aggrieved. Standing for a non-party depends on whether the interception was directed against them. Only the second path needs a closer look.

The definition requires the person to be tied to the interception — either on the call or targeted by it. A person who merely heard about the recording later, with no connection to it, does not fit the words on the page. That limit matters when your team triages complaints. Not every complaint about a recording comes from someone the statute describes.

Illustrative example: one call, two prongs

A revenue leader records a 20-minute discovery call with a buyer in Minnesota. The buyer was on the line from the start, so that buyer is a party and fits the first prong. Later, the rep shares a screen listing 3 other accounts. None of those account contacts speak on the call. Their names are captured in the recording. Whether any of them is an aggrieved person depends on whether the interception was directed against that person, not on the capture alone. The team logs the buyer's join time, notes the screen share, and sends the questions to counsel.

What counts as contents

The second definition swings the other way. Contents reaches wide. It is not limited to the words spoken. It includes any information about the substance, purport, or meaning of the communication. The Minnesota statute gives that definition directly.

Read it carefully and it sweeps in more than transcripts. A recording's tone can reveal meaning. A pause can reveal meaning. A rep's offhand mention of a discount structure reveals meaning. All of it sits inside the term as written.

This breadth has a consequence for your retention policies. If you keep recordings, you are keeping contents. If you keep notes generated from recordings, those notes may also qualify, because they carry the meaning of what was said. The definition does not care about format.

One carve-out does exist in the same section. The backup clause is clause (2) of the statute's storage definition, covering storage by an electronic communication service for backup protection of the communication. That carve-out is narrow. It covers service-provider backup, not a revenue team's archive of calls it chose to keep.

The plain read: if a document, snippet, or summary tells you what a call meant, Minnesota's statute treats it as contents. Plan your retention around that.

Side-by-side view of the two terms

Here are the two Minnesota terms laid out for quick reference.

TermWhat it capturesKey source
Aggrieved personA party to the intercepted communication, or a person against whom the interception was directedSec. 626A.01
ContentsAny information about the substance, purport, or meaning of the communicationSec. 626A.01

How these terms play out on a recorded sales call

Take a discovery call. Your rep is in Illinois. The buyer is in Minnesota. The rep records. Under the statute's first prong, the buyer was a party. Whether Minnesota law reaches a call between an Illinois rep and a Minnesota buyer is a separate question that needs analysis.

Now add a wrinkle. The buyer pulls in a colleague on the line. That colleague never signs anything and never agrees to recording. They were on the call, so the first prong still reaches them. Being added last-minute does not remove party status.

Consider the second prong instead. Your rep shares a screen showing a list of other prospects. None of them are on the call. Those people fit the second prong only if the interception was directed against them. Incidental capture of their names and company details does not by itself meet that test.

Your team's workflow should reflect both paths. Before a call, confirm who is on the line. During the call, watch what surfaces on screen. After the call, check whether any third-party data was captured. Each check maps to a clause in the definition.

The contents term enters at the same moment. A recording captures the words, which carry substance and meaning. Your post-call notes carry meaning too. Your CRM summary carries meaning. All of it is contents under the statute's language.

This is why retention policy and consent policy have to be designed together. You are not just storing audio. You are storing contents in every derived form.

What a revenue leader should check before the call

Before anyone hits record, run a short checklist. It maps directly to the two definitions.

Party status. Confirm every person on the call. A party can claim aggrieved-person status by definition. If someone joins mid-call, log when they joined.

Target status. Ask whether the call will surface data about anyone not present. Screen shares, shared documents, and read-outs from other accounts can all pull in outside persons.

Contents scope. Identify what forms of the communication you will keep. Audio, transcripts, notes, and CRM summaries can each carry that meaning, and when they do, each is contents.

Backup carve-out. Distinguish your own archive from a provider's backup. The statute's carve-out covers backup storage by an electronic communication service, not your choice to keep calls.

Consent path. Whether one-party or all-party consent applies on a given call is a question for counsel, not something these two definitions settle on their own.

That last point is worth stating plainly. The aggrieved-person and contents definitions tell you who and what. They do not tell you whether recording was lawful in the first place.

Where the definitions stop

These two terms do real work, but they do not do all the work. They answer standing and scope. They do not answer liability, remedy, or consent.

A person can satisfy the aggrieved-person definition and still have no claim, if the recording was lawful. A file can qualify as contents and still be retained without issue, if retention is permitted. The definitions are the entry gate, not the verdict.

This is where sources leave a question open: whether a particular recording scheme required consent, and what remedy follows, depends on facts these two definitions do not reach. Ask Minnesota counsel with the call facts in hand.

What the Massachusetts provisions show about adjacent issues

Revenue teams operating across state lines will sometimes encounter other states' rules in the same file. Massachusetts' wiretap statute addresses adjacent issues worth naming, because they surface in the same review.

Massachusetts allows duplicate recordings to be made for use in investigations under specified circumstances. Its statute also sets a service rule for one kind of recording: where the Commonwealth intends to offer evidence from recordings made under the paragraph B, subparagraph 4 exceptions in a criminal trial, the defendant must be served with a complete copy of each recording or a statement under oath of the evidence overheard. Both provisions come from Chapter 272, Section 99 of the Massachusetts General Laws.

That same section also lists a reasonable attorney's fee and other litigation disbursements reasonably incurred among available relief.

These Massachusetts points are not Minnesota rules. They are here because your team will see them alongside Minnesota material in multi-state files, and confusing the two is a common error. For another state's recording rules, see Montana recording penalty cases. Minnesota's aggrieved-person and contents definitions stand on their own text.

Common mistakes revenue teams make

The first mistake is treating party status as a formality. If someone was on the call, they fit the first prong. Logging who joined and when is not optional paperwork. It is a threshold fact for standing, and it does not settle liability.

The second mistake is narrowing contents to transcripts. The definition reaches meaning in any form. A bulleted summary of a call can be contents. Your retention rules should cover derived files, not just audio, and a call transcript record is one such file.

The third mistake is reading the backup carve-out too broadly. It names an electronic communication service storing a communication for backup protection. It does not bless a company's decision to keep its own call library.

The fourth mistake is assuming a bystander has no standing. The second prong reaches persons against whom the interception was directed. A screen share that incidentally captures an outside person's data does not by itself satisfy the second prong. Ask whether the interception was directed against that person.

The fifth mistake is letting the definitions answer a consent question. They do not. Route that question to counsel with the call facts.

Practical steps for your team this quarter

Start by mapping your recording stack. List every place a call can live: the recording platform, the transcript service, the CRM, and any notes app. Each location holds contents.

Next, tag your call flows by party status. Calls wholly inside your team, calls with one external party, and calls with multiple external parties each warrant a different handling rule.

Then audit screen-share practice. Screen sharing carries a data-exposure risk. Standing under the second prong depends on whether the interception was directed against a person, not on incidental capture. A habit of sharing live dashboards can pull in persons who were never on the call.

Write your retention rule in plain language. State that you keep recordings and derived notes for a defined period, and that the backup carve-out does not apply to your own archive. Make the rule match the statute's words.

Finally, brief your reps on the two definitions in one short session. Reps who understand that "party" and "meaning" carry legal weight will log joins and watch screens without being chased. For the wider rules on recorded business calls, see wiretap exceptions for recorded business calls.

Related guides: Recorded call interception: 3 Minnesota terms to check · Minnesota commission pay: 2 methods and the postmark date.

Questions this analysis leaves open

The two definitions do not resolve consent or remedy. Those answers depend on the specific statute's other provisions and the facts of each call. For a recorded call that could involve Minnesota parties, ask a Minnesota lawyer with the call log, recording, and screen-share history in hand. That is the one open question this post does not close, and it matters most when a complaint has already arrived.

Quick FAQ

Does being added to a call mid-way remove someone's party status? No. The first prong of the definition covers a person who was a party to the intercepted communication. If they were on the line when it was recorded, they fit the words. Log the join time for your records.

Are CRM notes contents? If they carry the substance, purport, or meaning of the call, they fit the definition. The statute's language reaches any information about what the communication meant. Keep them under the same retention rule as audio.

Does the backup carve-out cover our own recordings? No. The carve-out describes storage by an electronic communication service for backup protection of the communication. It is not a general license for a company to archive its own calls.

Can a person who never spoke complain? Yes, if they fall under the second prong — a person against whom the interception was directed. A screen share that incidentally captured their data does not by itself place them under the second prong. The interception must have been directed against them.

Do these two definitions tell you whether recording was legal? No. They identify who can claim status and what material counts. Whether consent was required is a separate question for counsel.

Where do I find the exact statutory wording? Both definitions sit in Section 626A.01 of the Minnesota Statutes, published by the Office of the Revisor of Statutes.

Sources