# show end-to-end encryption state of chat **URL:** \ **Category:** Feature Proposal\ **Created:** [February 4, 2019, 11:16am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230 "2019-02-04T11:16:40Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Der\_mor](https://support.delta.chat/letter_avatar_proxy/v4/letter/d/7c8e57/32.png) [@Der\_mor](https://support.delta.chat/u/Der_mor)\ **Post date:** [February 4, 2019, 11:16am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/1 "2019-02-04T11:16:40Z")
when you want to be sure end-to-end crypto is used, you have to manually check if you reply to a message with a lock symbol. else your message will get sent unencrypted. there should be a notification, when end-to-end crypto is downgraded to disabled. also a force encryption option may be useful: [#246](https://github.com/deltachat/deltachat-android/issues/246). similar to [#212](https://github.com/deltachat/deltachat-android/issues/212). (This proposal has been moved from the [issue tracker](https://github.com/deltachat/deltachat-android/issues/212)) ---
**Author:** ![adbenitez](https://support.delta.chat/user_avatar/support.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://support.delta.chat/u/adbenitez)\ **Post date:** [February 4, 2019, 2:27pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/2 "2019-02-04T14:27:00Z")
I also think there should be a more visible way to at least warn the user the message will be sent unencrypted (ex. when peer unexpectedly disabled encryption), users may expose sensitive information unintentionally!!! ---
**Author:** ![abrahamperez](https://support.delta.chat/letter_avatar_proxy/v4/letter/a/e19b73/32.png) [@abrahamperez](https://support.delta.chat/u/abrahamperez)\ **Post date:** [February 4, 2019, 4:17pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/3 "2019-02-04T16:17:25Z")
this is a great idea!!! and i agree on force encryption. ---
**Author:** ![Hocuri](https://support.delta.chat/user_avatar/support.delta.chat/hocuri/32/25_2.png) [@Hocuri](https://support.delta.chat/u/Hocuri)\ **Post date:** [February 5, 2019, 7:39am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/4 "2019-02-05T07:39:20Z")
What about this: one red point if the next message will be sent unencrypted two orange points if it is end-to-end encrypted three yellow points if it is end-to-end encrypted and the chat partner scanned my (static) qr code four green points if I scanned my chat partner’s qr code (or later if they scanned my dynamic qr code, this is not implemented currently; @testbird’s proposal 😉) Show it somewhere atop of the screen Or would you prefer a simple green lock/red crossed-out lock? ---
**Author:** ![testbird](https://support.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://support.delta.chat/u/testbird)\ **Post date:** [April 13, 2019, 12:59pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/5 "2019-04-13T12:59:01Z")
Any indicator outside of the text entry field, and especially on the send button, has the drawback that it may only come to the users attention _after_ writing the text, if at all. Nevertheless, (such) a clear, explicit indicator is still necessary. `However, a subject indication in the editor-` like explained [here](https://support.delta.chat/t/discussion-make-dc-a-replacement-for-muas/253/12) may also serve to draw attention to the fact that the plain email sending mode is going to be used. ---
**Author:** ![testbird](https://support.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://support.delta.chat/u/testbird)\ **Post date:** [April 13, 2019, 1:32pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/6 "2019-04-13T13:32:57Z")
For consitency, when composing a to-get-encrypted email-chat message, the editor may show the current `🔒-` encryption icon with the background and the dash “`-`”, which would also hint to the (automatic) subject line that gets used. An alternatively icon may be a `🔑-` key icon. This subject line feature might then be even the only encryption state indicator that is necessary. ---
**Author:** ![Simon](https://support.delta.chat/user_avatar/support.delta.chat/simon/32/287_2.png) [@Simon](https://support.delta.chat/u/Simon)\ **Post date:** [November 6, 2019, 4:44pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/7 "2019-11-06T16:44:17Z")
My thoughts on this: ## Indicator whether the next message will be encypted. Needs to come from the core and get live updates, so we can be sure it **never sends unencrypted when displaying otherwise**. I suggest a small ingicator that has an info button or can otherwise be exapnded to show the reason. ##### Encrypted (verified chats) _All messages in verified chats must be encrypted_ ##### Encrypted _Has key of [user] and will send encrypted. Got the key verified contact / directly / gossiped from []_ ##### Unencrypted (no reply yet) _DC doesn’t have the key of this person yet, your messages will be unencrypted until they reply._ ##### Unencrypted (reply, but no key) _Looks like your chatpartner hasn’t setup encryption._ _Ask them to do so and tell them about autocrypt and deltachat, if they use plain email._ ##### Unencrypted (error) _Can’t send encrypted: Key invalid [reason]_ ---
**Author:** ![Aviva](https://support.delta.chat/user_avatar/support.delta.chat/aviva/32/380_2.png) [@Aviva](https://support.delta.chat/u/Aviva)\ **Post date:** [November 7, 2019, 12:36am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/8 "2019-11-07T00:36:40Z")
We need the same idea on IOs version. We can open the ‘info’ of message and reaad the state but would be better to see a color or lock. ---
**Author:** ![Simon](https://support.delta.chat/user_avatar/support.delta.chat/simon/32/287_2.png) [@Simon](https://support.delta.chat/u/Simon)\ **Post date:** [November 7, 2019, 2:54pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/9 "2019-11-07T14:54:57Z")
This Feature Proposal is about all platforms so no worries there. ---
**Author:** ![jan](https://support.delta.chat/letter_avatar_proxy/v4/letter/j/ce7236/32.png) [@jan](https://support.delta.chat/u/jan)\ **Post date:** [December 1, 2019, 12:48pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/10 "2019-12-01T12:48:28Z")
Great idea! I can add my somewhat disappointing “very first time user” experience: - Installed delta chat - Added a friend, sent a message - Checked IMAP server what happens behind the scenes –\> Found a clear text message in the deltachat IMAP folder. Me as a developers knows why it was not encrypted. But a clear warning that “this user is not yet using Delta Chat, your message will NOT BE ENCRYPTED” would have added a lot of trust for me. In the end it is only about managing the expectations for the user. Hope this helps to improve the UX. DeltaChat is an awesome idea! Keep going! ---
**Author:** ![adbenitez](https://support.delta.chat/user_avatar/support.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://support.delta.chat/u/adbenitez)\ **Post date:** [January 14, 2020, 7:41pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/11 "2020-01-14T19:41:02Z")
for example, if the message will be sent unencrypted, the send button could be something like: ![android_send_insecure](https://support.delta.chat/uploads/default/original/1X/83969960afdb92e1efb34449952684325bef7364.png) ---
**Author:** ![lps](https://support.delta.chat/letter_avatar_proxy/v4/letter/l/8797f3/32.png) [@lps](https://support.delta.chat/u/lps)\ **Post date:** [January 30, 2020, 11:26pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/12 "2020-01-30T23:26:51Z")
this makes me wonder, if I can see my chats in the DELTA CHAT folder on my email provider is that only for the unencrypted chats? Will they appear scrambled on my email server if they’re encrypted? I’m worried about using this with google services that are scanned. ---
**Author:** ![Der\_mor](https://support.delta.chat/letter_avatar_proxy/v4/letter/d/7c8e57/32.png) [@Der\_mor](https://support.delta.chat/u/Der_mor)\ **Post date:** [June 2, 2020, 7:37am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/13 "2020-06-02T07:37:58Z")
@lps When we can encrypt it, your Mail Server cannot read the contents. The Mail Server can always see the transport metadata (From, To). We use a blinded Subject when we can encrypt so there is nothing to be seen. ---
**Author:** ![Simon](https://support.delta.chat/user_avatar/support.delta.chat/simon/32/287_2.png) [@Simon](https://support.delta.chat/u/Simon)\ **Post date:** [September 13, 2020, 12:02am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/14 "2020-09-13T00:02:16Z")
an idea I had recently when thinking about it: (its also about forcing a state, but for this feature we could just display it read-only). Also sorry that this isn’t more concrete, its just an idea dump after all: as indicator symbol in the bottom corner, on click open a full-screen popup with the following options: > **Set encryption mode for chat** > > - Oportunistic, focus on deliverability > - Force Encyption (is disabled until first handshake took place) > - Disable Encryption (warning) Also this screen could be reused for the global settings (minus the force encryption, because that would be confusing as it always requires a key that might not be available) ---
**Author:** ![Hocuri](https://support.delta.chat/user_avatar/support.delta.chat/hocuri/32/25_2.png) [@Hocuri](https://support.delta.chat/u/Hocuri)\ **Post date:** [September 13, 2020, 6:09pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/15 "2020-09-13T18:09:44Z")
> [@Simon](#): > > **Set encryption mode for chat** > > - Oportunistic, focus on deliverability > - Force Encyption (is disabled until first handshake took place) > - Disable Encryption (warning) +1 👍 just that “automatic” is probably better than “opportunistic” because this is clearer to the user. The indicator could be threema-like 🔴 no encryption 🟡🟡 encryption, unverified 🟢🟢🟢 verified (or we just take a lock) ---
**Author:** ![Hocuri](https://support.delta.chat/user_avatar/support.delta.chat/hocuri/32/25_2.png) [@Hocuri](https://support.delta.chat/u/Hocuri)\ **Post date:** [September 13, 2020, 6:44pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/16 "2020-09-13T18:44:50Z")
What might be a little tricky is, where do we put the symbol? The bottom already is pretty full on mobile phones. Threema puts the dot indicator to the subtitle where we show the email address. Signal just shows a very small lock on the send button. Options I see (can be combined): - show three dots (threema-like) before or behind the subtitle. Hard to make them clickable because they are small but we can show them again in the chat details view, where we show explanation and the options @Simon proposed when they are clicked. Might also not look as nice. ![Screenshot_20200913-204541](https://support.delta.chat/uploads/default/original/1X/e50481c51a04cf9e07b967696081cc0efb247e9b.png) - do what Signal does, show a small lock on the send button when sending encrypted. Looks clean but can’t be made clickable at all because this already is the send button. ![Screenshot_20200913-204503](https://support.delta.chat/uploads/default/original/1X/eaadc880837ea6dc5295260d7ac4bbb7acf67b0b.png) - somehow show a lock over the send button (in the bottom right corner of the messages view) as soon as the user starts to type. Can be clicked, as @Simon proposed. ![deltachat-2020-09-13-204903](https://support.delta.chat/uploads/default/original/1X/f7fd69f9eff74a0f713b098da301f33c3bd3bc4b.jpeg) ---
**Author:** ![k89a265r8975L](https://support.delta.chat/letter_avatar_proxy/v4/letter/k/ce73a5/32.png) [@k89a265r8975L](https://support.delta.chat/u/k89a265r8975L)\ **Post date:** [September 20, 2020, 8:47am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/17 "2020-09-20T08:47:52Z")
have a look in my [Changed Setup for email@xyz.xx](https://support.delta.chat/t/changed-setup-for-email-xyz-xx/1193). I also had the problem, that the encryption broke. ---
**Author:** ![adbenitez](https://support.delta.chat/user_avatar/support.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://support.delta.chat/u/adbenitez)\ **Post date:** [October 13, 2020, 9:26am UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/18 "2020-10-13T09:26:59Z")
being able to force encryption in some chats while forcing plain in another is something I miss a lot every day ---
**Author:** ![link2xt](https://support.delta.chat/user_avatar/support.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://support.delta.chat/u/link2xt)\ **Post date:** [April 10, 2021, 4:49pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/19 "2021-04-10T16:49:16Z")
> [@Hocuri](#): > > do what Signal does, show a small lock on the send button when sending encrypted. Looks clean but can’t be made clickable at all because this already is the send button. Signal shows a menu allowing to choose “Insecure SMS” on long tap. ---
**Author:** ![r10s](https://support.delta.chat/user_avatar/support.delta.chat/r10s/32/1513_2.png) [@r10s](https://support.delta.chat/u/r10s)\ **Post date:** [February 10, 2026, 4:59pm UTC](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230/20 "2026-02-10T16:59:42Z")
ftr, meanwhile all groups and messages are guaranteed end-to-end-encrypted _by default_, a special icon to indicate that state is no longer needed > **[Delta Chat: Delta Chat V2: a major security upgrade, beautified contact...](https://delta.chat/en/2025-08-04-encryption-v2)** > > With Delta Chat Version 2, chats are end-to-end encrypted, always and by default. Previously it was possible that chats without green checkmarks could contain messages without end-to-end encryption... [Next page](https://support.delta.chat/t/show-end-to-end-encryption-state-of-chat/230.md?page=2)