Privacy Policy

What we collect

Account information. When you sign up we receive your name, email address and profile image from your identity provider (Google, GitHub, or an email verification code). If you create an organization, we store its name and the membership and role of each user in it.

Cluster data. When you ask a question, or an alert triggers a diagnosis, our agent runs read-only commands against your cluster and receives their output — pod and namespace names, events, resource definitions and log excerpts. This is the most sensitive data we handle, and it is treated differently from everything else: see retention.

Configuration. Cluster names and identifiers, the API keys and executor tokens we issue you, webhook identifiers, and any integrations you connect. Credentials for connected integrations are stored encrypted.

Usage and diagnostics. We use a product analytics service to understand how the product is used and to capture errors. This includes pages viewed, features used, approximate location derived from IP address, and browser and device information. See analytics and session recording for the specifics, including what we do not record.

Billing. If you subscribe, our payment processor collects your payment details directly. We never see or store your full card number.

Why we use it

We use this data to operate the service, to diagnose your clusters when you ask us to, to bill you if you subscribe, to respond to support requests, to keep the service secure and enforce plan limits, and to improve the product.

We do not sell your data, and we do not use your cluster data to train models. Where the law requires a legal basis, we rely on performance of our contract with you for operating the service and billing, and on legitimate interests for security and product improvement.

Who we share it with

We share data with the sub-processors listed on the security page — hosting, database, authentication, payments, analytics and the model provider that performs diagnosis — and with no one else, except where we are legally required to, or where it is necessary to protect our rights or the safety of others.

Because diagnosis is performed by a large language model, cluster output is sent to a model provider. The security page names that provider and states exactly what it may do with the content.

How long we keep it

• Diagnosis conversations and cluster output: 7 days after the last message in the conversation, then automatically deleted. These are never written to our database.
• Account, workspace and configuration records: for as long as your account exists, and deleted when you delete it.
• Billing records: retained as long as tax and accounting law requires, typically seven years.

Analytics and session recording

We use PostHog for product analytics. On our marketing pages this includes session recording — a replay of the pages you visit — which helps us see where the product is confusing.

Session recording is disabled inside the signed-in dashboard. We turned it off there deliberately: the dashboard displays your cluster data, and recording it would put that data in a third-party tool for no benefit to you. Credentials, API keys, executor tokens and webhook secrets are additionally masked everywhere they appear.

You can opt out of analytics entirely by enabling “Do Not Track” in your browser; we honour it.

Where your data is

Our infrastructure runs in US East (Ashburn, Virginia). If you are outside the United States, using the service means your data is transferred there. Some sub-processors may process data in other regions; we rely on Standard Contractual Clauses where required.

Your rights

Depending on where you live you may have the right to access, correct, export or delete your personal data, to object to or restrict processing, and to complain to a supervisory authority.

You can download everything your workspace holds at any time from Settings → Your data. Deletion is requested from the same place — we complete it within 30 days and confirm by email, keeping only the billing records tax law requires. For anything else, write to privacy@kubently.io and we will respond within 30 days.

Children

Kubently Cloud is a tool for professional operators. It is not directed at anyone under 16 and we do not knowingly collect their data.

Changes and contact

If we make a material change to this policy we will email account holders before it takes effect. The controller of your data is Adam Dickinson, 62 Fire Flicker Place, The Woodlands, TX 77381, USA. Reach us at privacy@kubently.io.