--- title: "Kuberns Privacy Policy | Personal Data and Your Rights" description: "Read the complete Kuberns Privacy Policy to understand what personal data we collect, why we use it, where it is processed, who receives it, and your rights." source: "https://kuberns.com/privacy-policy" effective_date: "15 October 2026" version: "1.3" --- # Privacy Policy This Privacy Policy explains what personal data Kuberns handles, why we use it, where it is processed, who receives it, how long we keep it, and the choices and rights available to you. **Effective date:** 15 October 2026 **Version:** 1.3 **Policy owner:** Kuberns Tech Private Limited ## On This Page 1. [Who we are](#1-who-we-are) 2. [Our roles](#2-our-roles) 3. [Personal data we collect](#3-personal-data-we-collect) 4. [Why we use personal data](#4-why-we-use-personal-data) 5. [Who receives personal data](#5-who-receives-personal-data) 6. [Where personal data is processed](#6-where-personal-data-is-processed) 7. [GitHub and connected repositories](#7-github-and-connected-repositories) 8. [Artificial intelligence](#8-artificial-intelligence) 9. [Cookies, analytics, and advertising measurement](#9-cookies-analytics-and-advertising-measurement) 10. [Security and authorised access](#10-security-and-authorised-access) 11. [Your rights and account deletion](#11-your-rights-and-account-deletion) 12. [Children](#12-children) 13. [Privacy requests, grievances, and contact](#13-privacy-requests-grievances-and-contact) 14. [Changes and version history](#14-changes-and-version-history) Related documents: - [Terms of Service](https://kuberns.com/terms-conditions) - [Subprocessors](https://kuberns.com/subprocessors) - [Data Processing Addendum](https://kuberns.com/dpa) - [Data Retention](https://kuberns.com/data-retention) - [Security](https://kuberns.com/security) - [Contact Kuberns](https://kuberns.com/contact) ## 1. Who We Are Kuberns Tech Private Limited, referred to in this policy as "Kuberns," "we," "us," or "our," operates the Kuberns platform at [kuberns.com](https://kuberns.com/) and [dashboard.kuberns.com](https://dashboard.kuberns.com/). **Legal entity:** Kuberns Tech Private Limited **CIN:** U62011GJ2026PTC175393 **GSTIN:** 24AAMCK7161M1Z1 **Registered address:** B-100 Alap Century, Kalawad Road, Rajkot, Gujarat 360005, India ## 2. Our Roles Kuberns handles personal data in two different roles. ### When Kuberns is the controller or Data Fiduciary Kuberns determines how and why we handle personal data relating to account holders, website visitors, prospects, partners, and other people who interact directly with us. This includes account, billing, support, security, marketing, and product-usage data. This Privacy Policy applies to that processing. ### When Kuberns is the processor or Data Processor Customers determine how and why personal data inside their deployed applications is processed. This may include information in customer databases, application files, environment variables, source code, build artifacts, logs, and traffic generated by customer applications. Kuberns processes that data on the customer's documented instructions to provide the service. The customer remains responsible for its application and the personal data it collects. Our [Data Processing Addendum](https://kuberns.com/dpa) governs this processing. If your personal data is contained in an application hosted by a Kuberns customer, contact the operator of that application first. That operator is responsible for responding to your request. We will assist the customer where required by our Data Processing Addendum and applicable law. ## 3. Personal Data We Collect ### Information you provide Depending on how you use Kuberns, you may provide: - your email address when you create or access an account; - your name and profile-picture URL when you use Google sign-in; - your GitHub username when you use GitHub sign-in; - your first name, last name, profession, company name, and intended deployment use case; - your phone number when phone verification is enabled; - your acceptance of our Terms of Service; - your billing country and currency; - support messages, chat conversations, enquiry forms, and demo bookings; and - partner or affiliate information, including a display name, referral code, commission records, and information about referred clients. ### Information from connected accounts When you connect GitHub, we receive the account details and authorisation required for the permissions you approve. Repository access is granted separately through the Kuberns GitHub App and is limited to the repositories you select. ### Information about projects and deployments We may process: - repository URL, owner name, and repository ID; - commit messages, commit IDs, and committer names; - source files required to build and deploy a selected repository; - build logs, runtime logs, and deployment activity; - environment names, deployment regions, and resource configuration; - custom domains and SSL certificates; - environment variables, secrets, and managed-database credentials; and - container images and build artifacts created while providing the service. ### Information collected automatically We may collect: - IP address; - browser, operating-system, and device information; - pages visited and product interactions; - approximate country derived from an IP address to select currency and payment provider; - campaign-attribution parameters present when you first visit; and - account and product-usage events, such as whether a deployment was created. ### Information from payment providers Payment providers may give us order IDs, transaction IDs, invoice numbers, payment status, amounts, taxes, currency, billing country, and payment-method type. Kuberns does not store full payment-card numbers. Card information is handled by the applicable payment provider. ### Information we do not normally collect from individual customers Kuberns is passwordless, so we do not collect account passwords. We do not normally request government identification, dates of birth, or know-your-customer documents from individual self-service customers. ## 4. Why We Use Personal Data We use personal data to: - create, secure, and operate your account; - build, deploy, operate, and support applications and managed resources; - process payments, issue invoices, and maintain tax and accounting records; - detect, investigate, and prevent fraud, abuse, and security incidents; - keep records required by applicable law; - answer support requests, including through our AI support assistant; - diagnose build, deployment, and runtime failures; - send service messages about your account, deployments, security, and credit balance; - send marketing messages when you have requested them or when applicable law otherwise permits; - measure campaign conversions when you have provided the required advertising consent; and - understand product usage and improve Kuberns using permitted analytics and aggregated information. Depending on the activity and applicable law, processing may be necessary to provide the service, comply with a legal obligation, protect the platform and its users, pursue a permitted legitimate purpose, or act on your consent. Where we rely on consent, you may withdraw it through the available settings or by contacting us. We do not use personal data to make decisions that produce legal or similarly significant effects without meaningful human involvement. ### What we do not do We do not sell personal data or share it with data brokers. We do not build behavioural profiles of Kuberns users. Personal data inside customer applications is not used for Kuberns advertising or general product analytics. We process it to provide, secure, troubleshoot, and support the service, including AI-assisted diagnosis where described in this policy and the Data Processing Addendum. Kuberns does not use customer source code, application data, logs, or support conversations to train models owned by Kuberns. ## 5. Who Receives Personal Data We disclose personal data only as needed to operate Kuberns, complete transactions, comply with law, protect rights and security, or follow your instructions. The categories of recipients include: - **Cloud infrastructure:** Amazon Web Services, Cloudflare, and Docker Hub. - **Payments:** Razorpay for transactions in Indian Rupees and Dodo Payments for other supported transactions. - **Communications:** providers used for transactional email, phone verification, product email, support chat, and meeting scheduling. - **Business systems:** customer-relationship management, accounting, enquiry-form storage, historical support, and disposable-email detection providers. - **Monitoring and analytics:** providers used for error monitoring and permitted product analytics. - **Advertising measurement:** Google Ads and Meta Ads when the required consent is active. - **Artificial intelligence:** the providers described in Section 8 and on our Subprocessors page. Dodo Payments acts as the Merchant of Record for applicable transactions outside India. This means Dodo is the legal seller for the payment, calculates applicable taxes, and issues the invoice. Kuberns continues to provide and operate the Kuberns platform. The current provider list, purpose, and processing details are published on our [Subprocessors page](https://kuberns.com/subprocessors). We may also disclose personal data: - when required by law, a court, or a competent authority; - to protect Kuberns, our users, or others from fraud, abuse, security threats, or unlawful activity; - as part of a merger, acquisition, financing, reorganisation, or sale of assets, subject to appropriate confidentiality and continued protection; or - when you direct or consent to the disclosure. Where legally permitted, we will notify you before disclosing personal data in response to legal process so that you can challenge the request. ## 6. Where Personal Data Is Processed ### Customer applications Customer applications run in the AWS region selected by the customer. Available regions may include Mumbai, N. Virginia, London, Frankfurt, and Sydney. ### Kuberns account and control-plane data Account profiles, billing records, project metadata, and build logs are stored on the Kuberns control plane in Mumbai, India, regardless of the application region selected by the customer. ### AI processing AI processing may occur outside India through the providers listed on our [Subprocessors page](https://kuberns.com/subprocessors). The provider and processing location may vary according to service availability and the model used for a request. Where personal data is transferred across borders, Kuberns applies the safeguards required by applicable law and requires relevant providers to protect the data under written agreements. For transfers covered by the GDPR, the safeguards described in our [Data Processing Addendum](https://kuberns.com/dpa) apply, including Standard Contractual Clauses where required. You may contact us to request more information about the safeguards applicable to a transfer involving your personal data. ## 7. GitHub and Connected Repositories GitHub sign-in uses the `user:email` scope to obtain the email address associated with your GitHub account. Repository access is granted separately through a GitHub App installation. You choose which repositories the Kuberns GitHub App can access. We use repository access to: - clone the selected repository; - read the files required to build and deploy the project; - receive repository events that can trigger deployments; and - commit a proposed change only when you instruct the deployment agent to do so. We do not read connected repositories for unrelated purposes, sell source code, or use source code to train models owned by Kuberns. Access tokens are encrypted at rest. When you disconnect an integration or close your account, we revoke and remove the applicable connected-account tokens. Repository clones, container images, build artifacts, build history, and build logs are deleted according to the periods and events listed on our [Data Retention page](https://kuberns.com/data-retention). ## 8. Artificial Intelligence Kuberns uses artificial intelligence in the following areas. ### AI support assistant The support assistant is automated. Messages sent to it may be processed by a third-party AI provider to generate a response. Support-assistant conversations are retained for the period listed on our Data Retention page. ### AI deployment agent When you use the deployment agent, it may process relevant repository files, Dockerfiles, build logs, and runtime logs to identify configuration, diagnose failures, and propose fixes. It commits changes only when you request that action. ### Automatic failure diagnosis When a build or deployment fails, Kuberns may send the relevant error extract to an AI provider to classify the failure and provide an explanation. We limit the information sent to what is reasonably required for the diagnosis. Third-party AI providers are listed on our [Subprocessors page](https://kuberns.com/subprocessors). The provider used for a request may vary according to availability. Processing may occur outside India. Kuberns does not use repository content, logs, application data, or support conversations to train models owned by Kuberns. Processing by third-party AI providers is governed by Kuberns' agreements with those providers and the safeguards described in the Data Processing Addendum. Do not place secrets, payment-card data, health data, biometric data, government identifiers, or other highly sensitive information in support messages or repository files unless the service and your agreement with Kuberns expressly support that processing. ## 9. Cookies, Analytics, and Advertising Measurement Kuberns uses cookies and similar technologies for the following purposes. ### Strictly necessary technologies These technologies keep users signed in, remember workspace settings, maintain security, and provide requested functionality. They cannot be disabled through the Kuberns cookie controls. ### Analytics Analytics technologies help us understand how the website and product are used. They remain disabled until you accept the relevant cookie category where consent is required. ### Advertising measurement Advertising technologies measure which campaigns lead to signups or purchases. Kuberns does not use these technologies to build retargeting audiences. They remain disabled until you accept the relevant cookie category where consent is required. The services currently used for these purposes are listed on our [Subprocessors page](https://kuberns.com/subprocessors) and may include Google Ads, Meta Ads, PostHog, and Chatwoot. Where you have provided the required advertising consent and complete a signup or purchase, Kuberns may send Google or Meta a hashed version of your email address for conversion measurement. A hashed identifier is still treated as protected information where applicable law requires. You can accept, reject, or change optional-cookie choices through the **Cookie settings** control in the website footer. You can also block or delete cookies through your browser settings. Withdrawing consent does not affect processing that occurred before the withdrawal. You may contact [support@kuberns.cloud](mailto:support@kuberns.cloud) to object to or request the restriction of analytics or advertising processing where applicable. ## 10. Security and Authorised Access Kuberns uses technical and organisational measures designed to protect personal data, including: - TLS encryption for connections to the platform; - encryption at rest for sensitive fields, including account details, connected-account tokens, payment-mandate tokens, configured secrets, environment variables, managed-database credentials, and SSL private keys; - role-based access controls and restricted access to production systems; - authenticated and attributable administrative actions; - monitoring, security logging, and incident investigation; - webhook-signature verification and least-privilege cloud credentials; and - contractual security and confidentiality requirements for relevant providers and personnel. Build logs, deployment activity, transaction metadata, and similar operational information may be protected through storage encryption and access controls without separate field-level encryption for every value. ### Support and operational access Authorised personnel and automated systems may run administrative commands on infrastructure provisioned for a customer and may access environment configuration when necessary to operate, secure, troubleshoot, or support the service. Access is limited by role, attributed to an individual or system, and logged. ### Personal-data incidents If a personal-data breach affects information for which Kuberns is the controller or Data Fiduciary, we will provide notices required by applicable law. If a breach affects personal data Kuberns processes for a customer, we will notify that customer without undue delay and provide the information described in our [Data Processing Addendum](https://kuberns.com/dpa). ## 11. Your Rights and Account Deletion Depending on where you live, the type of processing, and applicable law, you may have the right to: - request access to personal data held about you; - request correction of inaccurate or incomplete data; - request deletion of eligible data; - withdraw consent where processing is based on consent; - object to or request restriction of certain processing; - request portability where applicable; - nominate another person to exercise rights in circumstances recognised by Indian law; and - complain to Kuberns or an applicable data-protection authority. These rights may be subject to identity verification, legal exceptions, and mandatory retention obligations. To submit a request, use your account settings or email [support@kuberns.cloud](mailto:support@kuberns.cloud). We aim to respond within 30 days. If a different period is required by applicable law, that period will apply. ### What happens when you delete your account You must stop active resources before deleting your account. When deletion begins, Kuberns: - terminates the infrastructure running your applications; - removes storage buckets, container images, and custom-domain configuration according to the applicable deletion process; - revokes connected-account tokens and cancels applicable payment mandates; - removes account details and marketing-attribution data that are not subject to a retention requirement; - instructs relevant subprocessors to delete eligible copies; and - retains only information required for legal, security, dispute-prevention, or documented operational purposes. The [Data Retention page](https://kuberns.com/data-retention) provides the current category-by-category schedule. It includes periods for build history, application logs, AI-assistant sessions, support conversations, payment records, provider copies, and backups. Where Kuberns cannot delete information because a legal or contractual retention period applies, we will explain what is retained and why. ## 12. Children Kuberns is not intended for anyone under 18, and we do not knowingly collect personal data directly from anyone under 18. We do not direct advertising to children. If you are a parent or guardian and believe a child has provided personal data to Kuberns, email [support@kuberns.cloud](mailto:support@kuberns.cloud). Provide only the information reasonably needed for us to locate and address the data. ## 13. Privacy Requests, Grievances, and Contact ### Privacy and data-rights requests Send privacy questions, access requests, correction requests, deletion requests, consent withdrawals, and other data-rights requests to [support@kuberns.cloud](mailto:support@kuberns.cloud). We aim to respond within 30 days. A different period may apply where required by applicable law. ### Grievance Officer **Name:** Harsh Kanani **Role:** CEO, Kuberns Tech Private Limited **Email:** [support@kuberns.cloud](mailto:support@kuberns.cloud) **Phone:** [+91 88661 90761](tel:+918866190761) **Address:** B-100 Alap Century, Kalawad Road, Rajkot, Gujarat 360005, India For grievances governed by applicable Indian intermediary rules, Kuberns aims to acknowledge the complaint within 24 hours and resolve it within 15 days, subject to any shorter period required for a specific complaint. Privacy requests and other complaints are handled within the periods required by the law that applies to the request. ### Marketing messages Service messages about account access, deployments, security, and credit balance are necessary to operate the service and cannot be disabled while the relevant service remains active. You may opt out of product and promotional emails through the unsubscribe method provided in the message, through available account settings, or by emailing [support@kuberns.cloud](mailto:support@kuberns.cloud). ## 14. Changes and Version History We may update this Privacy Policy to reflect changes to our services, providers, practices, or legal obligations. We will publish the updated policy on this page and change the effective date and version number. Where a change materially affects how we handle personal data or significantly reduces a user right, we will provide additional notice through email, the dashboard, or another appropriate channel before the change takes effect where required. ### Version 1.3, 15 October 2026 - Replaced the obsolete application domain with dashboard.kuberns.com. - Clarified Kuberns' controller, Data Fiduciary, processor, and Data Processor roles. - Reorganised data-collection categories and processing purposes. - Clarified international processing and the safeguards referenced in the Data Processing Addendum. - Expanded the GitHub and AI-processing disclosures. - Clarified optional-cookie consent and hashed-email conversion measurement. - Reworked the rights, deletion, grievance, and contact sections. - Linked retention statements to the Data Retention page. - Removed em dashes and corrected spacing and terminology. ### Version 1.2, 3 September 2026 Corrected the descriptions of AI-processing locations and linked the current provider list on the Subprocessors page. ### Version 1.1, 2 September 2026 Added the "What we do not do" explanation and updated the advertising-measurement and provider disclosures. ### Version 1.0, 1 September 2026 First published.