Skip to main content

Security & Privacy

What SmartHopper does with your code, your canvas, your keys, and your data.

Provider code verification​

Provider plugins are .NET assemblies, so SmartHopper gates them cryptographically before use. On Windows a provider must carry the same Authenticode certificate and strong-name key as SmartHopper itself — unsigned third-party DLLs simply can't load. On macOS the signature check is skipped, so third-party assemblies can load but stay unusable until you trust them. Every provider also gets a SHA-256 check against the official published-hash manifest — a changed or unknown file is blocked or warned about depending on your integrity-check mode. Components show a runtime warning when using an unsigned/unverified provider. → Enable & disable providers

Your API keys​

  • Stored encrypted via the OS secure store (DPAPI on Windows, Keychain on macOS) inside SmartHopper.json.
  • Scoped per provider — provider code can only read its own keys.
  • Never written to logs. Never sent anywhere except that provider's API.

What goes to AI providers​

Whatever you wire into an AI call — prompts, canvas content (GhJSON), files you convert, images — is sent to the selected provider's API under their terms. Canvas-reading tools only run because you asked; nothing leaves your machine on its own.

Diagnostics & logging — local only​

SmartHopper writes diagnostic logs to local files on your machine, with configurable level and retention — nothing is sent off-device. Logs are the first thing to check when a component misbehaves (see Troubleshooting).

MCP server posture​

Loopback-only with peer/Host/Origin guards (there is no LAN mode), optional bearer token, read-only tool surface until you opt into editing/view-control, and per-mutation review. → MCP Server component

Web fetching​

web2md/Web2AI respect robots.txt; screenshots may contain project data — be mindful when forwarding captures to external services.