BenAgent
Back to BenAgent

Privacy Policy

BenAgent is designed so your work can stay on your Mac. We do not run a BenAgent server to collect prompts, and we do not send your data to third-party analytics or ad networks.

Privacy stance

No hidden cloud path.

The privacy model is intentionally small: no hosted BenAgent account, no BenAgent prompt server, no third-party tracking pipeline.

No

BenAgent cloud collection

No

third-party tracking or ad pixels

Local

settings and secrets posture

No BenAgent server collecting prompts.
No third-party tracking pipeline.

No BenAgent server

We do not operate a BenAgent service that collects your prompts, documents, transcripts, or conversation history.

No data resale or tracking

We do not sell your data, share it for behavioral advertising, or add third-party analytics to watch product usage.

Secrets stay local

Provider API keys belong in the macOS Keychain. BenAgent does not need a cloud account to hold them for you.

01

Overview

This Privacy Policy explains how BenAgent is designed to handle data. The short version: BenAgent is local-first, does not rely on a BenAgent server, and does not add third-party tracking.

The landing page is also intended to be simple: no account signup wall, no behavioral ad network, and no analytics SDK requirement for the product promise described here.

02

What stays on your Mac

BenAgent settings, selected agent configuration, runtime status, local conversation records, and app preferences are designed to live on your Mac.

Provider secrets should be stored through macOS Keychain. They should not be copied into a BenAgent-hosted account because there is no BenAgent cloud account service required for the app.

No BenAgent account is required to hold your settings.
No BenAgent message archive is created on our server.
No third-party analytics SDK is needed to use the app.
03

What can leave your device

BenAgent itself does not send your prompts to a BenAgent server. If you configure an agent endpoint and choose to send a message, the app should send that request to the endpoint you selected.

That configured endpoint is controlled by you. Review the privacy and security terms for any provider or endpoint you connect.

04

What we do not collect or share

We do not collect prompts, transcripts, documents, API keys, provider responses, or conversation history on a BenAgent server.

We do not sell personal data, share product usage for behavioral advertising, or send your work to third-party analytics services.

05

Permissions

BenAgent may ask macOS for permissions such as microphone or speech access when you enable voice features. These permissions are controlled by macOS and can be changed in System Settings.

BenAgent does not forward raw microphone data to a BenAgent server. Voice features should be treated as local app features plus any system services or configured endpoints you choose to use.

06

Retention and deletion

Because BenAgent is local-first, deleting local app data, clearing local conversations, removing provider credentials from Keychain, or uninstalling the app are the main controls for data retained on your Mac.

BenAgent cannot delete data from an endpoint you configured yourself. Use that provider's own controls for any data sent directly to it.

07

Changes

If this policy changes, the updated version should be posted with a new updated date. Material changes should keep the same plain-language privacy stance visible.