Privacy Policy
Effective October 17, 2026
Who we are
Fleetscope (“we”) is a service that shows the state of your Kubernetes clusters in one place. This policy explains what information we collect when you visit fleetscope.store, sign in, or connect a cluster, why, how long we keep it, and what you can ask us to do. Fleetscope is in beta, so the service and this policy may change. Questions: [email protected].
What we collect
- Account. The email address and display name from your Google account when you sign in with Google. We ask Google only for the scopes
openid,emailandprofile, and we accept only an email address that Google has verified. If your organization uses a password, we store a salted hash of it, never the password itself. - Organization and activity. The organization name, its members and their roles, and an audit log of actions (sign-ins, changes to clusters, viewing a resource’s YAML or a pod’s logs) with the time and IP address.
- Cluster data, from the agent you install. Names, namespaces, labels, image names, status and replica counts of Kubernetes resources, events, node and pod details, the Kubernetes version, platform and region, and CPU, memory, network and disk metrics. The agent is read-only and never reads Secrets or ConfigMaps. It removes environment variable values, command arguments, URLs with credentials and most annotations before anything leaves your cluster.
- Container logs. Only when someone opens the log viewer. The lines are passed through to that person’s browser and are not stored.
- Sign-up form on this website. Email, company, number of clusters and language, plus your country as reported by Cloudflare. The form is protected by Cloudflare Turnstile.
- Cookies. Two essential cookies keep you signed in and protect against forged requests. We use no analytics, advertising or tracking cookies.
How we use it
To run the service, keep it secure, and send the alerts you set up (messages to the Slack, Telegram or Google Chat channel you choose contain cluster names and finding titles). We use the sign-up form to contact you about the beta. We do not sell your data and we do not use it for advertising.
Fleetscope’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How long we keep it
| Data | Kept for |
|---|---|
| Resources deleted from a cluster | 7 days |
| Kubernetes events | Warning events 7 days, other events 1 day |
| Change timeline | 30 days |
| Metrics | 35 days |
| Resolved findings | 30 days |
| Audit log | 90 days |
| Sign-in sessions | 12 hours without activity, 7 days at most |
| Sign-up form entries | Until you ask us to delete them or the beta ends |
Resources that still exist in a connected cluster are kept while the cluster stays connected.
Where it is stored and who handles it
Fleetscope runs on Google Cloud. The website, DNS and the sign-up form run on Cloudflare. Google provides sign-in. If you set up alerts, the message goes to the service you chose. We do not share your data with anyone else.
Security
Connections use TLS. The agent only connects outward from your cluster and needs no inbound port. Each organization’s data is separated in the database. Alert channel secrets are stored encrypted. No system is perfectly secure; if we learn of a breach that affects you, we will tell you.
Your choices
- Delete a cluster in Fleetscope and its stored resource data is removed; its metrics expire within 35 days. Uninstall the agent with
helm uninstallto stop all collection. - Ask us to see, correct, export or delete your personal data, or to delete your organization, at [email protected]. We answer within 30 days.
Children
Fleetscope is for IT professionals and is not meant for anyone under 16.
Changes
When we change this policy we update the date above, and for material changes we also email the account owners.