Confidentiality Agreement for Selling a Business: Customer Data

What customer information should you share after a business sale NDA?

Suppose the buyer requests your customer file to measure concentration risk. One file may identify customers, while other schedules add revenue, pricing, volume, discounts, margins, costs, prospects, or sales opportunities. The buyer doesn’t need every field to measure concentration.

Start with revenue by customer code or remove names from a top-customer list. The buyer can test the exposure without immediately learning the identities. If it later needs names or contract details, you can release them more carefully at a meaningful transaction milestone. An American Bar Association practitioner article calls this “progressive incremental disclosure,” while Morgan & Westfield describes a similar progression through aggregation, redaction, and wider disclosure. The right timing depends on the transaction.

Before relying on masking, consider whether the buyer can combine the schedule with the rest of the diligence file and identify the customer anyway. FTC staff guidance for competitor diligence identifies aggregation, redaction, masking, screened recipients, and staged disclosure as possible controls. It also tells parties to check whether separate documents can be pieced together. The guidance is fact-dependent and provides no safe harbor.

Customer contracts raise a different question. If the buyer needs to verify one provision, preserve it and redact only details the buyer doesn’t need. Goodwin’s pre-closing guidance discusses redacting customer names, specific pricing, and material nonstandard terms, particularly when competition concerns exist.

The remaining contract must still answer the buyer’s question. Hiding the relevant provision makes the document useless, while removing a name may accomplish little if other details identify the customer.

This decision belongs in your broader seller due diligence file. Treating customer data separately keeps a general diligence request from becoming an indiscriminate release of customer records.

When should you disclose customer names to a buyer?

Start with aggregated, coded, or redacted evidence. Hold customer names until the buyer explains why it needs them; no milestone automatically unlocks those identities.

Use transaction milestones to reconsider access rather than grant it automatically. In Morgan & Westfield’s buyer-screening process, an NDA and information memorandum come first, more financial information may follow, and fuller diligence comes after an LOI. Its confidentiality guidance says a seller may hold customer or employee names until late in diligence or, in some deals, until after a definitive agreement. That sequence can help you stage the decision, but it doesn’t set the timing for your sale.

A name connects otherwise limited figures to a live commercial relationship. A coded schedule may show that your largest customer represents a material share of revenue. Add the name, pricing, discounts, contract terms, sales opportunities, or projections, and the buyer has customer-specific intelligence instead of an anonymous concentration figure. That matters most when the buyer competes with your company.

Ask which diligence issue the identities will resolve and why coded or redacted information falls short. The answer separates necessary verification from convenience and helps limit the detail traveling with the name. The buyer may need the identity without also receiving account-level pricing, projections, or opportunity data.

Test masking across the whole diligence file. The Tower International clean-team agreement, for example, barred reports from including details that would let people outside the clean team work backward to customer-specific information. Several limited records may reveal an account together even when none names it alone.

Once the buyer has justified access to customer identities, decide who actually needs to see them.

Who inside the buyer’s organization should see customer data?

Don’t open the file to the buyer’s entire organization. Let a limited group inspect the underlying customer data and give the wider deal team only a cleaned report or approved summary. Set those roles before uploading the detail; a later restriction can’t undo access already given.

The Calpine and LS Power agreement allowed representatives to receive information if they participated directly in the evaluation or needed it for that purpose. Other transactions created a clean team: a screened group allowed to inspect sensitive detail while other buyer personnel received approved summaries or redacted conclusions.

Under the Tower International agreement, the wider team could receive reports after the clean team summarized, aggregated, redacted, or otherwise cleaned customer information and outside antitrust counsel reviewed the result. A Skullcandy and Incipio agreement separated detailed pricing, volume, discounts, rebates, margins, costs, and opportunities from counsel-approved summary or aggregate information.

The Sharps clean-team agreement excluded people in specified day-to-day competitive roles while they had access to clean-team information. Other buyer personnel could receive reports only after aggregation or redaction and outside antitrust-counsel approval. These filed agreements governed their own transactions; they don’t prescribe the structure for another sale.

We would settle four questions before detailed customer information moves: Who needs the raw detail? What decision will that person make? What output can the wider buyer team receive? Who checks it before it leaves the controlled group?

A clean team is one possible control, not an automatic requirement or guarantee. If the buyer competes with your company, ask qualified advisers to assess the material and intended viewers as part of your broader plan for selling a business to a competitor.

Control downloads as well as viewers. FTC staff identifies download limits as one possible safeguard in competitor diligence, but a restriction can’t retrieve earlier downloads, working copies, email attachments, or reports made from the data. Each new recipient or copy gives you more to find and control if the deal ends.

What happens to customer data if the sale does not proceed?

Closing the data room ends one route to the information. It doesn’t retrieve downloaded files, remove attachments from inboxes, or locate reports and working copies built from customer data.

Plan the closeout before releasing the information. Read the agreement’s return, destruction, and retention provisions for the trigger, timing, and copies covered. The Calpine agreement used a 30-day return-or-destroy process after a written request. The Sharps agreement required return or destruction where technically and reasonably possible, with exceptions for certain archives. The Tower agreement addressed documents, reports, and backup material separately. Your agreement may treat working copies and archives differently.

If the deal fails, follow the information wherever it went. Cooley’s guidance on failed M&A diligence explains that a recipient may need to separate confidential files and emails from ordinary internal material, then collect, sequester, return, or destroy them under the governing obligations.

1. End active access to the data room and shared systems.
2. Identify downloads, email attachments, reports, and working copies containing customer information.
3. Apply the agreement’s return, destruction, sequestration, or retention terms.
4. Treat backup or archival material separately from ordinary working copies when the agreement does.

We would start by finding every copy that left the data room, then follow the agreement’s terms for each one.