Glossary

Legal Hold

A pause on deletion. When litigation is reasonably anticipated, an organisation must preserve relevant records, including chat messages and attachments, and keep preserving them until the hold is lifted.

General definition

Legal Hold (also called a litigation hold or preservation notice) is the process by which an organisation suspends its normal record deletion so that evidence relevant to a legal matter is not lost. In the United States the duty to preserve arises as soon as litigation is reasonably anticipated, not when a lawsuit is filed, and Rule 37(e) of the Federal Rules of Civil Procedure lets courts sanction a party that fails to take reasonable steps to preserve electronically stored information. Comparable duties exist under the civil procedure rules of England and Wales and most other jurisdictions.

A hold has three parts: a scope (which custodians, systems, date ranges and topics are covered), a notice to the people and teams who hold the records, and a technical change that stops automatic deletion for the data in scope. Chat is now routinely in scope. Courts and regulators treat messages the same way as email, so the hold must reach every platform where business conversations happen, including internal team chat, customer messaging and collaboration tools. Typical conflicts:

  • Retention schedules: a policy that deletes messages after 90 days or a year must be suspended for the covered rooms and users
  • Ephemeral messaging: disappearing messages are incompatible with a hold and should be switched off for the people in scope
  • Erasure requests: GDPR Article 17(3)(e) lets a controller refuse erasure where the data is needed for the establishment, exercise or defence of legal claims, so a hold can lawfully override a deletion request
  • Account offboarding: accounts and devices of leavers who are custodians under a hold must not be wiped

Preservation is not the same as collection. A hold keeps data where it is, unchanged; collection copies it into a review platform with a documented chain of custody. The underlying message archive and its log retention settings decide whether there is anything left to collect, which is why hold procedures should be tested before they are needed.

In the Ethora ecosystem

Ethora keeps a server-side message archive with configurable retention and per-user erasure, plus a compliance audit trail that can be exported as immutable logs. Those same controls are what a legal hold must pause. Applying a hold on Ethora is a procedure the app owner runs through the admin panel: extend or suspend the retention period for the App or the rooms in scope, stop processing erasure requests for the named custodians, and record the decision in the audit trail. Because each customer project is an isolated App, a hold on one project does not change retention for any other.

On a dedicated server or self-hosted deployment the archive database and exported logs sit in your own cloud account, so your legal team, not the vendor, decides who may access the preserved data and when the hold is released. Pairing the archive with your own storage retention rules gives a defensible preservation record without relying on end users not to delete messages.