Privacy
Last updated 30 July 2026
Crontender has no servers, no account, and no analytics. Nothing you do in it is sent to us, because there is nowhere for it to be sent to.
What stays on your Mac
Your jobs, their prompts, their run history and your settings are files in
~/Library/Application Support/Crontender. API keys you save for an endpoint
are stored in the macOS Keychain, never in those files and never on a command line. All of it
is yours, readable by you, and deleted when you delete it.
The only connections Crontender itself makes
- Update checks. The app asks
crontender.comfor a small file listing the current version. That request carries nothing about you beyond what any web request unavoidably reveals — your IP address and the version you are asking from. You can turn it off in Settings. - Endpoint checks. Before a job runs, Crontender checks that the model server you configured is answering. That request goes to the address you entered — usually a program on your own machine — and nowhere else.
What the agents do is between you and them
Crontender schedules and runs command-line agents you have already installed and signed into: Claude Code, Codex, opencode, pi. When one runs, it talks to whichever provider you configured it with, under whatever terms you agreed with that provider. Crontender neither adds to nor intercepts that traffic — it starts the tool and records what came back.
If you point a job at a local model server, nothing leaves your machine at all.
What we never collect
No telemetry. No crash reports. No usage statistics. No email address, unless you write to us yourself. There is no analytics library in the app, and you are welcome to confirm that with Little Snitch or the network tools built into macOS.
Changes
If this ever stops being true, this page changes first and the app will say so plainly before the behaviour does.