Fifty honest answers to the questions people actually ask.

VeraCrypt is powerful but heavy for one folder. A plain-language look at simpler options and when a single-file vault is the honest fit.

Cryptomator is built for the cloud. For a folder that stays on your machine, a single-file vault does less and asks less. A fair comparison.

You can encrypt a folder without admin rights, without installers, and without an account. Here is how, and where each approach breaks down.

Encryption software you own outright, not rent. What one-time-purchase file vaults actually cost, and what you're trading for the lower price.

If you only need to keep a folder of secrets on your own machine, you don't need a password manager service. Here is the smaller shape.

7-Zip's AES-256 encryption is genuinely strong. The catch is what it does not protect and how easy it is to use wrong.

BitLocker protects the whole disk. For a single folder inside your Documents, you want something with a smaller scope and no admin requirement.

You don't need an account to keep private notes on your own laptop. Any text editor plus a single-file vault is enough.

'Military-grade' is a marketing phrase, not a spec. Here is what to actually look for on a product page — and how to smell out the noise.

Most encryption apps quietly assume the company outlives your files. The four things that decide whether your files survive the company.

Dropbox, iCloud, and OneDrive clients have broad filesystem access. How to have a folder they cannot read — even when the client is running.

Google Drive holds files as plaintext on Google's servers. Client-side encryption makes what you upload unreadable — including to Google.

The right moment to encrypt is on your machine, before the file ever sees a sync client. A minimal workflow, and where it breaks down.

Separate user accounts help, but not enough. How to have a folder that is unreadable to anyone else using the machine, including you if unlocked.

Encrypting file contents but leaving 'taxes-2024/audit-notice.pdf' visible is a common mistake. How to seal the metadata too.

A file vault that has never needed the internet — no license check, no cloud fallback, no 'first-time online activation'. The full offline shape.

Disk encryption handles the stolen-laptop case only if it is enabled. A layered approach: FileVault or BitLocker plus a sealed folder.

The right-click 'Encrypt contents' checkbox uses EFS — tied to your Windows account, and quietly weak in common scenarios.

Spotlight, Windows Search, and Recoll happily index folder contents by default. Sealing the folder is the reliable way to opt out.

Encrypting contents is only half the job. Sizes, timestamps, and filenames can rebuild the story on their own. How to seal that too.

ID scans are useful in a crisis and dangerous in a leak. A calm setup: originals in a safe, encrypted copies on your laptop, one backup.

A digital copy is useful; the legal original still lives on paper. How to keep an encrypted set that your executor can actually reach.

Journals need to feel unwatched to be honest. A minimal setup: plain markdown files, one sealed folder, no account anywhere.

A hardware wallet is best for large sums. For everything else, an encrypted folder on a laptop plus a paper backup is the honest tier.

Medical PDFs pile up in Downloads and email attachments. A minimal calm setup: one encrypted folder, one honest backup.

First drafts are half-thoughts. A quiet setup: local writing, one sealed folder, no cloud draft floating around.

A quiet folder that opens only when you want it to. The gentle mechanics of keeping what is still tender.

Digital estate is the folder your executor needs to open the day after. How to make it discoverable, encrypted, and honestly openable.

'Legacy contact' features hand your data to a provider. Two low-tech alternatives your executor will actually be able to use.

Some writing needs to feel unwatched. How to keep it local, encrypted, and out of every 'AI features enabled' upgrade.

Correspondence, timelines, receipts, screenshots. What to keep, how to organise it, and how to seal it so only you can open it.

The retention window is long; the subscription clock is longer. A one-time-purchase pattern that will still open in 2033.

A quiet folder for the sentences you meant. How to keep them local, encrypted, and out of every future feature update.

A letter for a wedding twenty years off. A message for a child's eighteenth. How to seal something with a purposeful long wait.

A local-only storage tier for confidential matters. What it does not solve (compliance, discovery) and where it fits alongside a case system.

For material that cannot be on a cloud, in an email, or in a search index. What a genuinely local, encrypted workflow looks like.

The clinician question is bigger than storage. Where a local encrypted folder helps, and where you still need a proper EHR and BAAs.

You signed something that said 'no third-party cloud storage'. A minimal setup that respects the clause without stopping your workflow.

IT owns the disk; you still owe employees discretion. A tool that runs without admin rights and leaves no trace on the machine.

Local-first is a shape of software: your data lives on your device, the cloud is optional, and nothing breaks if the company disappears.

'File over app' is the discipline of preferring plain, open file formats over any specific application. It is how you own your work in 2050.

The sovereignty conversation is happening at nation scale. Here's what it means for one person with one folder — and why it's the same problem.

The 'nothing to hide' framing quietly concedes the point. A better question turns the burden around and makes the real answer obvious.

Mortalware is software licensed so that its private ownership ends on a specific date. Not abandonware — planned, scheduled, in writing.

Scheduled open-source is a growing niche. The economic logic, the ethical logic, and why it fits some categories better than others.

Perpetual-license software has quiet advantages the subscription era forgot. The math and the ethics of buying instead of renting.

An account is a record with your name on it, held by the vendor. For a privacy tool, that record is the surface area you're trying to remove.

A plain-language walkthrough for macOS, Windows, and Linux. What a checksum proves, what it doesn't, and how to actually do it.

Two simple methods — one browser-native, one OS-native. Enough to satisfy 'is this thing really offline?'

Both are ways to make a passphrase expensive to guess. What the difference means for you, and why passphrase length still matters most.