Your Slack DMs aren't private. Your boss can read every one of them.
You type something snarky about a meeting in a Slack DM. You vent about your manager. You share a salary number with a trusted colleague. You assume it's private — two people, a locked channel. It isn't. Not even close.
Most people treat Slack like texting. It feels casual, fleeting, even intimate in DMs. But Slack isn't a messaging app between friends. It's an enterprise surveillance platform that your company pays for and controls. Every word you type belongs to them — legally, technically, and permanently.
Here's what actually happens to your messages, and why it should change how you think about workplace chat forever.
Everything is retained. Everything.
On Slack's paid plans — which virtually every workplace uses — all messages are retained indefinitely by default. Not just channel messages. DMs. Group DMs. Threads. Edited messages (including the original, pre-edit version). Deleted messages. Files. Reactions. Everything.
On Slack's Business+ and Enterprise Grid plans, workspace owners can export this data at will — including private channels and DMs — using a self-serve tool. No IT ticket. No notification to you. No consent required.
Think deleting a message protects you? Slack's compliance exports include deleted messages. The "delete" button is cosmetic — it hides the message from the interface but keeps it in the data layer, available to admins and compliance teams.
And it's not just Slack. Microsoft Teams stores compliance copies of every message — including deleted and edited versions — in Exchange Online mailboxes. Administrators can search through everything using Microsoft Purview eDiscovery. The "deleted" message you thought was gone? Teams keeps a copy in a hidden folder called SubstrateHolds, invisible to you but fully accessible to compliance.
Your DMs are discoverable in court
Workplace chat messages are considered business records. In litigation, they're subject to the same discovery obligations as emails, contracts, and financial records. Lawyers can — and regularly do — subpoena entire Slack workspaces.
This isn't hypothetical. In the Epic v. Google antitrust case, a federal judge sanctioned Google after discovering that employees had been using Google Chat's "history off" feature to avoid creating discoverable records. The court found this constituted deliberate spoliation of evidence. The jury — perhaps influenced by the implication that Google was hiding something — returned a verdict in under four hours.
The lesson isn't that Google used ephemeral messaging. It's that they used a tool that pretended to be ephemeral while actually operating within a system designed to retain everything. Half-measures are worse than no measures at all.
Discord is even worse than you think
If your team uses Discord for casual communication, the privacy situation is grimmer still. Discord routes user interactions through tracking endpoints regardless of any privacy settings you configure. Files uploaded to Discord persist on its CDN servers even after you delete your account. And Discord's privacy policy explicitly allows data retention for legal compliance, safety, and "other legitimate business purposes" — a category so broad it covers essentially everything.
Unlike Slack, Discord wasn't built for enterprise use. It was built for gaming communities and retrofitted for broader communication. Its data architecture reflects that origin: minimal user control, maximal platform access.
WhatsApp: encrypted but not private
Some teams migrate sensitive conversations to WhatsApp, believing end-to-end encryption provides protection. It provides some protection — against eavesdropping in transit. But WhatsApp collects extensive metadata: your contacts, message frequency and timing, device information, IP addresses, and more. This metadata is shared with Meta and used for advertising purposes.
More concerning: WhatsApp can activate enhanced metadata tracking for specific users, including a feature known as "prospective message pairs" that logs who you communicate with, when, and how often. The content of your messages may be encrypted, but the pattern of your communications — which in many contexts reveals more than content — is not.
The real problem: data that exists can be breached
Every message stored is a message that can be leaked, breached, subpoenaed, or weaponized. This isn't theoretical risk — it's documented reality:
- Disney (July 2024): Hacktivists exfiltrated 1.1 terabytes from internal Slack channels — 44 million messages, unreleased project details, credentials, and employee passport numbers. Disney subsequently announced it would stop using Slack entirely.
- Nikkei (September 2025): A single stolen employee credential exposed the chat histories of 17,368 users.
- Twitter v. Musk (2022): Hundreds of private text messages between billionaires — including a $1 billion investment commitment — were unsealed as public court exhibits.
The average cost of a data breach reached $4.88 million globally in 2024. In the United States, that number was $10.22 million. And the reputational damage — the thing that actually keeps executives up at night — is unquantifiable.
What ephemeral actually means
"Ephemeral messaging" has become a buzzword diluted to meaninglessness. Slack's message deletion isn't ephemeral — it's cosmetic. WhatsApp's disappearing messages aren't ephemeral — they can be screenshotted, backed up to cloud, or captured by MDM software. Even Signal's disappearing messages aren't truly ephemeral — they live on the device until the timer expires, and any participant can screenshot them.
True ephemeral communication means messages exist only in volatile memory (RAM), are never written to disk, and can be destroyed instantly and irrecoverably by any participant. When the room closes, the JavaScript garbage collector reclaims the memory. There's nothing to subpoena, nothing to breach, nothing to recover.
That's not a feature. That's an architecture.
Try a conversation that actually disappears
No accounts. No logs. No traces. Messages exist only in memory.
Hit burn and everything is destroyed forever.
What should you actually do?
This isn't about paranoia. It's about appropriate caution with a technology that most people fundamentally misunderstand. Here's the framework:
Use Slack for what it's designed for — project coordination, team announcements, non-sensitive collaboration. Treat every Slack message as a potential exhibit in a lawsuit, because legally, that's exactly what it is.
Move sensitive conversations off retained platforms entirely. Salary discussions, HR concerns, strategy debates, candid feedback — none of this belongs in a system that retains everything indefinitely and grants your employer full access.
Understand that "deleting" isn't deleting. On Slack, Teams, Discord, and most enterprise chat platforms, the delete button is a UI feature, not a data operation. The message is hidden from your view but preserved in the backend.
The safest message isn't an encrypted message, a deleted message, or a disappearing message. It's a message that was never stored in the first place.