This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
SendShield Files
Zero-Knowledge file send & request portal for teams
SendShield Files lets you securely send and request sensitive files. Send via encrypted links with optional passphrases, or use the request portal to let clients upload without passwords—perfect for lawyers, HR, and accountants. Files are encrypted in-browser with AES-256-GCM via WebCrypto API. The key stays after the # in the URL and never reaches our servers. The code is public at github.com/SendShield-Files/crypto. Publishing the repository is not an audit.
Hi Product Hunt! 👋 I’m Pyae Phyo Maung, the builder behind SendShield Files.
I built this to handle both sides of sharing sensitive documents: sending them securely, and requesting them without friction.
While sending files via encrypted links is essential, the part I actually use every day is the request portal: ask for a PDF, limit the formats, set an expiry, and skip sharing a password. Encryption is what makes that ask safe.
Everything is encrypted with AES-256-GCM via the WebCrypto API, in the browser, before upload. Because the decryption key stays in the URL fragment (#key=...), it never reaches our servers. We only store ciphertext that we cannot open.
To keep things transparent, our crypto implementation is public on GitHub, and we've published an in-depth Security Architecture Whitepaper on our site.
I’d love to hear your feedback, use cases, or answer any technical questions! Let me know what you think. 👇
No comment highlights available yet. Please check back later!
About SendShield Files on Product Hunt
“Zero-Knowledge file send & request portal for teams”
SendShield Files was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #158 on the daily leaderboard. SendShield Files lets you securely send and request sensitive files. Send via encrypted links with optional passphrases, or use the request portal to let clients upload without passwords—perfect for lawyers, HR, and accountants. Files are encrypted in-browser with AES-256-GCM via WebCrypto API. The key stays after the # in the URL and never reaches our servers. The code is public at github.com/SendShield-Files/crypto. Publishing the repository is not an audit.
SendShield Files was featured in Productivity (663.3k followers), Privacy (11.4k followers) and Legal (6.3k followers) on Product Hunt. Together, these topics include over 183.4k products, making this a competitive space to launch in.
Who hunted SendShield Files?
SendShield Files was hunted by Pyae Phyo Maung. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how SendShield Files stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Pyae Phyo Maung
Hi Product Hunt! 👋 I’m Pyae Phyo Maung, the builder behind SendShield Files.
I built this to handle both sides of sharing sensitive documents: sending them securely, and requesting them without friction.
While sending files via encrypted links is essential, the part I actually use every day is the request portal: ask for a PDF, limit the formats, set an expiry, and skip sharing a password. Encryption is what makes that ask safe.
Everything is encrypted with AES-256-GCM via the WebCrypto API, in the browser, before upload. Because the decryption key stays in the URL fragment (#key=...), it never reaches our servers. We only store ciphertext that we cannot open.
To keep things transparent, our crypto implementation is public on GitHub, and we've published an in-depth Security Architecture Whitepaper on our site.
I’d love to hear your feedback, use cases, or answer any technical questions! Let me know what you think. 👇