---
title: "Comment by Mark Reeves on \"Why Your QR Code Generator is a Privacy Risk (And the Client-Side Alternative)\" | Hashnode"
description: "qr codes are the sneakiest data leak - people encode wifi passwords and payment links into random generators without thinking. same reason we built swapfile.liv"
url: "https://hashnode.com/posts/why-your-qr-code-generator-is-a-privacy-risk/6aae693ebd99f19f6aaef300/comment/6ababa86370accef6c06906e"
---

[Discussion](https://hashnode.com/posts/why-your-qr-code-generator-is-a-privacy-risk/6aae693ebd99f19f6aaef300)

Comment [Why Your QR Code Generator is a Privacy Risk (And the Client-Side Alternative)](https://hashnode.com/posts/why-your-qr-code-generator-is-a-privacy-risk/6aae693ebd99f19f6aaef300)

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

[Sep 28](https://hashnode.com/posts/why-your-qr-code-generator-is-a-privacy-risk/6aae693ebd99f19f6aaef300/comment/6ababa86370accef6c06906e)

qr codes are the sneakiest data leak - people encode wifi passwords and payment links into random generators without thinking. same reason we built swapfile.live fully client side for file conversion: if the data never leaves the tab there is nothing to log. client-side rendering should be the default for anything personal
