Privacy policy

Information handled

Hack Engine handles the inspected tab and frame URLs, public Ruffle metadata, numeric WebAssembly memory values and addresses, scan settings, watches, labels, groups, and values entered for writes or freezes. Workspace files are read or saved only when the user explicitly imports or exports them.

Local use and storage

The information is used only for capture, scans, live candidates and watches, writes, and freezes. Active state is held for the inspected tab. UI preferences, watch metadata, and up to 20 history entries use extension-page session storage. Unknown-value scans can temporarily place compressed snapshot chunks in the inspected origin's IndexedDB; reset, replacement, cancellation, refinement, or the next snapshot-storage initialization removes them.

No external transmission

Hack Engine does not send browsing activity, page content, memory values, scan results, or analytics to the developer or any third party. It has no accounts, advertising, telemetry, or remote configuration and does not sell or share user information.

Permissions

tabs binds controls to the inspected tab. <all_urls> permits the document-start capture hook to run before arbitrary embedded Ruffle players instantiate WebAssembly, including in permitted child frames. Chrome's sidePanel permission keeps the user-requested controls visible beside the page.

Retention and control

Resetting or replacing a scan clears its active candidates and snapshot. Reloading closes active page memory state. Browser site-data controls remove origin snapshots, and normal extension-data removal applies when Hack Engine is uninstalled. Exported JSON remains only where the user saved it.

Contact

Email a.abduljawad@outlook.com or use the public issue tracker for privacy questions. Use the private security advisory form for vulnerabilities.

Use Hack Engine only with software and content you own or are authorized to inspect. Raw writes are experimental and can reset or crash the player.