Privacy and telemetry

Everything is local by default. Nothing is recorded, staged, or sent until you choose it, and the exact contents of a payload are printed below so the claim is checkable.

What stays local

The trial clock, the license file, state, logs, and verdict history live in your user data directory. The software does not send anything on its own. It has no remote patch channel and no remote execution channel into your machine, by design.

The support report is scrubbed, and even then it goes nowhere unless you attach it in your own mail app and press send. The one-button diagnostic send transmits nothing by itself. What leaves your machine is always your choice.

Telemetry is off until you turn it on

Telemetry is opt-in, off by default. Nothing is recorded, staged, or sent until you run cyberkaze telemetry on. Before you consent, cyberkaze telemetry preview prints exactly what a payload would contain, and every payload passes a scrub check before it can be sent. A payload containing any of the never-collected items is rejected outright.

What a payload carries

Version, platform, arch, CPU model string
Load averages, swap percent, verdict counts and reason kinds
Thermal truth, command-use counts, error codes
doctor PASS / WARN / FAIL kinds

What it never carries

File paths, user names, hostnames, IP or MAC addresses
Process command lines, model names, model hashes
Any content, any prompt, any document text

cyberkaze telemetry off stops all sends and deletes any staged payload. Sends are limited to at most once per day. The telemetry endpoint is a placeholder until the service exists, so as of this writing nothing has ever been sent anywhere.

The same promise, page by page.

The full terms are on the terms page, and the front desk can answer questions about any of it.