Telemetry

Kunobi includes optional telemetry to help improve the application through anonymous usage statistics. This page explains what telemetry is, what data is collected, and how to enable or disable it.

First Launch Prompt

When you first launch Kunobi, you'll be prompted to enable telemetry:

You can choose to:

Enable Telemetry: Help improve Kunobi by sharing anonymous usage data
Disable Telemetry: Use Kunobi without sending any data

This choice can be changed at any time in Settings.

What is Telemetry?

Telemetry is the automatic collection of anonymous usage statistics and performance metrics. It helps the Kunobi team understand how the application is used and identify areas for improvement.

Key principles:

✅ Completely Anonymous: No way to identify individual users
✅ Opt-In: Disabled by default, you choose to enable it
✅ Transparent: Clear documentation of what's collected
✅ Privacy-First: No sensitive data ever leaves your machine

Data Collected (when enabled)

When telemetry is enabled, Kunobi collects:

Usage Statistics:

Which features are used (e.g., "connected to a cluster", "opened a terminal")
How often those features are used, and whether it's the first time in a session
Which extensions are installed or removed
Whether the guided tour was completed or skipped

Performance Metrics:

Application startup time
How long the main window takes to become ready
Response times for operations (Kubernetes API calls, extension tools, terminal sessions)
Memory usage of the app itself

Error Logs:

Crash reports with stack traces
Error messages (sanitized of sensitive data)
Failed operations (e.g., "Failed to connect to cluster")
Which command failed, and a coarse category for the failure

Feature Usage Patterns:

Which Kubernetes resource kinds are acted on most
How many cluster connections are open at once
Whether keyboard shortcuts have been customized (a count only, never which keys)
Which first-run milestones you reach, such as connecting your first cluster

Basic Context:

App version and release channel
Your license tier (for example free or Pro), never a license key or account ID
Operating system and processor architecture

Data NOT Collected

When telemetry is enabled, Kunobi never collects:

Personal Information:

❌ Name, email, or any identifying information
❌ IP addresses or location data - see Downloads and Update Checks for the country our download service records
❌ Computer name or user account details
❌ Any information that could identify you

Cluster Data:

❌ Cluster credentials or kubeconfig contents
❌ Kubernetes manifests or resource definitions
❌ ConfigMaps, Secrets, or any cluster resources
❌ Pod logs or application data
❌ API server endpoints or cluster metadata

Sensitive Information:

❌ Environment variables
❌ File paths containing sensitive names
❌ Command arguments or user input
❌ Network traffic or requests to your clusters

Downloads and Update Checks

Downloading Kunobi, checking for updates, and installing extensions are separate from telemetry. They are ordinary web requests to our download service, they go out whether telemetry is on or off, and they never travel through the telemetry endpoint.

Those requests carry the app version, platform, architecture, and release channel needed to serve the correct build. As with any web request, the service sees the network address the request came from, and it records the country that address resolves to, so we can see roughly where Kunobi is being downloaded. City and region are never recorded, and nothing about your clusters or your activity inside the app travels on these requests.

For how that data is handled and retained, see the privacy policy.

Why Enable Telemetry?

Telemetry helps us understand which features are actually used, catch crashes and performance regressions early, and prioritize what to build next. Without it, we're guessing. With it, we can fix bugs before they spread and focus engineering time on what matters to real workflows.

Your Privacy Matters

Anonymity

All telemetry data is completely anonymous:

No way to trace data back to individual users
Aggregated with data from thousands of users
No persistent identifiers or tracking cookies
Each session uses a random ID that changes

Transparency

You can see exactly what data is collected:

Clear documentation of what we track (see above)
Open about what's collected and why
No hidden data collection or backdoors
Regular updates to this documentation

Control

You have complete control:

Telemetry is opt-in, not opt-out
Can be disabled at any time
No penalties or reduced functionality when disabled
Choice is respected - no nagging or dark patterns

For the full pre-release privacy policy, see https://kunobi.com/privacy/app/prerelease.

Data Usage

The collected telemetry data is used solely to:

Improve Kunobi's features and performance
Fix bugs and stability issues
Guide product development decisions
Understand user needs and workflows

The data is never:

Sold to third parties
Used for advertising or marketing
Shared outside of Zondax AG
Used to identify individual users
Combined with other data sources

Technical Details

Data Transmission

Sent over HTTPS to Zondax AG servers
Batched to minimize network usage
Sent in the background without affecting performance
Failed transmissions are silently dropped (no retries that could impact performance)

Storage

Stored securely on Zondax AG infrastructure
Access restricted to development team only
Retained for analysis purposes only
Automatically deleted after retention period

No Cluster Data

Your kubeconfig files never leave your machine
All cluster operations happen locally
Kubernetes resources are never transmitted
Cluster credentials remain on your machine only
API requests to clusters are never logged

Crash Reports

If Kunobi crashes, a full crash report is saved locally on your machine. The next time you launch the app, a dialog asks what to do with it:

Send full report transmits the full crash report (including a stack trace) to help us diagnose the problem, then deletes the local file.
Dismiss deletes the local report without sending anything.
The X in the corner (Close - decide later) hides the dialog but keeps the local file, so you're asked again on the next launch.

The full report is transmitted only when you click Send full report - an explicit action that works regardless of your telemetry setting. Separately, if telemetry is enabled, an anonymous crash signal (no stack trace or personal data) is sent automatically on the next launch; with telemetry disabled, no automatic signal is sent.

Changing Telemetry Settings

You can enable or disable telemetry at any time:

Open Settings (⌘+, or from the sidebar)
Navigate to the Privacy section
Find Telemetry: Enable
Toggle the switch on or off

For detailed instructions, see Settings: Telemetry.