Security and bug reporting

For ordinary bugs and feature requests, open an issue on GitHub. Useful reports include the Windows version and build, the exact action taken, and what you expected to happen instead.

If you believe you have found a security issue — for example an operation that does more than it claims, an undo that does not restore state correctly, or a signed update that could be tampered with — please do not open a public issue. Email viorelzeciu@gmail.com with enough detail to reproduce the problem.

• Include the product, its version and build, and the Windows version and build.
• Describe the exact steps, the observed result and the expected result.
• Include logs or screenshots only if they do not contain personal data.

No public builds exist yet. When a release is published, each one will state its architecture, Windows compatibility, file size, SHA-256 checksum and source tag before the download, so the file can be checked after it is saved.

• Some operations require administrator approval. The application marks which ones; other actions run as a standard user.
• Depending on the operation, it can modify files, registry settings, scheduled tasks and startup entries.
• Operations are planned before they run and recorded in an operation journal, with an undo offered only where the underlying change supports restoration.
• Update and guidance responses must be cryptographically authenticated before they are accepted; release and guidance checks are opt-in and off by default.

• Power Forensics is a local analysis tool. Privilege requirements are not documented yet for this pre-alpha product.
• Analysis does not require uploading measurements to a service; data leaves the machine only on an explicit export.

• In scope: Power Forensics, WinOptimizer, and this website.
• Out of scope: third-party services and dependencies, reports requiring physical access to a device, and social-engineering attacks.
• There is no paid bug bounty. Reports are acknowledged and fixed on a best-effort basis.