It is. You need to decide yourself, where to store encrypted data - config, settings file, etc.

Well, I wasn't sure if it's allowed. I promise to write an article, but the project is not mature enough (yet).

Use the System.Security.Cryptography.ProtectedData class. It's designed for exactly this task.

Hello Here is a free .NET obfuscator, I've created it to use for my own projects. What it currently can do: rename types and remove namespaces, rename methods and fields, remove properties and events declarations, rename (private) assembly files. Basically, my primary goal was to make it remove all meaningful information that can help reverse engineers to analyze the program. It provides 2 features, that I needed and couldn't find in existing products: 1. Flexible settings system that allows fine-grained control over classes and members obfuscation parameters. 2. It can obfuscate public types and members (useful for assemblies that are not exposed outside of your program) Looking forward to your feedback.