Can Someone Screenshot a Private Note?

Why No App Can Truly Block Screenshots

Some apps attempt to disable screenshots using operating system APIs. On Android, for instance, apps can set a flag that prevents the built-in screenshot tool from capturing a window. But this is trivially bypassed with another device's camera, a screen recording tool with root access, or an accessibility service. On desktop operating systems, there is no reliable mechanism at all, any user with access to the screen can capture it.

It is more honest to acknowledge this reality than to offer a false sense of security. Claims of "screenshot-proof" messaging are misleading, and I do not make them.

What SneakNote Does Instead

Rather than attempting to block screenshots, SneakNote focuses on limiting the opportunity for capture and reducing the number of people who can access the content in the first place.

• One-time viewing. The note self-destructs after being read. The recipient has one window to view the content. They cannot come back to it later, share the link with others, or re-read it. This dramatically narrows the timeframe in which a screenshot could be taken.
• Password protection. Adding a password means that even if the link is intercepted, the note cannot be viewed without the correct password. This limits access to only the person who has both the link and the password.
• Timed expiration. If the note is never opened, it is automatically destroyed after the expiration period. This prevents old, forgotten links from becoming a liability.
• End-to-end encryption. E2EE ensures that even the servers cannot read the note. The only person who can view it is the one who opens the link.

The Trust Model

Every act of sharing information involves trust. When you whisper something to a friend, you trust them not to repeat it. When you send a private note, you trust the recipient not to save it. SneakNote cannot replace human trust, but it can reduce the risk that comes from the infrastructure between you and the recipient.

Without SneakNote, a password shared in a Slack message exists forever in that workspace's message history, visible to administrators and potentially exposed in a breach. With SneakNote, that password exists only for the moment it is viewed, and then it is gone. The recipient could still screenshot it, but the same is true of anything displayed on any screen. The difference is that SneakNote eliminates the persistent copy on the server.

Why One-Time Viewing Still Matters

Even though screenshots are possible, one-time viewing provides meaningful protection. It prevents the note from being forwarded or shared with additional people through the original link. It eliminates the risk of the note being discovered months later in a compromised account. And it ensures that even you, the sender, cannot access the note after it has been created, which is important when dealing with information you should not retain.

The goal is not to achieve theoretical perfection. The goal is to provide a substantially safer alternative to leaving sensitive information in permanent, unencrypted message histories.

SneakNote is built on the principle that privacy tools should be honest about their limitations. If you need to share something sensitive and want to minimize its footprint, try creating a self-destructing note: it is free, requires no account, and gives you a meaningfully safer way to share.