This tool includes some very basic encryption tools to optionally mask sensitive data before exporting it. While this is probably very adequate in most development scenarios, I want to point out some very important notes.

• This is not suitable for highly sensitive data like passwords, credit card information, social security numbers, medical records, etc... That kind of data should not be stored in version control, and probably shouldn't be stored in Microsoft Access either, if you want my opinion on the matter. 😄
• Do not use an existing password or sensitive information as the key. It is stored in plain text and can be easily read from the registry or using source code in this add-in. I recommend using a password generator and storing a copy in a safe place.
• You need to determine if this is sufficient to protect PII (personally identifiable information) that you may be exporting out of your database. (Particularly when saving table data.) You are responsible for compliance with all applicable laws in this regard.
• If your key is reset or lost, it cannot be recovered by the program, nor can encrypted data be decrypted without it. If you lose or change the key, simply export the data again after setting the new key.

A private key is stored in the registry for the current user. Encrypted data is processed using a VBA implementation of RC4 to hash the data using the key. The key is not exported or stored anywhere with the project. Any user needing to decrypt the data will need to set the same key in the options dialog.

Multiple developers can still work on the same project using different computers and user profiles as long as they use the same encryption key when exporting or importing source.