Blaigent MCP privacy

Applies when you connect Blaigent via Model Context Protocol (OAuth Connect or API key).

What we process

Tool calls are scoped to the organization you authorize. Typical data includes order identifiers, ticket content, knowledge-base queries, and message drafts you ask the agent to produce.

Auth tokens

OAuth access tokens (mcpat_) and API keys (blgmcp_) identify your organization. Tokens are hashed at rest. Revoke keys in MCP Integrations; OAuth refresh tokens rotate on use.

What we do not do

We do not sell MCP traffic, train public models on your tool payloads, or move money from read-only or approval-gated tools without your existing Blaigent refund/consent controls.

Controllers & contact

See the site-wide Privacy Policy and Security pages. Security reports: /.well-known/security.txt.