# Does Delta Chat use hidden recipient? **URL:** \ **Category:** Uncategorized\ **Created:** [March 23, 2025, 10:49pm UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651 "2025-03-23T22:49:48Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\ **Post date:** [March 23, 2025, 10:49pm UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/1 "2025-03-23T22:49:49Z")
Does Delta Chat encrypt messages using PGP hidden recipient? In most cases there’s probably not much benefit, but it seems to me that in the case of email address porting, or if Delta Chat ever supports features like [multihoming](https://support.delta.chat/t/the-multihoming-idea/3366) or sealed sender, using hidden recipient could provide a modest privacy improvement. ---
**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\ **Post date:** [March 24, 2025, 2:31am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/2 "2025-03-24T02:31:43Z")
If you mean zeroing out fingerprints, currently they are not zeroed out. This will need to be done when we protect the addresses in the To field. ---
**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\ **Post date:** [March 25, 2025, 3:07am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/3 "2025-03-25T03:07:06Z")
> [@link2xt](#): > > If you mean zeroing out fingerprints, currently they are not zeroed out. I mean hiding/throwing away the key ID of the recipient, which is normally included in the encrypted message. > [@link2xt](#): > > This will need to be done when we protect the addresses in the To field. This sounds like it’s on the roadmap then, which is good to know. Now I’m curious, what do you have planned for protecting addresses in the To field? Anyway it seems to me that hiding/throwing away the key ID could already offer a privacy improvement for people using AEAP, making it more difficult for third parties to link the old and new address. ---
**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\ **Post date:** [March 25, 2025, 3:28am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/4 "2025-03-25T03:28:54Z")
> [@bencan](#): > > I mean hiding/throwing away the key ID of the recipient, which is normally included in the encrypted message. Key IDs are replaced with fingerprints in RFC 9580 where possible. But yes, key IDs are currently not zeroed out. > [@bencan](#): > > This sounds like it’s on the roadmap then, which is good to know. Now I’m curious, what do you have planned for protecting addresses in the To field? There is a WIP PR at [feat: hide the Date and To headers in encrypted messages by link2xt · Pull Request #6649 · chatmail/core · GitHub](https://github.com/chatmail/core/pull/6649) Some fixes that need to be done before this is possible have been merged, waiting for them to get into releases and for users to upgrade. Also there are some unresolved problems with chat assignment for large messages, this is postponed until [WIP: PGP-contacts by link2xt · Pull Request #6683 · chatmail/core · GitHub](https://github.com/chatmail/core/pull/6683) We also have a flag to protect Autocrypt header which is not enabled yet. > [@bencan](#): > > Anyway it seems to me that hiding/throwing away the key ID could already offer a privacy improvement for people using AEAP, making it more difficult for third parties to link the old and new address. This is not very useful by itself if Autocrypt header is not hidden. ---
**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\ **Post date:** [March 25, 2025, 4:00am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/5 "2025-03-25T04:00:41Z")
Thanks for this information! ---
**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\ **Post date:** [March 29, 2025, 4:14pm UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/6 "2025-03-29T16:14:37Z")
I filed an issue at [Use anonymous recipient for generated packets · Issue #507 · rpgp/rpgp · GitHub](https://github.com/rpgp/rpgp/issues/507) because it does not seem to be supported in rPGP yet and we will need it. ---
**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\ **Post date:** [March 30, 2025, 12:26am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/7 "2025-03-30T00:26:33Z")
Great to know this is being looked into and taken care of! I’m still trying to understand conceptually how hiding the To header will work. How will the email server know where to send a message without the To header/address? ---
**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\ **Post date:** [March 30, 2025, 12:53am UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/8 "2025-03-30T00:53:40Z")
> [@bencan](#): > > I’m still trying to understand conceptually how hiding the To header will work. How will the email server know where to send a message without the To header/address? There is a list of recipients in the “envelope” (`RCPT TO` commands in SMTP protocol). `To:` header that goes into IMF message plays no real role, you can put anything there. This is how Bcc works, you put the recepients into `RCPT TO` but not in the `To:` field. Basically we can just Bcc everyone. ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [October 6, 2026, 3:19pm UTC](https://forum.delta.chat/t/does-delta-chat-use-hidden-recipient/3651/9 "2026-10-06T15:19:50Z")