Can you sell Google Chat messages to AI companies?
Rarely as a whole, and only after careful cleaning. Google Chat messages are informal and full of names, so a licensable set usually means selected spaces with the people replaced. Two admin routes exist. Google Vault searches and exports Chat messages for legal and records purposes, and the Admin console data export tool packages a whole organization's data. Neither is a button an ordinary user can press, and a setting called chat history decides whether some messages exist at all.
What Google Chat holds
| Spaces | Topic or team rooms with many members. Messages in a space are the best candidates, since they are written for a group. |
| Direct and group messages | Chats between two people or a handful of colleagues. These are personal by nature and usually stay out. |
| Threads and replies | The structure of an answer to a question, which is what makes chat useful for describing how teams solve problems. |
| Attachments and linked files | Files shared in chat, which are stored with the sender's Drive in many cases and need separate handling. |
| Edit and deletion details | Vault exports note when a sender edited or deleted a message. |
How data leaves Google Chat, route by route
| Tool | What an export gives you | What is missing or needs an admin |
|---|---|---|
| Google Vault | Search by account, date and terms, then export. Vault adds messages from 12 hours before and after each match, groups a conversation into one document unless there is a 24-hour gap, and delivers PST or mbox zip files with a metadata file. | Preview is capped at 1,500 messages, though exports include all matches. Vault cannot hold or search direct messages sent while history was off. |
| Admin console data export tool | Packages data for the whole organization or chosen groups, including messages and attachments for rooms created by users, as zip files per user. | It needs a super admin account at least 30 days old, takes typically 72 hours and up to 14 days, and the temporary bucket is deleted after 60 days. |
| Chat API | Lists the messages in a space, with a filter on creation time, for an app a developer builds with the right authorization scope. | Needs a developer and administrator approval, and we confirmed the details only from search results, not the full reference page. |
Tool names belong to their owners and are used only to say where records usually live. Export features change by plan and version, so check the current rules for your account.
The history setting decides what exists
Google says a super admin can turn chat history on or off for direct and group messages. With history off, messages are deleted after 24 hours and Vault cannot hold or search them. Spaces have their own history option, and changes apply only to new messages.
So before counting anything, ask whether history was on, and since when. A team that turned it off last year has no direct message archive before that point to export.
Who has to run it
Vault is a separate admin product with its own roles, and Chat history settings need an admin with the Chat administrator privilege. The data export tool needs a super admin who has 2-Step Verification on. Organizations with more than 1,000 users, or FedRAMP authorization, are told to contact Google support before using the tool.
The practical consequence is that the owner of a small company often needs the person who set up the Workspace account. Find that person early.
Choosing spaces over conversations
Count messages by space and by year, and keep direct messages out of the first count entirely. A set built from five well-used project spaces is more defensible than a dump of everything, because each space has a purpose and a known membership.
Each message needs the sender replaced with a consistent code, and mentions inside the text replaced too. A thread stops making sense if one person is two different codes.
What stays out of a Google Chat set
| Direct and group messages | Left out unless every participant is accounted for and the content is cleaned. |
| Spaces with outside guests | Other companies' staff did not agree to your licensing. |
| Passwords, links with access tokens and keys | Removed from text; if a message cannot be cleaned, it goes out. |
| Messages about health, pay or discipline | Excluded from any sample. |
More on this: how personal details are removed, who carries the risk and how you get paid.
An example, invented for illustration
A software consultancy uses Google Chat spaces for each client engagement. The Workspace admin runs a Vault search over three internal engineering spaces for two years and exports them as mbox files. The firm replaces names with codes, removes any message containing a credential, drops every direct message, and has the owner read a sample before deciding whether the spaces are worth describing.
Questions owners ask about this
Can Vault export direct messages?
Yes, when history was on. Google says Vault cannot hold, retain or search direct messages sent while history was off, since those are deleted after 24 hours.
What file format does a Vault Chat export use?
Zip files of PST or mbox, with an XML or CSV metadata file and an MD5 checksum file. PST zips are split at 1 GB and mbox at 10 GB.
Do Chat spaces follow the same history setting as direct messages?
No. The organization-level setting covers direct and group messages. Spaces have their own history option.
How long does the Admin console export take?
Google says no sooner than 48 hours, typically 72 hours and up to 14 days. It also cannot be canceled in the console once started.
Didn't find your question? Ask us directly.
Sources
The vendor's own pages this guide draws on. Some help centers did not open for us, and where a step rests on a summary and not the page itself, the guide says so. Menus and limits change by plan and version, so check the current pages for your account.
Keep reading
Related kinds of records
- Team chat: Slack and Teams threads, where one person must stay one person and direct messages stay out.
- Google Drive export: How to keep the comments and the version history when documents leave Google Drive.
- Slack data export: Channels, threads and the settings that decide how much of your chat history can leave.
- Gmail data export: Shared mailboxes, labels and the export routes that fit a Google Workspace domain.