SealedPacket turns files and messages into portable encrypted .sju packets. Encryption and decryption happen in your browser, so plaintext files and recoverable packet secrets are not uploaded to a server.
Replies
Best
Maker
📌
I built it for people who need to send sensitive files or messages without turning a cloud server into the trusted place where plaintext lives.
The core flow is simple: choose text or a file, encrypt it locally in the browser, download a portable .sju packet, and share that packet through any channel. The recipient opens it with the right secret and access conditions.
The optional account/control-plane layer is for identity, quotas, device approval, audit, and managed access. It is not meant to store plaintext files or recoverable packet secrets.
I’d love feedback from privacy-minded builders, security people, freelancers, and anyone who has had to send sensitive files without wanting another shared-drive workflow.
Report
Maker
Hi I’m launching SealedPacket today.
I built it for people who need to send sensitive files or messages without turning a cloud server into the trusted place where plaintext lives.
The core flow is simple: choose text or a file, encrypt it locally in the browser, download a portable .sju packet, and share that packet through any channel. The recipient opens it with the right secret and access conditions.
The optional account/control-plane layer is for identity, quotas, device approval, audit, and managed access. It is not meant to store plaintext files or recoverable packet secrets.
I’d love feedback from privacy-minded builders, security people, freelancers, and anyone who has had to send sensitive files without wanting another shared-drive workflow.
Replies
Hi I’m launching SealedPacket today.
I built it for people who need to send sensitive files or messages without turning a cloud server into the trusted place where plaintext lives.
The core flow is simple: choose text or a file, encrypt it locally in the browser, download a portable .sju packet, and share that packet through any channel. The recipient opens it with the right secret and access conditions.
The optional account/control-plane layer is for identity, quotas, device approval, audit, and managed access. It is not meant to store plaintext files or recoverable packet secrets.
I’d love feedback from privacy-minded builders, security people, freelancers, and anyone who has had to send sensitive files without wanting another shared-drive workflow.