Privacy

Optional telemetry

Help us improve SpawnWP by sharing anonymous aggregate usage data. Telemetry is disabled by default, requires explicit consent and expires automatically after 90 days.

Collected

Operational metadata

A random installation identifier, event timestamp, SpawnWP version, operating system family and version, architecture, enabled feature flags and the aggregate number of current environments. For consents given under notice version 3, also aggregate performance counters (e.g. provisioning durations and failure counts), aggregate feature-usage counters, and rounded machine specifications (CPU count, RAM, disk and Docker space). Data is sent at activation and then weekly.

Excluded

No identity or project content

Payloads exclude domains, request IP addresses, email, usernames, site names, WordPress content, plugins, logs and credentials. The receiver access log is disabled.

Control

Enable, inspect or disable

Use the Updates page or sudo spawnwp telemetry enable. Inspect locally with spawnwp telemetry status and spawnwp telemetry payload. Disabling requests remote deletion and removes the local identifier and queue.

The receiver transforms the random ID with a server-side HMAC and stores only the latest state, not event history. Records not seen for 90 days are deleted. If a deletion request cannot reach the receiver, its record still expires within that period. Public submissions are not authenticated, so aggregate reports are directional rather than authoritative. Endpoint failures never block SpawnWP.