This page covers data handling for the Black Ice MCP connector — the remote Model Context Protocol server at https://black-ice.ai/mcp that AI clients (Claude, Anthropic-hosted assistants, IDEs, custom agents) connect to via OAuth 2.1. For everything else, see the main Privacy Policy.
Controller & contact
Black Ice is the data controller for information processed through the connector. Reach the team at support@black-ice.ai or, for security disclosures, security@black-ice.ai.
What the connector accesses
- Concepts, terms, classes, markets and approved translations in the workspace you authorize — read-only. A workspace owner or admin can optionally turn on candidate suggestions (the
suggest_candidates tool), which only add unconfirmed entries to the Candidates review queue. It is off by default and cannot approve, change or delete governed terminology. - Workspace metadata required to scope responses (workspace id, plan tier, source locale).
- Tool invocation metadata: tool name, timestamp, response size. Tool arguments are not logged. If your workspace has turned on candidate suggestions, terms sent through
suggest_candidates are stored as review-queue entries, because that is the purpose of the tool.
What the connector never accesses
- Other workspaces you are not authorized for (enforced by row-level security).
- Authentication credentials, signing secrets, billing details, or admin audit logs.
- Personally identifiable information about your teammates beyond display name.
OAuth tokens & DCR
- Authorization uses OAuth 2.1 with PKCE; we support Dynamic Client Registration (RFC 7591) so clients like Claude can self-register.
- Access tokens are short-lived (1 hour) bearer tokens; refresh tokens rotate on every use.
- Tokens are scoped to a single workspace chosen at consent time. They cannot pivot across workspaces.
- Tokens are stored hashed at rest. We never share them with model providers or third parties.
- You can revoke any authorized client at any time in Settings → Integrations.
Sub-processors involved in MCP traffic
- Supabase (EU region) — database, edge runtime, OAuth token storage.
- Cloudflare — TLS termination and DDoS protection for
black-ice.ai. - Full live list: Sub-processors.
Retention
- OAuth authorization records: kept until revoked, then deleted within 30 days.
- Connector request logs (no payloads): 30 days, then purged.
- Underlying ontology data follows the retention rules in the main Privacy Policy.
Your rights
GDPR/UK-GDPR rights (access, rectification, erasure, portability, objection) apply to connector data exactly as they do to the rest of the platform. See the main Privacy Policy for how to exercise them.