# \[RESOLVED\] Joplin leaks private info despite end-to-end-encryption enabled

**URL:** <https://discourse.joplinapp.org/t/resolved-joplin-leaks-private-info-despite-end-to-end-encryption-enabled/25373>\
**Category:** Features\
**Created:** [25 April 2022 11:14 UTC](https://discourse.joplinapp.org/t/resolved-joplin-leaks-private-info-despite-end-to-end-encryption-enabled/25373 "2022-04-25T11:14:53Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![CalebJohn](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/calebjohn/32/356_2.png) [@CalebJohn](https://discourse.joplinapp.org/u/CalebJohn)\
**Post date:** [25 April 2022 19:27 UTC](https://discourse.joplinapp.org/t/resolved-joplin-leaks-private-info-despite-end-to-end-encryption-enabled/25373/12 "2022-04-25T19:27:10Z")

</div>

> [@aleqx](#):
>
> I for one think enabling it by default brings more benefits than downsides.

You're not the only one. This is a [goal of the project](https://discourse.joplinapp.org/t/where-is-joplin-cloud-hosted/23077/6). There have been changes recently that make the ergonomics of using E2EE nicer, which will maybe tip the scales in favour of E2EE by default.

You're right to point out that the current UX isn't great, whether or not it's enabled by default, it should always be clear to the user. There was an on-boarding addition recently to give the user a more friendly selection of sync targets. Probably a selection about E2EE should be added to that workflow.

---

_[View the full topic](https://discourse.joplinapp.org/t/resolved-joplin-leaks-private-info-despite-end-to-end-encryption-enabled/25373)._