Cycle (Midware Networks LLC) uses a small set of vendors ("subprocessors") that process customer data on our behalf to provide the Service. We announce additions to this list at least 30 days in advance — on this page and by email to workspace owners — before a new subprocessor processes customer data. Exception: if replacing a subprocessor is reasonably necessary for security, service continuity, or a subprocessor's failure or insolvency, we may do so immediately and will announce the change as soon as practicable.
| Subprocessor | Purpose | Location |
|---|---|---|
| DigitalOcean, LLC | Cloud infrastructure hosting (Kubernetes, managed databases) | United States |
| Cloudflare, Inc. | Edge network, WAF, object storage (R2), bot protection (Turnstile) | United States (global network) |
| Stripe, Inc. | Payment processing and billing | United States |
| Amazon Web Services, Inc. (SES) | Transactional email delivery | United States |
| Grafana Labs | Operational telemetry and monitoring | United States |
| GitHub, Inc. | Source-platform APIs for connected repositories | United States |
| Google LLC (Google Workspace) | Business email and support communications | United States |
Sign-in providers. If you sign in with Google, GitHub, GitLab, or Bitbucket, that provider processes your sign-in under its own terms — you choose the provider; it is not a Cycle subprocessor.
AI providers. Cycle does not send customer data to AI providers on its own initiative. If you connect your own AI assistant to the Cycle MCP server, data it reads flows to your AI provider under your agreement with that provider (see Terms of Service §9.5).
Questions: privacy@cycle.sh