Privacy policy

The Bench is an AI-agent workspace operated by Brownmine ("we", "us"). Organizations create a Bench workspace, and their members work with AI agents through the Bench web application and, optionally, through the Bench app for Slack. This policy describes what data those products handle and why.

• Account information — your name, email address, and sign-in credentials. Passwords are stored only as salted hashes; passkeys are stored as public keys.
• Workspace information — your organization's name, membership list, and each member's role.
• Conversations and tasks — the messages you exchange with agents, the agents' replies, and the documents agents generate for you. These are retained so conversations keep their context and your files stay available to you.
• Files you upload — attachments you share with an agent are stored in your workspace's private storage so the agent can read them and you can retrieve them.
• Connected-service credentials — when you connect a service (Slack, Google, GitHub, or apps connected through Pipedream), we store the OAuth tokens needed to act on your behalf. Tokens are encrypted at rest and are used only for the actions you ask agents to perform.
• Technical logs — operational logs (request metadata, errors, task activity) used to run and secure the service.

When your organization installs the Bench app in a Slack workspace:

• The bot receives only messages addressed to it — direct messages, @-mentions, and replies in threads it is part of, including files shared in those messages. It does not read other channels or conversations.
• Messages sent to the bot are processed exactly like messages in the Bench web chat: they become part of a conversation with your organization's agents and are retained as described above.
• We store your Slack workspace identifier and the bot token Slack issues at install time (encrypted at rest) so the bot can post replies and upload agent-generated documents into your threads.
• Only Slack users who are also members of your Bench workspace can use the bot. Anyone else receives a decline message and their request is not processed.
• Uninstalling the app from Slack (or disconnecting it on the Bench Connectors page) revokes the bot's access immediately.

• To provide the service: routing your messages to AI agents, maintaining conversation context, generating and delivering documents, and performing the actions you request in connected services.
• To enforce workspace membership and role permissions.
• To respond to support requests.
• To secure, debug, and operate the platform.

We do not sell your data, and we do not use your data for advertising.

To generate agent responses, the content of your conversations (and files you share with agents) is sent to third-party AI model providers — currently OpenAI and Anthropic — under their respective API terms. We send only what is needed to answer the request, and we do not use your content to train models of our own.

We share data only with the service providers required to operate the platform:

• Cloud hosting and storage (Amazon Web Services).
• AI model providers (OpenAI, Anthropic) — see above.
• Slack — when your organization installs the Slack app, the bot's replies and uploaded documents are delivered through Slack's APIs.
• Pipedream — when you connect external apps through the connector marketplace, requests to those apps are routed through Pipedream's connect proxy using the account you authorized.
• Services you explicitly connect (for example Google Drive or GitHub) — accessed only with the OAuth grant you approve, for the actions you request.

• Conversations, files, and workspace data are retained while your workspace is active so agents keep their context and your documents remain available.
• Disconnecting an integration stops all further access to it; uninstalling the Slack app revokes the bot token.
• To delete specific data, your account, or an entire workspace, ask your workspace administrator or contact us through the support page.

• All traffic is encrypted in transit with TLS.
• OAuth tokens and connected-service credentials are encrypted at rest; passwords are stored only as salted hashes.
• Access to workspace data is scoped by organization membership and role — members of one workspace cannot read another's data.

If this policy changes in a way that affects how your data is handled, we will update this page and its "Last updated" date. Questions or requests — including data deletion requests — can be sent through the support page.