Privacy & data handling
Updated September 8, 2026
Who we are
AgentHub AI LLC, a limited liability company registered in Florida, operates agenthub.ai and the AgentHub application. This notice covers information handled through both services.
We use information to provide accounts and workspaces, maintain client operating records, process subscriptions, respond to inquiries, protect the service, and understand use of the public website.
What we collect
We collect the account and workspace information you provide, including your name and email, client records, workflow records and safe structural details such as step names and provider types, requests, approvals, changes, verification notes, client briefs, and evidence you choose to upload or paste. Step and node names can contain client information and are treated as private workspace data.
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.
If a workspace member emails a published client brief through AgentHub, we store the recipient name and email, the email subject, who initiated the send, the provider message reference, and the send status as a delivery receipt.
When an account owner receives the new-account onboarding sequence, we store the message type, frozen message copy, recipient address, send status, provider message reference, and whether the owner stopped the sequence. The messages are text-only, and their links are not routed through email open or click tracking. AgentHub does not add open or click tracking.
If a workspace member creates a client approval link, we store a frozen copy of the requested scope, an expiration time, and the time the approval page is first opened successfully. The open time does not identify the person who opened the page. If someone responds through that link, we store the name they provide, an optional email address, their decision, any response note, and the response time. The raw link token is not stored; only its security hash is retained. We do not collect an opener identity, IP address, device string, or open count for the approval record.
If a workspace member creates a standing client request link, we store the client it belongs to and the link’s security hash. A person using that link provides a name, an optional email address, the requested change, and a submission time. The submission remains a draft until a workspace member confirms or dismisses it. Dismissing it removes the submitted name, email, and request text. The raw link token is not stored.
When a workspace reaches a managed-client limit, we store the plan, managed-client count, limit, and the action taken, such as starting checkout or choosing managed clients. If you answer the optional plan feedback question, we also store the reason you provide. AgentHub does not automatically include client names, request text, or other operating-record content in these plan events.
Website inquiries, cookies, and security
Our contact form collects your name, work email, optional company or agency name, selected topic, and message. We use this information to respond to your inquiry. Messages pass through Lovable’s connector gateway and Resend to our inbox.
The application uses cookies to maintain your signed-in session and browser storage to remember interface preferences. Blocking required cookies may prevent sign-in from working.
The public website uses Google Analytics through Google Tag Manager to measure visits and interactions, including call-to-action clicks. Analytics can collect browser and device information, approximate location, referral information, and pages visited, and uses cookies to distinguish visits. You can manage cookies in your browser and use Google’s Analytics opt-out browser add-on.
Public website fonts load from Google Fonts. Authentication pages use Cloudflare Turnstile to help detect automated abuse. These providers receive connection or browser information needed to deliver their services. Hosting and security providers may also process technical logs. The approval-record limits described above do not mean that infrastructure providers never process IP addresses.
Slack monitoring
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.
How AI is used
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.
Service providers
Providers used by the website and application include:
- 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.
- ResendDelivers public-site contact inquiries, private new-account alerts, the short account-owner onboarding sequence, and published client briefs when an authorized workspace member chooses Send. Resend receives the recipient address and message content. Onboarding and brief emails are text-only, and their links are not routed through email open or click tracking. AgentHub does not add open or click tracking.
- LovableProvides the public website platform and the contact-form connector that routes inquiries to Resend.
- GoogleProvides public-website analytics, tag management, and web fonts.
- CloudflareProvides Turnstile protection on authentication forms.
- StripeProcesses paid-plan checkout, subscription billing, and payment account management. AgentHub does not store full card details.
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.
Email choices
AgentHub may send a short sequence to help a new account owner test the product and share feedback. Every message in that sequence includes a way to stop the remaining onboarding emails. Stopping the sequence does not stop account confirmation, security, billing, client brief, or other messages you explicitly request.
Credentials and access
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.
Keeping and deleting data
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.
Contact
Questions or requests to access, correct, or delete your information: info@agenthub.ai.
AgentHub AI LLC7121 W Craig Rd
Ste 113 PMB 1128
Las Vegas, NV 89129
United States
This notice describes our current data practices. It is not a data-processing agreement. We update this page when our practices change.