the per-phrase PIN lock in 3.0 is the right scope for the problem. most snippet managers make you choose between one vault-wide password that gets annoying to unlock constantly, or leaving everything in the clear. locking just the bank details and leaving everyday replies and SQL snippets frictionless is a much better tradeoff. source-available is also a smart call for something that's going to sit close to sensitive text.
PhraseVault
Third hunt, PhraseVault 3.0 is live. 20% off at phrasevault.app is auto-applied through the hunt window—no code.
The key change: lock one sensitive phrase at a time with a PIN. PhraseVault stays local, works on Windows and macOS, and is source-available.
Try it and tell me what you’d improve—I’m here for feedback.
Is the phrase locked with a PIN encrypted when saved, or is it only hidden from view on the screen?