Starting with version 3.6 of QueryConnect, passwords are stored securely using encryption via the windows DPAPI; it is setup so that when manually viewing config files, all passwords will appear as long random-character strings. Attempts to read passwords will only succeed if QueryConnect (or any batch files that it creates) are done so on the same computer. 

While this means that passwords are safe from prying eyes, it also means that any batch files that were created on a different computer will not run correctly. If it is important that batch files can be created on one computer and run on another, there is a way to allow this to happen: 


        Open the batch config file, SCSQLBatch.exe.config 

        Find the line where the password is stored. This looks something like <add key="passwordDpapi" value=".." /> 


        Change the key to password, and type in your (unencrypted and unencoded) password as the value 


Change the key to password64, and type in your base64-encoded password as the value. Base64 encoders can be found quite easily online. 


The connections that appear on the left panel within QueryConnect are saved as 

C:\Users\<user name>\AppData\Roaming\SharpCloudQueryConnect\connections.json 

When using SharpCloud (Excel) as a connection type, any password entered as part of the Source Story Settings will be saved here, protected using the DPAPI. This means that by transferring your connections to a new computer, any passwords stored here will become unreadable and you will have to re-enter your passwords for these connections. While this means there will be some inconvenience associated with this, it comes with the peace of mind that your passwords will be secure.