# 🔐 E2EE Adoption Threat Model (Fortunately Unfortunately Forest)

**URL:** <https://threatmodelingconnect.discourse.group/t/e2ee-adoption-threat-model-fortunately-unfortunately-forest/1175>\
**Category:** The Threat Gazette\
**Created:** [September 23, 2025, 4:15pm UTC](https://threatmodelingconnect.discourse.group/t/e2ee-adoption-threat-model-fortunately-unfortunately-forest/1175 "2025-09-23T16:15:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hewerlin](https://sea2.discourse-cdn.com/flex002/user_avatar/threatmodelingconnect.discourse.group/hewerlin/32/67_2.png) [@hewerlin](https://threatmodelingconnect.discourse.group/u/hewerlin)\
**Post date:** [September 23, 2025, 4:15pm UTC](https://threatmodelingconnect.discourse.group/t/e2ee-adoption-threat-model-fortunately-unfortunately-forest/1175/1 "2025-09-23T16:15:36Z")

</div>

Ever seen Fortunately Unfortunately Forest in action?

🔐 End-to-end encryption (E2EE) is known for it’s outstanding confidentiality and privacy properties. So why do so little vendors build E2EE solutions? Can we provide solutions for their challenges?

See the threat model:

> **[Threat Modeling of E2EE Adoption](https://threat-modeling.net/e2ee-adoption-threat-model/)**
>
> Solutions for challenges vendors face when adopting End-to-End Encryption

Feedback welcome! Contributions accepted!