Screenshot Privacy: What Screenshot Controls Can and Cannot Do

End-to-end encryption solves one problem extremely well: nobody between you and the person you are talking to can read the conversation. It does nothing about the person you are talking to. Once a message arrives and is decrypted on their screen, it can be screenshotted, recorded, forwarded or photographed, and the encryption has already done its job.

At VOIDEX we think a private messenger should be honest about that boundary. This article looks at screenshots, screen recording and forwarding as privacy risks, what screenshot controls can do, and where no software can help you.

The weakest link is the screen

Security people often describe encryption as protecting data "in transit" and "at rest". The screen is a third state: data in use. At that moment it is plaintext by design, because a human has to read it.

Everything that leaks at that moment falls outside the reach of cryptography:

• Screenshots, which turn a private message into an image that can be shared anywhere.
• Screen recordings, which can capture a whole conversation, a video call or a view-once photo.
• Forwarding and copying, which move content into chats and platforms the sender never chose.
• A second camera, the oldest method of all: someone photographs one screen with another device.

Most private messages that become public do not escape through a hacked server. They escape because someone who was allowed to see them decided to share them.

Why screenshots are a real privacy risk

A screenshot strips a message of its context and gives it a second life. It can be cropped to change its meaning, shared with an audience the sender never imagined, kept for years, and used as leverage. Screenshots are the raw material of workplace disputes, public shaming, harassment and extortion.

They are also the everyday mechanism of oversharing. Plenty of people screenshot a funny message to send to a friend without thinking of it as a privacy decision at all. That is exactly why controls help: they add a moment of friction and make the sender's expectations visible.

What screenshot controls can do

On some operating systems, an app can ask the system to protect its window from capture.

On Android, an app can mark a window as secure using a flag called FLAG_SECURE. The system then prevents that window from appearing in ordinary screenshots and on non-secure displays, and it is typically hidden in the recent apps view. Several private messengers use this to block screenshots in protected chats.

On desktop systems, applications can request that their windows be excluded from screen capture, which stops many screenshot and screen-sharing tools from recording them.

On iPhone the picture is different. iOS does not give apps a general way to block screenshots. It lets an app learn that a screenshot was taken, and lets it detect when the screen is being captured, for example during a recording or mirroring, so the app can hide sensitive content while that is happening.

In a web browser the options are weaker still. A web page cannot stop the browser or the operating system from taking a screenshot. The most it can do is react to the page losing focus.

So screenshot controls are real, useful and uneven. Their strength depends on the platform the other person is using.

What screenshot controls cannot do

This is the part many products leave out.

1. They cannot stop a second camera. If someone photographs a screen with another phone, no software on the first device can know, let alone prevent it.
2. They cannot stop someone reading and retyping. A message that can be read can be copied by hand.
3. They cannot control a compromised device. Malware or a modified operating system on the recipient's side can capture anything that is displayed.
4. They cannot guarantee a notification. Screenshot alerts depend on the platform, and there are ways around them.
5. They cannot undo the past. A control switched on today does not reach screenshots taken yesterday.

Any product that promises screenshots are "impossible" is overselling. Screenshot controls raise the cost and the effort of capturing a conversation. They do not make it impossible, and they cannot replace judgement about who you trust.

A control is also a signal

There is a second, quieter value to screenshot controls that has nothing to do with enforcement. When a conversation has capture protection switched on, both people know what the other expects. It turns an unspoken assumption into a visible setting.

That matters in practice. Many leaks are not malicious. A colleague shares a message to ask a friend for advice. A group member forwards a photo because it seemed harmless. A visible control reminds everyone in the chat that this particular conversation was meant to stay where it is, and most people respect that when they are told.

It also changes the social cost of breaking it. Capturing a chat that everyone agreed to protect is a deliberate act, and it is understood as one. Friction and clarity will not stop a determined person, but they stop a great many careless ones, which is where most real-world leaks begin.

The other quiet leaks: forwarding and history

Screenshots get the attention, but forwarding and long histories do just as much damage.

A forwarded message leaves the conversation it was written for and loses the sender's control entirely. A long chat history, kept for years on several devices, is a large target if one of those devices is lost, seized or shared.

Two habits address this directly:

• Disappearing messages limit how long content exists at all. They do not stop a determined recipient from capturing a message before it goes, but they shrink the archive that could leak later. We cover them in our disappearing messages guide.
• Deleting for everyone lets a sender remove a message from the conversation on every device, which is useful for a mistake, although it cannot recall a copy someone already made.

How VOIDEX approaches it

VOIDEX Messenger combines strong encryption with controls for what happens after a message arrives.

Conversations are end-to-end encrypted. Direct messages use a hybrid post-quantum key agreement, X25519 with ML-KEM-768, followed by a double ratchet with post-quantum re-keying, so each message has its own key. Groups and private channels use MLS. Keys are created on members' devices, and servers store public keys and ciphertext.

On top of that, VOIDEX offers per-chat screenshot control, so the people in a conversation can set their expectation for that specific chat rather than for the whole app. It also offers disappearing messages, delete for everyone, and editing within 15 minutes, so a typo can be corrected without sending a second message.

And VOIDEX is honest about the limit described above. Screenshot control is a protection against casual capture, not a guarantee against a determined person with a second camera. The public security report explains what VOIDEX protects and what it cannot.

Practical advice

1. Decide who you are really talking to. Encryption protects the channel. Trust decides what the other person does with it.
2. Use screenshot controls for sensitive chats, and treat them as friction, not a lock.
3. Turn on disappearing messages for conversations that do not need to exist forever.
4. Keep the truly sensitive for voice. A call is harder to capture casually than a thread of text, though it can still be recorded.
5. Protect your own devices. A strong passcode and up-to-date software protect your side of every conversation.
6. Be careful what you forward. Every forward is a privacy decision on someone else's behalf.

Honest protection

The best privacy tools are the ones that tell you exactly where they stop. Encryption keeps a conversation sealed from everyone outside it. Screenshot control, disappearing messages and delete for everyone shape what happens inside it. Beyond that, there is a person holding a screen, and no software can fully decide for them.

VOIDEX is built to be precise about all three. Read how VOIDEX Messenger works, or request access to the invite-only platform.

Sources

• Android Developers, WindowManager.LayoutParams FLAG_SECURE: https://developer.android.com/reference/android/view/WindowManager.LayoutParams#FLAG_SECURE
• Apple Developer, UIScreen isCaptured: https://developer.apple.com/documentation/uikit/uiscreen/iscaptured