| ▲ | DmitryDolgopolo a day ago |
| - Yep. You can read our privacy policy here: 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. |
|
| ▲ | devilkin a day ago | parent [-] |
| At that point calling it end-to-end encrypted is not true. |
| |
| ▲ | j4hdufd8 a day ago | parent | next [-] | | Can you elaborate where you think it stops being encrypted? | |
| ▲ | warkdarrior a day ago | parent | prev [-] | | What 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 a day ago | parent [-] | | In 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 |
|
|
