Zwisper
The short version
| Question | Zero-width steganography | Encryption |
|---|---|---|
| What does it change? | How a private payload is carried alongside visible text. | How the private payload looks to someone without the secret. |
| Can someone detect that data may be present? | Possibly. Invisible characters can be inspected or removed. | Yes, encrypted data is normally obvious as protected data. |
| Can someone read the private contents without the key or password? | Not necessarily protected by steganography alone. | Not when the encryption and secret are used correctly. |
| Can it guarantee a website will carry the message intact? | No. Editors and services may strip or transform characters. | No. Encryption protects contents, not delivery or compatibility. |
What zero-width steganography adds
Steganography is about placement. In Zwisper, an encrypted note is represented by non-rendering Unicode characters placed with an ordinary cover message. A person reading the message normally sees the cover words, not an added visible block of encoded text. This can make a short private note practical in a conversation where the visible message is still useful.
It does not mean the data is undetectable. A website can process the characters, an editor can remove them, and a recipient can inspect the original text. That is why Zwisper describes the feature as private notes in ordinary messages, not as a way to make a message disappear from scrutiny.
What encryption adds
Encryption protects the content of the private note. Zwisper encrypts that note on your device using a password or contact-based keys before it encodes the note into the text. The person opening it needs the correct secret. Its authenticated encryption also detects changes to the protected note instead of silently returning altered text.
With a saved contact’s agreed shared key, a note can be recognised as belonging to that contact and marked verified. That is a useful distinction: a note that opens is not automatically a note from the person you expected unless the relevant contact check succeeds.
Encryption does not hide the visible cover message, stop a recipient from sharing what they open, secure a compromised device, or prevent a website from learning the normal metadata involved in sending a message. Keep the private note proportionate to those realities.
Why Zwisper uses both
By combining the two, Zwisper gives a visible message and a separately protected note. The visible message remains understandable to everyone who receives it. The encrypted note is available to the intended recipient who has the needed password or saved contact. The two layers are complementary:
- Steganography keeps the private payload in the text itself rather than as a separate visible attachment.
- Encryption protects the contents of that payload against someone who only has the message.
- Validation and contact checks help Zwisper reject malformed data and recognise notes from an expected saved contact.
Choose a tool based on the risk
Zwisper fits a short, private addendum between people who trust each other and can test the route. If the entire conversation is sensitive, if reliable message preservation matters, or if you need a stronger communication workflow, choose a dedicated end-to-end encrypted messenger instead. If a website, employer, school, or community has rules about the message content, follow those rules rather than attempting to conceal information through formatting.
For any new site, test a harmless note end to end. Zwisper can warn when an editor strips its carrier characters, but only the received message demonstrates whether the route preserved them.