|
1.
|
Introduction
It is common for most companies that collaboration tools have already become fundamental infrastructure for their internal communication and document management. However, the implementation and configuration of collaboration tools are typically led by each company’s IT or administrative support department, while its legal department often steps in only after issues arise.
The issue is that these tools record the company’s decision-making process in an unrefined form. Collaboration tools enable more casual conversations with less reliance on emails, and automatically record each document’s history of changes from the initial draft to the final version. Accordingly, these records can be searched and extracted in bulk using administrative privileges. In many cases, items deleted by users still remain in the collaboration tools.
|
|
2.
|
What Is Preserved as a Record?
|
|
(1)
|
Records of Conversations and Emails
Since remote work became the norm in early 2020, collaboration tools have rapidly emerged to play the pivotal role in internal corporate communication. Since then, there has been a steady increase in cases where records accumulated within these collaboration tools have become the subject of field investigations or search-and-seizure operations. When acquiring data, the method employed involves the batch extraction of conversations and emails—specifically those involving certain individuals over a specific period—via the administrator console, rather than relying solely on individual devices.
In practice, a more significant issue lies in the language used in conversations and emails. For example, unrefined statements and unverified speculations are often exchanged unfiltered via instant messaging. These messages are preserved verbatim, despite containing (i) expressions that jump to conclusions with unverified facts, (ii) comments speculating about potential illegality, and (iii) statements containing jokes or hyperbole. For third parties who are unaware of the original context may read these messages literally, it is likely that these messages could be interpreted to the writers’ disadvantage, regardless of the writers’ intent.
|
|
(2)
|
Documents and Their History
Documents are an area that is often overlooked. Collaboration platforms such as SharePoint, Google Drive, and Confluence do not store only the final version. They retain the version history, details of changes, authors, and timestamps, while accumulating records of comments and suggestions made within the documents.
Thus, any statements deleted from the final version remain intact in the version history. This structure cannot be managed with the notion that “only the final version should be managed,” because in some cases the initial drafts that have been deleted reveal the decision-making process more clearly than the final version itself.
In addition, search and audit logs are generated, showing who accessed or downloaded which documents and when. While these logs can work to the company’s advantage in the event of an information leakage, they can conversely serve as evidence to prove exactly when specific officers/employees became aware of the incident.
|
|
(3)
|
Schedules and Meeting Records
Calendars serve as records, too. The list of attendees for a scheduled meeting reveals who were aware of specific matters and when, as well as who were involved in decision-making. Furthermore, video conference recordings capture the actual content of remarks in far greater detail than instant messaging conversations. Therefore, it is essential to identify whether recordings are available and their retention period.
|
|
3.
|
Retention and Deletion Policies and Management Tools
Indefinite retention of data expands the scope of exposure during investigations, while arbitrary deletion of data leads to controversy regarding obstruction of an investigation or destruction of evidence. Ultimately, the greatest risk is the absence of a policy. If a company manages its data without any standards in place, and individual departments arbitrarily clear out data when signs of a dispute emerge, this will become an issue.
In this connection, the highest priority should be placed on checking the current configuration settings. Many companies continue to use the default settings set at the time of implementing collaboration tools, and their legal departments are often unaware of what those settings are. Microsoft 365 Purview and Google Workspace Vault are tools that manage retention periods by data category and control how deleted items are handled.
Retention periods should not be determined solely by the IT department. A too short retention period may result in the loss of data that could have worked to the company’s advantage. On the other hand, a too long retention period is likely to widen the scope of exposure during investigations. Slack and Confluence operate under their own retention frameworks separate from M365 and Google Workspace. Thus, it important to consider how policies may become fragmented when using multiple tools simultaneously.
|
|
4.
|
Legal Department’s Checklist
To identify and properly manage the risks associated with collaboration tools, the legal department should consider taking the following measures:
(1) Conduct a comprehensive inspection of collaboration tools currently in use — including tools (Shadow IT) implemented at the departmental level
(2) Identify the current data retention settings for each tool — review the current configuration settings and document them in the company’s internal policy
(3) Check the scope of document histories, meeting recordings, and audit logs — identify what data is preserved and who has access thereto
(4) Distribute guidelines for communication and document creation — establish principles based on the understanding that records may be subject to ex-post access for scrutiny
|
|
5.
|
Conclusion
Once an incident occurs, it is too late to respond to the risks associated with collaboration tools. By the time an investigation begins, the records subject to the investigation are already fixed and the configuration settings at that time determine the scope of the company’s defense. Therefore, it is critical to have a system whereby the legal department can be involved from the initial stage of establishing the company’s internal IT policies.
|
[Korean Version]
[Related Newsletter] Legal Tech Practical Issues Update 2026