Privacy Policy
Last updated: July 18, 2026
What we collect
Nothing. FetchMatehas no backend that collects personal data, and the app sends no usage analytics or telemetry. We can't see your requests, responses, collections, environment variables, or keys.
The only network calls the app makes are the ones you initiate: the HTTP requests you send to your own APIs, an optional call to your chosen AI provider, optional Git/GitHub operations, and downloading app updates.
Where your data lives
Projects and collections are stored as plain-text YAML files in a folder on your computer (and anywhere you choose to commit them with Git). Request history is stored locally in the app's data directory. None of it is uploaded to us.
Requests you send
When you send a request, it goes directly from your machine to the target URL you entered — it does not pass through any FetchMate server. Responses are held in memory and in your local history until you clear them.
Secrets, tokens & keys
Secret values you store in the vault are encrypted at rest using your operating system's keychain (via the OS secure-storage APIs) and are never written into the plain-text collection files, so they don't end up in your Git history.
Before any prompt is sent to an AI provider, known secret values are stripped and replaced with their variable names, so raw tokens aren't transmitted in chat.
AI features (optional, bring-your-own-key)
AI features are off until you configure them. You supply your own API key for Anthropic or OpenAI, or use your locally installed Claude CLI. Your key is encrypted with your OS keychain and is only ever sent to the provider you chose. Prompts you submit are sent to that provider and are subject to their privacy policy —FetchMate is not an intermediary and keeps no copy.
Cookies
The optional cookie jar stores cookies returned by the APIs you call, on your machine, so sessions carry across requests like a browser. These are your APIs' cookies, used only to make your requests — you can view and clear them in Settings. This website itself sets no tracking cookies.
Git & GitHub (optional)
If you connect GitHub, the access token is stored encrypted on your machine and used only to perform the Git operations you request (e.g. pushing your collections to your own repository). We don't receive or store your token.
Browser & editor extensions
The FetchMate browser extension adds a panel to your DevTools and, only when you click, forwards a request into the desktop app via a fetchmate:// deep link. It requests no host permissions and collects no data. The VS Code extension reads collection files in your workspace and runs them locally.
The waitlist
If you join the waitlist, we store the email address you provide solely to notify you about the launch. Ask us to remove it at any time (see below).
Children
FetchMate is not directed to children under 13 and we do not knowingly collect their data.
Changes
We'll update this page if our practices change and revise the date above. Material changes will be noted on the site.
Contact
Questions or a data request? Open an issue on GitHub or reach out via the links in the footer.