The short version

Hoply has no account, no analytics and no server of its own. Nothing you type, read or run is ever sent anywhere by Hoply. There is nothing to opt out of, because there is nothing being collected.

You do not have to take this page on trust: Hoply is open source under the MIT license, so anyone can check every request listed below against the code at github.com/Milos5611/hoply. Release builds are made from that code by the repository’s public release workflow.

What the app stores, and where

The usage ledger, the model-server metric samples and the plan-limit readings (Claude’s and Codex’s) live in one SQLite database in ~/Library/Application Support/Hoply/; its settings are in its own macOS preferences. Session titles and prompt-derived names come from your own agent records and stay in that file.

Nothing is written into your repositories. Your agent transcripts, Copilot’s database and its session files are opened read-only; Hoply never edits, moves or deletes them except in Clean up, where you tick each item and confirm it, and files go to the Trash so Finder’s Put Back still works.

The network requests Hoply makes

Its listener is bound to 127.0.0.1 and drops any peer that is not loopback, before the request is parsed. That is how agents reach it; nothing outside your machine can.

Beyond that there are exactly three kinds of outgoing request: the model servers you added in Settings, Anthropic’s usage endpoint for the Claude plan-limits card (using your own Claude Code login, read from your Keychain after macOS asks you once), and the update check. Codex’s plan limits add none: Hoply reads them from Codex’s own session files.

A release build checks for updates at launch and twice a day by fetching https://hoply.dev/appcast.xml, which Cloudflare redirects to the release files on GitHub. Both see that request as any web server would: your IP address and a User-Agent naming Hoply’s and Sparkle’s versions. Sparkle’s optional system profile is not sent. Settings → Updates turns the check off.

There is no other traffic. No analytics beacon, no crash reporter, no error submission, no feature flag service.

Secrets

A model server’s token, password or header values are kept in your macOS Keychain, one item per server. They never appear in Hoply’s settings file, in a URL, or in a log line. A metrics URL on a different host is sent no credentials at all, and redirects are refused rather than followed.

This website

hoply.dev sets no cookies, runs no analytics and loads nothing from a third-party domain: the font is served from here, the styles are in the page, and there is no JavaScript beyond the few lines that remember whether you chose light or dark.

Pages are served by Cloudflare, which records standard request data (IP address, User-Agent, requested path) in its server logs for the time Cloudflare keeps them. There are no forms: the contact address is a mailto link, so writing to us happens in your own mail client.

Children, and the future

Hoply is a developer tool and is not directed at children; we do not knowingly collect anything from anyone. If this policy ever changes in a way that matters, the date above changes and the difference is stated here.

Contact

Questions about this policy, or a request about your data, go to coolcraftcoders@gmail.com. Since we hold no data about you, the honest answer is usually that there is nothing to delete — and we will say so.