When an Old Post Becomes Evidence: What You Can and Cannot Delete

--
title: "When an Old Post Becomes Evidence: What You Can and Cannot Delete"
description: "Once a post is part of a live dispute, deleting it can make things worse rather than better. Preservation obligations, why screenshots outlast the original, and which content is safe to remove and which is not. A practical line between routine cleanup and destroying your own record."
tags: ["privacy", "law", "security", "discuss"]

canonical_url: https://digital-footprint-health.shop/blog/old-tweets-as-court-evidence

Routine advice about old posts says to delete what you do not want read. That advice stops being safe the moment a dispute is live, because deletion at that point is not cleanup. It is the removal of a record that someone else is relying on.

The practical problem is that people usually realise this after they have already started deleting.

Why the original matters less than you think

The instinct is that deleting the source post removes the evidence. It rarely does, for three reasons that all make deletion a poor strategy.

Screenshots exist. Anyone involved in the dispute who saw the post has almost certainly captured it. A screenshot is out of your reach entirely.

Platform archives exist. Even after deletion, the platform may retain the content for its own periods and may produce it in response to a legal request. Your deletion does not bind the platform.

Third party mirrors exist. Archive services and aggregators copy public content independently, and they do not respond to your deletion on the platform at all.

So the expected outcome of deleting during a live dispute is that the record survives anyway, while you have created a separate problem.

What deletion looks like from the other side

Courts and opposing parties treat the destruction of records differently from the records themselves. Content that existed and was then removed during a dispute is a fact that can be established through the screenshots and the mirrors, and the removal itself becomes something to explain.

That is the asymmetry worth understanding. The post you did not want read is often the smaller issue. The removal, established through someone else's screenshot, is the larger one.

Preservation obligations in plain terms

Once litigation is reasonably anticipated, parties are generally expected to preserve relevant records rather than destroy them. The specifics vary by jurisdiction and by the type of proceeding, and this is where professional advice is worth the cost.

What generalises across jurisdictions is the direction of the obligation. It runs toward keeping things, not toward removing them, and it begins earlier than most people assume, at the point a dispute becomes foreseeable rather than at the point a claim is filed.

What is usually still safe to remove

The line is not between all posts and no posts. It is between content relevant to the dispute and content that is not.

Category	Deletion risk	Reasoning
Posts that are the subject of the dispute	High	Directly relevant, removal is the act in question
Posts discussing the dispute or the other party	High	Foreseeably relevant, even if written before it started
Posts establishing a timeline around the events	Moderate to high	Relevance is often not obvious until later
Unrelated personal content	Low	Outside the scope of the matter

The middle two rows are where people get caught. Posts written before a dispute began, which then turn out to establish a timeline, are the category most often deleted by someone who believed they were tidying up.

A sequence that avoids most of the trouble

Stop deleting as soon as a dispute becomes foreseeable. That includes situations where no claim has been filed, since the obligation attaches to foresight rather than to a filing date.

Inventory what exists before touching anything. Identify which posts relate to the events, including indirectly, and set those aside as preserved.

Handle only clearly unrelated content, and record what you removed and roughly when. A record of your own actions is cheap to keep and valuable if the question comes up.

Get advice before removing anything in the middle category. The cost of asking is small next to the cost of explaining a deletion later.

Where routine cleanup still belongs

None of this removes the value of ordinary hygiene. Identifying information, addresses, document photos and posts involving people who did not consent to being discussed are worth removing on an ongoing basis, precisely because a dispute is easier to handle when the archive is not carrying unrelated risk.

The mistake is treating both categories as the same task. One is maintenance, appropriate at any time. The other becomes a question of preservation, and the timing changes what the right action is.