GitLaunch ← Back to GitLaunch
Effective July 26, 2026

Terms of Service

These terms are the agreement between you and GitLaunch. They are written to be read rather than endured, but they are a binding contract — please read them, particularly sections 6, 14 and 15.

The short version

  • GitLaunch is a button, not a deployer. We trigger the pipeline you configured. What that pipeline does to your systems remains yours.
  • We are pre-launch. The service is provided as a beta, without a service level guarantee.
  • Your data stays yours. We claim no ownership of it and use it only to run the service.
  • Our liability is capped — see section 15, which is deliberately hard to miss.
  • Either of us can walk away. Cancel any time; we will not hold your data hostage.

This summary is for orientation only. The numbered sections below are the binding agreement.

Contents

  1. This agreement
  2. Who may use GitLaunch
  3. Your account
  4. Beta service
  5. What GitLaunch does
  6. What deploying means
  7. Your data
  8. Acceptable use
  9. Third-party services
  10. Plans, fees and taxes
  11. Term and termination
  12. Confidentiality
  13. Intellectual property
  14. Disclaimer of warranties
  15. Limitation of liability
  16. Indemnification
  17. Changes
  18. Governing law and disputes
  19. General

1. This agreement

These Terms of Service (the "Terms") are a binding agreement between you and GitLaunch LLC, a limited liability company organized under the laws of the Commonwealth of Puerto Rico, United States ("GitLaunch", "we", "us").

By creating an account, joining the waitlist, or using the GitLaunch service (the "Service"), you agree to these Terms. If you do not agree, do not use the Service.

Our Privacy Policy is incorporated into these Terms and explains how we handle personal information.

If you are agreeing on behalf of a company or other organization, you represent that you have authority to bind it, and "you" means that organization.

2. Who may use GitLaunch

You must be at least 18 years old and legally able to enter into a contract. You must not be located in, or ordinarily resident in, a country subject to US embargo, and you must not appear on any US government restricted-party list. GitLaunch is a US service and is subject to US export control and sanctions law.

3. Your account

You can sign in through GitHub, through Google, or with an email address and a password you set with us. You are responsible for everything that happens under your account and for the security of the credentials that reach it — including any API keys you generate.

If you set a password with us, choose one you do not use anywhere else, and keep it to yourself. We store it only as a one-way hash and can never tell you what it is. We may ask you to confirm your email address before your account is fully usable, and we may suspend an account whose address is never confirmed.

API keys are shown once. We store only a one-way hash and cannot recover a lost key; we can only issue a new one. Treat a key as you would a production password: anyone holding it can act as your account. Tell us promptly at support@gitlaunch.dev if you believe a key or account has been compromised, and revoke it in your settings.

If you add teammates to your account, you are responsible for their use of the Service and for the permissions you grant them.

4. Beta service

GitLaunch has not reached general availability. The Service is offered as a beta: features may change or be withdrawn, interfaces may break, and availability is not guaranteed.

We offer no service level agreement during beta, and no uptime, performance, or support-response commitment. If we later offer an SLA, it will be a separate written document; nothing in these Terms creates one.

Please do not make GitLaunch the only path to deploying a system you cannot afford to have unavailable. Keep the ability to run your pipeline directly.

5. What GitLaunch does

GitLaunch gives your team visibility into what is deployed where, and a controlled way to trigger a deployment or rollback. Concretely, it:

  • records the status of builds and deployments you or your systems report to it;
  • triggers workflows you have already configured — a GitHub Actions workflow, or a job on a Jenkins server you operate; and
  • shows your team the resulting history and current state.

Subject to these Terms, we grant you a non-exclusive, non-transferable, revocable right to use the Service for your internal business purposes during your subscription.

6. What deploying means

This section matters more than any other in these Terms, so it is stated plainly.

GitLaunch triggers your deployment pipeline. It does not write, review, test, or validate what that pipeline ships.

When you press deploy, GitLaunch asks GitHub or Jenkins to run a workflow that you wrote and configured, against infrastructure that you control. We do not inspect your code, evaluate whether a release is safe, or verify that a rollback target is one you can actually roll back to.

You are solely responsible for the consequences of the deployments you trigger, including any outage, data loss, corruption, cost, or breach that results from what your pipeline does. This is true whether the deployment was triggered deliberately, mistakenly, or by someone you gave access to.

You are responsible for configuring appropriate permissions, environment protections, and approval requirements in GitHub, Jenkins, and your own infrastructure. GitLaunch respects the controls you have set; it cannot substitute for controls you have not set.

7. Your data

You keep all rights in the data you put into GitLaunch and the data your systems report to it ("Your Data"). We claim no ownership of it.

You grant us a limited licence to host, process, transmit, and display Your Data solely to operate and support the Service for you, and to comply with the law. That licence ends when the data is deleted. We do not use Your Data to train machine learning models, and we do not sell it.

You are responsible for having the right to give us Your Data, and for not putting things into GitLaunch that do not belong there — production secrets in a build label, or personal data you have no basis to share. Where Your Data includes personal data subject to the GDPR, we act as your processor and process it only on your instructions.

You can export your data at any time through the API. On request within 30 days of termination we will provide a machine-readable export.

8. Acceptable use

You agree not to:

  • use the Service to deploy, host, or distribute malware, or to attack any system;
  • access any account, data, or part of the Service that is not yours;
  • probe, scan, or test the vulnerability of the Service without our prior written consent — but see the note below;
  • interfere with the Service or place a disproportionate load on it, including through automated request volume beyond documented rate limits;
  • reverse engineer, decompile, or attempt to derive the source code of the Service, except where that restriction is unenforceable by law;
  • resell, sublicense, or offer the Service to third parties as your own; or
  • use the Service in violation of any applicable law, or to infringe anyone's rights.

Security research is welcome. If you find a vulnerability, tell us at support@gitlaunch.dev. We will not pursue legal action against good-faith research that respects other users' data, avoids degrading the Service, and gives us a reasonable chance to fix the issue before you publish.

We may suspend an account that is causing harm to the Service or to others. Where the circumstances allow it, we will warn you first and give you a chance to fix it.

9. Third-party services

GitLaunch works by talking to systems that are not ours: GitHub, a Jenkins server you run, Stripe for payments, Google if you sign in with it, and Resend to deliver our email. Your use of those systems is governed by their terms, not ours. Our Privacy Policy lists what each one receives.

We are not responsible for third-party outages, changes, or decisions. If GitHub is down, rate-limits us, changes an API, or suspends your organization, GitLaunch may be unable to trigger your deployments, and that is not a breach of these Terms by us. We will tell you what we know when it happens.

10. Plans, fees and taxes

Paid plans are billed in advance through Stripe on the cycle shown at checkout, and renew automatically until cancelled. Prices are in US dollars.

Free trials. Where we offer a trial, we will tell you its length and what happens at the end. Cancel before it ends and you will not be charged.

Cancellation. You may cancel at any time, effective at the end of the current billing period. You keep access until then. Fees already paid are non-refundable except where the law requires otherwise, or where we have materially failed to provide the Service and cannot put it right in a reasonable time.

Price changes. We will give you at least 30 days' notice before a price increase takes effect on your plan. If you do not want to pay the new price, cancel before it applies.

Failed payments. If a payment fails we may suspend the account after notifying you and allowing a reasonable time to fix it.

Taxes. Fees are exclusive of taxes. You are responsible for any sales, use, value-added, or similar taxes on your purchase, including Puerto Rico sales and use tax (IVU) where it applies, other than taxes on our net income. If you are exempt, send us valid documentation before we invoice you.

11. Term and termination

These Terms apply for as long as you have an account or use the Service.

You may stop using the Service and close your account at any time.

We may terminate or suspend your account if you materially breach these Terms and do not cure the breach within 30 days of our notice; immediately if you use the Service unlawfully or in a way that endangers the Service or other users; or on 30 days' notice if we discontinue the Service, in which case we will refund any prepaid fees covering the period after termination.

On termination your right to use the Service ends. We will delete Your Data as described in the Privacy Policy. Request an export within 30 days if you want one.

Sections 7, 12, 13, 14, 15, 16, 18 and 19 survive termination, along with any obligation to pay fees already incurred.

12. Confidentiality

Each of us may learn confidential information of the other. Each of us agrees to protect the other's confidential information with at least reasonable care, to use it only to perform under these Terms, and not to disclose it except to people who need it and are bound by similar obligations.

This does not cover information that is public through no fault of the recipient, was already known to the recipient, or is independently developed. If disclosure is legally compelled, the recipient will give notice where lawfully able, so the other can seek protection.

13. Intellectual property

The Service, including its software, design, and documentation, belongs to GitLaunch. These Terms grant you a right to use it, and transfer no ownership. Our name and logo are ours; please do not use them to suggest an endorsement we have not given.

Feedback. If you send us ideas or suggestions, we may use them freely and without obligation or compensation to you. We will not identify you as the source without your permission.

14. Disclaimer of warranties

The service is provided "as is" and "as available", without warranties of any kind, whether express, implied, or statutory. To the fullest extent permitted by law, we disclaim all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement.

In plain terms: we do not promise the Service will be uninterrupted, error-free, or secure against every attack; that it will meet your requirements; or that every deployment you trigger will succeed. This is a beta product and we are telling you so in advance.

Some jurisdictions do not allow the exclusion of implied warranties, so parts of this section may not apply to you, and nothing here limits any right you have that cannot be waived by contract.

15. Limitation of liability

To the fullest extent permitted by law, neither party will be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, or business interruption, even if advised such damages were possible.

Our total aggregate liability arising out of or relating to these Terms or the Service will not exceed the greater of (a) the fees you paid us in the twelve months before the event giving rise to the claim, or (b) one hundred US dollars (US$100).

This cap is central to the bargain. GitLaunch triggers deployments to systems whose value we cannot know and whose failure modes we do not control. We could not offer the Service at this price while accepting unlimited exposure to the consequences of a deployment you configured. If that allocation of risk does not suit your circumstances, please do not use the Service.

These limits do not apply to either party's liability for fraud, willful misconduct, gross negligence, death or personal injury caused by negligence, or any other liability that cannot be limited by law. They also do not limit your obligation to pay fees.

16. Indemnification

You will defend and indemnify GitLaunch against third-party claims, and reasonable legal costs, arising from your use of the Service in breach of these Terms, from Your Data, or from the consequences of deployments triggered through your account.

We will defend and indemnify you against third-party claims that the Service, used as permitted, infringes that party's intellectual property rights.

In each case the indemnified party must give prompt notice, let the indemnifying party control the defence, and cooperate reasonably. No settlement that admits fault or imposes an obligation on the indemnified party may be made without its consent.

17. Changes

To the Service. We are actively building GitLaunch and will add, change, and remove features. We will give reasonable advance notice before removing functionality you materially rely on, where we can.

To these Terms. We may update these Terms. For material changes we will give at least 30 days' notice by email or in the application before they take effect. If you keep using the Service after that, you accept the new Terms; if you do not accept them, cancel before they take effect and we will refund any prepaid fees covering the period after your cancellation. Changes will not apply retroactively to a dispute that already exists.

18. Governing law and disputes

These Terms are governed by the laws of the Commonwealth of Puerto Rico and applicable United States federal law, without regard to conflict of law rules. The UN Convention on Contracts for the International Sale of Goods does not apply.

Talk to us first. If something goes wrong, email support@gitlaunch.dev with the details. Both of us agree to try in good faith to resolve it informally for 30 days before filing anything. Most disputes end here, faster and cheaper than they would otherwise.

If that does not resolve it, the courts sitting in San Juan, Puerto Rico have exclusive jurisdiction, and both of us consent to venue there. Either of us may still seek injunctive relief in any competent court to protect intellectual property or confidential information.

Nothing in this section deprives a consumer of the protection of mandatory law in their country of residence, or of the right to bring proceedings in their local courts where that right cannot be excluded by contract.

19. General

Entire agreement. These Terms and the Privacy Policy are the whole agreement between us about the Service, and replace anything said before. If we sign a separate written agreement with you, that one controls where they conflict.

Severability. If a provision is unenforceable, it is modified to the minimum extent needed to make it enforceable, or severed, and the rest stays in force.

No waiver. Not enforcing a provision once does not waive it later.

Assignment. You may not assign these Terms without our written consent. We may assign them to an affiliate or in connection with a merger or sale of substantially all our assets, on notice to you.

Force majeure. Neither party is liable for a delay or failure caused by events beyond its reasonable control, excluding the obligation to pay.

Independent parties. Nothing here creates a partnership, agency, or employment relationship.

Notices. We will send notices to the email on your account; keep it current. Send legal notices to us at support@gitlaunch.dev, and at our registered address in Puerto Rico.

GitLaunch · deployment control your whole team can drive Privacy Terms Contact © GitLaunch