1. Information We Collect
We collect only the information required to run the Fleet deployment platform:
- Account Information: Your name, email address, and avatar provided during GitHub or Google OAuth sign-in.
- Workspace & Team Configuration: Organization names, team member emails, and permission roles (Owner, Admin, Developer).
- Deployment Configuration: Repository URLs, branch names, build commands, and environment variable names.
- Encrypted Secrets: Environment variable values, which are encrypted at rest using AES-256-GCM before being saved.
- Operational Telemetry: Live deployment logs (stdout/stderr during build and start) and host metrics (CPU, RAM, and Disk utilization) sent by the Fleet Agent.
2. How We Use Your Information
We use your data solely to provide, secure, and maintain the Fleet deployment platform:
- To authenticate your access and manage workspace permissions.
- To dispatch deployment jobs to your registered server agents.
- To stream live build progress and display server health metrics in your dashboard.
- To notify you about important deployment errors or security notices.
3. Source Code & Secret Privacy
Your source code belongs exclusively to you:
- Fleet never uses your proprietary code or secrets to train machine learning or AI models.
- Git tokens are used strictly in memory during the deployment step and are scrubbed from all logs.
- Your application code executes locally on your own servers—not on Fleet infrastructure.
4. Data Sharing & Third Parties
We do not sell, rent, or monetize your personal or operational data. We only share information with trusted infrastructure providers required to operate Fleet (such as our database, cloud hosting, and transactional email providers), or when required by applicable law.
5. Cookies & Authentication
Fleet uses secure HTTP-only session cookies strictly for user authentication and preserving your theme preference. We do not use third-party advertising or cross-site tracking cookies.
6. Security & Encryption
All network communication between your browser, the control plane, and server agents is encrypted in transit using TLS / HTTPS / WSS. All agent communication is cryptographically signed using Ed25519 key pairs. For more technical details, visit our Security Architecture page.
7. Contact Us
If you have any questions about this Privacy Policy or your data, please contact us: