Documentation library.

This library answers the questions that need more than a trust us answer. Read why the app needs admin access, why protected code can trigger security warnings, what it changes in Windows, and how you can check a release.

Start with the part you want to verify.

Each page separates what the app does from what we can prove. A signed app can still be unsafe, an obfuscated app can still be legitimate, and a reversible setting can still cause problems.

The questions people ask first.

Quick answers to the concerns that come up most often.

Does obfuscation mean malware?
No. Obfuscation makes .NET code harder to read and copy. Good and bad software can both use it, so you still need to look at what the app does and where the file came from.
Why does AckerTech Optimizer request administrator access?
Many system wide registry keys, services, scheduled tasks, power settings, and protected Windows configuration areas cannot be changed by a standard user process.
Can security software still warn about a signed build?
Yes. Code signing and antivirus warnings are separate things. A scanner can still react to administrator-level changes, bundled code, a new file with few downloads, or a changed file hash.
Is every action reversible?
No. Configuration changes are designed with revert paths and registry state capture where applicable. Cleanup operations that delete disposable files cannot restore the deleted data.

Need the legal or privacy detail?

These pages explain what the app does. The privacy policy explains data handling, and the terms explain the rules and risks of using the software.