Check it yourself. That's the point.
Last updated: 9 November 2026
Izuki can use your mouse and keyboard, so it has to be something you can trust, and something you can check rather than take on faith. Here's how to make sure your copy is genuine, what protects you while it works, and how to tell us about a problem.
Where to get Izuki
Only from these two places:
- the Download button on nova-izuki.github.io/izuki;
- github.com/nova-izuki/izuki/releases.
Izuki is free. A copy on another site, in a bundle, or for sale isn't from us, so don't run it.
Why Windows says “Windows protected your PC”
Windows SmartScreen shows that warning for new apps whose installer isn't signed with a paid code-signing certificate. Izuki's installer isn't code-signed yet, so you'll see “Unknown publisher”. That's a statement about the certificate, not a finding about the file. Check your download first (next section), then choose More info → Run anyway.
If you're not sure, don't run it. Ask us at izuki.hq@gmail.com, or open an issue on GitHub.
Verify your download
GitHub publishes a SHA-256 fingerprint for every file in a release. If the fingerprint of your file matches, it's byte-for-byte the file we released.
- Open the latest release and find Izuki-Setup.exe under Assets. GitHub shows its
sha256:fingerprint next to it. - Open PowerShell (Start → type “PowerShell”) and run:
Get-FileHash "$env:USERPROFILE\Downloads\Izuki-Setup.exe" -Algorithm SHA256 - Compare the Hash it prints with GitHub's fingerprint. Upper or lower case doesn't matter, but every character must match. If they don't, delete the file and download it again from GitHub.
You can also upload the file to VirusTotal for a second opinion from many virus scanners.
Signed updates
Once Izuki is installed, it updates itself. Every update is signed with Izuki's private signing key, and the app checks the signature with the public key built into it (key ID 079F8F3DAA47A42C) before it installs anything. An update whose signature doesn't match is refused. Updates come only from Izuki's GitHub releases.
Changed your mind about an update? Settings can go back to the previous version, using the same signature check.
Safety rules built into the code
A free AI model can be told to behave and still not do it. So these rules are enforced by Izuki's own code, not left to the AI's judgement:
- No password boxes. It checks what a box is before typing and refuses password fields, and it never reads them.
- Not on the lock screen. A keystroke there would go into your PIN.
- No final buttons unless you asked. Submit, Send, Pay, Buy, Delete, Erase, Format, Share, Invite, Close account: only when you asked for exactly that.
- No graded quizzes or tests. It explains and coaches; it won't pick or submit answers.
- No surprise commands. It won't type a command into your terminal unless you spelled it out, and the Chat shows every command it runs.
- Asks before sending email or messages from your linked apps.
- Stops at once. Esc stops everything, Ctrl+Shift+Q works any time, and you can pause a task between steps. Eye control has its own emergency stop and is off unless you turn it on.
All of this is open source: read the code on GitHub.
Keeping your keys safe
Your AI and app keys are saved in Izuki's settings file in your Windows user folder (%APPDATA%\Izuki), in plain text. If you link your phone or TV, the keys it needs are copied to that device too, so it can work on its own. Anyone who can sign in to your Windows account (or open the linked device) could read them, so:
- keep a password or PIN on your Windows account;
- prefer free keys, or set a spending limit at the provider;
- if you think a key leaked, revoke it on the provider's site and paste a new one into Izuki.
Izuki sends each key only to the service it belongs to.
Report a security problem
Found a way Izuki could be misused, or a bug that exposes data? Email izuki.hq@gmail.com with “Security” in the subject. Please include Izuki's version (shown in Settings) and the steps to reproduce it, and give us a chance to fix it before you post details publicly. We'll reply as soon as we can and credit you in the release notes if you'd like.
For everything else, open an issue on GitHub.