Privacy policy

Hanki Tools runs on your PC. It has no account, no app analytics, no crash upload and no background updater. This page lists what it keeps locally and every network connection you can start.

Last updated 9 October 2026

Who is responsible

Hanki Tools is made by Iikka Isosaari in Finland. Questions about privacy: hello@hanki.tools.

This describes the shipped application's behavior, not a guarantee about third-party services or operating-system records. No app analytics, crash-upload service, background updater or automatic diagnostic-report upload is implemented.

Local data

The app uses %LOCALAPPDATA%\IgezziGuard for up to 100 scan summaries, startup/recovery journals, disabled-startup file backups, optional app-observation mappings/coverage, error logs and an optional debugger symbol cache. Paths, application names, command strings, network configuration and dates can be sensitive. Recovery/observation/error records are not automatically removed when the portable app folder is deleted. Keep recovery backups until changes are restored.

The Windows Update and Battery & startup checks read Windows' own local records (update history, startup events, battery report); on laptops Windows writes its battery report to a temporary file, which Hanki deletes straight after reading. Neither check contacts the network. The scan also reads which apps crashed or stopped responding in the last 14 days (app names and the failing module, from the Application log), the Windows Time service's sync records, and the speed each connected network adapter negotiated; none of these send anything.

Hanki Pro and Technician (paid, optional): a licence key is kept in Windows Credential Manager for your Windows account, with the edition, the activation id and when it was last checked; no name or email from the purchase is kept. A scheduled check (Pro) is a Windows Task Scheduler task for your account that runs the same read-only scan without network probes or repairs and adds it to local history. Technician customer reports are saved where you choose; a minimized record of each report (labels, scan titles and results, repair outcomes) and your business name and contact are kept under %LOCALAPPDATA%\IgezziGuard\technician.

Hanki Performance reads graphics, display, processor, memory and storage information from Windows and, on NVIDIA PCs, the NVIDIA driver's own settings. Nothing about it leaves the PC. It keeps, under %LOCALAPPDATA%\IgezziGuard: your game list (games.json: names and program paths found in Steam, Epic, GOG and other launchers' local records, or added by you), the latest Performance check (performance-checks.json) and Performance sessions (performance-sessions.json: measurements and the settings changed). Measurements in Performance Lab include the names of the busiest programs and how much data arrived over the network each second (a total, not what it was); saving one to a file is your choice. Frame-rate capture reads Windows' DirectX timing events for the chosen game only, on this PC, while you measure. On AMD Radeon PCs it reads Radeon settings through AMD Software's own interface (ADLX). The gaming check and Tune my PC take a one-second sample of running programs (names and CPU and memory use) to point out overlays, recorders and busy programs, and read RivaTuner's global frame limit from its profile file. Tune my PC also reads which video encoder each OBS Studio profile uses (from OBS's settings files; nothing else in them), whether AMD's 3D V-Cache and Intel's Dynamic Tuning drivers are installed, and the speed each connected network adapter negotiated. The programs it points out are saved with the latest Performance check; the rest of the sample isn't kept. Your own NVIDIA presets are kept in nvidia-presets.json. Launch and measure saves its measurements, and what limited each run, as Performance sessions. Deleting files, uninstalling apps and removing leftover app entries only happen after you confirm; each one is recorded in removals.json (what was removed and when), shown under History → System actions, and a leftover entry is saved to a .reg file in app-entry-backups before it's removed. Home's "Your PC at a glance" reads the Windows version, uptime, system drive space, memory, graphics adapter and Windows Security Center's antivirus and firewall status; nothing is saved. Settings Hanki Performance changes (display mode, per-app GPU choice, processor maximum, NVIDIA per-game and global settings, AMD Radeon settings, Windows gaming settings, power mode, Energy saver level and mouse acceleration) are recorded in Recovery before they change.

File inventories, current reports and checklists are normally session data. Explicit exports and saved monitoring runs are written where you choose; monitoring runs include the machine name. Clipboard content copied through Assistant can be available to other local applications or Windows clipboard history/sync. Redaction helpers only mask common patterns and are not comprehensive.

API key, AI draft and chat are held in process memory until cleared or exit; they are not intentionally persisted by Hanki. This does not rule out operating-system paging, crash dumps, screen capture or other software observing memory. Error logs are local and may contain paths and exception details.

Connections you initiate

The source build scripts additionally contact Microsoft's runtime metadata and .NET package sources. Signing uses the configured timestamp service. Those are publisher/build operations, not background behavior of the installed app.

Support and privacy contact: hello@hanki.tools. The hanki.tools website, GitHub issues and Discord have their own logging and analytics, separate from the app.