Privacy & data handling

We collect the account and workspace information you provide, including your name and email, client records, workflow records, requests, approvals, changes, verification notes, client briefs, and evidence you choose to upload or paste.

When you connect another service, we also store the connection details needed to provide that feature, such as the provider, account or workspace identity, authorized scopes, sync status, and encrypted access credentials.

AgentHub reads new messages only from Slack channels that an authorized workspace member explicitly selects and maps to an AgentHub client. The AgentHub Slack app must already be a member of the channel. We do not monitor direct messages, backfill channel history, or read unselected channels for this feature.

A selected-channel message is temporarily stored while AgentHub decides whether it may be a workflow request. If it is not a candidate, the message text is removed after classification. If it is a candidate, the message and an AI-prepared draft remain in the Intake inbox for a person to confirm, edit, or dismiss. Dismissing a candidate removes the stored message text. AgentHub never treats a Slack message as approval and never changes a connected workflow.

AgentHub uses AI to organize submitted evidence, prepare operational recommendations, and identify likely workflow requests in selected Slack channels. AI output is a draft. A person decides whether to create a request, approve a change, or record verification.

Content sent to the OpenAI API is not used to train OpenAI models by default. AgentHub sends Responses API requests with store: false, which prevents application state from being retained for later retrieval. This is not the same as Zero Data Retention: standard API abuse-monitoring logs may retain content for a limited period under OpenAI’s API data controls.

We use a small set of service providers to run AgentHub:

• OpenAIProcesses the content needed for AgentHub’s AI-assisted features.
• SupabaseHosts authentication, application data, and private file storage.
• VercelHosts and runs the application, so submitted data passes through its infrastructure.

If you connect Slack, HubSpot, n8n, Make, or Zapier, data also passes between AgentHub and that provider according to the connection you authorize and that provider’s terms. AgentHub’s current connections are read-only or inbound: the application does not run or edit a connected client workflow.

Connected-service tokens are encrypted before storage. Access to workspace data is limited by workspace membership and role. You are responsible for making sure you have permission to connect a service, select a Slack channel, upload evidence, and process the client data involved.

Do not paste passwords, private keys, API keys, or other secrets into request or evidence fields. AgentHub does not need those secrets to maintain an operating record.

Workspace records and confirmed request evidence remain until they are deleted or the workspace is closed. Some integration records may be retained long enough to preserve an operating history or meet security and legal obligations. Disconnecting a provider stops new access but does not automatically remove records already imported into AgentHub.

To request deletion of your workspace or account data, email info@agenthub.ai. We may need to verify the request and preserve limited records where the law requires it. Self-service workspace deletion is not yet available.

Questions, data requests, or deletion requests: info@agenthub.ai.