Is it ethical to license a dead company's Slack archive?

Why Slack is harder than tickets or invoices#

Slack is harder to license ethically than tickets or invoices because people wrote it as conversation, not as a record. Engineers debated designs in public channels, but the same workspace holds jokes, complaints about managers, health updates, family news and private disagreements that nobody expected an outsider to read.

Critics of selling startup chat logs to AI developers make a fair point: the people in the archive did not negotiate the deal and will not see the proceeds. A founder who takes that criticism seriously ends up with a narrower, better-prepared license, or decides not to license at all.

There is also a reason the question keeps coming up. Threads where a team diagnosed an outage, scoped a feature or handled a customer escalation show how real work gets done, which is what developers of AI agents want to learn from. The ethical task is to separate that work record from the personal lives around it.

Five principles for an ethical Slack license#

The five principles below work as a practical test for an ethical Slack license. If any one fails, the license should be narrowed or dropped.

• 1Notice and consent: former employees learn what is proposed before records leave the company, and requests to exclude their messages are honored where practical.
• 2Removal: names, contact details, personal stories, health, family and HR matters are removed, and a person reviews what automated tools miss.
• 3Scope: only channels with work content are included; direct messages, private channels and social channels stay out by default.
• 4Purpose limits: the license restricts use to model development and evaluation, bans re-identification and resale, and requires deletion or return at the end.
• 5Accountable approval: a named person, usually the founder or wind-down officer with board sign-off, approves the final scope after reviewing a prepared sample.

What to include and what to leave out#

The content worth including in a Slack license is work discussion that shows a problem, the reasoning and the outcome; everything else starts excluded. The table gives a default position for each part of a typical workspace.

Defaults can move in either direction after review. A private channel used only for release coordination may be fine to include, while a public engineering channel that drifted into personal conversation may need heavy trimming.

What former employees deserve to hear#

Former employees deserve a plain notice that says which records are being considered, what will be removed, who will use them and for what, and how to ask questions or request exclusion. A notice sent before the license is signed is far more credible than an explanation afterward.

Whether consent is legally required depends on the company's policies, employment agreements, the states and countries where people worked, and how the messages will be used. Counsel assesses that deal by deal. Ethically, a notice with a real contact point is the minimum, even where the law may not demand one.

Keep the tone factual. People react badly to vague language and to surprises, and better to specifics such as a statement that direct messages are excluded and names are removed before anything leaves the company.

• 1Which workspace and channels are being considered, and which are excluded outright.
• 2What will be removed before anything leaves the company, such as names, contact details and personal content.
• 3The kind of licensee and the permitted use, without overstating what is known.
• 4How long the licensee may keep the records and what happens at the end of the term.
• 5A named contact and a date by which to ask questions or request exclusion.

Can redaction make chat safe enough?#

Redaction makes chat safer but never perfectly safe, which is why removal is paired with exclusion and contract limits. Presidio, an open-source toolkit for detecting and anonymizing personal information that is now governed by the community Data Privacy Stack organization, warns in its own documentation that automated detection cannot guarantee it will find all sensitive information and that additional protections should be used.

Small teams add a further risk: writing style, in-jokes and context can reveal who wrote a message even after names are gone. The answer is layers, where each covers the gaps in the others.

• 1Exclude the riskiest channels entirely rather than trying to clean them.
• 2Run automated detection for names, contact details and secrets on what remains.
• 3Have people review samples from every included channel and fix what the tools missed.
• 4Bind the licensee not to attempt re-identification, resale or use beyond the stated purpose.

Questions a founder can ask before saying yes#

A founder can test the decision with a few direct questions, and honest answers often narrow the scope more than any policy would. If an answer is uncomfortable, that part of the archive should probably stay out.

• 1Would I be comfortable if a former employee read the full license and the notice?
• 2Can I explain why each included channel is useful and why each excluded one is out?
• 3Have I seen a prepared sample, not just a description of the process?
• 4Does the contract ban re-identification, resale and use beyond the stated purpose?
• 5Where do the proceeds go: creditors, unpaid staff, investors or the wind-down budget?
• 6Would I make the same decision if the company were still operating?

Illustrative: a founder narrows the archive#

Illustrative: a fictional design collaboration startup shuts down after its last funding round falls through. Its Slack workspace holds years of engineering, support and product channels, plus social channels and direct messages. Engineering work is tracked in Linear and GitHub, and support runs through Zendesk.

The founder considers only the incident, engineering and support escalation channels whose threads link to Linear issues or Zendesk tickets. Direct messages, private channels, the leadership channel and the social channels are excluded. A notice goes to former employees at their last known personal email, with a contact for questions, and the few who ask for their messages to be removed are taken out.

The board reviews a prepared sample before approving. The final license covers a narrower set than first imagined, and the founder can describe every part of it to the people whose work it records.

How SourceX approaches workplace chat#

SourceX treats workplace chat as a high-care record family. In the SourceX five-step transaction, the Preparation step removes personal and confidential details, and the Approval step lets the supplier review prepared records before anything is delivered.

The SourceX Evidence Packet records the privacy record, permitted use and release authorization for each package, so the choices behind a license, including what was excluded and why, are written down rather than assumed.