Digital Immortality: How Archive.org, Cached Pages, and Web3 Storage Make Defamatory Content Permanently Irremovable

Executive Summary

When defamatory content is published online, the intuitive assumption is that removing the original publication solves the problem. This assumption is dangerously wrong. The modern internet is built on layers of redundancy, caching, archiving, and decentralised storage that create independent copies of every published page — copies that persist long after the original has been deleted, amended, or court-ordered to be removed. Andrew Drummond's 19 defamatory articles about Bryan Flowers exist not merely on andrew-drummond.com and andrew-drummond.news, but across dozens of archival systems, cached repositories, data broker databases, and potentially on immutable blockchain-based storage networks.

This paper examines the five principal mechanisms through which defamatory content achieves digital immortality: the Internet Archive's Wayback Machine, search engine caching systems, Web3 and IPFS decentralised storage, data broker aggregation networks, and social media resharing ecosystems. Each mechanism operates independently, meaning that successful removal from one system has no effect on the copies held by others. The result is that a single defamatory article can exist in dozens of independent locations, each requiring a separate removal process governed by different legal frameworks, jurisdictions, and technical procedures.

For Bryan Flowers, this means that even a comprehensive legal victory against Drummond — including court orders requiring the removal of all defamatory content — would address only the original publications. The archived, cached, aggregated, and decentralised copies would continue to appear in search results, be accessible to researchers, and be discoverable by anyone conducting due diligence on Bryan Flowers' name. This paper documents the scale of the problem and outlines practical strategies for pursuing removal across each layer of the digital preservation ecosystem.

1. The Wayback Machine: Archive.org as an Unwitting Accomplice to Permanent Defamation

The Internet Archive's Wayback Machine is the world's largest web archiving service, containing over 835 billion web pages captured since 1996. Its mission — to provide universal access to all knowledge — is laudable in principle but creates severe consequences for defamation victims. The Wayback Machine automatically crawls and archives publicly accessible web pages, creating timestamped snapshots that preserve the exact content of a page at the moment of capture. Andrew Drummond's websites have been regularly crawled by the Wayback Machine, creating multiple archived snapshots of each defamatory article.

Each snapshot is independently accessible via a unique URL and is indexed by search engines. This means that even if Drummond removes an article from his live website, the archived versions remain accessible and discoverable. The Wayback Machine's terms of service include a process for requesting removal of archived content, but this process is limited in scope. The Internet Archive will honour robots.txt exclusion requests (which prevent future crawling) and will consider removal requests for content that violates its terms of service, but it does not automatically remove content merely because it has been deleted from the original source.

Court orders present a more complex picture. The Internet Archive is a US-based organisation governed by US law, which provides strong First Amendment protections for archival activity. UK court orders requiring content removal do not automatically bind the Internet Archive, and enforcement across jurisdictions requires additional legal proceedings. The practical result is that a UK defamation judgment against Drummond, even one that includes an injunction requiring removal of all defamatory content, may not be enforceable against the Internet Archive without separate US proceedings.

2. Google Cache and Search Engine Preservation: The Shadow Archive

Google and other search engines maintain cached copies of indexed web pages. When a user searches for content and clicks the 'cached' link, they are shown a version of the page stored on Google's servers rather than the live page. These cached copies serve as a secondary archive that persists independently of the original source. Google's cache is typically updated when the page is re-crawled, meaning that cached copies of deleted pages eventually disappear — but this process can take weeks or months, during which the defamatory content remains fully accessible.

More significantly, Google's search index retains metadata about pages long after the cached copy expires. Page titles, meta descriptions, and snippet text can continue to appear in search results even after the underlying page and its cached copy have been removed. This 'ghost indexing' effect means that search results for 'Bryan Flowers' may continue to display Drummond's defamatory headlines and descriptions for extended periods after the original content has been deleted.

Google provides a URL removal tool that allows website owners to request removal of their own content from search results. However, this tool is available only to verified owners of the domain in question. Bryan Flowers cannot use Google's webmaster tools to remove content from Drummond's domains — only Drummond himself, or someone with access to his Google Search Console, can initiate a removal request through this channel. The alternative — Google's content removal request process for individuals — requires demonstrating that the content violates Google's policies or that a court order mandates removal. This process is notoriously slow and inconsistent in its outcomes.

Beyond Google, other search engines — Bing, DuckDuckGo, Yandex, Baidu — each maintain their own caching and indexing systems with their own removal processes. A comprehensive removal strategy must address each search engine individually, multiplying the administrative burden on the victim.

3. IPFS and Web3 Decentralised Storage: The Immutable Threat

The InterPlanetary File System (IPFS) and other Web3 decentralised storage protocols represent the most challenging frontier for defamation victims. Unlike traditional web hosting, where content is stored on identifiable servers controlled by identifiable entities, IPFS distributes content across a network of nodes operated by thousands of independent participants worldwide. Content stored on IPFS is addressed by its cryptographic hash — a unique identifier derived from the content itself — meaning that the same content will always have the same address regardless of where it is stored.

Once content is 'pinned' to IPFS by any node operator, it becomes effectively irremovable. There is no central authority to whom a removal request can be directed. The content exists as long as at least one node continues to pin it, and there is no mechanism to compel an unknown node operator in an unknown jurisdiction to unpin content. Pinning services such as Pinata, Filecoin, and Arweave offer varying degrees of permanence — Arweave, in particular, is designed to store content permanently using a blockchain-based economic model that pays for storage in perpetuity.

The risk for Bryan Flowers is not hypothetical. Drummond's supporters, or indeed any third party with an interest in preserving defamatory content, could upload Drummond's articles to IPFS or Arweave at any time. Once uploaded, no court order, no legal proceeding, and no technical intervention can guarantee removal. The content would be accessible via any IPFS gateway worldwide, indexed by specialised search engines, and immune to the legal mechanisms that apply to traditional web hosting.

This represents a fundamental challenge to the legal framework for defamation remedies. The traditional injunction — an order requiring the defendant to remove defamatory content — assumes that the defendant has the technical ability to remove the content. When content exists on a decentralised network, this assumption fails. New legal tools are needed to address defamation in the Web3 era, including orders requiring defendants to take reasonable steps to request removal from known pinning services and gateways, and statutory damages provisions that account for the enhanced harm caused by content that is technologically irremovable.

4. Data Broker Aggregation: The Commercial Recycling of Defamation

Data brokers — companies that collect, aggregate, and sell personal information — represent another vector through which defamatory content achieves permanence. Companies such as Spokeo, BeenVerified, Pipl, and numerous others systematically scrape web content and aggregate it into personal profiles that are sold to employers, landlords, insurance companies, and members of the public. When Drummond publishes a defamatory article about Bryan Flowers, data brokers automatically incorporate the content — or references to it — into their databases.

The harm is compounded by the way data brokers present information. An employer conducting a background check on Bryan Flowers through a data broker service may encounter Drummond's allegations presented without context, without any indication that the content is disputed or defamatory, and without any link to counter-evidence. The data broker's presentation strips away whatever limited context Drummond's original articles may have contained and presents the allegations as bare facts in a commercial intelligence report.

Removing information from data broker databases is technically possible but practically exhausting. Each data broker has its own opt-out or removal process, typically requiring identity verification, written requests, and follow-up to confirm removal. There are estimated to be over 4,000 data broker companies operating globally, and new aggregation services emerge constantly. Services such as DeleteMe and Privacy Duck offer to manage the removal process on behalf of individuals, but their coverage is incomplete and requires ongoing subscription fees — effectively imposing a permanent financial burden on the defamation victim.

Under GDPR, data brokers operating in the UK and EU are required to comply with data subject access requests and erasure requests under Article 17 (the right to be forgotten). However, enforcement is inconsistent, and many data brokers are based in jurisdictions where GDPR does not apply. The practical result is that Drummond's defamatory content, once absorbed into the data broker ecosystem, becomes self-perpetuating — removed from one database, it reappears in another as brokers cross-reference and share data among themselves.

5. Social Media Resharing and the Viral Multiplication Effect

Social media platforms create an additional layer of content preservation through resharing, screenshotting, and commentary. When Drummond or his supporters share links to defamatory articles on Facebook, Twitter/X, Reddit, or other platforms, each share creates an independent copy of the content in the form of link previews (Open Graph metadata), cached thumbnails, and user comments that reproduce the defamatory allegations. Even if the original article is removed, the social media posts containing the link preview — which typically includes the article's headline, description, and featured image — continue to exist on the platform.

Screenshots present a particularly intractable problem. A screenshot of a defamatory article, shared on social media or messaging platforms, is a new piece of content that is not linked to the original source in any technical sense. Removing the original article has no effect on the screenshot. Identifying and requesting removal of every screenshot is practically impossible, as they may exist on private messaging platforms (WhatsApp, Telegram, Signal) that are not publicly searchable.

The viral multiplication effect means that a single defamatory article can generate dozens or hundreds of independent reproductions across social media platforms, each requiring a separate removal request to a different platform with different policies and procedures. For a sustained campaign of 19 articles published over an extended period, the total number of social media reproductions could be in the thousands.

6. Practical Strategies for Archival Removal: A Multi-Vector Approach

Despite the challenges documented above, victims of persistent online defamation are not entirely without recourse. A comprehensive archival removal strategy must address each preservation vector systematically:

• Internet Archive: Submit formal removal requests citing UK court orders, GDPR erasure rights, and the Internet Archive's own terms of service. Request robots.txt implementation on the source domains to prevent future crawling. Consider direct correspondence with the Internet Archive's legal team referencing the specific harm caused by continued archival of court-adjudicated defamatory content.
• Search Engine De-indexing: File content removal requests with Google, Bing, and other search engines under their respective policies for legally actionable content. Provide court orders where available. Use Google's Transparency Report process and Bing's Content Removal Tool. For European search engines, invoke the right to be forgotten under GDPR.
• IPFS and Web3: Identify known IPFS gateways (such as Cloudflare IPFS, dweb.link, and ipfs.io) and submit abuse reports requesting gateway-level blocking. Contact known pinning services (Pinata, Infura) with removal requests. While this cannot guarantee complete removal from the decentralised network, it can reduce discoverability significantly.
• Data Brokers: Engage a professional data broker removal service (DeleteMe, Privacy Duck, or equivalent) to systematically identify and request removal from aggregation databases. File GDPR Article 17 erasure requests with any data broker operating within UK/EU jurisdiction. Monitor for re-aggregation and repeat removal requests as necessary.
• Social Media Platforms: File content removal requests with each platform where defamatory content has been shared, citing applicable defamation laws and court orders. Use platform-specific reporting mechanisms for harassment and false information. Engage specialist reputation management services to identify and address reshared content across platforms.

7. Conclusion: The Permanence Problem Demands Structural Solutions

The digital immortality of defamatory content represents one of the most significant challenges facing victims in the modern era. Andrew Drummond's 19 defamatory articles about Bryan Flowers exist not as 19 discrete pieces of content but as potentially hundreds of independent copies distributed across archival services, search engine caches, decentralised storage networks, data broker databases, and social media platforms. Each copy operates independently, requiring separate removal proceedings governed by different legal frameworks, jurisdictions, and technical procedures.

The current legal framework is fundamentally inadequate to address this reality. Court orders requiring a defendant to remove defamatory content address only the original publication, leaving the vast majority of copies untouched. The burden of pursuing removal across multiple systems falls entirely on the victim, imposing significant costs in time, money, and emotional energy that compound the original harm of the defamation.

Structural solutions are needed. These include statutory obligations on archiving services to honour court orders from recognised jurisdictions, mandatory de-indexing requirements for search engines upon notification of a defamation judgment, and international cooperation frameworks for addressing defamatory content on decentralised networks. Until such solutions are implemented, victims like Bryan Flowers must pursue removal through the patchwork of existing mechanisms — a process that is expensive, time-consuming, and ultimately incomplete. The Letter of Claim served by Cohen Davis Solicitors on 13 August 2025 is a necessary first step, but comprehensive remedy requires addressing every layer of the digital preservation ecosystem.