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., "Clusters page viewed")
• How often features are accessed
• Navigation patterns within the application
• Button clicks and user interactions

Performance Metrics:

• Application startup time
• Page load times
• Response times for operations
• Memory and CPU 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")
• Application state at time of error

Feature Usage Patterns:

• Which Kubernetes resource types are viewed most
• How many clusters users typically manage
• Which settings are commonly changed
• Workflow patterns and user journeys

Data NOT Collected

Kunobi never collects:

Personal Information:

• ❌ Name, email, or any identifying information
• ❌ IP addresses or location data
• ❌ 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

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.ninja/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

Changing Telemetry Settings

You can enable or disable telemetry at any time:

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

For detailed instructions, see Settings: Telemetry.