Skip to main content

Privacy Policy — Monarch Connect

Effective Date: March 31, 2026 Last Updated: March 31, 2026

Mono Labs R&D LLC 28 Geary St STE 650, Suite 568 San Francisco, CA 94108 Contact: legal@mono-labs.org

Monarch Connect is a Tauri 2 desktop application for monitoring and managing blockchain validator nodes remotely via SSH. Most data is stored locally on your device. One optional feature (Claude AI chat) sends operational data to a third-party API.

Data Stored Locally​

All of the following is stored exclusively on your device and never transmitted to Mono Labs:

  • Server connection profiles — host, port, username, SSH key file path, network label, tags
  • Command history — last 500 entries, in-memory only, cleared on app restart
  • Application settings — UI preferences, feature toggles
  • MCP server configuration — tool definitions and authorization settings
  • Claude API key — stored in your operating system's keychain (macOS Keychain, Windows Credential Manager, or Linux Secret Service), not in plaintext files

Data We Do NOT Collect​

  • SSH private keys (only the file path is stored)
  • Server passwords (used for SSH authentication only, zeroed in memory after use)
  • Keyring passwords (Monarch Connect does not handle keyring passwords — transaction commands are not available)
  • Blockchain transaction data
  • Personal information (name, email, location)
  • Analytics, telemetry, or usage metrics

Third-Party Data Sharing: Anthropic (Claude AI)​

Monarch Connect includes an optional AI chat sidebar powered by Anthropic's Claude API. This feature is only active when:

  1. You have opened the Claude chat panel, AND
  2. You have configured your own Anthropic API key in Settings

What is sent to Anthropic​

When you interact with the Claude chat:

  • Your messages typed into the chat
  • Server context — server labels, IDs, and network names (included in the system prompt for diagnostic accuracy)
  • Command log summary — the last 10 command names with exit codes (from the command log, not from interactive terminal sessions)
  • Tool results — output from diagnostic tools: node status, logs, health check results, peer information

What is blocked from Anthropic​

The following commands are blocked from execution through the AI:

  • Key management: keys create, keys recover, keys delete, export-key, import-key
  • Transactions: stake delegate, stake unbond, stake redelegate, gov vote, gov deposit, validator register, validator edit, validator unjail, rewards claim

If Claude attempts to run any of these commands, it receives an error message explaining that the command must be run on the server directly.

What is redacted before sending​

All command output and log data passes through a redaction layer before it reaches the frontend or Claude. The following patterns are stripped:

  • Passwords and passphrase references
  • Mnemonics and seed phrases
  • Private key material (including priv_validator_key)
  • Hexadecimal strings longer than 64 characters (potential private keys)
  • Key file references

How data is transmitted​

  • Data is sent directly from your device to Anthropic's API at api.anthropic.com
  • Your own API key is used for authentication
  • Mono Labs does not receive, proxy, or store any of this data
  • The anthropic-no-log: true HTTP header is sent with every request, which opts out of Anthropic's standard 30-day safety data retention
  • Anthropic's API data is not used for model training (see Anthropic's Usage Policy)
  • Anthropic maintains SOC 2 Type II certification

Interactive terminal isolation​

The interactive terminal (PTY mode) in Monarch Connect is a direct SSH channel between you and your server. Claude has zero visibility into interactive terminal sessions — no input, output, or keystrokes are logged or accessible to any AI feature. This is the recommended mode for running sensitive operations.

MCP Integration​

When configured, Monarch Connect can expose monitoring tools to external Claude clients (Claude Code, Claude Desktop) via the Model Context Protocol (MCP). The same data categories and redaction rules apply:

  • Only monitoring and diagnostic tools are exposed
  • Transaction and key management commands are not available
  • Output is redacted before returning to the MCP client
  • You control which servers and tools are authorized in the MCP configuration

No Analytics or Telemetry​

Monarch Connect does not include any analytics, crash reporting, or telemetry of any kind. There are no user accounts, no remote configuration, and no phone-home behavior. The only network requests are:

  1. SSH connections to servers you explicitly configure
  2. Claude API requests when you actively use the AI chat feature
  3. Update checks (can be disabled in Settings)

Contact​

For privacy-related questions or concerns about Monarch Connect: