[Rayid]

Totally understand the concern — I’ve thought a lot about that.

I'm not encouraging illegal use; it's designed for privacy-conscious developers, teams, and individuals who want simple, disposable file transfers. And like with any tool, it depends on how users choose to use it.

That said, I'm keeping an eye on best practices (and legality) around hosting this kind of service. Appreciate you bringing it up!

[cedws]

The minutiae don't matter, if they think your service is serving data it shouldn't be, encrypted or not they will bust down your door.

[Rayid]

At the moment, this website is still in its early stages, but I'm fully committed to finding ways to prevent any unethical use of the platform. It's something I’ll continue working on as I develop and improve it. Thanks for the concern!

[7bit]

> it depends on how users choose to use it.

Protect yourself as best as you can. The worst that could happen is if this is used for CSAM, and then it's over.

[Rayid]

Well, since all files are encrypted on the client side, I can’t actually read or access the contents of the files being uploaded. That means I can't know what’s being shared. However, I’ll be adding clear policies that will allow me to delete any files that appear to be used unethically or in violation of the guidelines.

[rad_gruchalski]

Since you have access to raw data as it is being encrypted, you can know what material is being uploaded. You could in theory maybe claim that data is encrypted on the client but it is your client served from your domain.

[Rayid]

Right, since the client is served from my domain, trust in the code is essential. Encryption happens in-browser, and nothing is logged or intercepted, but to back that up, I’m planning to open-source the website in the future so anyone can verify exactly what’s going on.