Privacy Policy
Effective October 5, 2026
Gazey is an AI helper for your Mac. It runs on your computer and has no servers or accounts of its own. This policy explains what Gazey sees, where that goes, and what stays on your Mac.
The short version
- Gazey collects no analytics, no telemetry and no personal data. We can't see what you ask it.
- When you send a request, it goes to the AI you chose (Claude Code, Codex, or a service you added your own API key for), with a screenshot of your screen, under that service's own privacy terms. Simple actions can instead run on a free model on your Mac, and then nothing leaves it.
- Everything else stays on your Mac.
Voice commands
When you hold ⌥ in the box or click the microphone, Gazey listens until you let go. Your speech is turned into text on your Mac by Apple's on-device speech recognition; the audio is never recorded, stored or sent anywhere. The text is then handled like something you typed: simple Mac actions (opening or quitting apps, opening websites, web searches, installing VS Code extensions) run on your Mac; if you turned on smart routing with a TypeSafe key, a command Gazey can't place by itself is sent to TypeSafe (the words of that command plus the names of your installed apps) to understand it; anything else goes to your AI agent as described below. Installing a VS Code extension looks up its name on Microsoft's Visual Studio Marketplace.
Operating your Mac
To carry out a task, your AI agent can use Gazey's Mac tools: run AppleScript in apps, choose menu items, press keys, take a fresh screenshot, and read and fill the fields and buttons of an app's window (through macOS Accessibility). What it reads this way, such as the labels and contents of a window's fields, goes to the agent you chose, like the screenshot does. The tools work only during a request you made, anything that changes something follows your approval setting, and macOS asks you once before Gazey controls each app (System Settings → Privacy & Security → Automation). If you set up a TypeSafe key, the labels of a window's controls are sent to TypeSafe to decide which one you meant ("the name field").
When Gazey drives. For some tasks Gazey works through an app's window by itself, a click at a time: your screen gets a frame, Gazey's own cursor shows each click, and Esc stops it. At each step it reads the window's controls and the text it shows. If you set up a TypeSafe key, that (the controls' labels and the window's visible text, with the goal you gave) is sent to TypeSafe so Jev can pick the next control; without a key, a model running on your Mac picks it and nothing leaves your Mac. Whatever your approval setting, Gazey asks you before pressing anything that deletes, sends, buys or can't easily be undone.
What Gazey sees when you summon it
- A screenshot of the display your pointer is on. It is taken only when you press the Gazey shortcut, never in the background.
- The app you're in and its window title, and any text you've highlighted (with your Accessibility permission). In web browsers, which don't share highlighted text that way, Gazey copies it and then puts your clipboard back exactly as it was.
- What you type in the box.
Where your requests go
The AI agent you choose. Your request, the screenshot, the app name, window title and highlighted text are sent to Claude Code (by Anthropic) or Codex (by OpenAI), using your own account with them. They handle it under their privacy policies, exactly as if you used them in a terminal:
- Anthropic: https://www.anthropic.com/legal/privacy
- OpenAI: https://openai.com/policies/privacy-policy
Your own API key (optional). If you add an Anthropic, OpenAI or OpenRouter API key instead of using Claude Code or Codex, your request, the screenshot, the app name, window title and highlighted text, and what Gazey's tools read while working (such as a window's fields), are sent to that service with your key, under its own privacy policy, and billed to your account there. OpenRouter passes requests on to the model's maker. The key is kept in your Mac's Keychain and is only ever sent to that service.
- OpenRouter: https://openrouter.ai/privacy
The local model (optional). If you set up the local model, simple actions and the quick reply run on a model on your Mac (through Ollama). What it handles never leaves your Mac. When a request is too much for it, it's passed to the agent you chose, as described above. If you click Install during setup, Gazey downloads the official Ollama app from ollama.com (served from GitHub), checks it is signed and notarized by Ollama's developer, and puts it in your Applications folder; the model itself is downloaded by Ollama from its library. Neither download sends anything about you beyond the request itself.
If you click Set up for Claude Code or Codex, Gazey runs that tool's official installer (from claude.ai or releases.openai.com), then the tool's own sign-in, which opens your browser. You sign in with Anthropic or OpenAI directly; Gazey never sees your password.
The quick reply. To acknowledge actions instantly, Gazey sends your typed request, the app name and the window title, but no screenshot and no highlighted text, to Claude Haiku through your Claude Code account.
Smart routing (off by default). If you turn on routing and add a TypeSafe key, your typed request, the app name and the window title are sent to TypeSafe to pick an agent. Screenshots are never sent to TypeSafe.
Your connected apps. When an agent uses a connection you set up (for example Notion or Slack), it reads or changes data there on your behalf. Gazey itself also connects to them directly, from your Mac, so the local model and your own API key can use them: it sends the service only what the request needs, with the sign-in you approved. What comes back goes to whichever model handles the request (on your Mac for the local model). Anything that changes something follows your approval setting, and anything that deletes or sends asks first in Auto.
Finding connections. Searching in Control Center → Connections sends what you type to the official MCP Registry (registry.modelcontextprotocol.io). Connector icons are loaded from the services' own sites or through Google's favicon service, which receives only the service's web address.
What stays on your Mac
- Screenshots are kept in a private temporary folder only until your request is sent, then deleted. Unused ones are deleted when you close the box, and any leftovers when Gazey quits or restarts.
- Your task list lives in memory and is cleared when Gazey quits.
- Settings and sign-in tokens for connections Gazey set up are stored in your user account, readable only by you.
- A diagnostic log at ~/Library/Logs/Gazey.log records events such as "summoned over Safari" or "screen captured". It never contains your requests, the agent's replies or window titles.
- Your activity history at ~/Library/Application Support/Gazey/activity.json: your last 300 requests (their text), which agent or model handled each, the actions it took, the tokens and estimated cost it reported, and how it ended, so you can see them in Control Center → Activity. It stays on your Mac and is never sent anywhere; Clear History there deletes it.
Updates
Gazey checks the Gazey website for new versions (you can turn this off in About). That request includes nothing about you beyond what any web request reveals, such as your IP address.
Feedback
"Report a Bug" and "Suggest a Feature" open a form in Gazey. When you press Send, your message, the reply email you choose to add (if any) and the diagnostics the form shows you (your Gazey and macOS versions, which agents are signed in, and, unless you untick it, the last lines of the diagnostic log) are sent to the Gazey website, which forwards them to the developer by email. Nothing is sent until you press Send, and nothing else is stored.
Children
Gazey is not directed at children under 13.
Changes
If this policy changes, the new version will ship with Gazey and be posted on the Gazey website, with a new effective date.
Contact
Questions about privacy: use "Report a Bug" in Gazey → Control Center → About.
This website
This site has no analytics or tracking either, and loads no third-party fonts or scripts. The one thing it counts is downloads: each click on Download adds one to a total. No cookies, no IP addresses, nothing about you is stored. Feedback you send from the app passes through this site on its way to the developer's inbox; to keep out spam, a one-way hash of your IP address is kept for an hour, then deleted.