Last updated: October 2, 2026

Privacy Policy

This Privacy Policy describes how Fleetwide (“Fleetwide”, “we”, “our”), operated by Cloud2Scale at fleetwide.io, handles information when you use the service. It is written to be read: what we collect, why, how long we keep it, and how to reach us. The Terms of Service govern use of the service.

Information we collect

  • Account. Your email address and display name. If you sign in with Google we also receive your Google account ID and profile photo URL. Sign-in codes are stored only as hashes and expire within minutes.
  • Organization and team. The organization name, the members you invite, their roles, API tokens (stored as hashes) and plan and trial status.
  • Operational content. The apps, releases, channels, fleets and deployments you configure, the image digests and tags you publish, and the registry or repository credentials you add for your fleets. We never store your container images.
  • Telemetry from your containers. Each enrolled container reports its version, health, start and exit events, and CPU, memory and disk use read from its cgroup. If your app declares metrics, the container reports only the ones you named. When a fleet has live logs switched on, log lines are streamed to the console while you watch and are not stored.
  • Contact forms. What you send through contact-sales and plan-request forms: name, email, company and message.
  • Technical data. Server logs with IP addresses, request paths and timestamps, kept for operating and securing the service.
  • Website analytics. The public pages at fleetwide.io, not the console, use Google Analytics to count visits and see which pages are read. Google sets its own cookies for this and receives your IP address and browser details; see Google\u2019s privacy policy for how it handles them. Visitors in Europe are asked first, and nothing is set until they allow it; anyone can block it with a browser setting or extension and the site works the same.

How we use information

  • To run the service: sign you in, enroll containers, deliver releases and show fleet status.
  • To send transactional email: sign-in codes, activation links, invitations and notices about your account or plan. We do not send marketing email without asking first.
  • To answer your requests and support questions.
  • To keep the service secure and to understand how it is used, in aggregate.

Retention

Container telemetry is kept for 7 days on the Dev plan and 30 days on the Team plan; Enterprise organizations choose their own retention. Live logs are never stored. Account, organization and operational content are kept while your organization exists and deleted when you ask us to delete it, except where we must keep records to meet legal or accounting duties.

Sharing

We do not sell your information. We share it only with providers that help us run the service and only for that purpose: cloud hosting, a managed workflow service that schedules promotions and maintenance, an email delivery provider, and Google Analytics on the public website. Google receives what is needed to sign you in. We may disclose information when the law requires it or to protect the service and its users.

Security

Containers talk to the service over mutually authenticated TLS with per-container certificates. Sign-in codes, API tokens, deployment keys and invitation links are stored as hashes. Registry credentials are delivered only to the fleets they are scoped to. No system is perfectly secure; tell us at info@cloud2scale.com if you believe something is wrong.

Your choices

  • Remove a container from a fleet at any time; its telemetry is deleted with it.
  • Delete credentials, tokens and members from the console.
  • Ask us to export or delete your organization’s data at info@cloud2scale.com.

Changes to this policy

We may update this policy. The date at the top says when it last changed, and we will tell account owners by email about changes that matter.

Contact

Cloud2Scale · info@cloud2scale.com

fleetwide

Over-the-air updates and fleet management for Docker containers. The supervisor runs inside the container; nothing on the host.

© 2026 Fleetwide