Agentlas connector

Hephaestus Network Connector Privacy Policy

Last updated: July 15, 2026

1. Scope

This policy explains how Agentlas handles information when you use the Hephaestus Network remote MCP connector with Claude or another MCP client.

The connector routes requests to public Agentlas Hub agents, returns BYOM runtime bundles, reads allowlisted package files, and resolves required plugins.

2. Information processed

Public search tools process the task text or capability keywords you provide in the tool arguments.

Authenticated runtime bundle calls process your Agentlas account and workspace identifiers, the selected agent slug, requested version, and tool call metadata.

The connector may process standard security metadata such as IP address, request time, user agent, rate-limit keys, and authentication state.

3. Information stored

Agentlas does not store Claude conversation text through this connector.

Runtime bundle calls may store minimal invocation metadata such as agent slug, manifest id, package version, caller workspace, status, reason, and timestamp for security, billing, abuse prevention, and operational auditing.

For subscription offers, Agentlas stores plan, trial or introductory-offer status, billing dates, and prior-subscription history needed to enforce one first-account offer.

Search and plugin-resolution calls are designed to operate without storing raw prompts as product data.

4. Use of information

Agentlas uses connector information to provide the requested MCP tools, authenticate users, enforce rate limits and credit gates, troubleshoot failures, prevent abuse, and maintain service reliability.

Agentlas may use aggregated or de-identified operational metrics to improve routing quality and connector reliability.

5. Third-party processing

Claude and Anthropic process connector requests according to their own terms when you use this connector in Claude.

Agentlas uses infrastructure, authentication, database, analytics, email, and support providers as needed to operate the service.

6. Retention

Authentication records and invocation metadata are retained for as long as needed to provide the service, maintain security, comply with legal obligations, resolve disputes, and support billing or abuse investigations.

Operational logs are retained for a limited period appropriate for security and reliability monitoring.

7. User choices

You can disconnect the connector in Claude and revoke Agentlas access from your Agentlas account.

You may contact Agentlas to request access, correction, deletion, or export of personal information where applicable law provides those rights.

8. Security

The connector uses HTTPS and OAuth Bearer tokens for authenticated tools.

Runtime bundles are compiled from public Hub packages and return compact execution context rather than raw full package dumps.

Allowlisted file reads are controlled by the package manifest and redact secret-like values.

9. Contact

For privacy, support, or security questions, contact appbridge@appbridge.co.kr.

Hephaestus Network Connector Privacy Policy - Agentlas