TL;DR: Three popular work platforms, three different answers. Slack says "A Customer owns and controls all content submitted to their workspace. Slack processes customer data on behalf of the Customer" [3], and on Free and Pro plans the export table lists private channels and DMs as unavailable [1]. On Business+ and Enterprise that changes: Slack lists "Export messages and file links from public channels, private channels, and direct messages (including Slackbot conversations)" as available, with the footnote "Workspace Owners and Org Owners must apply to use these export types" [1]. Microsoft journals everything: "All Microsoft Teams 1:1 or group chats are journaled through to the respective users' mailboxes" [5], and the licence wall is "Both admins and users working with eDiscovery cases require a Microsoft 365 Enterprise E3 or E5 license" [4]. Google shows activity by default, since "As an administrator, you can view reports and log events in the Google Admin console to review activity in your organization" [7], and Google Vault opens the content layer: "With Vault, authorized users can search for data, put data on hold, and export data for further analysis" across Gmail, Drive, Chat and Groups [9].

Three Tiers of Visibility, Not One

The question of whether your boss can read your messages flattens three very different powers into one. Sorting them out is the whole trick, because the answer is usually neither as grim as you fear nor as reassuring as you hope.

Tier one is activity. Who signed in and when [7]. Device names and URLs from a managed browser [8]. Which docs were created and shared [7]. Who joined which meeting [5]. Nobody needs a licence or a court order for any of that, and no vendor has to read a single message to produce it. Google builds a whole admin surface around it: admins can "view reports and log events in the Google Admin console to review activity in your organization" [7], and the reports cover "your organization's Gmail and Drive usage, like types of email activity, the number of docs created and shared" [7], sign-ins, "administrator activity", and "important events such as suspicious login attempts or service setting changes made by other administrators" [7].

Tier two is content search through compliance tooling. This is where a full export of your private messages can be produced. It is not a casual feature. It needs a plan tier, a licence, a role, an application, or a case file. That friction is the entire point, and it is also why the tooling gets enabled without anyone announcing it to staff.

Tier three is the legal and government layer. Legal holds, discovery exports, and subpoenas. This is where messages stop being reversible and start being evidence.

Here is the honest summary of the three platforms, in one line each: Slack gates bulk message export behind plan tier and an approval step, Microsoft gates it behind a Microsoft 365 licence and an eDiscovery case, and Google splits the difference with always-on activity reporting and a separate Vault product for content.

Slack: Public Channels Are the Default, Private Ones Are a Plan Upgrade

Slack's own export documentation is unusually specific, and the specificity is the story. The help article "Export your workspace data" breaks the available exports down by plan, and for Free and Pro workspaces the only message export on offer is this: "Workspace Owners and Admins can export message and file links from public channels in JSON format." [1]

Business+ gets more. The same page describes a self-service tool where, "For legal and regulatory compliance, Workspace Owners can apply to access a self-serve data export tool for messages and file links from public channels, private channels, and DMs in JSON format." [1] Approved workspaces get one more lever: "Workspace Owners can also schedule recurring data exports" [1]. The plan table marks that export row "Not available" for Free and Pro and available for Business+ and Enterprise, and the footnote on the table reads "Workspace Owners and Org Owners must apply to use these export types" [1].

Two Enterprise-only rows are worth knowing about. One is "Export data from all conversations for a single user", listed as unavailable on Free, Pro and Business+ [1], and another is "Export messages and file links by conversation type, member, or for a specific workspace" [1]. Recurring exports also sit in the Enterprise column, with the schedule set to "weekly or monthly" [1].

Then there are legal holds, which are a different mechanism entirely. Slack's help article "Create and manage legal holds" states that "In an Enterprise organization, anyone with the Legal Holds Admin system role can place a legal hold on specific members to preserve their messages and files in Slack." [2] The scope is wide: "When you create a legal hold, you can include message and file data from all conversations or just the direct messages a member is a part of." [2] And it is final: "With a hold in place, messages and files sent by all members in a conversation will be saved regardless of retention settings or if members edit or delete any content." [2] Held data is then reachable "from a JSON export or using the Discovery API" [2]. One limit is documented: Slack Connect conversations, Slack Sales Home notifications, emoji reactions and snippet version history "are not included in legal holds" [2].

Retention is the quiet lever, and it is not yours. Slack's trust page says that "On the free version of Slack, you'll have the option to choose whether messages and files are deleted after 90 days, or whether messages and files (including edits) are kept for a year." On paid plans, "the default message and file retention setting is to keep everything for as long as the paid workspace exists." [3] "Workspace owners can customize their retention policies" [3], and the same page is blunt about ownership: "The Primary Owner of a workspace or org controls their workspace's data (we call this Customer Data). This includes all of the content submitted by members, along with member profile information." [3]

So the privacy of a Slack DM depends on which plan your employer bought and how hard they push the paperwork, not on whether you used a DM instead of a channel.

Microsoft Teams: Every Chat Lands in a Mailbox Somebody Else Owns

Microsoft's documentation is franker than most vendors' about the architecture, and the architecture is the finding. Teams content is not just sitting in Teams. Microsoft Learn explains that "In Microsoft 365, data is stored across three platforms: Exchange, Microsoft Teams, and SharePoint." User data covers "their mail, 1:1 Teams messages, and OneDrive files." [6] A Teams group pulls in "Exchange mailbox storage for Teams chats and emails, as well as all associated SharePoint sites for channels and the team." [6]

The copying is the part that matters: "All Microsoft Teams 1:1 or group chats are journaled through to the respective users' mailboxes. All standard channel messages are journaled through to the group mailbox representing the team." [5] Private channels are no refuge. For those, "Messages sent in a private channel are stored in the Exchange Online mailboxes of all members of the private channel." [5]

Microsoft is careful about where the copies physically live, and the answer is reassuring in one narrow way. "Teams data is stored in Azure Cosmos DB. Exchange Online stores Teams compliance records that the substrate captures, and eDiscovery can access these records. The data stored in Exchange Online is hidden from clients. eDiscovery never operates against the real Teams message data, which remains in Azure Cosmos DB." [5]

What can actually be pulled is broad. The searchable content list for chat messages "includes content in standard Teams channels, 1:1 chats, 1:N group chats, chats with yourself, and chats with guests." [5] Meeting records go further than the conversation itself, since the discoverable meeting metadata includes "Meeting join and leave events for each participant" [5] alongside VOIP joins and guest joins. One gap is documented: "Not all Teams content is eDiscoverable." [5]

The barrier is a licence, and it is a real one. Microsoft Learn states: "Both admins and users working with eDiscovery cases require a Microsoft 365 Enterprise E3 or E5 license." [4] For the premium tier, the same documentation points to "Microsoft 365 Enterprise E5 licensing" as the subscription requirement [6]. A workspace on a cheaper Microsoft 365 plan simply cannot run these searches. That is why so many teams cannot read chats: the tool was never bought.

One switch is worth knowing for sensitive meetings. Teams has a "Hide Attendee Names" feature, which Microsoft describes as one that "hides the name of attendees from other attendees so only organizers can see attendees names", with names hidden "in the meeting roster, meeting chat, and meeting recordings" [5]. The limit is honest and worth knowing: "Hidden attendee names are only available in the organizer's mailbox." [5]

Google Workspace: Reports Are Always On, Vault Is the Separate Product

Google splits the problem in two, and the split is the most useful thing in this whole comparison.

The always-on half is reporting. The admin console lets "As an administrator, you can view reports and log events in the Google Admin console to review activity in your organization" [7], covering the things that describe behaviour without reading it: sign-ins ("Track who signs in and when"), content creation ("Understand how users create and share content"), admin actions ("Analyze administrator activity"), and security signals ("Examine potential security risks") [7]. The security report also "Lets you assess your domain's overall exposure to data breach and lets you see if your team is using 2-Step Verification" [7].

The browser is the leak people miss. Google records events for "managed Chrome browsers and ChromeOS devices" [8], and the scope limit is the thing to remember: "The browser must be managed by Chrome Browser Cloud Management, a ChromeOS device that's enrolled with your organization, or a user profile managed in Chrome browser." [8] Inside that scope the log is detailed. The event record includes the URL, the browser profile, the device name, and the client type, and the event types listed include login, extension install, malware transfer, password change and reuse, suspicious URLs, unsafe site visits, content transfers and URL filtering. As the documentation puts it, "You can also see when there has been an unsafe site visit." [8]

The content half sits in Google Vault, a separate tool from those reports. Its overview is brief: "Google Vault is an information governance and eDiscovery tool for Google Workspace." [9] "With Vault, authorized users can search for data, put data on hold, and export data for further analysis." [9] The search is broad, and the documentation is specific about it: "You can search your organization's Google Workspace data by user account, organizational unit, date, or keyword, and preview messages, attachments, and supported files." [9]

The content types in scope include Gmail messages, Google Drive files, Google Calendar events, Google Groups messages, Google Voice text messages and transcripts, and Google Chat messages, where the documentation notes the condition "when conversation history is turned on" [9]. Holds work at scale: "To preserve data indefinitely for legal or other retention obligations, you can put holds on accounts, organizational units, and groups." [9] And anything found can leave: "After you search for data, you can export it for processing and analysis." [9]

Side by Side

PlatformActivity your employer sees without askingWho can read message contentWhat it takes
Slack Workspace owners and admins, retention policies, and export options [3] On Free and Pro, message export covers public channels only [1]. On Business+ and Enterprise it covers public channels, private channels and DMs [1] Business+ and Enterprise plans, plus an application from a Workspace or Org Owner [1]. Legal holds are an Enterprise capability run by the Legal Holds Admin role [2]
Microsoft Teams Meeting join and leave events, VOIP joins, guest joins, and the mailbox copies of every chat [5] Admins with eDiscovery permissions, searching 1:1 chats, 1:N group chats, standard channels and chats with guests [5] A Microsoft 365 Enterprise E3 or E5 license for everyone using an eDiscovery case [4]
Google Workspace Sign-ins, Gmail and Drive usage, docs created and shared, administrator activity, and events from managed Chrome browsers and ChromeOS devices [7][8] Authorized Vault users, searching by user account, organizational unit, date or keyword across Gmail, Drive, Calendar, Groups and Chat [9] Google Vault, the separate eDiscovery tool for Workspace [9]

What You Can Actually Do

None of this is a reason to quit your job. It is a reason to know which of the three worlds you are standing in, because the answer changes with the plan, the licence and the setting.

  • Read your workspace settings first. Slack's trust page says the Workspace Settings page shows "Message and file retention policies" and "Available data export options" [3]. Those two lines tell you what your employer is actually set up to keep and to pull. It takes a minute and it is the highest-value minute you will spend on this.
  • Find out whether your company holds the eDiscovery licence. If your Teams tenant is not on Microsoft 365 Enterprise E3 or E5, admins cannot run eDiscovery cases at all [4]. If it is, the capability exists whether or not anyone has ever used it.
  • Do not run personal browsing on a managed Chrome profile. Google's Chrome event log covers managed browsers, enrolled ChromeOS devices and managed profiles [8]. Because the browser has to be managed for the log to record it, an unmanaged personal profile stays out of this log, and the event record captures the URL [8].
  • Use Hide Attendee Names for the meetings that matter. It hides attendee names "in the meeting roster, meeting chat, and meeting recordings" [5]. Just remember the organizer's mailbox still holds them [5].
  • Check whether Chat conversation history is on. Google scopes Vault's reach into Chat to messages "when conversation history is turned on" [9], which makes that setting a genuine lever if your administrator controls it.
  • Treat a work DM as a work document. On Slack Business+ and Enterprise, DMs are inside the export set [1]. On Teams, 1:1 chats are journaled into mailboxes [5]. Neither platform gives you privacy from your employer, only from your coworkers.
  • Ask, in writing, what is retained. Retention defaults differ by plan, owners can customize them [3], and a legal hold suspends the normal settings entirely [2]. A short question to IT or a manager about retention and export policy tells you more than any general privacy guide.

The Part Nobody Wants to Hear

Every document here describes what the tooling can do, not what your employer does. A company holding Business+ has the ability to export DMs and private channels. A tenant with E3 licences has eDiscovery in the building. Whether anyone has ever opened either is a question only your employer can answer, and the vendor documentation does not say. The absence of use is not a promise that it will stay unused, and a new admin, a lawsuit, or a quiet policy change can change the answer overnight.

The narrower good news is real too. Slack's Free and Pro export covers public channels only [1], legal holds leave out Slack Connect conversations, emoji reactions and snippet version history [2], Google logs Chrome events only for managed browsers [8], and Google Vault's Chat reach depends on conversation history being turned on [9]. Small gaps, but they are the gaps you can actually check.

Know which platform you are on, know which plan it is on, and know who owns the workspace. That is the difference between suspecting your employer could read it and knowing which setting says whether they can today.

Sources

  1. Slack Help Center, "Export your workspace data". No publication date given; retrieved 8 November 2026.
  2. Slack Help Center, "Create and manage legal holds". No publication date given; retrieved 8 November 2026.
  3. Slack Trust Center, "Privacy at Slack". No publication date given; retrieved 8 November 2026.
  4. Microsoft Learn, "Get started with eDiscovery" (April 1, 2026)
  5. Microsoft Learn, "Finding content in Microsoft Teams in eDiscovery" (April 2, 2026)
  6. Microsoft Learn, "Data sources in eDiscovery" (September 19, 2026)
  7. Google Workspace Admin Help, "Monitor usage and security with reports". No publication date given; retrieved 8 November 2026.
  8. Google Workspace Admin Help, "Chrome log events". No publication date given; retrieved 8 November 2026.
  9. Google Workspace Help, "Vault overview". No publication date given; retrieved 8 November 2026.