Legal hold and eDiscovery for call recordings and transcripts

See also

Sources

1. 1
   Letting a recording platform's scheduled autopurge continue to delete relevant recordings after a duty to preserve has arisen exposes a party to Rule 37(e) remedies, because routine operation is only one factor in the reasonable-steps assessment rather than a safe harbour.inferred

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Rule 37(e) and 2015 Committee Note, Subdivision (e) · Checked 2026-10-14
2. 2
   AWS recommends a dedicated Amazon Connect call recording bucket for Object Lock because all objects are locked once the default retention policy is applied, and advises testing the policy outside production first.

   How to set up S3 Object Lock for immutable call recordings · Important things to know · Checked 2026-10-14
3. 3
   For Amazon Connect call recording buckets, S3 Object Lock can be enabled on new or existing buckets but cannot be removed once enabled.

   How to set up S3 Object Lock for immutable call recordings · Important things to know · Checked 2026-10-14
4. 4
   FRCP Rule 34(a)(1)(A) lets a party request production of designated documents or electronically stored information, which is the procedural route by which call recordings and transcripts held as ESI are requested in US federal civil discovery.

   Rule 34. Producing Documents, Electronically Stored Information, and Tangible Things, or Entering onto Land, for Inspection and Other Purposes · Rule 34(a)(1)(A) · Checked 2026-10-14
5. 5
   The current text of FRCP Rule 37(e) dates from the amendment adopted April 29, 2015 and effective December 1, 2015, which replaced the 2006 version of subdivision (e) and applies only to electronically stored information.

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Amendment history line and 2015 Committee Note, Subdivision (e) · Checked 2026-10-14
6. 6
   The 2015 Advisory Committee Note to Rule 37(e) states that the rule is based on the common-law duty to preserve when litigation is reasonably foreseeable and does not create a new duty to preserve.

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Notes of Advisory Committee on Rules, 2015 Amendment, Subdivision (e) · Checked 2026-10-14
7. 7
   The 2015 Committee Note to Rule 37(e) states that reasonable steps to preserve suffice and that the rule does not call for perfection; the rule is inapplicable when information is lost despite reasonable steps.

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Notes of Advisory Committee on Rules, 2015 Amendment, Subdivision (e) · Checked 2026-10-14
8. 8
   The 2015 Committee Note to Rule 37(e) names proportionality as a factor in evaluating the reasonableness of preservation efforts and asks courts to be sensitive to a party's sophistication with regard to litigation.

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Notes of Advisory Committee on Rules, 2015 Amendment, Subdivision (e) · Checked 2026-10-14
9. 9
   FRCP Rule 37(e) applies when electronically stored information that should have been preserved in the anticipation or conduct of litigation is lost because a party failed to take reasonable steps to preserve it and it cannot be restored or replaced through additional discovery.

   Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Rule 37(e) introductory clause · Checked 2026-10-14
10. 10
    The 2015 Committee Note to Rule 37(e) treats the routine, good-faith operation of an electronic information system as a relevant factor in assessing whether a party failed to take reasonable steps to preserve.

    Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Notes of Advisory Committee on Rules, 2015 Amendment, Subdivision (e) · Checked 2026-10-14
11. 11
    Under FRCP Rule 37(e)(1), on finding prejudice to another party from the loss of ESI, a court may order measures no greater than necessary to cure the prejudice.

    Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Rule 37(e)(1) · Checked 2026-10-14
12. 12
    Under FRCP Rule 37(e)(2), a court may presume lost ESI was unfavourable, give an adverse-inference jury instruction, or dismiss or enter default judgment only on finding that the party acted with intent to deprive another party of the information's use in the litigation.

    Rule 37. Failure to Make Disclosures or to Cooperate in Discovery; Sanctions · Rule 37(e)(2)(A)-(C) · Checked 2026-10-14
13. 13
    Genesys Cloud allows at most 1000 conversations to be protected per organisation.

    Protect recordings from deletion · Note / limits · Checked 2026-10-14
14. 14
    The Genesys Cloud recording audit trail captures protection events, and the Interactions view shows a lock icon for protected recordings.

    Protect recordings from deletion · Audit and Interactions view sections · Checked 2026-10-14
15. 15
    Applying protection to one Genesys Cloud recording protects all recordings in the same conversation, including future recordings added to that conversation.

    Protect recordings from deletion · Introductory section · Checked 2026-10-14
16. 16
    Genesys Cloud recording protection does not apply to a conversation for which no recording exists.

    Protect recordings from deletion · Note · Checked 2026-10-14
17. 17
    In Genesys Cloud, protecting a recording prevents manual deletion and overrides existing policy deletion dates for as long as the protection remains in place.

    Protect recordings from deletion · Introductory section · Checked 2026-10-14
18. 18
    Applying and removing Genesys Cloud recording protection require the permissions Recording > Protect recordings from deletion > apply and Recording > Protect recordings from deletion > revoke respectively.

    Protect recordings from deletion · Prerequisites · Checked 2026-10-14
19. 19
    When Genesys Cloud recording protection is removed, any existing policy deletion date is applied again, so a recording past its deletion date can be deleted under that policy.

    Protect recordings from deletion · Remove protection section · Checked 2026-10-14
20. 20
    Genesys Cloud recording protection also protects associated attachments and transcripts, and applies to policy-based recordings of calls, chats, emails and messages and their screen recordings.

    Protect recordings from deletion · Introductory section · Checked 2026-10-14
21. 21
    If an administrator removes a user's Vault-supporting licence, Vault holds no longer protect that user's Google Voice data from deletion.

    Place Google Voice data on hold · Licensing note · Checked 2026-10-14
22. 22
    Google Vault holds on Google Voice data override retention rules, preserving supported Voice data indefinitely while the hold is in place.

    Place Google Voice data on hold · Introductory section · Checked 2026-10-14
23. 23
    A Google Vault Voice hold targets either specific accounts or an organisational unit, not both; accounts cannot be added to an OU-scoped hold and the scope type cannot be changed after creation.

    Place Google Voice data on hold · Create a hold section · Checked 2026-10-14
24. 24
    After a Google Vault Voice retention period expires it can take up to 30 days for Voice to purge the affected data.

    Retain Google Voice data with Vault · Retention period expiry note · Checked 2026-10-14
25. 25
    A new or changed Google Vault retention rule for Voice can take up to 24 hours to propagate, and items users delete during that window are not retained.

    Retain Google Voice data with Vault · Before you begin / timing note · Checked 2026-10-14
26. 26
    Google Vault supports retention and holds for three Google Voice data types: text messages, voicemails with their transcripts, and call logs with recordings.

    Retain Google Voice data with Vault · Supported data types section · Checked 2026-10-14
27. 27
    Google Vault does not cover Voice data for a number assigned to more than one user, Voice data created before June 5, 2019 (GMT-7), or Voice data for accounts with Archived User licences.

    Retain Google Voice data with Vault · Unsupported data section · Checked 2026-10-14
28. 28
    Recording legal hold granularity differs by platform: Webex Control Hub and Google Vault hold by custodian (or Google OU), Genesys Cloud protects by conversation with a 1000-conversation cap, and Amazon S3 holds individual object versions, so a single hold procedure cannot be reused unchanged across platforms.inferred

    Protect recordings from deletion · Introductory section and limits note, read with the Webex, Google and AWS sources · Checked 2026-10-14
29. 29
    When an item targeted by Purview priority cleanup is subject to an eDiscovery hold, approval from an assigned eDiscovery admin is required in addition to a priority cleanup admin; one eDiscovery approver suffices.

    Override holds to clean up files for Copilot and reclaim storage · Prerequisites for priority cleanup > Policy approvers · Checked 2026-10-14
30. 30
    Microsoft Purview priority cleanup can delete OneDrive and SharePoint content, including stale Teams meeting recordings and transcripts, despite existing retention settings or eDiscovery holds, moving items to the second-stage Recycle Bin.

    Override holds to clean up files for Copilot and reclaim storage · Introductory section and typical use cases · Checked 2026-10-14
31. 31
    Data already copied into an eDiscovery review set cannot be deleted by Purview priority cleanup; it is deleted only when the whole eDiscovery case is deleted by an eDiscovery admin.

    Override holds to clean up files for Copilot and reclaim storage · Important exceptions for priority cleanup · Checked 2026-10-14
32. 32
    An S3 Object Lock legal hold prevents an object version from being overwritten or deleted, has no expiration date, remains until explicitly removed, and is independent of any retention period on the same version.

    Locking objects with Object Lock · How S3 Object Lock works > Legal holds · Checked 2026-10-14
33. 33
    Any user with the s3:PutObjectLegalHold permission can freely place or remove an S3 Object Lock legal hold.

    Locking objects with Object Lock · How S3 Object Lock works > Legal holds · Checked 2026-10-14
34. 34
    S3 Object Lock works only in buckets with S3 Versioning enabled.

    Locking objects with Object Lock · Introductory section · Checked 2026-10-14
35. 35
    Teams call logs, which include call data records and other call metadata, are retained indefinitely by default and can be targeted as a single workload by a Purview retention policy whose only applicable action is deletion.

    Learn about retention for Teams · How retention works with Microsoft Teams call logs · Checked 2026-10-14
36. 36
    Microsoft documents finding Teams recording and transcript files with an eDiscovery (Premium) case by creating and committing a collection and filtering the review set.

    Manage Teams recording policies for meetings and events · eDiscovery search for recordings and transcripts · Checked 2026-10-14
37. 37
    Permanent deletion of Teams chat and channel messages from the SubstrateHolds folder is suspended while the mailbox is under Litigation Hold, delay hold, an eDiscovery hold, or another Teams retention policy for the same location.

    Learn about retention for Teams · How retention works with Microsoft Teams messages, Important note · Checked 2026-10-14
38. 38
    Teams meeting recordings are uploaded to the organiser's OneDrive for private meetings and to the channel's SharePoint site for channel meetings, and Microsoft Purview applies to them as to other files.

    Manage Teams recording policies for meetings and events · 'When a meeting is recorded' list · Checked 2026-10-14
39. 39
    Purview retention policies for the Teams chats and channel messages locations do not cover meeting recordings and transcripts; those need a policy on the OneDrive accounts location (user chats) or Microsoft 365 Group or SharePoint site locations (channel meetings).

    Learn about retention for Teams · What's included for retention and deletion · Checked 2026-10-14
40. 40
    Webex Calling CDRs have a default retention of 400 days (13 months).

    Ensure regulatory compliance of Webex Calling content (Calling retention) · CDR retention section · Checked 2026-10-14
41. 41
    Webex Control Hub eDiscovery lets compliance officers search Webex Calling CDRs and call recordings, generate reports downloadable with the eDiscovery Download Manager, and logs all compliance officer searches for audit.

    Ensure regulatory compliance of Webex Calling content (Calling retention) · eDiscovery section · Checked 2026-10-14
42. 42
    Cisco's Webex Calling compliance article states that legal hold preserves Webex Calling data beyond the retention policy and helps preserve call recording data for individual users.disputed

    Ensure regulatory compliance of Webex Calling content (Calling retention) · Legal hold section · Checked 2026-10-14
43. 43
    Webex Calling takes approximately 1 to 30 days to delete compliance data after it expires under the retention policy.

    Ensure regulatory compliance of Webex Calling content (Calling retention) · Retention policy section · Checked 2026-10-14
44. 44
    Webex Calling call recordings, transcripts, summaries and action items have a fixed 360-day retention without Pro Pack; with a Webex Calling Pro Pack licence the period is configurable from 7 to 3600 days with a 360-day default.

    Ensure regulatory compliance of Webex Calling content (Calling retention) · Retention policy section · Checked 2026-10-14
45. 45
    Webex keeps a departed or deleted user's content and identity for up to 13 months, after which compliance and eDiscovery reports cannot be generated for that user even if the user was on hold while active.

    Manage compliance data for legal hold · Deleted users note · Checked 2026-10-14
46. 46
    The Webex Control Hub legal hold article defines held Calling content as Call Detail Records only, and does not list Webex Calling call recordings, transcripts or voicemail.disputed

    Manage compliance data for legal hold · Content types list: Calling content · Checked 2026-10-14
47. 47
    Only a user holding the compliance officer role can create a legal matter and access legal holds in Webex Control Hub.

    Manage compliance data for legal hold · Overview / prerequisites section · Checked 2026-10-14
48. 48
    The Webex Control Hub legal hold article lists three held content types: space content (messages, files, whiteboards), Meetings recordings, and Calling content.

    Manage compliance data for legal hold · Content types list near top of article · Checked 2026-10-14
49. 49
    In Webex Control Hub a compliance officer creates a legal matter under Legal Matters by naming it and uploading a CSV template listing custodian email addresses; custodians are later added or removed by uploading an updated CSV.

    Manage compliance data for legal hold · Create a legal matter; Add or remove custodians sections · Checked 2026-10-14
50. 50
    A Webex Control Hub legal hold can be placed on an active user's content but not on a deleted user's content.

    Manage compliance data for legal hold · Overview / restrictions · Checked 2026-10-14
51. 51
    Webex Control Hub legal hold is part of Pro Pack for Control Hub.

    Manage compliance data for legal hold · Overview / prerequisites section · Checked 2026-10-14
52. 52
    When a Webex legal matter is released, no information related to the matter is retained and the data is released or deleted according to the organisation's retention policy.

    Manage compliance data for legal hold · Release a legal matter section · Checked 2026-10-14
53. 53
    If a Webex user under legal hold deletes a recording and it is later purged, the recording is permanently deleted from Webex and the compliance officer cannot retrieve it.

    Manage compliance data for legal hold · Content under hold note · Checked 2026-10-14
54. 54
    No Cisco document reviewed describes a per-custodian or per-recording legal hold for Webex Contact Center recordings: the WxCC retention article does not mention legal hold and the Control Hub legal hold article does not list Contact Center content, so the only documented lever against autopurge is the org-wide retention period.inferred

    Manage Retention and Purge Recordings and Transcripts in Webex Contact Center · Whole article (absence of any legal hold section) · Checked 2026-10-14
55. 55
    Webex Contact Center autopurge permanently deletes recordings during the purge, making them unrecoverable.

    Manage Retention and Purge Recordings and Transcripts in Webex Contact Center · Overview · Checked 2026-10-14
56. 56
    Webex Contact Center recording retention can be set from 7 to 3600 days; new organisations default to 1095 days and existing organisations retain indefinitely until an administrator sets a period.

    Manage Retention and Purge Recordings and Transcripts in Webex Contact Center · Set the retention period section · Checked 2026-10-14
57. 57
    A single Webex Contact Center retention setting governs both call recordings and transcripts, and a change applies from the next purge cycle.

    Manage Retention and Purge Recordings and Transcripts in Webex Contact Center · Key features section · Checked 2026-10-14
58. 58
    Zoom's launch announcement describes Zoom Compliance Manager legal hold as capturing and holding communications of specific individuals, with case management and data export requests.

    Zoom announces communications compliance solution, Zoom Compliance Manager · Legal hold bullet in feature list · Checked 2026-10-14
59. 59
    Zoom announced Zoom Compliance Manager on March 20, 2024 as a paid-plan add-on, built on Theta Lake technology, whose archiving automatically captures phone recordings along with meetings data, AI summaries, team chat and whiteboard content.

    Zoom announces communications compliance solution, Zoom Compliance Manager · Archiving bullet in feature list · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). Legal hold and eDiscovery for call recordings and transcripts. WarmTransfer. https://warmtransfer.net/knowledge/recording-legal-hold-ediscovery

@misc{warmtransfer-recording-legal-hold-ediscovery,
  title  = {Legal hold and eDiscovery for call recordings and transcripts},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/recording-legal-hold-ediscovery},
  note   = {Verified 2026-10-14}
}