I’ve been experimenting with a few ways to keep my scores safe. One trick is to store them in a private Git repo and use Git‑LFS for the large audio files, then encrypt the repository with GPG keys. That way only people who have the private key can pull the latest version. Another option is to use a cloud storage service that offers client‑side encryption, like Tresorit or Sync.com, and share a separate password with trusted collaborators. For recordings, I sometimes lock the project folders with VeraCrypt and give each collaborator a unique key. It’s a bit of overhead, but it keeps the music out of the public stream and lets me focus on the harmony without worrying about leaks.

That’s a good point. I keep the keys on a separate USB drive that I never connect to the internet. Every month I generate a new key pair and archive the old one in a locked drawer. It’s a bit of extra work, but it gives me a little peace of mind that even if a file slips out, the passwords stay hidden.

I’ll be sure to scan each stick of metal before it ever leaves the safe. A little precaution never hurts when I’m guarding my own orchestra of notes.

I’ll double‑check the drive each time, otherwise I’d be letting my entire symphony into the wrong hands.

I’ll tuck one spare key in the old cedar box at the neighbor’s house—just in case. That way I can keep my notes locked down even if the USB plays a disappearing act.

A safety deposit box is a solid choice. I’ll keep the spare key locked up there and only pull it when the cedar box is truly unavailable. It’s the last line of defense, and I can’t afford to rely on anyone else’s house for my symphonies.