Release transparency
Know what
you are installing.
Each public release must identify its real version, publisher, file size and final SHA-256 checksums.
Release preparation
No signed Windows installer has been published on this site. The implementation has development tests, but those do not replace Windows GUI, DPAPI, native-dialog and installation validation.
Available implementation
- Encrypted signed messaging and document transfers.
- Encrypted local history, key backups and fingerprint comparison.
- PDF/JSON transcript exports with offline verification.
- Central authentication, routing and encrypted offline queues.
Before the first installer release
- Test installation, upgrade, uninstall and native features on declared Windows builds.
- Validate local permissions, DPAPI, lock behavior and backup recovery.
- Complete independent security review and resolve material findings.
- Sign and timestamp application binaries and installers with the actual publisher identity.
- Verify Authenticode and publish final checksums with the release manifest.
- Complete legal notices and support/security contact details.
Release notes must describe actual changes and known issues. No synthetic installer or certification is used to imply readiness.
Check download availability ↗