When a key employee leaves with your customers, your clients’ data, files, or other company information, you have more ways to respond than a lawsuit. You can talk with the former employee, call the new employer’s owner, work to keep the customers, or have the devices examined. You can also settle the return in a short written agreement, send a demand letter, or ask a court for an order. Whichever you choose, the same first steps keep each of those options open: preserving the evidence, cutting off access, and asking for your property back without touching the final paycheck.
Trade secret claims are statutory. The Minnesota Uniform Trade Secrets Act (“MUTSA”), Minn. Stat. § 325C.01 and the sections after it, and the federal Defend Trade Secrets Act (“DTSA”), 18 U.S.C. § 1836, both reach misappropriation of information that qualifies as a trade secret. The employee’s duty of loyalty and the claim for conversion come from Minnesota court decisions rather than a statute. A signed agreement adds a contract claim, and Minn. Stat. § 181.988 voids employee noncompetes in agreements entered into on or after July 1, 2023, outside two narrow exceptions. This page is written for Minnesota owners responding to a taking that has already happened, and it is part of my material on trade secret protection for Minnesota businesses.
How Should You Preserve the Evidence?
I suggest setting aside the departing employee’s laptop, phone, email account, and system logs as they are, and stopping any routine wiping or reissue of that equipment. Those records can show what was copied, when, and where it went. Minnesota law also expects a business holding evidence to keep it once a lawsuit is foreseeable.
Miller v. Lankow, 801 N.W.2d 120 (Minn. 2011) was a homeowner’s moisture-damage case. In it, the Minnesota Supreme Court wrote that “we also reaffirm the fundamental duty of every party to preserve relevant evidence for use in litigation.” The court added that “even when a breach of the duty to preserve evidence is not done in bad faith, the district court must attempt to remedy any prejudice that occurs as a result of the destruction of the evidence.” The duty arises “whenever a party knows or should know that litigation is reasonably foreseeable,” and a company that wipes a laptop in the normal course after that point can lose the proof it needs and face a sanction at the same time.
The records worth holding include:
- The company laptop, tablet, and phone the employee used, powered down and stored.
- The employee’s company email account and cloud storage, suspended rather than deleted, with any automatic deletion turned off.
- Access, download, print, and remote-login logs, which some systems overwrite on a schedule.
- Texts and messages between managers and the employee in the final weeks.
- Screenshots of any posts or messages the former employee has sent your customers, with dates.
I suggest having a qualified forensic examiner copy each device before anyone in the company searches it, because opening files can change the dates that show when they were last used. When someone wrote to me about a former employee who had harmed the company, my suggestions included preserving the records relating to the former employee and the harm, including emails and text messages. I suggested keeping them without deleting or altering anything, and gathering the employee’s agreements and handbook. When a manager asked me about a letter to a former employee, I suggested saving screenshots, messages, and client reports with dates, because posts and messages can be deleted.
I suggest putting the findings in a short written investigation report as they come in. The report should cover a timeline of the departure and the suspected taking, the systems and devices reviewed, and the files or data copied, sent, or deleted. It should also carry the forensic examiner’s conclusions with copies of the supporting logs. That report can support a demand letter, a police report, or a court affidavit.
Signs of Data or IP Theft by an Employee
Warning signs of a taking include large downloads or print jobs in the weeks before a resignation and company files forwarded to a personal email account. Others are files copied to a USB drive or uploaded to a personal cloud account, access at unusual hours or to files outside the employee’s job, and login attempts after the employee has left. None of these proves theft by itself, because employees sometimes have innocent reasons. When you see several together around a departure, I suggest preserving the records and having a forensic examiner review them before you confront anyone.
How Do You Cut Off Access Without Exposing the Company?
I suggest disabling the former employee’s company accounts, collecting keys and badges, and changing any shared passwords the employee knew, such as vendor portals, social media accounts, and company cloud folders. Each one is a way back in. The employee’s personal email and cloud accounts are off limits without the employee’s authorization or a court process.
Two statutes set the line. Under the federal Stored Communications Act, 18 U.S.C. § 2701(a), it is an offense when a person “intentionally accesses without authorization a facility through which an electronic communication service is provided,” and obtains a stored communication. The statute excepts conduct authorized “by the person or entity providing a wire or electronic communications service,” which is why the email system your company provides stands differently from an account the employee opened with an outside provider. In Minnesota, under Minn. Stat. § 609.891, subd. 1, “A person is guilty of unauthorized computer access if the person intentionally and without authorization attempts to or does penetrate a computer security system or electronic terminal.” That statute applies to an employer as fully as to the employee.
Prompt revocation protects the information going forward, which matters for a later claim because a trade secret must be “the subject of efforts that are reasonable under the circumstances to maintain its secrecy,” under Minn. Stat. § 325C.01, subd. 5.
What Are the Rules for Getting Company Property Back?
I suggest asking the former employee in writing to return every company device, document, and file, and to identify any personal device or account where copies went. The same letter can ask the employee to sign a statement that the copies have been returned. I suggest paying final wages on the schedule Minnesota law sets while you do, because Minnesota law limits deductions from pay for lost or stolen property.
Under Minn. Stat. § 181.79, subd. 1, an employer may not deduct from wages “for lost or stolen property, damage to property, or to recover any other claimed indebtedness running from employee to employer.” The exceptions include when the employee, “after the loss has occurred or the claimed indebtedness has arisen, voluntarily authorizes the employer in writing to make the deduction or unless the employee is held liable in a court of competent jurisdiction for the loss or indebtedness.” Any written authorization “shall set forth the amount to be deducted from the employee’s wages during each pay period,” and a deduction “may not be in excess of the amount established by law as subject to garnishment or execution on wages.” Subdivision 2 makes an employer that violates the section liable “for twice the amount of the deduction or credit taken.”
The timing of final pay depends on how the job ended. When an employer discharges an employee, under Minn. Stat. § 181.13, “the wages or commissions actually earned and unpaid at the time of the discharge are immediately due and payable upon demand of the employee.” When the employee quits, under Minn. Stat. § 181.14, subd. 1, earned wages “shall be paid in full not later than the first regularly scheduled payday following the employee’s final day of employment,” unless a collective bargaining agreement provides otherwise. If the first regularly scheduled payday “is less than five calendar days following the employee’s final day of employment, full payment may be delayed until the second regularly scheduled payday but shall not exceed a total of 20 calendar days following the employee’s final day of employment.” Under subdivision 4, when a discharged or quitting employee was “entrusted with the collection, disbursement, or handling of money or property,” the employer “shall have ten calendar days after the termination of the employment to audit and adjust the accounts of the employee” before those wages are due.
I suggest asking for copies on personal devices to be returned or held, not deleted, until a forensic examiner has looked at them. A deletion destroys the proof of what was taken and where it went.
What Are Your Options When an Employee Leaves With Clients or Data?
You have at least nine ways to respond, legal and non-legal, and they can be combined. Each one fits a different goal, costs a different amount, and carries a different risk. The place to start is the outcome you want most: the information back, the harm stopped, or money for losses already suffered.
When someone wrote to me about a former employee who had harmed the company, I asked which outcome would be most valuable: recovering the money, stopping any ongoing harm, or holding the former employee accountable. The answer changes which of these routes fits:
- A direct conversation with the former employee. This fits when the relationship was good, the amount taken is small, or the employee may not have understood the obligation. It costs nothing but time. The risk is warning someone who then deletes or moves the information, so I suggest preserving the evidence first. When a manager asked me about a letter to a former employee, I suggested holding off on contacting the former employee until the business had legal advice. That way, the business’s first statement of its position would be the one it intended.
- An owner-to-owner call to the new employer. This fits when the new employer is an established business that has no interest in using your information. It costs little and can stop the use without a filing. Under Minn. Stat. § 325C.01, subd. 3, misappropriation includes use of a trade secret without express or implied consent by a person who, “at the time of disclosure or use, knew or had reason to know” where the information came from. That reaches information from someone with a duty to keep it secret. A new employer told the facts has its own reason to stop the use. The risk is that the new employer tells the employee, who then moves the files. I suggest describing what is missing and asking what the new employer will do, rather than accusing the employee, because your facts may still be incomplete.
- Keeping the customers. Reaching out to the affected customers first, with accurate statements about your service and no accusations about the former employee, can protect the relationships while the legal steps proceed. I suggest assigning a familiar person to each account, confirming who will serve it, and fixing any service gap the departure exposed. The cost is staff time. The risk is saying more than you can prove about the former employee, which can turn a customer conversation into a second dispute.
- A forensic review of the devices. A digital forensic examiner can show what was copied, sent, or deleted, and when, which tells you which of the other routes your facts support. The cost is the examiner’s fee, which grows with the number of devices and accounts. The risk is low when the review comes before anyone at the company opens the files.
- A return-and-certification agreement. This middle path is a short written agreement in which the former employee returns company devices and files and lets a neutral examiner find and remove company files from personal devices and accounts. The employee also signs a certification and confirms existing nondisclosure and nonsolicitation duties. It gets by agreement the kind of relief MUTSA allows a court to order, because under Minn. Stat. § 325C.02, “In appropriate circumstances, affirmative acts to protect a trade secret may be compelled by court order.” It fits a cooperative employee whose personal devices hold copies, and it costs less than a court order. The risk is a release written too broadly, which can give up claims you discover later, so I suggest limiting any release the business gives to what is known when it is signed.
- A demand letter. A cease and desist letter can identify the information, demand its return, ask for a signed certification, and put the employee and any new employer on written notice. It costs more than a call and less than a court filing. When that manager asked about a letter, I explained that an overstated letter can be used against the business later, so it should claim only what the facts support.
- A court order. A temporary restraining order or temporary injunction fits when the employee or a competitor is using or sharing the information now. It costs more than a letter and requires security, as explained in the next section.
- A lawsuit for damages. A suit fits when the harm has already happened, such as customers moved or sales lost. It is the costliest and slowest route, and its discovery process can reach the personal accounts you cannot open yourself. The claims section below describes what a suit can recover.
- A police report. A report fits when the conduct may be a crime, and it costs nothing to make. The risk is that prosecutors, not you, control what happens next, as explained in the section on crimes.
A demand letter carries its own legal risks. Under Minn. Stat. § 325C.04, a court “may award reasonable attorney’s fees to the prevailing party” when “a claim of misappropriation is made in bad faith.” A letter may also rely on a noncompete signed on or after July 1, 2023. Minn. Stat. § 181.988, subd. 2, calls that covenant “void and unenforceable.” The same subdivision lets a court award “an employee who is enforcing rights under this section reasonable attorney fees.” I suggest building the letter on the nondisclosure terms, nonsolicitation terms, and trade secret rights that survive, because those carry no fee exposure of that kind. A letter that threatens to report the employee to police carries a criminal risk too: under Minn. Stat. § 609.27, subd. 1, “Whoever orally or in writing makes any of the following threats and thereby causes another against the other’s will to do any act or forbear doing a lawful act is guilty of coercion,” and the listed threats include “a threat to make or cause to be made a criminal charge, whether true or false.”
The business side runs beside the legal one. I suggest telling the remaining team plainly that the employee has left, reminding them of their own confidentiality duties, and keeping speculation about the departure out of team conversations. Remarks inside the company can reach customers. A departure like this can feel personal, especially from a trusted employee. I suggest choosing among these routes by the outcome you named rather than by the anger of the moment, because a step such as an accusation to customers is hard to take back.
When Is a Temporary Restraining Order Worth Seeking?
A temporary restraining order (“TRO”) is worth seeking when the employee or a competitor is using or sharing the information now and money damages later would not undo the harm, such as customers being moved or a secret about to be disclosed. It costs more than a letter, it requires security, and on a temporary injunction the judge weighs a set of factors before ruling.
The Minnesota Rules of Civil Procedure set the steps. Under Minn. R. Civ. P. 65.01, a TRO may issue without notice “only if (1) it clearly appears from specific facts shown by affidavit or by the verified complaint that immediate and irreparable injury, loss, or damage will result to the applicant before the adverse party or that party’s attorney can be heard in opposition, and (2) the applicant’s attorney states to the court in writing the efforts, if any, which have been made to give notice or the reasons supporting the claim that notice should not be required.” Rule 65.02 provides that “No temporary injunction shall be granted without notice of motion or an order to show cause to the adverse party.” Rule 65.03 requires “the giving of security by the applicant, in such sum as the court deems proper,” to cover a party “found to have been wrongfully enjoined or restrained.”
For a temporary injunction, Minnesota judges weigh five factors from Dahlberg Bros., Inc. v. Ford Motor Co., 137 N.W.2d 314 (Minn. 1965), a car-dealer franchise case. The factors are the parties’ relationship before the dispute and the harm to each side from granting or denying the order. The others are the likelihood of success on the merits, public policy, and the burden of supervising the order. Applying those factors to former employees, the Court of Appeals stated in Softchoice, Inc. v. Schmidt, 763 N.W.2d 660 (Minn. Ct. App. 2009) that “Of these factors, the most important is a party’s likelihood of prevailing on the merits at trial.” The court affirmed an injunction on one employee’s nonsolicitation agreement. It also affirmed the denial of an injunction against a second employee, whose noncompete failed for lack of consideration under the Missouri law the contract chose.
A signed agreement can help on harm. In Cherne Industrial, Inc. v. Grounds & Associates, Inc., 278 N.W.2d 81 (Minn. 1979), the Minnesota Supreme Court quoted one of its earlier decisions and labeled the quoted statement dictum. That label means the statement was not needed to decide the earlier case. The statement was that “an inherent threat of irreparable injury may be inferred from the breach of an otherwise valid and enforceable restrictive covenant [not to compete or not to disclose trade secrets], sufficient to invoke at least temporary equitable relief.” The employees there had signed confidentiality and noncompete agreements, and the case predates both MUTSA and the 2023 noncompete ban.
The trade secret statutes add their own tools. Under § 325C.02, “Actual or threatened misappropriation may be enjoined,” and a court may compel affirmative acts such as returning files. In federal court, the DTSA allows a seizure order “upon ex parte application but only in extraordinary circumstances.” Among other findings, the court must find that an ordinary injunction would not work because the person “would evade, avoid, or otherwise not comply with such an order,” before it orders a seizure. A person harmed “by reason of a wrongful or excessive seizure” has “a cause of action against the applicant for the order under which such seizure was made” under the same seizure provision. A DTSA injunction may not “prevent a person from entering into an employment relationship,” and any conditions on the job must be “based on evidence of threatened misappropriation and not merely on the information the person knows.” Nor may the injunction “otherwise conflict with an applicable State law prohibiting restraints on the practice of a lawful profession, trade, or business.” Filing does not mean publishing your secret, because under Minn. Stat. § 325C.05, “a court shall preserve the secrecy of an alleged trade secret by reasonable means,” including protective orders and sealed records. How a case moves from that first order to a damages award is covered in trade secret litigation in Minnesota.
What Claims Does Minnesota Law Give Your Business?
A Minnesota business can have three kinds of claims against a former employee who took information. They are a trade secret claim under MUTSA or the DTSA and a claim for breach of the duty of loyalty or for conversion. The third is a contract claim on any surviving nondisclosure or nonsolicitation agreement, or on a noncompete signed before July 1, 2023. Each has its own conditions, and the facts of what was taken and what the employee signed decide which ones fit.
Trade Secret Claims Under MUTSA and the DTSA
Information is a trade secret under Minnesota law only if it has actual or potential value from not being generally known to, and not being readily ascertainable by proper means by, other people who can gain economic value from its disclosure or use. It also must be the subject of efforts that are reasonable under the circumstances to keep it secret. A customer list, pricing, a process, or source code can qualify. A claim reaches taking by improper means and use or disclosure in breach of a duty of secrecy.
Under Minn. Stat. § 325C.01, subd. 5, the information must be something that “derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use,” which rules out information a competitor could readily assemble from proper sources. It also must be “the subject of efforts that are reasonable under the circumstances to maintain its secrecy.” Before MUTSA, the Minnesota Supreme Court reasoned in Cherne that “even assuming the presence of an alternate means of obtaining the names of consulting engineers, this, without more, is not sufficient to establish that the information is generally ascertainable,” in a case about the employer’s information on its prospective customers. Subdivision 2 defines improper means to include “theft, bribery, misrepresentation, breach or inducement of a breach of a duty to maintain secrecy, or espionage through electronic or other means.” Under subdivision 3, misappropriation includes “acquisition of a trade secret of another by a person who knows or has reason to know that the trade secret was acquired by improper means.” It also includes “disclosure or use of a trade secret of another without express or implied consent by a person who,” among other routes, “at the time of disclosure or use, knew or had reason to know that the discloser’s or user’s knowledge of the trade secret was,” among other sources, “acquired under circumstances giving rise to a duty to maintain its secrecy or limit its use.” More on what counts as a trade secret is on a separate page.
The remedies follow. Under Minn. Stat. § 325C.03, “Damages can include both the actual loss caused by misappropriation and the unjust enrichment caused by misappropriation that is not taken into account in computing actual loss.” When “willful and malicious misappropriation exists, the court may award exemplary damages in an amount not exceeding twice any award made under paragraph (a).” Under § 325C.04, willful and malicious misappropriation can also support reasonable attorney fees to the prevailing party. If you are deciding which remedy to pursue, see how Minnesota trade secret remedies compare.
The federal act runs on a parallel track. Under 18 U.S.C. § 1836(b)(1), an owner may sue “if the trade secret is related to a product or service used in, or intended for use in, interstate or foreign commerce.” The court may award damages for actual loss and unjust enrichment, or a reasonable royalty instead, plus exemplary damages “not more than 2 times” those damages for willful and malicious misappropriation. Whether to add a federal Defend Trade Secrets Act claim is covered on its own page.
A forensic accountant or other damages expert can quantify your lost profits, the employee’s or competitor’s unjust enrichment, or a reasonable royalty. The expert works from your sales records, the customers who moved, and the other side’s records obtained in discovery.
You also have a limited time to investigate and sue. Under Minn. Stat. § 325C.06, “An action for misappropriation must be brought within three years after the misappropriation is discovered or by the exercise of reasonable diligence should have been discovered. For the purposes of this section, a continuing misappropriation constitutes a single claim.” The federal act is parallel: under 18 U.S.C. § 1836(d), a civil action “may not be commenced later than 3 years after the date on which the misappropriation with respect to which the action would relate is discovered or by the exercise of reasonable diligence should have been discovered.” I suggest checking the current text of both sections before relying on that period. Contract and computer-law claims carry their own deadlines, so I suggest starting the investigation as soon as you suspect a taking.
The Duty of Loyalty and Conversion
The duty of loyalty reaches what the employee did while still on your payroll, such as soliciting your customers for a new venture. It does not bar preparing to compete. For dealings with customers after the job ends, the Minnesota Supreme Court found no error in denying an injunction where no restrictive covenant applied, subject to the principles of unfair competition. That case is discussed below. Conversion reaches willful interference with company property, done without lawful justification, that deprives the company of its use and possession, such as keeping a laptop or original files.
Rehabilitation Specialists, Inc. v. Koering, 404 N.W.2d 301 (Minn. Ct. App. 1987) involved an employee with no written contract and no noncompete. The Court of Appeals stated that “An employee’s duty of loyalty prohibits her from soliciting the employer’s customers for herself, or from otherwise competing with her employer, while she is employed.” The same court recognized that “An employee has the right, therefore, while still employed, to prepare to enter into competition with her employer,” and that “An employee’s breach of his duty of loyalty may constitute unfair competition.” The court reversed a summary judgment in her favor and sent the case to trial. The Minnesota Supreme Court put the same line more plainly in Sanitary Farm Dairies, Inc. v. Wolf, 112 N.W.2d 42 (Minn. 1961): an employee “cannot feather his own nest at the expense of his employer while he is still on the payroll.” For dealings after departure, the court held, “In the absence of a restrictive covenant, and subject to the principles of unfair competition,” that denying a temporary injunction was not error. The same opinion held that the employee’s conduct in “lulling” the employer “into a belief that he had reconsidered his intention to quit” was unfair competition. It added that the trial court “should have enjoined defendants from soliciting or doing business with such customers until plaintiff had an adequate opportunity to do its own soliciting.” The court affirmed because it concluded that the restraining order it entered when the appeal was taken “has accomplished the same purpose, and that a temporary injunction is therefore no longer necessary.” More on the employee duty of loyalty is on a separate page.
Conversion is older and simpler. In DLH, Inc. v. Russ, 566 N.W.2d 60 (Minn. 1997), the Minnesota Supreme Court, quoting an earlier decision, defined it as “an act of willful interference with personal property, “done without lawful justification by which any person entitled thereto is deprived of use and possession.”” A company laptop or a box of files kept after you asked for it back is personal property of the company.
Both claims have a limit where trade secrets are involved. Under Minn. Stat. § 325C.07, MUTSA displaces “conflicting tort, restitutionary, and other law of this state providing civil remedies for misappropriation of a trade secret,” while preserving “other civil remedies that are not based upon misappropriation of a trade secret.” A loyalty or conversion claim is strongest when it rests on conduct beyond the trade secret taking itself. How these claims fit together when the employee leaves to compete is covered on a separate page.
What Does a Signed Agreement Add After the Noncompete Ban?
A signed nondisclosure or nonsolicitation agreement adds a contract claim that does not depend on proving a trade secret. That claim can include a breach of confidentiality at work by a current or former employee who signed one. Minnesota’s noncompete ban leaves those agreements in place. A noncompete signed on or after July 1, 2023, is void outside the sale-of-business and dissolution exceptions.
Under Minn. Stat. § 181.988, subd. 1, “A covenant not to compete does not include a nondisclosure agreement, or agreement designed to protect trade secrets or confidential information. A covenant not to compete does not include a nonsolicitation agreement, or agreement restricting the ability to use client or contact lists, or solicit customers of the employer.” Subdivision 2 provides that “Any covenant not to compete contained in a contract or agreement is void and unenforceable,” with exceptions when “the covenant not to compete is agreed upon during the sale of a business” or “in anticipation of the dissolution of a business.” The session law that enacted the ban, Laws 2023, chapter 53, article 6, section 1, states, “This section is effective July 1, 2023, and applies to contracts and agreements entered into on or after that date,” so an older noncompete needs a separate analysis. Kallok v. Medtronic, Inc., 573 N.W.2d 356 (Minn. 1998) arose from an executive’s noncompete agreements. In it, the Minnesota Supreme Court stated that noncompete agreements “are enforceable if they serve a legitimate employer interest and are not broader than necessary to protect this interest.” Quoting an earlier decision, the same court listed the elements of a claim against a third party, there the new employer, for interfering with a contract: “(1) the existence of a contract; (2) the alleged wrongdoer’s knowledge of the contract; (3) intentional procurement of its breach; (4) without justification; and (5) damages.” A void noncompete does not sink the rest of the document: “Nothing in this subdivision shall be construed to render void or unenforceable any other provisions in a contract or agreement containing a void or unenforceable covenant not to compete.”
MUTSA leaves contract claims alone. Under § 325C.07, the act does not affect “contractual remedies, whether or not based upon misappropriation of a trade secret.” The Minnesota Supreme Court in Cherne upheld relief where the former employees “had both contractual and common law duties not to disclose this information and not to use it to harm plaintiff’s business.”
How long the duty lasts depends on its source. A contractual confidentiality term lasts for the period the agreement states. Trade secret protection has no end date in MUTSA: information is protected while it still meets the subdivision 5 definition. Under Minn. Stat. § 325C.02, an injunction “shall be terminated when the trade secret has ceased to exist, but the injunction may be continued for an additional reasonable period of time in order to eliminate commercial advantage that otherwise would be derived from the misappropriation.”
A spoken confidentiality promise is harder to prove than a signed one, and I suggest putting every such promise in writing. Trade secret law does not depend on a written agreement, though. Under § 325C.01, subd. 3, misappropriation can take several routes. One is disclosure or use of a trade secret without express or implied consent. That route requires that the person, when disclosing or using it, knew or had reason to know the knowledge came with a duty of secrecy. As quoted above, that duty can arise from the circumstances in which the knowledge was acquired. The statute does not require that the duty be in writing. The information must still meet the subdivision 5 definition, including reasonable efforts to keep it secret.
Three conditions can limit what an agreement delivers. A nonsolicitation term must be reasonable. Quoting an earlier decision, the Softchoice court wrote that “In order to be enforceable, [non-compete] agreements must be reasonable and supported by consideration,” and it held “that the one-year duration of the non-solicitation period ordered by the district court was not unreasonable.” A nonsolicitation term signed after the job began needs something new in exchange. In Softchoice, the court held “that a promotion serves as consideration for a non-compete agreement at the time when the terms of the promotion have been defined and the promotion has been formally offered and accepted in writing.” And under the federal act, 18 U.S.C. § 1833(b)(3)(C), “If an employer does not comply with the notice requirement in subparagraph (A), the employer may not be awarded exemplary damages or attorney fees under subparagraph (C) or (D) of section 1836(b)(3) in an action against an employee to whom notice was not provided.” That notice describes the employee’s immunity for disclosures made in confidence “to a Federal, State, or local government official, either directly or indirectly, or to an attorney,” or in a sealed court filing. Subparagraph (A) calls for it “in any contract or agreement with an employee that governs the use of a trade secret or other confidential information,” for agreements entered into or updated after May 11, 2016. Under subparagraph (B), “An employer shall be considered to be in compliance with the notice requirement in subparagraph (A) if the employer provides a cross-reference to a policy document provided to the employee that sets forth the employer’s reporting policy for a suspected violation of law.” More on non-solicitation agreements in Minnesota is on a separate page.
When Does Taking Company Data Become a Crime?
Taking company data can be a crime under Minnesota and federal law when each statute’s elements are met, such as when a person “intentionally retains copies of any computer software or electronic data beyond the individual’s authority,” and you may report it to police. Reporting is your choice: prosecutors control a criminal case, and it does not by itself return your files or stop a competitor’s use.
Minnesota’s computer data theft statute, Minn. Stat. § 609.89, subd. 1, reaches a person who “intentionally retains copies of any computer software or electronic data beyond the individual’s authority.” It also reaches a person who “intentionally and without authorization or claim of right accesses or copies any computer software or electronic data and uses, alters, transfers, retains, or publishes the computer software or electronic data.” The penalty depends on the owner’s loss. Federal law, 18 U.S.C. § 1832(a), makes trade secret theft a crime. Among the listed acts is when a person knowingly and “without authorization copies, duplicates, sketches, draws, photographs, downloads, uploads, alters, destroys, photocopies, replicates, transmits, delivers, sends, mails, communicates, or conveys such information,” while acting “with intent to convert a trade secret, that is related to a product or service used in or intended for use in interstate or foreign commerce, to the economic benefit of anyone other than the owner thereof, and intending or knowing that the offense will, injure any owner of that trade secret.”
The federal Computer Fraud and Abuse Act also offers a civil claim, but a narrow one. Under 18 U.S.C. § 1030(g), “Any person who suffers damage or loss by reason of a violation of this section may maintain a civil action,” subject to conditions on the type of loss. Van Buren v. United States, 593 U.S. 374 (2021) was a criminal case. The U.S. Supreme Court read the act’s “exceeds authorized access” language as a “gates-up-or-down inquiry.” It held that the defendant did not violate it, “even though he obtained information from the database for an improper purpose.” An employee who downloaded files the job already allowed the employee to open may fall outside that language.
When a Fired Employee Deleted Company Files
Deleting or wrecking company data is a different wrong from copying it, and both Minnesota and federal law reach it. I suggest having a forensic examiner image the affected systems and backups before anyone tries to restore them, because the examiner may be able to recover deleted files and show who deleted them and when.
Minnesota’s computer damage statute, Minn. Stat. § 609.88, subd. 1, makes it a crime when a person “intentionally and without authorization damages or destroys any computer, computer system, computer network, computer software, or any other property specifically defined in section 609.87, subdivision 6,” and the penalty depends on the size of the owner’s loss. On the civil side, the federal Computer Fraud and Abuse Act defines “damage” in 18 U.S.C. § 1030(e)(8) as “any impairment to the integrity or availability of data, a program, a system, or information.” Section 1030(a)(5)(A) reaches a person who “knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer.” A civil suit under § 1030(g) “may be brought only if the conduct involves 1 of the factors set forth in subclauses” of the penalty section. One of those factors is “loss to 1 or more persons during any 1-year period . . . aggregating at least $5,000 in value.” Under § 1030(e)(11), “loss” means “any reasonable cost to any victim, including the cost of responding to an offense, conducting a damage assessment, and restoring the data, program, system, or information to its condition prior to the offense, and any revenue lost, cost incurred, or other consequential damages incurred because of interruption of service.” Subsection (g) also provides that “No action may be brought under this subsection unless such action is begun within 2 years of the date of the act complained of or the date of the discovery of the damage.” I suggest checking the current text of § 1030(g) before relying on that period.
When Must You Notify Customers, Employees, or Authorities?
Reporting a taking of business information to police is your choice, as described above. A separate notice duty can arise when the employee took computerized personal information about Minnesota residents, whether your customers or your own employees. Examples include a name combined with a Social Security number, driver’s license number, or financial account number with its access code.
The duty comes from Minn. Stat. § 325E.61, subd. 1(a). It reaches a business “that owns or licenses data that includes personal information, shall disclose any breach of the security of the system following discovery or notification of the breach in the security of the data to any resident of this state whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person,” and the next sentence of the subdivision sets the timing. It provides that “The disclosure must be made in the most expedient time possible and without unreasonable delay, consistent with the legitimate needs of law enforcement, as provided in paragraph (c), or with any measures necessary to determine the scope of the breach, identify the individuals affected, and restore the reasonable integrity of the data system,” which allows time for those measures. Under subdivision 1(e), personal information means a person’s name combined with “any one or more of the following data elements,” which are a Social Security number, a driver’s license or Minnesota identification card number, or a financial account or card number “in combination with any required security code, access code, or password that would permit access to an individual’s financial account,” in the statute’s words. A business that holds personal information it does not own, such as data kept for a client, “shall notify the owner or licensee of the information of any breach of the security of the data immediately following discovery,” under subdivision 1(b). Under subdivision 1(d), a breach “means unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of personal information maintained by the person or business.” The same definition matters for a departing employee: “Good faith acquisition of personal information by an employee or agent of the person or business for the purposes of the person or business is not a breach of the security system, provided that the personal information is not used or subject to further unauthorized disclosure.” An employee who copies payroll records or customer account data for personal use or a new employer falls outside that safe harbor. Under subdivision 2, notice to more than 500 people at one time also requires notice “within 48 hours” to the nationwide consumer reporting agencies. Under subdivision 1(c), notice “may be delayed to a date certain if a law enforcement agency affirmatively determines that the notification will impede a criminal investigation.”
Some businesses answer to their own industry rules. Subdivision 4 exempts any financial institution “as defined by United States Code, title 15, section 6809(3).” Health-care providers, banks, and other regulated businesses may have separate federal notice or safeguarding duties for patient or customer data. This page does not cover those industry rules, which sit outside the Minnesota statute described here. I suggest that a regulated business check them as soon as it learns personal data left with an employee.
What Other Professionals Help After an Employee Takes Company Information?
Several professionals each handle a different part of the response: a digital forensic examiner, the company’s IT provider, its insurance agent, a CPA or forensic accountant, a human resources professional, and a business attorney. Many first steps need no lawyer at all.
- A digital forensic examiner copies the devices and accounts, recovers deleted files, and reports what was copied, sent, or deleted and when. That report, and the examiner’s expert testimony if a case goes to court, can be the core of the proof.
- The company’s IT provider or administrator disables accounts, suspends the mailbox, and keeps the logs from overwriting. I suggest asking the IT provider to preserve, not search, the departing employee’s devices until the examiner has copied them, because searching changes the file dates.
- The company’s insurance agent can answer whether any policy responds to the loss, such as commercial crime or employee dishonesty coverage, or a cyber policy if personal data left with the employee. I suggest reading the policy’s notice terms early, because the policy’s own words decide what is covered and how a claim must be reported.
- A CPA or forensic accountant measures the loss, including the actual loss and unjust enrichment that Minn. Stat. § 325C.03 allows a court to award.
- A human resources professional handles the exit paperwork, the final pay schedule, and what the remaining team is told.
- A business attorney writes the demand letter or the return-and-certification agreement, analyzes which claims your facts support, and brings any court filing.
Setting the devices aside, disabling accounts, asking in writing for your property, paying final wages on time, and talking with your customers are steps you can take yourself. Those steps also protect whichever legal route you choose later.
How Can You Protect Your Business From Future Employee Data Theft?
Prevention works best in layers. Under MUTSA, information qualifies as a trade secret only if it “is the subject of efforts that are reasonable under the circumstances to maintain its secrecy.” I suggest these steps:
- Need-to-know access. Give each employee access only to the files and systems the job requires, use role-based permissions, encrypt sensitive data, and keep audit trails of who opens and downloads what. Lock physical files and restricted areas too.
- Training. Teach employees what your confidential information is, why it matters, and what your confidentiality policy requires, at hiring and at regular intervals afterward.
- Signed agreements. Use a written nondisclosure and, where it fits, a nonsolicitation agreement, with the federal whistleblower-immunity notice described above.
- Exit reminders. At the exit interview, remind the departing employee of the confidentiality agreement in writing and collect all company property. Ask the employee to sign an acknowledgment that every company file has been returned and that the confidentiality duties continue.
- Monitoring tools. Data-loss-prevention software, alerts on large downloads or uploads to personal cloud accounts, and blocks on USB storage can flag a taking while it is happening. Disable every account, token, and password on the last day.
- Retention and disposal. Keep sensitive data only as long as you need it and destroy it securely after that, because data you no longer hold cannot be taken.
Can I look through the former employee's personal email or cloud account to see what was taken?
Not without the employee’s permission or a court process. Under 18 U.S.C. § 2701, intentionally accessing without authorization a facility through which an electronic communication service is provided, and thereby obtaining a communication in electronic storage there, is a federal offense. Minn. Stat. § 609.891 makes it a crime to intentionally and without authorization attempt to or penetrate a computer security system or electronic terminal. I suggest reviewing the systems your company provides and using a lawsuit’s discovery process for the personal accounts, because that path keeps the evidence usable.
Is a customer list a trade secret if the customers can be found online?
It can be. Under Minn. Stat. § 325C.01, subd. 5, it needs actual or potential value from not being generally known or readily ascertainable by proper means, and reasonable efforts to keep it secret. Guarded pricing and buying history strengthen a list. Before that statute, Minnesota’s Supreme Court reasoned in 1979 that another source of the names, “without more, is not sufficient to establish that the information is generally ascertainable,” but in 1961 declined to treat as a trade secret a route driver’s customers, “whose patronage has been secured by the joint efforts of an employer and a route employee.”
Can I also bring a claim against the employee's new employer?
Possibly. Under Minn. Stat. § 325C.01, subd. 3, misappropriation can include the new employer’s use of a trade secret. That use counts when it is without express or implied consent and the new employer, when using it, knew or had reason to know it came from a person owing you a duty of secrecy. Written notice can supply that knowledge. Under Minn. Stat. § 325C.03, a material and prejudicial change of position before it knew or had reason to know of misappropriation can make a monetary recovery inequitable. If it knew of the employee’s valid agreement and intentionally procured its breach without justification, causing damages, it can be liable for interference.
Do I have to warn the employee before asking a judge for a restraining order?
Not always. Minnesota Rule of Civil Procedure 65.01 allows a temporary restraining order without notice only if two conditions are met. Specific facts in an affidavit or verified complaint must show immediate and irreparable injury before the employee can be heard. Your attorney must also state in writing what efforts were made to give notice or why notice should not be required. A temporary injunction, the longer order, requires notice of motion or an order to show cause under Rule 65.02.
What if the former employee says the documents were taken to report a legal violation?
Federal law protects some such disclosures, not the taking. Under 18 U.S.C. § 1833(b), an individual is not liable under any federal or state trade secret law for two kinds of disclosure. One is a disclosure in confidence to a government official or to an attorney, solely to report or investigate a suspected violation of law. The other is a disclosure in a sealed court filing. The immunity does not cover using the information to compete or sharing it with a new employer. Nor does the section “limit liability for, an act that is otherwise prohibited by law, such as the unlawful access of material by unauthorized means.”
Should I wait to see whether the employee actually uses the information?
Waiting has costs. Minn. Stat. § 325C.02 allows a court to enjoin actual or threatened misappropriation, so you do not need proof of use before asking for an order. Waiting also lets device and account records age. Under Minn. Stat. § 325C.06, “An action for misappropriation must be brought within three years after the misappropriation is discovered or by the exercise of reasonable diligence should have been discovered.” I suggest checking the current text when you learn of the taking.
Responding When an Employee Leaves With Your Information
I suggest taking the steps in a set order, because each earlier step protects the later ones. First comes preserving the devices and records, then cutting off access without entering the employee’s personal accounts. Next comes asking for your property back while paying final wages on time, and then choosing the least costly route that will stop the harm. That route may be a conversation, a call to the new employer, a push to keep the customers, a return-and-certification agreement, a demand letter, or a court order.
Protection for the next departure should be in place before anyone resigns. My page on how to stop employees from taking company information covers it, along with my broader material on Minnesota trade secret protection. If a former employee has taken information from your business and you want to know which route fits your facts, email [email protected] with a brief description. I can start an intake and conflict check before you send any confidential documents.