Skip to main content

Kubezilla Desktop Privacy Policy

This Privacy Policy describes how the Kubezilla Desktop application ("the App") processes personal data. It applies only to the App.

Who We Are

The controller of personal data processed through the App is the operator of Kubezilla Desktop. You can reach us at the contact address listed at the bottom of this page.

What We Collect

Update Checks

When automatic updates are enabled, the App contacts our App Manager service to check whether a newer version is available. The request may include or reveal:

  • IP address
  • app identifier and app version
  • operating system platform
  • CPU architecture

Purpose: provide updates, security fixes, and release information.

Session Initialization

When telemetry, feedback, or crash reporting is used, the App creates a session with our App Manager service. The session request may include:

  • operating system platform
  • CPU architecture
  • operating system version
  • app version
  • a stable hashed device identifier derived from the device or operating system, where available

Purpose: operate App Manager features, associate telemetry and diagnostics with an app session, prevent abuse, and understand app compatibility.

Telemetry and Usage Metrics

Telemetry is used to understand how the App is used and to improve reliability and product quality. Depending on your settings, telemetry may include:

  • app opened / app closed events
  • session duration
  • feature usage events, such as opening settings, using port forwarding, opening logs or shell views, using PVC mount features, or opening feedback
  • selected high-level Kubernetes resource kind, where relevant
  • counts, such as number of open windows or selected items
  • app CPU usage
  • app memory usage

Telemetry does not intentionally include Kubernetes resource contents, kubeconfig contents, Kubernetes secrets, workload YAML, terminal contents, log contents, or PVC file contents.

You can disable telemetry in the App settings.

Crash Reports

If the App crashes, it may save a crash report locally. On the next launch, the App may offer to send the report to us. Crash reports are submitted only when you choose to send them.

A crash report may include:

  • app version
  • operating system and CPU architecture
  • crash timestamp
  • panic or error message
  • source location
  • stack trace / backtrace
  • optional text you enter describing what happened

Crash reports may sometimes contain file paths, resource names, or other information present in diagnostic output.

Purpose: diagnose and fix crashes.

Feedback and Attachments

If you send feedback from inside the App, we collect:

  • the feedback text you enter
  • optional image or video attachments you choose to upload
  • app session identifier

Supported attachment types may include images and videos such as PNG, JPEG, GIF, WebP, MP4, WebM, and MOV.

Do not include secrets, credentials, customer data, or confidential cluster information in feedback or attachments unless you intend to share that information with us.

Purpose: customer support, troubleshooting, and product improvement.

Data Stored Locally on Your Device

The App stores configuration and state locally on your device. This information is not normally sent to our App Manager service, but it may be used by the App to connect to your infrastructure.

Local data may include:

  • selected kubeconfig, context, namespace, and resource kind
  • local kubeconfig paths and macOS security-scoped bookmarks
  • inline kubeconfig YAML, if you choose to paste one into the App
  • SSH remote names, addresses, remote kubeconfig paths, and tunnel settings
  • SSH authentication settings, which may include passwords, key file paths, and optional key passphrases, depending on the method you choose
  • UI preferences, window sizes, theme, hidden columns, favorites, and resource groups
  • telemetry and automatic-update settings
  • EULA acceptance state
  • MCP server settings
  • MCP bearer token, if the MCP feature is enabled
  • locally saved crash report files until removed or overwritten

You are responsible for protecting access to your device and user account, especially if you store kubeconfigs, SSH credentials, or inline cluster configuration in the App.

MCP Server

If you enable the MCP server feature, the App exposes selected Kubernetes operations over a local HTTP interface protected by a bearer token.

By default, the MCP server is intended to bind to localhost. If you change the bind address, other software or devices may be able to reach it depending on your network and firewall settings.

The MCP token is stored locally on your device. MCP clients that have the token may be able to request Kubernetes data or perform supported operations through the running App.

What We Do Not Do

  • We do not sell personal data.
  • We do not use advertising cookies in the App.
  • We do not intentionally collect Kubernetes secrets, kubeconfig contents, workload manifests, terminal contents, logs, or PVC file contents through telemetry.
  • We do not use App telemetry for automated decision-making that produces legal or similarly significant effects.

Where GDPR applies, we rely on the following legal bases:

  • Contract / requested service: to provide App functionality such as update checks, feedback submission, crash report submission when requested, and App Manager session handling.
  • Legitimate interests: to operate, secure, debug, and improve the App, including basic diagnostics and abuse prevention.
  • Consent, where required: for optional telemetry or other optional processing controlled by App settings.

You may disable telemetry in the App settings. Crash reports and feedback are sent only when you choose to submit them.

Data Processors and Transfers

Personal data submitted through App Manager features is processed by infrastructure providers used to operate our services.

Where data is transferred outside the European Economic Area, we use appropriate safeguards such as adequacy decisions, the EU-US Data Privacy Framework, or Standard Contractual Clauses where applicable.

Retention

We retain App telemetry, metrics, and diagnostic data only as long as necessary for the purposes described above, and no longer than 12 months unless a longer period is required for security, legal, or abuse-prevention reasons.

Feedback and crash reports may be retained for as long as necessary to handle support requests, investigate issues, improve the App, and maintain internal records.

Local App configuration remains on your device until you delete it or uninstall/remove the App data.

Your Data-Protection Rights

You have the right to:

  • access a copy of your personal data
  • correct inaccurate data
  • erase your data ("right to be forgotten")
  • restrict or object to processing
  • withdraw consent where processing is based on consent
  • lodge a complaint with your national data-protection authority

To exercise these rights, contact us using the details below.

Contact

For privacy questions or data-subject requests, email the address shown on the Download page or open a ticket in our support channel.