In short
- Ziora runs on your computer. Your code isn’t uploaded anywhere.
- It reads your code but never runs it.
- There’s no account, no tracking and no analytics.
- It goes online only for the things in the network table below, like updates and scanner downloads.
- The one feature that sends code is Ask Ziora AI, and only when you use it: the code around the one problem you pick, with secrets removed.
How Ziora is built
Ziora has two parts, and both run on your computer: the desktop app, built with Flutter, and an analysis engine written in Python. Release builds include the engine as a standalone program, so you don’t need Python installed.
- The app starts the engine as a child process and talks to it with JSON-RPC over standard input and output. No network port is opened, so nothing else on your machine or network can talk to the engine.
- If the engine stops while you work, the app restarts it and reopens your project on the next action.
Your code
- Never executed. The engine reads files and parses syntax trees. It never imports, builds, installs or runs anything from the repository it reviews.
- Read in place. File access from the app is confined to the project folder. Requests for paths outside it, including path traversal, are rejected, and there are tests for it.
- Hostile files are expected. XML such as Android manifests is parsed with entity declarations refused, so a malicious file can’t expand entities or reach outside the project.
- Secret values stay out. When Ziora finds a hardcoded secret, it records where it is, not what it is. gitleaks always runs with
--redact, so secret values never reach Ziora or its files. - Notes stay out of git. Review state lives in a
.ziora/folder inside the project, which gets its own.gitignoreso notes aren’t committed by accident.
Network access
Ziora has no telemetry, analytics or crash reporting. These are the only times it connects to the internet:
| When | Connects to | What is sent |
|---|---|---|
| You clone a repository or pull from the branch menu | Your git host, using the git installed on your computer | Whatever git sends. Ziora uses the sign-in git already has (Git Credential Manager, SSH keys) and never asks for, sees or stores a password or token. |
| OSV-Scanner checks your dependencies | api.osv.dev | Package names, versions and ecosystems from your lockfiles. No source code. |
| Semgrep loads its default rule set | semgrep.dev | A request for the rules. Ziora runs Semgrep with --metrics=off and --disable-version-check. |
| You install a scanner from inside Ziora (macOS and Linux) | github.com for gitleaks and OSV-Scanner, pypi.org for Semgrep. On Windows all three come with Ziora, so this never happens | A standard download request. |
| Ziora starts | ziorasecurity.com | A request for a small file that names the latest version. If a newer version exists, Ziora shows a link to the download page. It never downloads or runs an installer by itself. Microsoft Store copies are updated by the Store. |
| Before each scan, and when you activate a plan | Ziora’s plan server at ziorasecurity.com | A one-way (SHA-256) hash of your computer’s IDs, your licence key if you have one, and two hashes that identify the project (of its first git commit and of its list of file names). Nothing about your code. The server answers with a signed scan pass, which Ziora checks before it scans. |
| When Ziora opens, and when you come back to it (at most every few minutes) | Ziora’s plan server at ziorasecurity.com | The same hashed computer ID and licence key. Nothing about your code. The server answers with your plan and scans left, and adds to daily totals of computers and sessions that keep no IDs. |
| You use Ask Ziora AI | Ziora’s AI service at ziorasecurity.com, which asks Groq. Or, if you added your own API key, that provider: Groq, OpenAI or Anthropic | The code around the finding you picked, with secret values removed, plus your licence key or a one-way hash of your computer’s ID to count your plan’s AI answers. Nothing is stored. Your own key, if you add one, is stored encrypted on your computer. |
Everything else works offline, including all of Ziora’s own analysis. If Semgrep can’t reach its registry, Ziora runs it with a built-in rule set instead and tells you.
Scanners
Semgrep, gitleaks and OSV-Scanner are optional. Ziora’s own checks work without them.
- Each scanner runs as a separate process with a fixed argument list, never through a shell, and with a timeout.
- On Windows, Semgrep, gitleaks and OSV-Scanner come inside Ziora’s package, checked against pinned checksums when Ziora is built. Ziora never downloads a program or starts an installer while you use it. On macOS and Linux, Ziora downloads the official release for your system from GitHub and verifies its SHA-256 against the checksums file published with that release. If the checksum doesn’t match, the download is discarded.
- gitleaks and OSV-Scanner live in Ziora’s own folders. They need no administrator rights and add nothing to your
PATH. - On macOS and Linux, if you choose to add Semgrep, Ziora installs it with pip in a private environment that it owns.
AI agents
Ziora sends nothing to an AI provider unless you use Ask Ziora AI, and then only the code around that one problem, with secrets removed. You decide whether to give your agent the fix plan or connect it to Ziora.
- Fix plans never include secret values.
- The MCP server speaks the Model Context Protocol over standard input and output. It never exposes secret values and writes nothing but protocol messages to its output.
- Once your agent reads a fix plan or queries Ziora, what it does with that information is governed by the agent and its provider.
Data on your computer
This is everything Ziora itself stores. Ziora has no server, so there is no copy anywhere else. Scanners you install may keep their own caches.
| What | Where |
|---|---|
| Review state: findings, triage, notes and coverage | .ziora/ inside each project |
| Recent projects | Windows: %APPDATA%\Ziora\recent.jsonmacOS and Linux: ~/.config/Ziora/recent.json |
| Engine log | Windows: %LOCALAPPDATA%\Ziora\logsmacOS: ~/Library/Logs/ZioraLinux: ~/.local/state/ziora |
| Scanners installed by Ziora | Windows: %LOCALAPPDATA%\Ziora\toolsmacOS: ~/Library/Application Support/Ziora/toolsLinux: ~/.local/share/ziora/tools |
| Your licence key and plan, as last checked | Windows: %APPDATA%\Ziora\license.jsonmacOS and Linux: ~/.config/Ziora/license.json |
| Your AI provider key for Ask Ziora AI, encrypted (Windows DPAPI on Windows) | Windows: %LOCALAPPDATA%\Ziora\ai-key.jsonmacOS: ~/Library/Application Support/Ziora/ai-key.jsonLinux: ~/.config/ziora/ai-key.json |
| A downloaded update, until it is installed | Your system’s temporary folder, in a folder starting with ziora-update |
Deleting a project’s .ziora/ folder removes its review. Deleting the folders above removes everything else.
Verify a download
Before you run a file you downloaded, check that its SHA-256 checksum matches the one listed here for the latest release. Copies from the Microsoft Store are checked by Windows, so you don’t need to do this for them.
Windows (PowerShell)
Get-FileHash .\<file name> -Algorithm SHA256
macOS
shasum -a 256 ~/Downloads/<file name>
Linux
sha256sum ~/Downloads/<file name>
If the values don’t match, don’t run the file. Delete it and download it again from this site.
Report a vulnerability
If you find a security problem in Ziora or on this website, email [email protected].
- Include the Ziora version, your operating system, what you found and the steps to reproduce it.
- Please don’t include real secrets or someone else’s data in your report.
- Give us a reasonable amount of time to fix the issue before you share it publicly.
We’ll confirm that we received your report and keep you updated while we work on a fix. Our contact details are also published in security.txt.