How to respond when a former employee objects to a company data license

How should a company respond when a former employee objects?

Listen first, confirm what is actually in scope, offer exclusion where it is feasible before delivery, write down what was said and done, and send any legal question to counsel. Many complaints begin as a request for information, and a prompt, plain answer can settle some of them.

This guide is for owners, CEOs and HR leads at a company that is exploring or has agreed a data license. It is general information, not legal, tax or financial advice. Employee privacy rights vary by state and by what was disclosed to staff, so confirm with your own counsel before acting.

What you need in place before a complaint arrives

Preparation makes the first reply easier.

• A named person who owns employee questions about the license, usually the HR lead or general counsel.
• A one-page description of what is in scope and out of scope, written in plain language.
• The internal announcement, if one was sent. The employee announcement template gives a starting point.
• A list of the systems involved and the date ranges covered, so you can answer "were my emails included?" accurately.
• A way to record each complaint and each reply.

Sponsors who hold portfolio companies should also read portfolio data licensing and reputational risk, because a complaint at one company can become a story about the whole portfolio.

The six steps

1. Acknowledge within a business day or two. A short note saying you received the message, who is looking into it and when they will reply is enough. Silence is what escalates a complaint.
2. Ask what they want. Some people want information, some want their content excluded, some are angry about how they heard. Ask one open question and note the answer in their own words.
3. Check scope. Find out whether their content is in the systems and date ranges under discussion. A former employee who left before the earliest records in scope may not be affected at all.
4. Decide what can be excluded. If the license has not yet been delivered, ask whether their mailbox, channels or documents can be left out. Exclusion is far easier before delivery than after, and some content cannot be separated from group threads.
5. Reply in writing. State what is in scope, what protections apply, whether exclusion is possible and who to contact. Do not argue, do not speculate about legal rights and do not promise outcomes you cannot control.
6. Document and close the loop. Save the complaint, the reply and any exclusion decision. Tell the person when the action is complete.

What to say

A short reply tends to work better than a long defense.

Adapt the dates and names. Never include a promise that cannot be kept, such as "your messages will never be seen by anyone".

Which questions belong with counsel?

Handle the practical steps yourself and route the legal ones.

Common mistakes

When the complaint exposes a real problem

Sometimes the person is right. The announcement went out late, a system with personal notes was left in scope, or a notice was missing. Fix the issue, say so plainly, and tell them what changed. If the problem is serious, pause the deal until counsel has reviewed it. Our guide to common concerns about licensing company data and the page on what employees think when a company licenses records show how to anticipate the same issues in advance. If layoffs are in the picture, read whether licensing during layoffs is insensitive first.

Example (Illustrative)

A fictional logistics firm with 180 staff is considering a license of five years of dispatch tickets and internal chat. A former dispatcher writes: "I saw a headline saying my old employer sells Slack messages. Is mine in there?" The HR lead replies within a day, checks that the dispatcher's channels fall inside the date range, confirms that names are removed under company-approved rules, and offers to leave the dispatcher's direct messages out before delivery. The reply is logged, and the dispatcher is told when the exclusion is done. No dollar figures or buyer names enter the exchange.

What this means for referral partners

Partners never touch records, so you do not respond to complaints yourself. You can help by telling the owner early that a response process exists. Partners earn a share of fees only after a deal closes and payment is received, so a clean process protects everyone. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The referral earnings calculator explains the formula, and the FAQ covers program basics. For sizing a dataset before any announcement, see how big a dataset should be.

Next step

If you advise a US company with 50+ full-time employees at peak (contractors excluded) and want to introduce it, register as a partner. Owners can also apply at sourcex.si/apply.