Privacy policy

Data we process

• Account: when you sign in with GitHub, we receive your identifier, username, name, e-mail and profile picture. On first access you give your company, role and team size, and your phone number if you want.
• Organization and team: organization name, members, roles, the clients each person can see and invitations.
• Data you register: clients, clusters (API address, certificates and tokens), Azure and AWS accounts, RabbitMQ, Azure Service Bus, MongoDB and Redis credentials and the organization’s AI provider API key. Credentials are stored encrypted and never shown on screen.
• Cluster content: Kubepier queries the cluster API when you open a screen and shows the result; we do not store the content of resources, logs or the shell.
• Audit: every write action (edit, scale, restart, delete), every shell and Bastion session, queue purge, Redis key edit, connection-route or queue-threshold change, every AI diagnosis and every setup and plan change (adding, editing and removing clusters, Clients, credentials and cloud accounts, syncing accounts, subscribing to and cancelling a plan, metadata only, never the credential or payment data) is recorded with who did it, when, on which cluster, client and resource and whether it succeeded, without the content, for your organization to review.
• Payment: Mercado Pago processes the subscription. We store the subscription id, plan, period, status, amount and next charge date; we never receive card data.
• Technical logs: IP address, date and time, browser and pages visited, in the access logs of our servers and of Cloudflare, for security and to comply with Brazil’s Internet Civil Framework.
• Installer downloads: which file, when, the country, the browser (user agent) and the IP address, the latter only in irreversible (salted hash) form, to count downloads per version and system.
• Kubepier Desktop: you sign in with the same account as the web, approving a code in the browser, so the app applies the organization’s plan. We keep the authorized device (machine name, operating system and app version) and the usage record: app start, minutes of use, sign-in, version and operating system. Never cluster names, namespaces, kubeconfig or resource content, which stay on your machine. You can see and disconnect your devices at app.kubepier.com.br/desktop. The app checks which is the newest published version and downloads updates from kubepier.com.br. The AI diagnosis (on Kubepier Web and, from version 2.2.0, on Kubepier Desktop) sends the provider the pod name, namespace, phase, conditions, owner and node and, for each container, the image (name:tag only), state, reason, message, exit code and restarts, and the names of the environment variables, never the values. For the pod owner, its kind and name. During the 7-day trial, which each user of a Pro or Team organization gets from their first diagnosis (including the plan’s 14-day free trial), the provider is OpenAI, with TR’s API key; the pod events from the last 60 minutes and the latest log lines, up to 16 KB, are only sent after a preview of what will be sent, and on desktop (from version 2.7.0) the request goes through the Kubepier API, with the context already redacted in the app and redacted again on the server. To count the trial, we keep the date of your first diagnosis and how many you asked for each day; the audit log marks diagnoses made with the trial key and their origin (web or desktop). Pro or Team organizations with their own key use that key and are not part of the trial. After the trial, on paid plans, the provider is the one the organization picks (Anthropic or OpenAI), with your organization’s API key (web) or your own (desktop; from version 2.7.0, without your own key, the organization’s, through the Kubepier API), and events and logs are only sent with consent turned on, after a preview of what will be sent. In every case, private keys, tokens, cloud keys, passwords, credentials in URLs, e-mail addresses, IP addresses and long strings that look like secrets are removed before sending. Kubepier neither stores nor logs the text sent or the answer; the audit log only records that a diagnosis happened, by whom and on which pod. The history on the AI analyses screen stays only in your browser (web) or on your computer (desktop, from version 2.7.0). On desktop, with your own key, the data goes straight from your machine to the provider and the key lives in the OS keychain; on the web, it goes through Kubepier’s server and the organization key is encrypted.

Purposes and legal bases

• Providing the service and keeping the account, organization and billing: performance of a contract.
• Security, fraud and abuse prevention, auditing of actions and product improvement: legitimate interest.
• Keeping access logs and tax records: legal obligation.
• Sending news, content and offers: consent, given in the communications checkbox on first access.

Notices and communications

Service notices, such as billing, security, changes to these documents and new versions, apply to every user and are given in Kubepier itself or by e-mail. Marketing goes only to those who agreed to receive it, and every message has a link to leave the list. You can also ask to leave by e-mail.

Who we share data with

• Microsoft Azure: hosting of Kubepier and its database, in the Brazil South region.
• Cloudflare: website delivery and protection against attacks; processes the technical access logs.
• GitHub: authentication.
• Mercado Pago: subscription processing.
• OpenAI, during the 7-day AI diagnosis trial of the Pro and Team plans (web and desktop): only when someone asks for a diagnosis, with what is described above and TR’s API key, going through Kubepier’s server.
• Anthropic or OpenAI, whichever provider the organization picks, after the trial: on the web, only when someone asks for an AI diagnosis, with what is described above and the organization’s API key. On desktop, with your own key, the request goes straight from your machine, without going through Kubepier.
• Authorities: when the law or a court order requires it.
• We do not sell personal data. Cloudflare, GitHub and the AI providers may process data outside Brazil, under the contractual safeguards the LGPD allows.

How long we keep data

• Account and organization data: while the account exists. After it is closed, it is deleted within 30 days.
• Access logs: at least 6 months, as Brazil’s Internet Civil Framework requires.
• Billing data and tax records: for the period the tax law sets (5 years).
• Audit records: while the organization exists.

Security

Cluster and service credentials are encrypted before they reach the database, communication uses TLS and access to production systems is restricted to the team that runs Kubepier. If an incident may put you at risk, we notify you and Brazil’s data protection authority (ANPD) as the law requires.

Your rights

You can ask for confirmation that we process your data, access to it, correction, anonymization, blocking or deletion of what is unnecessary, portability, information about who we share it with and withdrawal of consent. Write to contato@kubepier.com.br; we reply within 15 days. You can also complain to Brazil’s National Data Protection Authority (ANPD).

Cookies

The kubepier.com.br website uses no tracking cookies or analytics tools; your light or dark theme choice stays in your browser only. Kubepier Web uses one session cookie, essential to keep you signed in. Cloudflare may use technical security cookies.

Changes to this policy

When this policy changes, the date at the top is updated and relevant changes are announced in advance by e-mail or in Kubepier.