My five cents:
Like others have mentioned the password can be read as a string inside the binary if you store the password as a string (and it's stored as a string by default), so it's not a very secure solution, it's just better than nothing, I believe it's the solution that the developer behind OpenTibiaUnity wrote a thread about where he vaguely mentioned Zip encryption with no real clear references to anything which I read and decided to pay a dev about $30 to pursue for me for fun/curiosity's sake before I was using any encryption myself as I was only using obfuscation at that time.
The purpose of the release was just to give the first OTClient encryption solution published by anyone for free; a free and simple solution that protects you more than nothing, it protects you about as much as locking your door at night, anyone can break open or lockpick your door if they want to, but a locked door is better than an open door imo.
And for anyone concerned about the security beyond a simple easily crackable lock, you can obfuscate the password to prevent static analysis for example, but the choice of obfuscation is up to you, my goal was just to release something simple for free, you'll have to figure the rest out yourself or hire someone to do it for you if you're looking for something more advanced.
Protip: if you don't know how to implement any kind of obfuscation you can simply learn how to construct a std::string from a non-string-literal, that is use numeric ascii values instead of ascii characters enclosed in quotation marks "" and construct a string from those values, now the password isn't stored as a string literal in the binary anymore, now write a small simple scrambling algorithm to mix the numbers up in a deterministic yet as compex as possible way to make static analysis difficult and you should have yourself the equivalent of a good bike lock, it can still be cut through and sliced open by someone determined, but at least you probably won't be able to find someone cracking this for say 20 bucks on fiver which is a good start if you're someone running a small to medium size OT.
Personally I implemented my own much stronger (WBC) encryption for my own use case, but the implementation is much more complicated and not something I will ever release for free, requiring additional tools (file generation, WBC key generation), and a lot more code, not to mention that the WBC key generation is intended to be run on Linux only etc.