Question 1

Can we get employees' Slack DMs, or are they private?

Accepted Answer

On eligible plans, workspace owners can law full y reach DMs via corporate export or discovery APIs: subject to the platform's eligibility process and, critically, UK employment and data protection law: necessity, proportionality, transparency obligations and any workspace privacy commitments weighed before the switch is thrown (the guide 51 balance, Slack edition). "Private" in the interface means private from colleagues, not from properly governed disclosure: but the governance is the point, and it is documented before, not after.

Question 2

Our client's Slack only goes back 90 days. Is the case dead?

Accepted Answer

Not before three questions: when was that retention set (a rule predating the dispute is misfortune; Example 1's timing is conduct); what does the periphery hold (end point caches, integration mirrors, email forwards, Connect counterparts: §8's map); and what does the roll-off's shape support by inference? Cases survive roll-offs regularly: on the periphery's fragments and the destruction's own story: what dies is the assumption that the workspace was the only copy.

Question 3

Are Slack messages disclosable documents like email?

Accepted Answer

Entirely: they are documents under CPR 31 and PD 57AD, within the duty to preserve from the moment litigation is contemplated, and within adverse-document obligations however in form a l the tone. The practical differences are logistical: the lattice, the routes, the processing: not jurisprudential. Parties who treated channels as off-the- record have learned otherwise at cost: the candour that makes Slack valuable evidence was typed by people making that exact assumption.

Question 4

The key message says "(edited)". What can we find out?

Accepted Answer

Route-dependent, per §5: compliance-grade collections capture original versions with edit timestamps; ordinary exports show final text and flag only. If the collection has not happened, the fidelity choice is live: make it (Example 3's lesson); if it has, interrogate what the route captured; and either way the edit's timing: recovered from history or bracketed by caches and mirrors: joins the chronology. An edit contemporaneous with the dispute's crystallisation is a fact worth having what ever the original said.

Question 5

How should Slack evidence be presented to a tribunal?

Accepted Answer

As conversations, not exhibits-by-message: threads rendered in order with identities resolved, dates and times explicit, edits and deletions annotated, reactions preserved where they carry meaning, and enough surrounding traffic that context survives challenge: with the collection route and its fidelity stated in the evidence's pedigree. The completeness attack on selective chat quotation is now routine; the answer is built at processing, per §7, not improvised at trial.

Question 6

What about Teams, Discord, and the other chat platforms?

Accepted Answer

The method transfers; the lattices differ. Teams is guide 56's territory (Purview-governed, Exchange-linked storage); consumer platforms (Discord, Telegram groups) sit closer to guides 63-64's device-and-counterpart world; and each enterprise tool has its own tier-and-retention lattice to audit first. The transferable discipline is exactly this guide's: audit what can exist, freeze what does, choose the route by fidelity, and interrogate productions against capability: the platform names change; the questions do not. cflab. u k · e-disc ove r y. u k ©2026 Computer Forensics Lab Ltd ·cflab.uk ·e-discovery.uk ·info@cflab.uk ·+44 (0)20 7164 6915 Page 15 of 17

Slack EDiscovery