Disable Telemetry and Personalization for Air-Gapped Deployments

By default, n8n sends anonymous usage telemetry to its servers and may display personalization prompts. In regulated environments (healthcare, finance, government) or air-gapped networks, this outbound traffic may violate compliance requirements or simply fail and generate noise in logs.

Real-world example: A financial services company deploys n8n inside a network with strict egress controls. n8n repeatedly attempts to reach telemetry endpoints, triggering firewall alerts and creating false positive security incidents.

# .env configuration for air-gapped / compliance deployments

# Disable telemetry data collection and transmission

N8N_DIAGNOSTICS_ENABLED=false

# Disable the personalization survey on first login

N8N_PERSONALIZATION_ENABLED=false

# Disable version update notifications (requires outbound HTTP)

N8N_VERSION_NOTIFICATIONS_ENABLED=false

# Disable community templates (fetches from n8n servers)

N8N_TEMPLATES_ENABLED=false

# If n8n must not make any outbound connections:

# Also disable external error tracking

N8N_SENTRY_DSN=

# Disable public API if not needed

N8N_PUBLIC_API_DISABLED=true
```text
For Docker deployments, you can also restrict outbound network access at the container level:

```yaml

# docker-compose.yml -- restrict outbound access

services:
  n8n:
    image: n8nio/n8n:latest
    networks:
      - internal
      - proxy  # Only for reverse proxy communication

    # ...

networks:
  internal:
    internal: true  # No outbound internet access

  proxy:
    # Connected to the reverse proxy for inbound HTTPS only

```text
> **Tip: Verify No Outbound Calls**
>
> After configuring these settings, monitor outbound traffic from the n8n container for 24 hours using `tcpdump` or your network monitoring tool. Verify that no connections are attempted to `telemetry.n8n.io`, `api.n8n.io`, or `sentry.io`.

**Related:** [Use Docker Compose with Health Checks for n8n and PostgreSQL](../self-hosting-operations/01-use-docker-compose-with-health-checks-for-n8n-and-postgresql.md) | [Use Path Parameters in Webhook URLs for Dynamic Routing](../webhook-mastery/01-use-path-parameters-in-webhook-urls-for-dynamic-routing.md)