Licensing Payload Disclosure

1. Heartbeat Request Payload Fields

In heartbeat mode (Team plan), periodic 7-day license validation requests sent to https://api.zimmerapp.co/v1/license/verify contain exactly five metadata fields:

• licenseKeyId: The customer's activation key identifier (e.g. lic_live_...).
• instanceId: A randomly generated UUID identifying the server installation instance (e.g. inst_...).
• nonce: A single-use cryptographic token generated per-request to prevent replay attacks.
• appVersion: The release version of the running Zimmer Server (e.g. 0.3.50).
• platform: The host operating system and architecture tuple (e.g. darwin-arm64).

2. What Is Never Transmitted

To maintain complete data sovereignty, Zimmer Server never collects or transmits telemetry, content, or user metrics. Specifically, the heartbeat payload never contains:

• User identities or email addresses
• Document, prompt, chat, or index content
• Model names, weights, or inference parameters
• File paths, directory structures, or file names
• Hostnames, IP configurations, or internal network topology
• Seat usage counts, active user counts, or session metrics

3. Air-Gapped Enterprise Deployments

For regulated environments and high-security air-gapped deployments, Zimmer Enterprise supports offline signed license files. In offline mode, licensing verification is performed 100% locally with Ed25519 public key verification and makes zero outbound network calls.