Data & privacy · 15 October 2026

A local view.
Clear boundaries.

Overseer observes workloads on your Mac and applies the rules you configure. Its cleanup decisions do not require an LLM or a cloud account.

Local observations

Depending on enabled features, Overseer records application and process identities, executable paths, start times, process resource counters, listening ports, simulator states, workload activity and cleanup results. Settings, recent state and history are saved locally in the app’s Application Support storage.

This information can reveal which tools you use and local project paths. Treat exported diagnostics and screenshots as potentially personal information. Not every process or resource measurement is available through macOS.

Model connections and credentials

Supported integrations query configured local service endpoints. Overseer verifies endpoint ownership before sending credentials or supported unload requests. API tokens are stored in macOS Keychain rather than the app’s plain-text configuration.

The Unsloth adapter keeps model identifiers, status and activity dates. It does not persist prompt/reply previews returned by its activity API. It does not load a model or send a generated test prompt to determine activity. Services you connect have their own data handling and settings.

Model-file evidence

The optional model-worker scan examines accessible open-file listings for this user’s processes. It stores matching file names and process metadata, not model-file contents or command-line arguments. A report is evidence to investigate, not proof that a worker is idle or abandoned.

Actions and access

Discovery does not itself authorize cleanup. Enabled rules can request an app quit, stop an eligible registered process, shut down a simulator, unload supported models or record a reminder. More forceful behavior requires its explicit rule option. macOS protection and the app’s ownership checks limit what can be targeted.

Closing the window leaves the app running; explicitly quitting stops its monitoring. Supported service connections may require a Keychain approval or their own API authorization.

History and retention

Long-term monitor history is stored locally, with a default retention of one year and settings for up to five years. Tracking storage use is visible and a 1 GB warning is available. Retention concerns stored observations; removing a watch or deleting app history does not delete models or project files.

This website

This product page uses locally hosted artwork, styles and scripts, with no analytics, advertising, embedded third-party media or account form. Its interactive rule example runs in your browser using sample values; it has no connection to your apps or models.

The hosting provider may process normal request information, including IP addresses and server logs. Following a link to another site is subject to that site’s own practices.

Support

If you contact the developer, the information you choose to share is used to respond to your request. Please don’t send credentials or private model prompts. For questions, contact Zach about Overseer.