You know that feeling. You have a sensitive file — a contract, a personal document, something you’d never want anyone else to see. You think about encrypting it. Then you remember the steps: open an app, select the file, choose a cipher, set a password, wait for the process, and you close the folder. Maybe later.
That later never comes. And that’s not your fault.
The security industry has spent decades telling you that encryption is hard because it has to be. That the only way to protect your data is to learn command-line tools, install bloated suites, or hand over your files to a cloud service. They’ve convinced you that the friction is a feature, not a bug.
They’re wrong.
The best encryption is the one you actually use. And the one you actually use is the one that takes zero extra thought.
I stumbled across a small GitHub project called Fingerlock that does exactly one thing: it adds an “Encrypt” option to your right-click context menu. Right-click a file, choose encrypt, pick a password, and done. No extra windows, no configuration, no tutorials. The whole interaction takes under two seconds.
Now, you might be thinking: “That’s too simple. It can’t be secure.” But that’s the trap. The algorithm doesn’t matter if nobody runs it. AES-256 is useless sitting in a feature list. What matters is whether a user — any user — will actually use it. And the data says they won’t, unless the path is frictionless.
The barrier to widespread personal data security isn’t a lack of education or tools. It’s a few extra seconds of UI friction.
Fingerlock takes that friction down to zero. It integrates encryption directly into the operating system’s native interaction model — the right-click menu. You don’t learn a new workflow. You don’t switch contexts. You just do what you already do, with one extra click.
I helped a friend who handles client contracts encrypt her entire drive over coffee. She was skeptical. By the second file, she was sold. “Why doesn’t every computer do this?” she asked. That’s the question.
Because the industry overcomplicated it. Because vendors sell features, not behavior. Because we’ve been trained to believe that security must be painful to be effective.
It’s a lie. Security doesn’t have to be painful — it just has to be present. And presence is a design problem, not a cryptographic one.
Fingerlock is open source, written in .NET, and lives on GitHub. It won’t win any awards for innovation in encryption. But it might win the award for actually getting people to encrypt their files — which is the only award that matters.
Stop blaming yourself for being lazy. Blame the tools that made security feel like a chore. And then find the ones that make it feel like nothing at all.
FAQ
Q: Is right-click encryption really secure enough for sensitive files?
A: Yes — Fingerlock uses standard encryption algorithms (AES) applied locally. The security is identical to what you'd get from a full-featured encryption tool. The difference is that you'll actually use it, which makes it infinitely more secure than the alternative: nothing.
Q: What's the practical implication of this for someone who handles sensitive data daily?
A: It means you can encrypt a file in under two seconds instead of avoiding it for hours. For professionals — lawyers, accountants, freelancers — this turns encryption from a chore into a habit. The result: your sensitive data gets protected without you even thinking about it.
Q: Isn't this just a gimmick? Real security needs more than a context menu entry.
A: Real security needs adoption. The most robust encryption in the world is worthless if people don't use it. By reducing friction to zero, tools like Fingerlock solve the actual adoption problem. The gimmick is the industry standard that expects users to jump through hoops — not the one that meets them where they already are.