---
title: "Comment by Mark Reeves on \"Why Your PDF Workflow Is Leaking Sensitive Data (And How to Fix It)\" | Hashnode"
description: "millions dragging sensitive pdfs into upload-first tools every week is the stat that should scare people - most have no idea the file persists on infrastructure"
url: "https://hashnode.com/posts/why-your-pdf-workflow-is-leaking-sensitive-data-and-how-to-fix-it/6a09a69b3104e2aff088868b/comment/6abba08dd36930a07a1750b5"
---

[Discussion](https://hashnode.com/posts/why-your-pdf-workflow-is-leaking-sensitive-data-and-how-to-fix-it/6a09a69b3104e2aff088868b)

Comment [Why Your PDF Workflow Is Leaking Sensitive Data (And How to Fix It)](https://hashnode.com/posts/why-your-pdf-workflow-is-leaking-sensitive-data-and-how-to-fix-it/6a09a69b3104e2aff088868b)

[Mark Reeves](https://hashnode.com/@mreevestools)

[Sep 29](https://hashnode.com/posts/why-your-pdf-workflow-is-leaking-sensitive-data-and-how-to-fix-it/6a09a69b3104e2aff088868b/comment/6abba08dd36930a07a1750b5)

millions dragging sensitive pdfs into upload-first tools every week is the stat that should scare people - most have no idea the file persists on infrastructure they will never see. the fix framing matters too: telling people to check the network tab themselves beats any privacy policy. what do you find convinces skeptics fastest, the technical demo or the breach stories?
