A narrow relay with explicit boundaries.

BotLatch is designed to expose only a public bot ID to the visitor. The production n8n destination remains encrypted at rest and is used only by the server-side relay.

Built-in controls

• Exact origin allowlists for configuration, preflight, and message requests.
• HTTPS-only destinations, with private and reserved network ranges rejected by default.
• DNS resolution checked before outbound connections, with redirects and cookies disabled.
• Per-IP and per-session rate limits, request-size limits, and upstream timeouts.
• Encrypted webhook destinations and persistent ASP.NET Core data-protection keys.
• Hashed report links, revocation, expiry, owner-only administration, and closed registration.
• Minimal logs that exclude message bodies, webhook URLs, license keys, and report tokens.

Deployment boundary

The operator is responsible for TLS, host patching, Docker access, backups, origin configuration, and the security of the connected n8n workflow. BotLatch does not make an unsafe workflow safe.

Report a vulnerability

Send security reports to support@botlatch.com. Do not open a public issue. In the first report, do not include a secret, report token, webhook URL, transcript, client name, visitor content, database, backup, license key, or Data Protection key. Include the affected BotLatch version, deployment shape, safe reproduction steps, expected and actual behavior, and impact. Use synthetic data.