Skip to main content
Back to BenAgent

Terms of Service

Terms of Service

Simple terms for an agent-first, local-first macOS app: BenAgent is designed to sit beside your work, not between your work and a hosted BenAgent server.

Updated August 8, 2026
Service model

Local utility, not hosted SaaS

BenAgent does not run a cloud account service or proxy prompts through a BenAgent server. Landing-page analytics are separate from data stored in the macOS app.

BenAgent servers required
0
website analytics from app data
Separate
control configured endpoints
You
No BenAgent server collecting prompts.
Website analytics stay separate from app content.

Local utility, not hosted SaaS

BenAgent is provided as a macOS app. The product is not built around a BenAgent account, workspace, or hosted message server.

Website analytics stay separate

The landing page uses Vercel Analytics for website measurement. BenAgent does not route macOS app content or Clipboard History into that integration.

Your endpoint choices

If you configure an agent provider, you are responsible for that provider and endpoint. BenAgent does not silently reroute it through us.

Agreement to these terms

By downloading, installing, or using BenAgent, you agree to these Terms of Service. If you do not agree, do not use the app.

BenAgent is an agent-first, local-first macOS app for working with agent runtimes. These terms cover your use of the app and the landing page that describes it.

Local-first service model

BenAgent does not require a BenAgent-hosted account, workspace, or message server. The app is designed to run as a local macOS utility.

Your settings, selected provider configuration, and local app state are controlled on your Mac. Model-provider credentials stay with the runtime you control, while BenAgent-owned administrative secrets stay in the macOS Keychain rather than a BenAgent cloud account.

  • No BenAgent server is required for the app shell.
  • No BenAgent prompt proxy is inserted into your agent workflow.
  • Landing-page analytics are separate from macOS app data and configured agent workflows.

Configured agent endpoints

BenAgent can be configured to talk to an agent endpoint that you choose. When you send a message to a configured endpoint, you are responsible for that endpoint, its availability, and its own terms.

BenAgent does not make your configured provider a BenAgent server. The app should send requests directly to the endpoint you configure for that workflow.

Your responsibilities

Use BenAgent lawfully and only with data you have the right to process. Do not use the app to violate another service's terms, compromise systems, or send harmful content.

You are responsible for keeping your Mac, provider credentials, and configured endpoints secure.

Updates and availability

BenAgent may check a configured update manifest and may offer downloads for newer versions. Update availability can change over time.

Because BenAgent is not a hosted SaaS account service, these terms do not promise cloud uptime, hosted storage, or account recovery from a BenAgent server.

Disclaimers and limits

BenAgent is provided as-is, without warranties of uninterrupted operation, fitness for a particular purpose, or error-free output from configured agent providers.

To the fullest extent allowed by law, BenAgent is not liable for indirect, incidental, consequential, special, or punitive damages arising from your use of the app.

Changes

If these terms change, the updated version should be posted with a new updated date. Continued use after a change means you accept the updated terms.