Privacy Policy

Last Updated: October 2026

1. Introduction

Welcome to Roam. We respect your privacy and are committed to protecting it. This Privacy Policy explains our practices regarding the collection, use, and disclosure of information when you use the Roam applications ("App"): the mobile app for iOS and Android, and the desktop app for macOS, Windows and Linux, whether downloaded from our website and GitHub Releases or installed from the App Store, Google Play, the Microsoft Store (where it is listed as Kuberoam), the Snap Store or Flathub.

2. Data Collection and Usage

Roam is designed with privacy and security as its core principles.

  • No Data Collection: We do not collect, store, or transmit any personal data, usage data, or telemetry to our servers. We do not operate any server that the App sends your data to.
  • Information the App Accesses: To connect to your clusters, the App reads the kubeconfig files you import or point it to (on desktop, ~/.kube by default). Kubeconfig files can identify you — for example user names, client certificates, bearer tokens and cloud accounts. On desktop, the App may run the credential plugins your kubeconfig names (such as aws, gke-gcloud-auth-plugin or kubelogin) on your computer to obtain tokens. This information is used only to connect to your clusters.
  • Local Processing: All data related to your Kubernetes clusters, including kubeconfig files, credentials, cluster metrics, logs, and resources, are processed and stored locally on your device.
  • Encrypted Credential Storage: Sensitive credentials that you import — kubeconfig files, bearer tokens, cloud provider keys (AWS, GCP, Azure) and AI provider API keys — are kept separate from ordinary app data:
    • Mobile: in your device's OS-protected secure storage (iOS Keychain / Android Keystore-backed encrypted storage).
    • Desktop: in an encrypted vault in the App's data folder, whose key is held by your operating system's credential store (macOS Keychain, Windows Credential Manager, or the Secret Service on Linux, such as GNOME Keyring or KWallet). If no credential store is available, the key is kept in a file in the App's data folder, and Settings tells you so.

3. Network Connections

The App only connects to services you configure, plus a check for updates on desktop:

  • Your Clusters: The App connects directly from your device to the Kubernetes API servers in your kubeconfig, and, if you set them up, through the proxy, jump host or Roam Gate gateway that you run. Your data never passes through any intermediary servers operated by us.
  • Cloud Providers: When your kubeconfig or a sign-in you start uses AWS, Google Cloud or Azure, the App (or the provider's own tool) talks directly to that provider to obtain cluster credentials.
  • Your AI Provider: Only if you enable AI features (see section 5).
  • Update Checks (desktop): Copies of the desktop app downloaded from our website or GitHub check GitHub Releases for a newer version shortly after launch and then every few hours, and download the update you choose to install. These requests go to GitHub, which receives standard request information such as your IP address and is subject to GitHub's privacy statement. No information about you or your clusters is included. Copies installed from an app store are updated by that store instead.

4. Google Account Sign-in (Google Kubernetes Engine)

You can connect to Google Kubernetes Engine (GKE) clusters by signing in with your Google account. This is optional: a service account key works instead.

  • Data accessed: the App asks for the OAuth scopes openid and https://www.googleapis.com/auth/userinfo.email, and two read-only Google Cloud scopes: https://www.googleapis.com/auth/cloudplatformprojects.readonly and https://www.googleapis.com/auth/container.read-only. With them it accesses your email address, the IDs and names of the Google Cloud projects you can access, and the names, locations, API endpoints and CA certificates of the GKE clusters in those projects, plus the OAuth tokens Google issues for the sign-in. The App cannot create, change or delete anything in Google Cloud with these scopes. It does not create aggregated or anonymized data from Google user data.
  • Data use: the App uses this data only for the feature you start: it shows which account is signed in, lists your projects and GKE clusters so you can pick one, and connects to the clusters you add (the cluster identifies you by your email address). It is not used for anything else — not for analytics, advertising, profiling, or training AI or machine-learning models.
  • Data sharing and transfer: the App runs on your device and Roam has no server, so Google user data goes only to these two recipients, directly from your device and only to do what you ask in the App:
    • Google: the App sends your OAuth tokens to Google's sign-in service and to the Google Cloud Resource Manager and Kubernetes Engine APIs, to list your projects and clusters and read a cluster's connection details.
    • The Kubernetes API server of each GKE cluster you add, which Google Cloud runs in your own Google Cloud project: the App sends your Google access token to it to sign you in.
    Google user data, raw or aggregated, is not shared with, transferred to or disclosed to anyone else. It is not sent to us (we never receive it, so we cannot disclose it to anyone), not sent to AI providers, data brokers, advertisers or other third parties, not sold, and not read by people.
  • Data protection: all connections to Google and to your clusters use HTTPS (TLS). On iOS and desktop, the sign-in (a refresh token) and your email address are kept in the App's encrypted credential storage described in section 2 (iOS Keychain; on desktop, an encrypted vault whose key your operating system's credential store holds). On Android, Google Play services keeps the sign-in and the App stores only your email address, in Android Keystore-backed encrypted storage. Access tokens are kept in memory only. The project and cluster lists are kept in memory while you choose a cluster; the connection details of the clusters you add are saved with them on your device.
  • Data retention and deletion: Google user data stays on your device for as long as the cluster that uses it is in the App. Removing the cluster from the App deletes its stored sign-in, email address and connection details. Access tokens expire within about an hour and are discarded when the App closes. You can also revoke the App's access at any time at myaccount.google.com/permissions. Because we never receive Google user data, we hold none that would need deleting.
  • Limited Use: Roam's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5. AI Features

The App includes optional AI-powered features that explain warnings, diagnose workloads and answer questions about your clusters. They are off until you configure a provider.

  • Local AI Engine: If you choose an AI engine that runs on your own device (e.g., the on-device Llama engine on mobile, or Ollama running on your computer), all analysis stays on your device. No data is transmitted externally.
  • Remote AI Engine: If you configure a third-party remote API (e.g., OpenAI or another OpenAI-compatible service such as Groq, or an Ollama server on another machine), the App will transmit the cluster information needed for your request (such as event descriptions, logs, resource definitions and your question) to your designated provider to generate the answer. You are subject to the privacy policies of the provider you configure, and we are not responsible for how your configured third-party provider handles this data.

6. Third-Party Services

The App does not integrate with any third-party analytics, crash reporting or advertising services that track your behavior. The store you install the App from (Apple, Google, Microsoft, Canonical or Flathub) may collect information under its own privacy policy, such as download and installation statistics.

7. Security

We value your trust in providing us with your Kubernetes configurations. Cluster credentials are stored as described in section 2; other locally stored data is protected by your device's security mechanisms (e.g., device passcode or login password, biometric authentication, disk encryption, and sandboxing). We strongly recommend keeping your device secure, enabling a passcode or login password, and turning on disk encryption.

8. Data Retention and Deletion

All data remains on your device and under your control.

  • Removing a Cluster: When you remove a cluster from the App, its stored credentials (kubeconfig content, tokens, and cloud provider keys) are deleted from the App's secure storage, along with the cluster's saved configuration. Kubeconfig files of your own that the App only read (such as ~/.kube/config) are left unchanged.
  • Uninstalling the App: Uninstalling the mobile app removes all locally stored data, subject to your operating system's standard app-data removal behavior. On desktop, depending on how the App was installed, its data folder and credential store entry may remain after uninstalling so that a reinstall can pick them up. To remove everything, delete the data folder (~/Library/Application Support/Roam on macOS, %AppData%\Roam on Windows, ~/.config/Roam on Linux) and the "dev.roam.desktop" entry in your credential store.

9. Children's Privacy

The App is a professional tool for managing Kubernetes clusters and is not directed to children. We do not knowingly collect personal information from anyone, including children.

10. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date.

11. Contact Us

If you have any questions or suggestions about our Privacy Policy, please contact us at [email protected].