By Joseph Caruso, Founder, CEO and CTO, Global Digital Forensics

How Deleted Email and Personal Accounts Leave an Evidentiary Trail

In high profile regulatory inquiries, government investigations and complex commercial litigation, disputes frequently center on whether executives used unapproved personal email accounts, communicated via off channel messaging applications like WhatsApp or Signal, or attempted to purge email servers prior to a subpoena. Emptying the Deleted Items folder or wiping a single server touches one copy of a communication, and the examination looks for the others.

Multi Endpoint Correlation and Server Artifact Recovery

Electronic communication is inherently distributed: every email or message sent by one custodian leaves independent forensic traces across sending servers, intermediate transport gateways, cloud recoverable item substrates in Microsoft Purview, recipient mailboxes and synchronized mobile handsets. Working directly for retained litigation and regulatory counsel, Global Digital Forensics reconstructs deleted communication records by examining Exchange EDB databases, PST and OST local cache files, unallocated disk space, mobile SQLite write ahead logs and counterparty server headers. When a party uses specialized wiping utilities to purge records after a preservation duty attaches, our examiners document the exact execution artifacts of those wiping tools to support Rule 37(e) spoliation remedies.

Rule 37(e) and the Facts an Examiner Supplies

Spoliation disputes over electronic communications are decided under Rule 37(e), and the rule's structure tells us what the examination must establish. It 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". Each clause is a technical question before it is a legal one. Was the information lost, or does it survive in a recoverable items folder, a backup, a recipient's mailbox or a synced handset? Were the steps taken reasonable in light of the retention settings and holds available on the platform? Can the content be restored or replaced from another source? The examiner works those questions through the platform's own records, and counsel argue from the answers.

The remedies turn on two further findings. Under subsection (e)(1), a court that finds prejudice "may order measures no greater than necessary to cure the prejudice". Under subsection (e)(2), the severe remedies of an adverse inference, a presumption instruction, dismissal or default are available "only upon finding that the party acted with the intent to deprive another party of the information's use in the litigation". Intent is where forensic evidence matters most. The execution of a wiping utility days after a preservation letter, a retention policy shortened the week a subpoena arrived, a mailbox purged through a hard delete that bypassed the ordinary deleted items path, or a phone reset the night before a collection are the kinds of events the record captures with timestamps. We lay those sequences out as a timeline and let the court draw the inference. Our email forensics practice has supported hundreds of email related depositions and testimony engagements built on exactly this kind of analysis.

Where Deleted Email Persists and What Each Copy Shows

A message that a custodian believes is gone usually survives in several places, each with different evidentiary value. In Microsoft 365, deleted items move through the Recoverable Items folder, where retention policies and litigation holds can keep them long after the user has emptied every visible folder, and the unified audit log records SoftDelete, HardDelete, MoveToDeletedItems and MailItemsAccessed events by account, client and time. Microsoft publishes how long those audit records are kept by license level, and we export them before the window closes. Google Workspace keeps comparable records in Vault and in the Gmail log events. On the server side, Exchange database files and their transaction logs, and on the client side the OST and PST caches, retain message fragments in unallocated space that carving can recover. Every recipient's mailbox holds an independent copy, and every synced phone holds another.

Each source establishes something different, and the report says which. Audit logs record that a message existed and when it was deleted, by which account and through which client, which stands as evidence in its own right alongside any recovered content. Recoverable Items and backups establish content, and their metadata establishes the original dates. Recipient copies establish content and transmission, and the sender's own mailbox and server records are where we look for what became of the sender's copy. Handset databases show the message as the custodian saw it, together with read status and attachments. The scope of each source matters as much. For a retention window that closed before the engagement began, the examination turns to backups, recipients and handsets, and carved fragments are dated through surrounding records when their headers are incomplete. When a personal account is involved, counsel pursues the provider's records through the available legal process and the account holder's own access, and we tell counsel early what to ask for. The Microsoft 365 forensics page describes the sources in more depth.

Off Channel Messaging and the Handset Collection

Regulators and courts have made off channel communications a central discovery issue, and the handset is where the record lives. iMessage, WhatsApp, Signal and Telegram each store messages in SQLite databases on the device, and the write ahead log files beside those databases frequently retain records of messages that the application no longer displays. Disappearing message settings are themselves recorded, so a conversation set to vanish after one day leaves evidence that the setting was chosen and when, which is often the point for a spoliation argument. Cloud backups of the handset, when they exist, carry earlier states of those databases. Veronica Perez leads our mobile work, and her examinations of mobile communications, application activity and location records have been designated in state superior courts and in federal court.

Collection can leave the phone with its owner. Our supported remote collection works through a link and a computer connection, normally with the custodian keeping the phone in use, and the collection usually runs from a few minutes to overnight depending on the setup. For executives whose phones hold both personal and business communications, counsel typically agree an inspection protocol that limits the examination to the accounts, contacts and date ranges at issue, and we document what was reviewed against the protocol so its observance is on the record. The full examination then ties the handset record to the server and mailbox record, so that a message deleted from the mailbox but present on the phone, or present in a recipient's handset but absent from the custodian's, is placed in a single timeline the court can follow.

Building the Spoliation Timeline Into a Declaration

A spoliation motion rises or falls on sequence, and the examiner's product is a timeline in which each entry is tied to an artifact. The preservation letter date comes from counsel. The retention policy change comes from the tenant's configuration audit log. The execution of the wiping utility comes from Prefetch, Amcache and the UserAssist key on the workstation, and from the SRUM database that records how much data the program read and wrote. The hard delete of the mailbox contents comes from the unified audit log, with the client application and IP address attached. The phone reset comes from the device's own logs and from the gap between the cloud backup date and the collection. Laid side by side, these entries show what happened and in what order, and they are the facts that support a finding of intent or refute one.

The declaration that carries the timeline is written to be tested. Each entry states the source, the tool used to parse it and how the result was validated, so that the opposing expert has to dispute the artifacts themselves rather than the examiner's description of them. Where the record supports more than one reading, the declaration sets out each, because candor on the small points earns trust on the large ones. Testimony follows the same discipline under Rule 702, and the examiner who built the timeline is the one who defends it at deposition. The digital forensics process guide explains how collection, examination, analysis and reporting fit together.

The same method serves a party accused of spoliation. A retention policy that deleted messages on schedule, a device replaced in the ordinary course or a mailbox cleaned under a documented records program all produce timelines in which the sequence shows routine administration rather than destruction, and the examiner's job is to present that sequence with the same precision. Counsel defending a motion need the configuration history of the tenant, the records policy in force and the dates on which each applied, laid against the date the preservation duty arose. A timeline that shows the deletions predated the duty, or followed a policy adopted long before the dispute, answers the intent prong directly and often narrows the remaining question to whether the content can be restored from another source.

Consult With a Senior Email and Messaging Forensic Examiner

Call Global Digital Forensics at (800) 868-8189 to discuss email recovery, off channel mobile collection or spoliation analysis for your matter. Our email forensics page describes what the examination covers. The initial consultation is free.

Where Deleted Email Still Lives and What Each Copy Establishes

The guide explains that a message a custodian believes is gone usually survives in several places, each with different evidentiary value. This table lists those sources, what each establishes and how the examiner reads it, so counsel can see which copy answers which question in a spoliation dispute. Read the last column alongside the dates of your matter, because retention windows and fragment headers shape which copy carries each point. Audit logs record that a message existed and when it was deleted, which stands on its own alongside any recovered content.

Where deleted email survives, what each copy establishes and how the examiner reads it.
SourceWhat it establishesHow the examiner reads it
Recoverable Items folderContent kept by a hold after the user emptied foldersGoverned by the retention and hold settings
Unified Audit Log delete eventsThat a message existed and when it was deleted180 days standard per Microsoft
Exchange database and transaction logsMessage fragments in unallocated spaceDated through surrounding records when headers are incomplete
OST and PST client cachesCarved fragments on the workstationImaged early to capture unallocated space
Each recipient mailboxContent and transmissionThe sender's mailbox is checked for the sender's copy
Synced handset databaseThe message as the custodian saw itDisappearing settings are recorded alongside the content
Personal account recordsContent held by the providerReached through counsel's subpoena

The COMLAB v. Kal Tire matter turned on a claimed deletion after an alleged virus, where metadata analysis contradicted the explanation, the multi source reconstruction this guide applies to deleted email.

How to Begin and What Happens on the First Call

Have ready the accounts and devices involved, the platform and license tier for the corporate mailboxes, the dates that matter, including any preservation letter, subpoena or regulatory request, and what has already been done to recover or preserve messages. The examiner asks whether litigation holds are in place, whether audit logging was enabled and for how long records are kept, which messaging applications the custodians use, whether personal accounts or devices are implicated and what the court or regulator has asked for. Counsel then receive a written scope setting out the preservation steps in order of urgency, the recovery and analysis phases, the collection approach for handsets and the timing, with a proposal. The initial consultation is free, and the hotline at (800) 868-8189 answers 24/7.

Technical References and Further Reading

Related GDF pages for this work: digital forensics solutions.

Earlier reporting on this subject: The Washington Post on the court pressing the State Department about the Clinton email server, August 20, 2015.

Authorities cited in this guide: Federal Rule of Civil Procedure 37(e), Failure to Preserve Electronically Stored Information. Sets the threshold findings and the two tiers of remedies for lost electronically stored information, current rule text as amended in 2015. Microsoft Learn, Manage audit log retention policies. Documents how long Microsoft 365 mailbox audit events are retained by license level, current Microsoft documentation. Federal Rule of Evidence 702, Testimony by Expert Witnesses. Governs the reliability showing for the examiner's spoliation testimony, as amended effective December 1, 2023. NIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response. Describes the collection, examination, analysis and reporting phases applied to mailbox, server and handset evidence, final version 2006.