Skip to content
Zephyr Cloud

Legal

Terms of service

Terms for using Zephyr Cloud’s websites, deployment services, and connected tools.

1. Our agreement

These terms describe the relationship between Zephyr Cloud, Inc., a Delaware corporation, with its address at 1226 King St, Wilmington, DE 19801, USA (“Zephyr,” “we,” or “us”) and the person or organization using our services (“you”). By accepting these terms or using the services after they are presented to you, you agree to them. If you use Zephyr for an organization, you must have authority to act for it, and “you” means that organization. A separately signed agreement or order governs wherever it conflicts with these terms.

The services are built for developers and businesses. You must be at least 18 years old, or the age of majority where you live, to create an account. Some terms below apply differently to consumers, meaning individuals using the services outside their trade, business, or profession; where they do, we say so. A “business customer” is anyone using the services for their trade, business, craft, or profession, including through any organization account.

2. Accounts, credentials, and automation

Provide accurate account information, protect your credentials, and use only accounts and organizations you are authorized to access. Organization administrators manage membership and permissions. Tell us promptly if you suspect unauthorized access. Connecting an assistant or other integration authorizes it to perform the actions you request within your Zephyr permissions; it does not give you access to another customer’s data.

Each user account belongs to one individual. Do not share your login credentials, session tokens, or personal access tokens with anyone else, and do not let more than one person use the same account, whether at the same time or at different times. Everyone who builds, deploys, or manages releases through Zephyr for your organization needs their own account. Visitors to your deployed sites do not need Zephyr accounts.

Builds and deployments that run without a person directing each one, such as CI/CD pipelines, scripts, and bots, must authenticate with CI or service tokens issued to your organization, not with a person’s login, session, or personal access token. Do not store personal credentials in CI systems, build environments, or shared secret stores.

Activity under an account is attributed to its account holder, and activity under a CI or service token is attributed to the organization that issued it. You are responsible for all activity under your accounts and tokens, including activity by anyone you let use them.

3. Deployment authorship verification

To protect your organization from deployments it did not authorize, Zephyr links every build to the people and tokens behind it. A build is accepted into your organization only when both of these are true:

  • it was uploaded by a registered member of the organization with permission to deploy, or with a CI or service token issued by the organization; and
  • the commit it was built from was authored by a registered member of the organization, or by an automation identity, such as a dependency bot, that an administrator of the organization has approved.

A CI or service token therefore deploys only commits from members of your organization or from automation you have approved. It does not let anyone else deploy through your account.

Other builds may be rejected, or held until an administrator approves them or invites the commit author to the organization. To make this check, we compare the authenticated account or token with build metadata, including git commit author and committer details. We use the same signals to detect stolen or shared credentials. Our privacy policy describes this processing. Commit metadata can be edited by anyone with access to a repository, so this check supplements, and does not replace, your own repository and CI access controls.

4. Your content

You retain ownership of the code, files, and other content you submit. You grant Zephyr the rights necessary to store, copy, process, transmit, and serve that content to operate the services you request, including through our infrastructure providers. You are responsible for having the necessary rights to your content and for complying with applicable laws and third-party licenses.

Publishing makes the selected files available at deployment URLs according to the site’s access settings. Do not upload credentials, private keys, confidential files, or personal information intended to remain private to a public site. Review generated code and deployment targets before publishing.

If you send us feedback or suggestions, we may use them without obligation to you.

5. Builds, environments, and connected services

Zephyr keeps builds so you can select which retained version an environment serves. Changing an environment can change the content visitors see. Distribution and cache propagation can take time. Retention, storage, bandwidth, and other limits depend on your service configuration and plan; keep independent copies of content you need to preserve.

When you bring your own cloud, your content is stored and served by your cloud provider under your account with them. That provider’s terms, charges, and retention apply, and deleting content there is in your control.

Integrations such as ChatGPT and Codex are also governed by their providers’ terms. Disconnecting an integration does not itself delete previously published sites or cancel a Zephyr subscription. Use Zephyr’s account controls or contact support to revoke access, remove content, or manage your subscription.

You decide which assistants, agents, API clients, and other automated integrations to connect, what permissions to give them, and how to supervise them. Within those permissions, an integration can publish, replace, promote, or delete content, and those actions are treated as yours. Review permissions and set appropriate safeguards before enabling automated operations. We are not responsible for what a third-party integration does outside our reasonable control, except where that liability cannot lawfully be excluded.

Features we label as beta, preview, or experimental may change or be withdrawn, and are provided without any service level commitment.

6. Acceptable use

Do not use Zephyr to distribute malware, conduct phishing or fraud, infringe intellectual property or privacy rights, publish unlawful content, send unlawful spam, interfere with the service, or access systems without authorization. Do not bypass access controls or authorship verification, use another person’s account or credentials, or evade service limits, including by sharing accounts to reduce the number of editing users on your plan.

Do not resell, sublicense, rent, or lease the services, or give third parties access to them, without our written permission. This does not restrict members of your organization using their own accounts, or the public visiting your deployed sites. Do not reverse engineer, decompile, or try to extract non-public source code from the services, except where the law allows it; this does not restrict your own content or open-source components under their licenses.

7. Reporting illegal content and copyright infringement

Anyone can report content hosted on Zephyr that they believe is illegal or violates these terms by emailing support@zephyr-cloud.io with the URL, an explanation of why the content is illegal or infringing, your name and email address (unless the report concerns child sexual abuse material), and a statement that the report is accurate and made in good faith. We review reports promptly and diligently, confirm receipt, and tell you what we decided.

For copyright claims under the U.S. Digital Millennium Copyright Act, send a notice meeting 17 U.S.C. § 512(c)(3) to our designated agent: Legal Department, Zephyr Cloud, Inc., at the address in section 19, or by email to support@zephyr-cloud.io. If your content was removed and you believe that was a mistake, you can send a counter-notice to the same address. We terminate, in appropriate circumstances, the accounts of repeat infringers.

8. Plans and charges

Paid plans, usage charges, billing cycles, and renewal terms are those disclosed in your applicable order or checkout and account settings. You must authorize a paid purchase or plan change. Connecting the Zephyr plugin or publishing through it does not, by itself, authorize a paid upgrade.

Plans include a set number of editing users. Every individual who builds, deploys, publishes, or manages releases through Zephyr needs their own editing user, however often they do it; view-only users cannot do these things. Sharing an account to stay within your editing user limit is evading a service limit. Routing several people through a shared interface, proxy, integration, or automated system does not reduce the number of editing users needed when each of them directs builds or releases.

Paid subscriptions renew automatically for the same period until cancelled. You can cancel online at any time in your account settings; cancellation takes effect at the end of the current billing period. Prices exclude taxes, including VAT, unless stated, and we will add taxes we are required to collect. We will tell you at least 30 days before a price increase applies to your subscription.

If you are a consumer in the European Union, the European Economic Area, the United Kingdom, or Switzerland, you may withdraw from a paid subscription within 14 days of purchase without giving a reason. If you asked us to start the paid service during that period, you pay only for the service provided until you withdraw. Any other mandatory consumer cancellation or refund rights also remain available.

9. Privacy and data protection

Our privacy policy explains how we handle personal information. You are responsible for appropriate notices, permissions, and safeguards for information you collect through your own sites. Where we process personal data on your behalf, we will enter into a data processing agreement with you on request; contact support@zephyr-cloud.io.

10. Service changes, suspension, and enforcement

We may change service features and may remove content or restrict access to address security threats, unlawful content, violations of these terms, or unpaid amounts under an applicable agreement. We decide based on the report, the content, and the context, using automated tools for some security and abuse signals and human review for decisions about an account.

If we remove your content or restrict your account, we will tell you what we did, why, which term or law we relied on, and whether automated means were involved, unless the law or a request from a competent authority prohibits telling you. You can contest any decision by replying to that notice or contacting support@zephyr-cloud.io. A person will review it, and we will reverse it if it was wrong.

If your use does not match your plan, for example several people deploying through one editing user or automation running on a personal account, we will tell you and give you at least 14 days to add editing users, change plan, or move automation to CI or service tokens. If it is not resolved, we may limit deployments until it is. Where shared or exposed credentials create an immediate security risk, we may revoke them or restrict access right away and will tell you promptly.

11. Ending the agreement, export, and switching

You can close your account at any time. We may end these terms for convenience with 30 days’ notice, or sooner if you seriously or repeatedly breach them or if the law requires it. If we end a paid subscription for convenience, we refund prepaid amounts for the unused period.

You can export your content, including builds, assets, configuration, and deployment metadata, in commonly used machine-readable formats while your account is active, and for at least 30 days after it closes, unless the content is unlawful or the law prohibits it. After that period we delete your content, except copies we must keep by law and backups that expire on their normal schedule.

If you want to move to another provider or to your own infrastructure, including under the EU Data Act, tell us with up to two months’ notice. We will support a transition period of 30 days, extended if a full switch is not technically feasible in that time, and the agreement ends when the switch is complete. We do not charge switching or data export fees for leaving Zephyr.

Terms that by their nature should survive, including sections 4, 12 to 16, and 18, and any amounts already owed, survive the end of the agreement.

12. Disclaimer

Except for commitments in a separate agreement and rights that cannot lawfully be excluded, the services are provided “as is” and “as available.” To the extent permitted by law, we disclaim all implied warranties, including merchantability, fitness for a particular purpose, and non-infringement. We do not promise uninterrupted or error-free operation, error-free generated content, or that every deployment will suit a particular purpose. Agreed service levels or remedies remain governed by your separate agreement.

13. Limitation of liability

To the extent permitted by law, neither Zephyr nor its suppliers will be liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, business opportunities, data, or goodwill. Our total liability arising out of or relating to these terms or the services is limited to the greater of the amounts you paid us for the services in the 12 months before the event giving rise to the claim and USD 100.

These limits do not apply to liability for death or personal injury caused by negligence, fraud, intentional misconduct, or gross negligence, or to any liability that cannot be limited by law. They do not affect your statutory rights as a consumer, including your rights if the services do not conform to these terms.

14. Indemnity

If you are a business customer, you will defend Zephyr and its officers, employees, and affiliates against third-party claims arising from your content, your sites, your unlawful use of the services, your infringement of third-party rights, or your material breach of these terms, and pay the resulting damages and reasonable legal costs. This does not apply to the extent a claim results from our own unlawful conduct or breach of these terms. We will notify you promptly of the claim, let you control its defense, and cooperate reasonably. This section does not apply to consumers.

15. Export controls and sanctions

You may not use the services in violation of U.S., EU, UK, or other applicable export control or sanctions laws. You confirm that you are not located in, organized under the laws of, or ordinarily resident in a country or region subject to comprehensive sanctions, and that you are not on, or owned or controlled by anyone on, a government restricted-party list.

16. Governing law and disputes

These terms are governed by the laws of the State of Delaware, United States, excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods. Disputes will be resolved exclusively in the state and federal courts located in Delaware, and both parties consent to their jurisdiction. Before filing a claim, please contact support@zephyr-cloud.io so we can try to resolve it informally.

If you are a consumer, you also keep the protection of the mandatory laws of your country of residence, and you may bring proceedings in the courts where you live.

17. Changes to these terms

We will post updated terms with their effective date. For material changes that affect you adversely, we will give at least 30 days’ notice by email or in the product, unless a change is required sooner by law or to address security or abuse. If you do not agree, you may stop using the services and close your account before the change takes effect; if you are a consumer, we will refund prepaid amounts for the unused period. Changes will not alter accrued rights retroactively.

18. General

  • These terms, together with any order and the documents they reference, are the entire agreement on their subject.
  • If a provision is unenforceable, the rest remains in effect, and the provision is applied to the extent the law allows.
  • Not enforcing a provision is not a waiver of it.
  • You may not assign these terms without our consent, except to a successor of your whole business. We may assign them to an affiliate or a successor of our business, and will tell you if we do.
  • Neither party is liable for delays caused by events beyond its reasonable control, except for payment obligations.
  • We may send notices by email to your account address or in the product. The English version of these terms controls if a translation differs.

19. Contact

Zephyr Cloud, Inc., 1226 King St, Wilmington, DE 19801, USA. For questions, account issues, reports, or a concern about these terms, contact support@zephyr-cloud.io. This address is also our point of contact for users and for authorities under the EU Digital Services Act; we communicate in English.

Effective: October 30, 2026. Last updated: October 26, 2026.