2 ms·
- Yep. You can read our privacy policy here: https://dimadolgopolovn.notion.site/Amber-Privacy-Policy-2568a89c5295807fb21cf8a4e0ea882a https://dimadolgopolovn.n
by DmitryDolgopolo 1y ago
- Yep. You can read our privacy policy here: https://dimadolgopolovn.notion.site/Amber-Privacy-Policy-2568a89c5295807fb21cf8a4e0ea882a https://dimadolgopolovn.notion.site/Amber-Privacy-Policy-256...
- Check out the demo in the original post.
- We use native API or reverse-engineer a solution depending on the platform. This approach maintains the security standard as high as the original app. Everything is done locally on your computer.
- f4ye 1y agocould you please link to stuff like the demo and the privacy policy on the site? i only found this thread by chance and would have missed it otherwise ^^;
- devilkin 1y agoAt that point calling it end-to-end encrypted is not true.
- warkdarrior 1y agoWhat definition of "end-to-end encrypted" do you refer to, if on-device processing does not qualify? Isn't your device one of the endpoints in E2EE?
- magackame 1y agoIn context of instant messaging E2EE usually means that service providers servers don't ever see the plaintext with messages stored on device. Just the transport encryption is already an expectation for all networking. - Signal: E2EE - Telegram: by default, nah - Discord, nah
- j4hdufd8 1y agoCan you elaborate where you think it stops being encrypted?