Defensible Deletion: What Delete Means for Vendor Files

Privacy & Compliance

Defensible Deletion: What Delete Means for Vendor Files

Defensible deletion is the practice of removing records under a documented policy and keeping evidence that the removal was complete, timely and consistent. When a vendor holds your file, "delete" usually removes only the visible copy, so you need written terms and proof for backups, logs and derived data. This article walks through what to ask, what to record and how document tools such as HiDocument, which analyzes PDFs, Word files and images, fit into the process.

What does "delete" actually mean when a vendor holds your file?

It depends on the system, and the button label rarely tells you which meaning applies. A delete action can hide a file from your account, mark it for later removal, erase it from primary storage, or ultimately purge it from every backup. Each of those is a different promise, and only the last one ends your exposure.

NIST Special Publication 800-88, the media sanitization guideline, separates three outcomes: clear, purge and destroy. Those terms were written for physical media, but the distinction carries over to cloud files: a record can be made inaccessible without being unrecoverable.

Deletion levelWhat happensTypical recovery risk
Hidden (soft delete)File disappears from your view but stays in storage with a flagHigh: the vendor or an attacker with access can still read it
Primary store removalFile is erased from live storageMedium: copies may remain in backups and caches
Backup expiryBackup sets containing the file age out on a scheduleLow, but only after the full backup cycle ends
Cryptographic erasureThe encryption key is destroyed, so remaining ciphertext is unreadableLow, if keys were truly unique to your data
Derived-data removalExtracted text, embeddings, thumbnails and search indexes are purgedOften overlooked, so ask about it explicitly

The practical point: a deletion is complete only when the slowest layer in that table has finished. Ask the vendor for that date, not the date you clicked the button.

What makes a deletion defensible?

A deletion is defensible when you can show it followed a rule you adopted before anyone asked for the records. Courts, regulators and auditors rarely object to deletion itself. They object to deletion that looks selective, late or undocumented.

Five elements carry most of the weight:

  • A written schedule. Each record type has a retention period and a trigger, such as contract end date or last customer activity. Our guide to building a document retention schedule covers how to set those periods.
  • A consistent process. Deletion runs on a calendar or an event, not whenever someone feels like clearing space.
  • A legal hold override. When litigation or an investigation is reasonably foreseeable, scheduled deletion stops for the affected records until counsel releases them.
  • Scope that includes vendors. The policy names the third parties that hold copies and how each one is instructed to delete.
  • Evidence. A log entry, vendor confirmation or certificate that shows what was deleted, when and by whom.

If you skip the last item, you have a policy but not a defense. A schedule nobody can prove was followed is hard to distinguish from no schedule at all.

Where do copies of a document hide after you delete it?

Copies hide in any place the document was processed, shared or backed up. The original upload is usually the easiest copy to remove and the least likely to be the only one.

  • Backups and snapshots that retain data for a fixed cycle.
  • Caches and content delivery layers that keep a rendered version for speed.
  • Derived data such as extracted text, search indexes, summaries and embeddings.
  • Exports you or colleagues downloaded as PDFs, spreadsheets or reports.
  • Email attachments and chat uploads that sit outside the vendor system entirely.
  • Sub-processors that the vendor uses for storage, OCR or support tooling.

Under the GDPR, a processor must delete or return personal data at the end of the services, at the controller's choice. That obligation appears in Article 28(3)(g) of the official GDPR text. It is a good template for any contract, even where the GDPR does not apply.

How do you verify that a vendor really deleted your documents?

You verify it by asking specific questions in writing and keeping the answers. Marketing pages describe intent; a signed data processing addendum or a written support reply describes commitment. Follow this sequence:

  1. Inventory which vendors hold which document types, and note the retention period for each.
  2. Read the vendor's terms and privacy documentation for deletion timing, backup retention and sub-processors.
  3. Send a written deletion request that names the account, the record set and the deadline.
  4. Ask for written confirmation that covers primary storage, backups and derived data, with the date each layer finishes.
  5. Save the request, the reply and a dated screenshot of the empty account in your records file.
  6. Re-check at the backup expiry date, because a primary-store deletion does not prove the backups are gone.

This is also what auditors expect when they request evidence. Our article on responding to a SOC 2 evidence request shows how deletion logs fit into that package.

How can you reduce what a vendor holds in the first place?

The cheapest deletion is the one you never need to request. Minimizing what you upload shrinks every layer in the table above.

  • Remove personal data before sharing a file. See how to redact PII before sharing documents.
  • Upload the pages you need, not the whole case file.
  • Download your results, store them in your own records system and remove the vendor copy.
  • Prefer vendors that let you delete individual files rather than only closing the entire account.

Retention triggers also depend on facts buried in contracts, such as termination dates, notice periods and data return clauses. Pulling those out by hand across dozens of agreements is slow. HiDocument can extract dates and key terms from contracts and run up to ten files at once in bulk mode on Pro, which gives you a starting list of triggers to confirm against the originals.

What if you cannot audit the vendor's backups?

Most small teams cannot, and that is a reasonable objection. You are not expected to inspect another company's infrastructure; you are expected to make a sensible request and document the answer. If a vendor will not state its backup retention period in writing, treat that as a risk and weigh it against the sensitivity of the files.

For highly sensitive documents, the safer choice may be to avoid uploading them at all, or to redact them first. Nothing here is legal advice. HiDocument is a tool, not counsel, so confirm retention periods and hold obligations with a qualified attorney.

People also ask

Is deleting a file the same as destroying it?

No. Deleting usually removes access or a directory entry, while destruction makes the data unrecoverable. In cloud systems, backups and derived data often outlive the visible delete.

Who is responsible when a vendor fails to delete?

Responsibility depends on your contract and the law that applies. Under the GDPR the controller stays accountable for choosing and instructing its processors, so written instructions matter.

Should deletion stop during a dispute?

Yes, for the records that may be relevant. Suspend scheduled deletion for those records until counsel confirms the hold is lifted.

What is the next step?

Pick one vendor that holds contracts or personal data and run the six-step verification above this week. If you want a faster way to list the dates and clauses that drive your retention periods, create a free HiDocument account. The free tier includes 10 analyses per month with a 5 MB file limit, so you can test it on a few agreements before deciding on Pro pricing.

Frequently Asked Questions

What is defensible deletion?

Defensible deletion is removing records under a written retention policy and keeping evidence that the removal was consistent and complete. It lets you show a regulator, court or auditor that records were deleted for a documented reason rather than selectively. It also requires pausing deletion when a legal hold applies.

Does deleting a file from a cloud tool remove it from backups?

Usually not immediately. Deleting normally removes the file from live storage, while backups keep copies until their retention cycle ends. Ask the vendor in writing how long backups last and whether derived data, such as extracted text or search indexes, is removed on the same schedule.

How do I prove a vendor deleted my documents?

Send a written deletion request and ask for written confirmation covering primary storage, backups and derived data, with a completion date for each. Save the request, the reply and a dated screenshot. Re-check after the backup expiry date, since primary deletion alone does not prove complete removal.

What is the difference between soft delete and hard delete?

A soft delete flags a record as removed but leaves it in storage, so it can be restored or read by someone with access. A hard delete erases the data from live storage. Neither automatically covers backups, caches or copies held by sub-processors.

When should I stop deleting records?

Stop scheduled deletion for any record that may be relevant to litigation, an investigation or an audit once such a matter is reasonably foreseeable. Keep the hold in place until your attorney releases it, then resume the normal schedule and log the date.

Ready to analyze your own documents?

Upload any PDF, Word doc, or image — get 10 types of AI analysis instantly. Free to start, no credit card required.

Try HiDocument Free →

Related Articles