Can a closed startup sell its Slack messages and emails?

The yes-if rule for Slack and email archives#

The yes-if rule says a closed startup can license a Slack channel or a mailbox only if it passes all four conditions in the table. Apply the rule channel by channel and inbox by inbox, because an archive is almost never all in or all out.

The rule is a screen, not a legal conclusion. Laws that may apply, such as state privacy laws and, for staff abroad, GDPR, are assessed deal by deal with counsel.

Which documents settle each condition?#

The documents that settle each condition are usually scattered across the founder's drive, the HR system and the contract folder, so gather them before anyone debates whether a channel qualifies. A closed company that cannot find a document should treat the related condition as unresolved, not as passed.

Authority is the condition founders tend to assume away. Once a company stops operating, the person who used to run it may no longer be the right signer, especially after an assignment for the benefit of creditors or a bankruptcy filing. Confirm who can approve before scoping work begins.

Why Slack and email usually get different answers#

Slack and email usually get different answers under the yes-if rule because Slack conversations are mostly internal and organized by channel, while email crosses company boundaries in most threads and is organized by person. The four conditions are the same, but they fail in different places.

In Slack, the confidentiality condition tends to fail in specific, findable places: Slack Connect channels, customer escalation channels and threads where someone pasted a customer export. Those can be excluded channel by channel. The personal-details condition is harder, because chat is informal and people mention health, family and colleagues in passing.

In email, the confidentiality condition fails far more often, because customers, investors, vendors and lawyers are copied on most threads, and it fails inside individual messages rather than whole folders. Email is also stored by mailbox, so scoping means choosing people rather than topics, which pulls each person's private correspondence into the review. For many closed startups, a set of internal Slack channels is the workable part and external email is left out.

Which channels and mailboxes usually stay out#

The channels and mailboxes that usually stay out are those centered on individuals, legal advice or other companies' confidential material. Mark them as excluded during the inventory, before anyone starts preparing data.

What remains is often a smaller but cleaner set: public engineering, product, support and incident channels, plus shared internal inboxes where customer content can be removed.

• 1Direct messages and small private group messages.
• 2People, HR, recruiting and compensation channels.
• 3Threads with outside counsel or in-house legal, which may be privileged.
• 4Board, investor and fundraising communications.
• 5Slack Connect channels shared with customers, partners or vendors.
• 6Individual mailboxes with personal correspondence, health or family matters.
• 7Channels used to pass around customer exports, credentials or production data.

How personal details are removed from chat and email#

Removing personal details from chat and email means replacing names, handles, email addresses, phone numbers and signatures with consistent placeholders, and redacting personal disclosures inside the text. Consistency matters: giving each person the same role token across every thread keeps conversations readable.

Automated tools help with volume but are not enough on their own. Presidio, an open-source toolkit for finding and anonymizing personal information that began at Microsoft and is now community-governed, states in its own documentation that it cannot guarantee it will find all sensitive information and that additional protections should be used. Plan for sampled human review of each channel after the automated passes.

Attachments and images need their own handling. Screenshots, pasted logs and shared files often contain customer names or credentials that text redaction never touches, so the safer default is to exclude attachments unless each one is reviewed.

Illustrative: a closed procurement software startup scopes its archive#

Illustrative: a fictional procurement software startup that had more than fifty employees at its peak closes after a down round falls through. Its Slack workspace holds public engineering, support and incident channels, many private channels, and Slack Connect channels with its largest customers. Email runs on Google Workspace, with a shared support inbox and individual mailboxes.

The founder, acting as wind-down officer, applies the yes-if rule. Public engineering and incident channels pass once names are replaced and pasted customer data is redacted. The support inbox fails the confidentiality condition, because the customer agreements treat support content as confidential. Direct messages, the people channel, legal threads and every Slack Connect channel are excluded, and individual mailboxes are left out entirely.

The board approves a non-exclusive license covering the passing channels, linked to the Jira issues they reference. The company keeps ownership, and the rest of the archive is retained or deleted under its shutdown retention plan.

How SourceX handles workplace communications#

SourceX handles workplace communications as a separate record family inside the SourceX five-step transaction, with its own rights and privacy review. The fit check uses channel names, date ranges and system descriptions only, and no messages are shared during the initial assessment.

Each approved channel set is documented in a SourceX Evidence Packet, including the privacy record of what was removed and the release authorization showing who approved it. The supplier approves the scope at every step and can exclude any channel.