What we collect, why we collect it, and what you can do about it.
Last updated: November 19, 2026
CloudPloy ("CloudPloy", "we") runs cloudploy.com, the CloudPloy console, the API at brain.cloudploy.com and the CloudPloy MCP server. We decide how your personal data is used. Contact us about privacy at hello@cloudploy.com.
Your account. Your email address and name, to create your account, sign you in and write to you about your account.
How you sign in. CloudPloy has no passwords. We store what each sign-in method needs:
Sessions and security. The IP address and browser (user agent) of each session, and of each sign-in attempt, to keep your account safe and to stop abuse.
Your teams. Team names, members and their roles, and the email addresses of people you invite. A log of what members did in the team, such as a deploy or a deleted app, so the team can see its history.
Your apps and servers. What you set up so we can deploy for you: repositories and branches, app settings, domains, server names, IP addresses and sizes, and build and deploy logs. Environment variables you set; values marked as secret are stored encrypted. The SSH keys CloudPloy creates to reach your servers, stored encrypted, and public SSH keys you add.
Your connections. The AWS access key you give us, stored encrypted, with the region and the name of the instance role you created. Access tokens for GitHub, GitLab or Bitbucket and a Cloudflare API token, if you connect them, all stored encrypted. Records of the AI agents and apps you connect and of your API tokens (we keep only a hash of each token).
Billing. Your Stripe customer id, your plan and subscription status, and invoice ids. Stripe keeps your card details, not us.
Waitlist and newsletter. The email address (and name, if you give it) you put on the waitlist. For the newsletter, your email address, and the time and IP address of your confirmation as proof that you asked for it. The newsletter is double opt-in: you only get it after you confirm by email.
Emails you send us. What you write and your email address, to answer you.
Website visits. If you allow analytics cookies, Google Analytics records the pages you visit, your browser and an approximate location. We use it to see which pages help people.
We do not sell your personal data. We do not use it for advertising.
We use these companies to run CloudPloy. Each one gets only what it needs for its job.
Your apps run on your own servers: in your AWS account, or on a server you connect over SSH. The data your apps hold stays on those servers. We do not copy it.
We may also share data when the law requires it, or with a company that takes over CloudPloy, which must then follow this policy.
Our servers are in the United States. If you use CloudPloy from another country, your data is moved to the United States.
When you delete your account in the console, we delete your user record, the teams only you own (with their apps, server records, domains, connections and settings), your passkeys, sessions, tokens, connected apps, your waitlist entry and used invitations. The console refuses the delete while a paid plan is active, or while you are the only owner of a team that has other members or running servers. Deleting the account does not delete servers in your AWS account or on your own server. Records at Stripe stay with Stripe. To remove a newsletter address too, email us.
We set these cookies:
__Host-cp_): your session, which lasts up to 30 days, and short-lived cookies that protect each sign-in step and return you to the right page. They are needed for the console to work.cp_theme (light or dark), cp_sidebar (console sidebar open or closed), cloudploy_user_country (your country, from Cloudflare, for one day, to decide whether to ask about cookies first), and cloudploy_cookie_consent and cloudploy_analytics_consent (your cookie choice, one year)._ga and _ga_*): only if you allow analytics. In the EU, the UK and other places that require it, we ask first. Elsewhere they are on by default. You can turn them off at any time with Manage cookies at the bottom of every page.All traffic uses HTTPS. Secrets such as access keys, tokens, SSH keys and authenticator secrets are stored encrypted. Only the few people who run CloudPloy can reach the production systems. No system is perfectly safe, so we cannot promise that your data will never be exposed. If a breach affects your personal data, we will tell you.
You can:
To use a right, email hello@cloudploy.com from the address of your account. We answer within 30 days. We may ask you to prove that the account is yours.
CloudPloy is not for children. You must be at least 18 to use it. We do not knowingly collect data from anyone under 18. If you think a child gave us data, write to us and we will delete it.
We may change this policy. We change the date at the top of this page each time. If a change is important, we will tell you by email or in the console first. See also our Terms of Service.
Questions about privacy: hello@cloudploy.com.