What Should Companies Know Before Producing Trade Secrets or Sensitive Business Records in Litigation? Florida, North Carolina, and Federal Litigation Guide

Companies should not produce trade secrets or sensitive business records in litigation without first evaluating relevance, confidentiality, privilege, protective orders, attorneys’ eyes only restrictions, sealing procedures, redactions, ESI controls, and who will have access to the information. Litigation may require disclosure of relevant business records, but disclosure should be structured to reduce competitive harm, preserve trade secret protection, and avoid unnecessary public exposure.

In Florida, North Carolina, and federal business litigation, sensitive information should be handled before production—not after it has already been delivered, filed publicly, or shown to a competitor. A company should treat production of trade secrets, customer lists, pricing, source code, financial records, proprietary methods, strategic plans, and confidential commercial information as a litigation-risk decision with discovery, injunction, trial, settlement, and appeal consequences.

The answer depends on several factors

What a company should do before producing trade secrets or sensitive business records depends on:

1. Whether the case is in Florida state court, North Carolina state court, federal court, arbitration, Business Court, or an appellate court

2. Whether the information is a trade secret, confidential commercial information, financial record, customer list, pricing model, source code, product roadmap, vendor contract, payroll record, acquisition file, board material, or personal identifying information

3. Whether the information is relevant and proportional to the needs of the case

4. Whether the information is privileged, work product, confidential but discoverable, or not discoverable

5. Whether a protective order has been entered

6. Whether ordinary confidential treatment is enough or attorneys’ eyes only treatment is needed

7. Whether the receiving party is a competitor, former employee, customer, vendor, investor, regulator, or business adversary

8. Whether experts, consultants, vendors, in-house counsel, executives, or business decision-makers will see the records

9. Whether the production involves ESI, metadata, native files, databases, Teams, Slack, mobile messages, source-code repositories, or accounting exports

10. Whether the records may later be attached to motions, used at injunction hearings, filed at summary judgment, offered at trial, or included in the appellate record

11. Whether redaction, sealing, in-camera review, phased discovery, sampling, source-code protocol, or a neutral expert is needed

12. Whether disclosure could waive trade secret protection, violate contractual confidentiality obligations, trigger privacy obligations, or affect business operations

13. Whether the company must respond to a party discovery request, third-party subpoena, regulatory demand, or court order

14. Whether emergency relief, sanctions, remand, or appeal issues may arise

The core question is not only “Do we have to produce this?” The better question is “How can we produce only what is required, under protections that preserve confidentiality and litigation strategy?”

What counts as sensitive business records?

Sensitive business records may include information that is not necessarily privileged but could harm the company if disclosed broadly.

Examples include:

• Trade secrets

• Customer lists

• Pricing models

• Discount structures

• Profit margins

• Source code

• Technical specifications

• Product roadmaps

• Manufacturing processes

• Research and development

• Proprietary formulas

• Sales strategies

• Vendor contracts

• Supplier pricing

• Franchise records

• Business plans

• Marketing plans

• Strategic plans

• Board materials

• M&A documents

• Investor materials

• Financial statements

• Tax records

• Bank records

• Payroll records

• Employee compensation

• Cybersecurity information

• Access logs

• Download logs

• CRM records

• Accounting exports

• Internal investigations

• Confidential settlement materials

• Nonpublic regulatory submissions

• Data security policies

• Personal identifying information

Not all sensitive information is protected from discovery. But sensitive information may require controlled production.

What is a trade secret?

A trade secret is business information that derives value from not being generally known and is subject to reasonable efforts to maintain secrecy. The precise definition depends on the governing law, but trade secret disputes often involve information such as formulas, methods, programs, processes, customer data, pricing, technical designs, source code, and business strategies.

The company should be ready to show:

• What the alleged trade secret is

• Why it has independent value

• Who had access to it

• How it was protected

• Whether confidentiality agreements were used

• Whether access controls existed

• Whether the information was shared outside the company

• Whether the information is public or readily ascertainable

• Whether disclosure in litigation could harm secrecy

If a company treats information casually during discovery, it may weaken later arguments that the information is truly secret.

Confidential does not always mean privileged

A common mistake is confusing confidentiality with privilege.

Privileged information may be withheld from production if it is protected by attorney-client privilege, work product, or another recognized protection.

Confidential business information may still be discoverable if it is relevant and proportional, but production may be limited by protective order, redaction, confidentiality designation, or access restrictions.

A company should separate:

• Privileged legal communications

• Attorney work product

• Confidential but discoverable business information

• Nonresponsive information

• Public information

• Personal identifying information

• Trade secret information

• Highly sensitive competitor information

That distinction should be made before production begins.

Start with relevance and proportionality

Before producing sensitive records, the company should ask whether the requesting party is entitled to the information at all.

Questions include:

• What claim or defense does the request relate to?

• Is the request proportional to the needs of the case?

• Is the request overbroad?

• Is the time period reasonable?

• Are the custodians reasonable?

• Are the requested categories specific?

• Is the information available from less sensitive sources?

• Can aggregated or redacted data answer the question?

• Can sampling work?

• Can the request be phased?

• Is expert-only access appropriate?

• Is the request designed to obtain competitive intelligence rather than evidence?

The best confidentiality protection begins with narrowing the production.

Do not produce before a protective order is entered

A company should usually avoid producing trade secrets or highly sensitive business records before a protective order is signed by the court or otherwise enforceable.

A protective order may address:

• What information may be designated confidential

• What information may be designated attorneys’ eyes only

• Who may access each category

• How documents and ESI are marked

• How deposition testimony is designated

• How experts receive access

• Whether in-house counsel may view material

• Whether business executives may view material

• Whether competitors may view material

• How information may be stored

• How documents may be used

• How filings under seal are handled

• How designation challenges work

• How inadvertent disclosure is handled

• How privileged material is clawed back

• How documents are returned or destroyed after litigation

• How violations are remedied

A handshake agreement may not be enough for trade secrets or competitor-sensitive information.

What is attorneys’ eyes only?

Attorneys’ eyes only, often called AEO, is a heightened confidentiality designation that restricts access to a smaller group, usually outside counsel, experts, litigation vendors, and sometimes limited in-house counsel.

AEO may be appropriate for:

• Source code

• Pricing strategy

• Customer lists

• Profit margins

• Product roadmaps

• Bid strategy

• Vendor pricing

• Technical designs

• Research and development

• Competitive strategy

• Highly sensitive financial data

• M&A materials

• Confidential algorithms

• Security architecture

AEO designations should not be overused. Courts may reject overbroad restrictions if they prevent the other side from litigating fairly. But in competitor litigation, AEO protection may be essential.

Should in-house counsel get access?

Sometimes yes, sometimes no.

The key issue is whether in-house counsel is involved in competitive decision-making or business operations that could misuse sensitive information, even unintentionally.

A protective order may distinguish between:

• Outside counsel

• In-house litigation counsel

• In-house business counsel

• Executives

• Business decision-makers

• Competitive decision-makers

• Experts

• Consultants

• Vendors

• Witnesses

• Court personnel

In competitor cases, the company should evaluate whether disclosure to opposing business personnel would cause competitive harm.

Experts and consultants require special controls

Experts may need access to sensitive information to analyze damages, causation, lost profits, accounting, source code, valuation, trade secret use, or industry practice.

Before producing sensitive materials to experts, consider:

• Expert acknowledgment forms

• Advance disclosure of expert identity

• Opportunity to object to expert access

• Limits on use in other matters

• Restrictions on copying or retaining materials

• Secure storage requirements

• Return or destruction obligations

• Source-code review procedures

• Limits on access by competitors or consultants with conflicts

• Restrictions on publication or reuse of data

Expert access can become one of the highest-risk parts of sensitive production.

Source code needs a special protocol

Source code is often among the most sensitive information a company can produce.

A source-code protocol may address:

• Secure review location

• Standalone review computer

• No internet access

• No external storage devices

• Printing restrictions

• Screenshot restrictions

• Copying restrictions

• Reviewer identification

• Expert access

• Logging of review sessions

• Limits on notes

• Treatment of excerpts in reports

• Deposition procedures

• Trial exhibit procedures

• Return or destruction after litigation

• Access for remote review, if allowed

• Code repository preservation

Do not treat source code like ordinary PDF production.

ESI and metadata can reveal more than the document text

Sensitive business production often includes electronically stored information.

ESI may reveal:

• Metadata

• authorship

• edit history

• comments

• hidden columns

• formulas

• tracked changes

• file paths

• access history

• system logs

• deleted content

• embedded data

• version history

• links to other systems

• confidential notes

• privileged comments

• security information

Before producing native files, spreadsheets, databases, or chat exports, the company should review what the production format reveals.

Redaction may be appropriate

Redaction can protect sensitive information that is not relevant to the dispute.

Possible redactions include:

• Personal identifying information

• bank account numbers

• tax identification numbers

• unrelated customer names

• irrelevant pricing data

• unrelated product information

• privileged content

• trade secret details not relevant to the dispute

• employee private information

• cybersecurity details

• unrelated business strategy

Redactions should be defensible and documented. Over-redaction can trigger motions to compel.

Sealing is different from a protective order

A protective order governs how parties handle information exchanged in discovery. It does not automatically seal documents filed with the court.

If sensitive information is attached to a motion, used at summary judgment, introduced at an injunction hearing, or offered at trial, the company may need a separate sealing or redaction motion.

Before filing sensitive materials, ask:

• Does the local rule require a motion to seal?

• Can the filing be redacted instead?

• Is the sensitive material truly necessary?

• Can the court review the material in camera?

• Is the request narrowly tailored?

• Does the public have a right of access?

• Can the confidential material be summarized without disclosure?

• Will the appellate record include sealed materials?

• What happens if the sealing motion is denied?

Companies should not assume that discovery confidentiality will protect public court filings.

Subpoenas create third-party risk

Sensitive company records may be sought through third-party subpoenas to vendors, customers, banks, accountants, consultants, cloud providers, payment processors, or former employees.

A company should monitor subpoena activity because a third party may produce sensitive information without understanding the company’s confidentiality concerns.

If a subpoena seeks sensitive records, possible responses include:

• Notice to the subpoenaed party

• Objections

• Motion to quash

• Motion to modify

• Motion for protective order

• Confidentiality agreement

• Narrowed production

• Redaction

• AEO designation

• Court order limiting use

• Clawback provisions

• In-camera review

A company should not wait until after the third party produces the records.

Producing trade secrets in injunction cases

Trade secret and confidential-information cases often involve emergency injunctions.

A company may need to show the court enough information to prove:

• The information qualifies as a trade secret

• It was subject to reasonable secrecy measures

• The defendant acquired, disclosed, or used it improperly

• Irreparable harm is likely

• The requested injunction is specific and enforceable

• A bond or security issue is addressed

But the company must avoid disclosing the trade secret publicly in the very filing meant to protect it. That may require redacted filings, sealed exhibits, in-camera review, declarations describing categories without revealing details, protective orders, and careful hearing procedures.

Producing sensitive records at depositions

Depositions can reveal confidential information through exhibits and testimony.

Before depositions involving sensitive records, consider:

• Whether the protective order covers testimony

• Whether the transcript is temporarily confidential

• How exhibits will be marked

• Who may attend the deposition

• Whether remote deposition procedures are secure

• Whether confidential exhibits can be displayed

• Whether trade secret testimony requires special handling

• Whether objections should preserve confidentiality

• Whether transcript designations must be made by a deadline

A company should prepare witnesses not to disclose protected business information unnecessarily.

Producing sensitive records at summary judgment

Summary judgment can increase public-exposure risk because parties often file key documents with the court.

Before summary judgment, evaluate:

• Which exhibits are necessary

• Whether confidential information can be redacted

• Whether sealing is justified

• Whether a public version and sealed version are needed

• Whether declarations can summarize sensitive details

• Whether opposing counsel may file sensitive records publicly

• Whether the protective order requires advance notice before filing

• Whether local rules impose specific sealing procedures

• Whether appellate review may later require sealed-record management

Summary judgment strategy should include confidentiality strategy.

Producing sensitive records at trial

Trial is the most difficult stage for confidentiality.

Information protected during discovery may become public if used at trial.

Possible protections may include:

• Motions in limine

• redacted trial exhibits

• sealed exhibits

• limited courtroom closure in rare circumstances

• confidentiality instructions

• witness limitations

• special handling of source code

• protective orders for demonstratives

• post-trial sealing procedures

• appellate record protection

The company should plan early for how trade secrets or sensitive records will be used if the case reaches trial.

Practical framework: what should a company do before producing sensitive records?

1. Identify the sensitive categories

List the records that could create competitive, financial, privacy, regulatory, or operational harm if disclosed.

2. Separate privilege from confidentiality

Privileged material may be withheld. Confidential nonprivileged material may need protected production.

3. Analyze relevance and proportionality

Determine what must be produced and what can be narrowed, phased, sampled, redacted, or withheld.

4. Negotiate a protective order

Do this before production. Include confidential, AEO, expert, deposition, ESI, filing, and return-or-destruction provisions.

5. Decide access levels

Determine who may see each type of material, including in-house counsel, executives, experts, consultants, vendors, and witnesses.

6. Review ESI carefully

Check metadata, formulas, comments, hidden data, version history, and native-file risks.

7. Redact where appropriate

Use targeted redactions for irrelevant sensitive information, personal identifiers, privileged content, and unrelated business information.

8. Plan for depositions and filings

Discovery production is only the first step. Decide how the information will be handled in testimony, motions, hearings, trial, and appeal.

9. Monitor third-party subpoenas

Watch for attempts to obtain the company’s sensitive information from others.

10. Document decisions

Keep a record of confidentiality review, production limits, designations, objections, and protective measures.

Deadlines matter

Companies should track deadlines for:

• Discovery responses

• Objections

• Protective order negotiation

• Motion for protective order

• Motion to quash or modify subpoena

• ESI protocol

• Confidentiality designations

• Deposition designations

• Expert disclosures

• Summary judgment filings

• Motions to seal

• Trial exhibit deadlines

• Pretrial disclosures

• Injunction hearings

• Appeal deadlines

• Mandate or remand deadlines

• Return or destruction after litigation

If a production deadline is near and no protective order is in place, the company may need agreement or court relief quickly.

Evidence considerations

Before producing sensitive business records, review:

• Contracts

• confidentiality agreements

• NDAs

• employee agreements

• vendor agreements

• customer contracts

• board materials

• financial records

• tax records

• pricing data

• source code

• technical files

• product designs

• customer lists

• CRM records

• Slack and Teams messages

• emails and attachments

• texts and mobile messages

• accounting exports

• access logs

• download logs

• security records

• audit logs

• metadata

• expert materials

• insurance communications

• litigation hold materials where relevant

Sensitive evidence should be reviewed for responsiveness, privilege, confidentiality, and production format.

Risks of producing without protections

Producing sensitive information without adequate protections can create risks such as:

• Competitor access to trade secrets

• loss of trade secret secrecy

• customer list exposure

• pricing harm

• source code exposure

• public filing of confidential records

• privacy violations

• contractual confidentiality breaches

• employee or customer data exposure

• regulatory issues

• loss of settlement leverage

• expert misuse

• broader discovery demands

• trial publicity

• appeal-record exposure

• injunction complications

Once information is disclosed, it may be hard to undo the damage.

Risks of over-designating everything confidential

Over-designation also creates risk.

A company may face:

• Motions challenging designations

• judicial skepticism

• sanctions or fee shifting

• delayed discovery

• credibility problems

• difficulty using evidence at hearings

• disputes over trial exhibits

• sealing problems

• unnecessary cost

• settlement friction

Use confidentiality designations seriously and consistently.

Risks of refusing to produce sensitive information

A company cannot simply refuse to produce relevant information because it is sensitive.

Refusal may lead to:

• Motions to compel

• fee awards

• discovery sanctions

• adverse rulings

• exclusion of defenses or evidence

• injunction problems

• summary judgment consequences

• trial sanctions

• credibility loss

The better approach is usually to narrow, protect, redact, phase, or condition production rather than refuse categorically.

Forum considerations

Federal court

Federal Rule of Civil Procedure 26(c) allows protective orders for good cause, including protection of trade secrets and other confidential research, development, or commercial information. Federal Rule of Civil Procedure 45 provides tools to protect subpoenaed persons and affected parties when subpoenas seek trade secrets or confidential commercial information. Federal Rule of Civil Procedure 5.2 governs privacy redactions in federal filings.

Florida state court

Florida companies should consider Florida’s trade secret statutes, protective-order practice, confidentiality under Florida court-record rules, and state procedural rules before producing trade secrets or sensitive business records. Florida law recognizes trade secret remedies and preservation of secrecy issues, but court filings and discovery still require careful handling.

North Carolina state court

North Carolina companies should consider the North Carolina Trade Secrets Protection Act, protective orders, Business Court procedures where applicable, sealing rules, and discovery obligations. Sensitive business records may need targeted production, redaction, confidentiality designations, or court protection.

Arbitration

Arbitration may provide more confidentiality than public court litigation, but that depends on the agreement, provider rules, protective orders, and award-confirmation proceedings. Sensitive records still need production controls.

Appeals

If sensitive materials become part of the trial-court record, the company may need to protect sealed or confidential materials on appeal. Appellate courts may apply their own rules for sealed filings, public access, appendix materials, and record excerpts.

Appeal consequences

Sensitive-record disputes can create appeal issues.

Appeal-sensitive questions may include:

• Whether the protective order was properly entered

• Whether the court abused discretion in ordering disclosure

• Whether trade secrets were adequately protected

• Whether AEO restrictions were justified

• Whether sealing was properly granted or denied

• Whether public access standards were applied correctly

• Whether disclosure caused irreparable harm

• Whether sanctions were imposed for refusal to produce

• Whether privilege was waived

• Whether the record preserved objections

• Whether an injunction was specific and supported

• Whether confidential materials were included in the appellate record

• Whether mandamus or interlocutory review may be available in rare circumstances

A company should build a clear record when objecting to production or seeking protection.

Common mistakes

Common mistakes include:

• Producing sensitive records before a protective order is entered

• Assuming “confidential” means privileged

• Marking everything confidential

• Failing to request AEO protection in competitor cases

• Producing native files without metadata review

• Producing source code without a source-code protocol

• Forgetting third-party subpoenas

• Failing to prepare witnesses for confidential deposition testimony

• Assuming discovery confidentiality automatically seals court filings

• Filing trade secrets publicly in injunction papers

• Failing to redact personal identifiers

• Sharing sensitive records with experts without access controls

• Waiting until summary judgment to think about sealing

• Failing to preserve objections for appeal

• Ignoring return or destruction obligations after litigation

Confidentiality protection must be built into the case plan.

Authority and legal framework

Federal Rule of Civil Procedure 26(c) authorizes protective orders for good cause to protect parties and persons from annoyance, embarrassment, oppression, or undue burden or expense. Rule 26(c)(1)(G) specifically allows courts to require that trade secrets or other confidential research, development, or commercial information not be revealed or be revealed only in a specified way.

Federal Rule of Civil Procedure 45 allows courts to quash, modify, or condition subpoenas that require disclosure of trade secrets or other confidential research, development, or commercial information.

Federal Rule of Civil Procedure 5.2 requires redaction of certain personal identifiers in federal court filings. That rule is separate from broader trade secret or commercial confidentiality protections.

The Florida Uniform Trade Secrets Act defines trade secret concepts, provides remedies for misappropriation, authorizes injunctive relief, damages, attorney’s fees in specified circumstances, and addresses preservation of secrecy.

The North Carolina Trade Secrets Protection Act defines trade secret and misappropriation concepts and provides statutory protection for trade secrets under North Carolina law.

The U.S. Supreme Court has recognized a common-law right of access to judicial records, while also recognizing that access is not absolute. That is why companies must distinguish between confidential discovery production and public court filings.

These authorities show why producing sensitive business records requires more than ordinary document production. Companies should address discoverability, confidentiality, privilege, protective orders, sealing, ESI, subpoenas, trial use, and appeal consequences before disclosure occurs.

How Biazzo Law approaches sensitive business-record production

Biazzo Law approaches production of trade secrets and sensitive business records as a litigation, business, injunction, and appellate issue.

That may include:

• Reviewing discovery requests for relevance, proportionality, privilege, and confidentiality

• Negotiating protective orders and attorneys’ eyes only provisions

• Preparing motions for protective order, motions to quash, or motions to modify subpoenas

• Structuring source-code, ESI, expert-access, and deposition confidentiality protocols

• Protecting customer lists, pricing, financial records, trade secrets, source code, board materials, and proprietary data

• Coordinating sealing, redaction, and in-camera review strategies

• Preserving confidential information for injunction hearings, summary judgment, trial, and appeal

• Advising general counsel, executives, trial counsel, and referring counsel on confidentiality risk and appellate preservation

Biazzo Law represents businesses, organizations, executives, professionals, individuals, general counsel, trial counsel, and referring counsel in Florida, North Carolina, and federal litigation involving business disputes, trade secrets, confidential-information disputes, emergency injunctions, federal discovery, protective orders, summary judgment, appeals, U.S. Supreme Court strategy, and amicus curiae briefs.

This appellate-aware approach matters because sensitive-information disputes do not end at production. They can affect injunctions, sanctions, summary judgment, settlement leverage, trial exhibits, sealed filings, appellate records, and broader legal strategy.

Related Biazzo Law resources

For more information, review these related Biazzo Law resources:

• Business Litigation — parent page for business disputes involving breach of contract claims, fraud and misrepresentation, fiduciary duty claims, unfair competition, trade secret issues, emergency injunctions, federal business litigation, complex motions, trial support, and appellate preservation.

• How Do Federal Protective Orders Help Companies Protect Confidential Information? — related post addressing Rule 26(c), protective orders, AEO designations, ESI, subpoenas, sealing, and confidentiality in federal litigation.

• Can We Keep Trade Secrets and Customer Lists Confidential in Litigation? — related post addressing protective orders, sealing, redactions, injunctions, and confidentiality strategy for trade secrets and customer information.

• Contact Biazzo Law — use the contact page to schedule a litigation strategy review for trade secret protection, sensitive business-record production, protective orders, subpoenas, sealing, ESI, injunctions, or appellate-sensitive litigation.

Frequently Asked Questions

What should companies do before producing trade secrets in litigation?

Companies should evaluate relevance, privilege, confidentiality, proportionality, protective orders, AEO restrictions, redactions, ESI format, sealing strategy, and who will have access before producing trade secrets.

Are trade secrets immune from discovery?

No. Trade secrets are not automatically immune from discovery. But courts may require special protections, such as protective orders, AEO designations, limited access, redactions, in-camera review, or controlled production.

What is the difference between confidential and attorneys’ eyes only?

Confidential information may be shared with a broader group under a protective order. Attorneys’ eyes only information is usually limited to outside counsel, experts, and litigation vendors, with tighter restrictions to prevent competitive harm.

Should companies produce sensitive records before a protective order is entered?

Usually no. If the records include trade secrets, customer lists, pricing, source code, financial records, or proprietary data, the company should usually seek a protective order or confidentiality agreement before production.

Can sensitive documents be filed under seal automatically?

No. A protective order does not automatically seal court filings. A party may need a separate sealing motion, redacted filing, or court permission depending on the forum and local rules.

How should companies handle source code in litigation?

Source code should usually be governed by a specific source-code protocol addressing secure review, access, printing, copying, screenshots, expert review, storage, deposition use, and return or destruction.

What if a subpoena seeks my company’s confidential records from a third party?

The company may need to object, seek a protective order, move to quash or modify the subpoena, request confidentiality designations, negotiate narrowing, or ask the court to condition production.

Does Biazzo Law help protect trade secrets and sensitive records in litigation?

Yes. Biazzo Law helps businesses, organizations, general counsel, trial counsel, and referring counsel with protective orders, AEO designations, subpoena objections, trade secret confidentiality, ESI protocols, source-code protection, sealing strategy, injunctions, and appellate preservation in Florida, North Carolina, and federal litigation.

Schedule a litigation strategy review

If your company is being asked to produce trade secrets, customer lists, pricing, source code, financial records, board materials, or other sensitive business information, the production strategy should be evaluated before disclosure.

Schedule a litigation strategy review with Biazzo Law to evaluate trade secret protection, sensitive-record production, protective orders, AEO designations, ESI risks, subpoenas, sealing, injunction readiness, and appeal consequences.