Privacy
Nothing is collected. That is the whole policy.
Zephyr has no backend, so there is nowhere for your data to go. This page says exactly what is written to disk, what leaves your machine if you choose to send it, what GitHub Pages records about visits to this site, and how to erase everything in one step.
The app
What Zephyr does not do.
- No telemetry, no usage counters, no unique or random identifiers.
- No analytics SDK, no crash reporter, no error-reporting service.
- No accounts. There is no sign-in, no email address, and no user record.
- No cookies and no local storage used for tracking in the app or on this site.
- No advertising, no ad tracking, no third-party ad or analytics scripts.
- No data sold, licensed, shared, or brokered. There is nothing collected to do it with.
Stored locally
Everything the app persists, in one folder.
All of it lives under %APPDATA%\zephyr on your own machine. The project has no access to your disk, and the folder is not read by anything except Zephyr.
Settings
Theme, layout, font size, keybindings, and editor preferences you change.
Editor history
Recently opened folders and files, kept so the window can reopen where you left off.
Extension list
The extensions found in your extensions folder, loaded at startup.
Logs
Local diagnostic output in the same folder. Never uploaded, never read by the project.
Provider keys
Only if you choose to store one, obfuscated with XOR and BLAKE3. That is reversible obfuscation, not encryption. See the security page for what that does and does not buy you.
What leaves the machine
Only what you deliberately send.
Zephyr itself has no endpoint to send anything to. Traffic leaves your machine only in two situations, and both start with you pointing the app at something.
To your AI provider
If you use the built-in AI chat or an agent mode, the prompts and context you send go to the model provider you configured, under that provider's terms. Zephyr does not see, log, or forward a copy. Files the agent reads for you are included only in the request you asked for.
To servers you run
A language server, a local MCP client, a dev server, and a git remote all talk to endpoints you chose. Those connections carry the data those services need, and they are governed by wherever they terminate. Uninstalling Zephyr stops them.
The update check
Checking for a new version fetches a small manifest and stops. No identifier, no machine details, and no usage data are included in that request. The signature is verified locally before anything is applied, so the check does not even need to succeed for the app to work.
This website
Static files, standard server logs.
This site is static files served by GitHub Pages. Serving a page produces a normal access log on the GitHub side, containing the requested path, a timestamp, a user agent, and an IP address. That log is GitHub’s, not the project’s, and is handled under the GitHub privacy statement.
The site itself runs no client-side tracking: no analytics script, no tag manager, no pixels, no consent banner because there is nothing to consent to. Fonts are self-hosted and there are no third-party embeds.
Source is in the open
You do not have to take this page on trust. The website repository is the same place the claims are written down.
App source too
If you want to confirm that no telemetry call exists, grep the tree. There is no analytics dependency to find.
Reset
Delete the folder and you are done.
Close the window, then delete %APPDATA%\zephyr. That removes your settings, editor history, extension list, logs, and any key you stored, in one step. There is no server-side record to delete afterwards, because nothing was ever sent.
- Close Zephyr. On Windows, check the tray or Task Manager first.
- Open the folder in File Explorer and delete it.
- Reopen Zephyr when you want a clean install. It recreates the folder with defaults.
If the machine is shared or you are unsure who had access, rotate any API key you had stored. Deleting the file obfuscates it away, but it does not un-share a key that was already copied.
Related: the security page covers the MCP server and release signing, and the terms cover the license and warranty.