Skip to content

Security & Data

How AgentHub protects access to your work.

Workspace access and purpose-specific sharing links help you control who can see your work. This page explains how each kind of access works.

Control boundaries

Access stays tied to the record and the decision.

AgentHub uses workspace access controls for signed-in members and purpose-built links for clients.

Workspace access
Signed-in users work inside workspace-scoped records. Database policies and ownership checks restrict access to the active workspace.
Secure approval links
Unanswered approval links expire after 14 days. Each link accepts one client response and can be revoked or replaced. AgentHub creates the link. It does not send it automatically.
Human control
AgentHub does not automatically approve, implement, verify, publish, send, or edit a client automation. Those decisions remain with the people responsible for the work.

Client approval links

Clients approve through a link, without an account.

The link lets its holder review one frozen request and respond once. AgentHub records the named response, but the link itself is not an electronic signature or proof of the viewer’s identity.

Credential handling
The secret stays in the URL fragment. AgentHub stores only its SHA-256 hash, not the raw token.
Opening the link
The record can show when the approval page was first opened successfully. It does not identify who opened it and does not store an IP address, user agent, or open count for that event.
Privacy on the approval page
The approval page is configured as no-index, no-store, and no-referrer, and it does not load third-party analytics.
Invalid links
Revoked, replaced and invalid links, and unanswered links that have expired, do not disclose the client, workspace, or requested scope. An answered link stays readable and shows the frozen scope and the response.

Data boundaries

Record enough to support the decision.

Imported workflow snapshots contain structural information. They exclude credential fields and execution payloads.

Workflow snapshots
Snapshots exclude credentials, node parameters, field values, and execution payloads.
Implementation evidence
Evidence stores a link and reference. AgentHub does not ingest the linked source code.
Approval records
Approval records preserve the decision while keeping missing identity evidence visible.

Your content

Questions about what you share.

Still have a question? Ask about security.

What happens to an email I forward?

Only what you forward, and only from you. Each workspace has a private forwarding address. A forwarded email becomes a draft only when it comes from the email address of an active workspace member; anything else is dropped without a reply. A forward that fails its sender domain’s email authentication is dropped too. One whose sender can’t be confirmed still becomes a draft, marked Sender not confirmed.

AgentHub stores the forwarded text, capped at 12,000 characters, the subject, the sender named in the forwarded header, the forwarding member’s name and email address, the message ID and the result of the sender check. It does not connect to your mailbox and reads nothing you do not forward.

Dismissing a draft removes its text. The record keeps who forwarded it and when, the original sender’s address, and who dismissed it.

Who can open my conversations with AgentHub?

Other members and the workspace owner cannot open your conversations with AgentHub. What you choose to share into a job, and any request you create from a draft, becomes part of the workspace’s records.

Security status

This page is not a certification.

It does not attest to SOC 2, ISO, privacy-law, or industry compliance. It describes how AgentHub works today and will be updated as the product changes.

Workspace controls reviewed

Report a concern