# Technology preview: Sealed sender for Signal

DevFeed: [Technology preview: Sealed sender for Signal](<https://devfeed.tech/articles/technology-preview-sealed-sender-for-signal-1820.md>)

Original publisher: [Read original article](<https://signal.org/blog/sealed-sender/>)

Published: 2018-10-29T00:00:00Z

Content type: release

Language: en

Sources: [Signal Blog](<https://devfeed.tech/sources/signal-blog.md>)

Topics: [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [identity](<https://devfeed.tech/tags/identity.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [spoofing](<https://devfeed.tech/tags/spoofing.md>), [tls](<https://devfeed.tech/tags/tls.md>)

## AI overview

Signal previews sealed sender, a design intended to hide sender metadata from the service while preserving asynchronous delivery, sender verification, and abuse protection. It uses short-lived sender certificates and delivery tokens.

## Source excerpt

In addition to the end-to-end encryption that protects every Signal message, the Signal service is designed to minimize the data that is retained about Signal users. By design, it does not store a record of your contacts, social graph, conversation list, location, user avatar, user profile name, group memberships, group titles, or group avatars. We have been exploring techniques to further reduce the amount of information that is accessible to the service, and the latest beta release includes changes designed to move Signal incrementally closer to the goal of hiding another piece of metadata: who is messaging whom. Read more...