Who we are
GitLaunch ("GitLaunch", "we", "us") is operated by GitLaunch LLC, a limited liability company organized under the laws of the Commonwealth of Puerto Rico, United States.
For the purposes of the EU and UK General Data Protection Regulation, we are the data controller for the account and marketing information described in this policy. Where our customers use GitLaunch to process information about their own staff or systems, we act as a data processor on that customer's instructions, and our Terms of Service govern that relationship.
You can reach us about anything in this policy at support@gitlaunch.dev.
What this policy covers
This policy applies to the GitLaunch website, the GitLaunch application, and our API. It does not apply to the third-party systems you connect to GitLaunch — your GitHub organization, or a Jenkins server you operate. Those systems remain under your control and your own policies, and connecting them to GitLaunch does not put us in charge of them.
Information we collect
Account information
There are three ways into GitLaunch, and what we hold depends on which you use. In every case we store your email address, your display name, your avatar URL where one is available, and the times your account was created and last used.
-
Sign in with GitHub. We request only the
user:emailscope and store your GitHub user ID and username. We never receive your GitHub password. -
Sign in with Google. We request only the
openid email profilescopes — enough to know who you are and reach you — and store the account identifier Google gives us. We never receive your Google password. - Sign in with an email address and a password. We store your password only as a one-way bcrypt hash. We cannot read it, recover it, or tell you what it is, and no one at GitLaunch can. We also store whether your address has been confirmed, and while it has not, a single-use confirmation token that expires after 24 hours.
Signing in with GitHub or Google means those companies learn that you use GitLaunch. Their own privacy policies govern what they do with that.
Deployment and build data
To do its job, GitLaunch stores the operational record of your deployments: service and environment names, repository names and identifiers, build and deployment status, version or commit identifiers, timestamps, and which user triggered a given deploy or rollback. This is a record of what happened, not of what your code contains.
Integration credentials
If you connect a Jenkins server, we store the credentials you provide so we can talk to it on your behalf. These are encrypted at rest using authenticated encryption with a key held outside the database. API keys you generate for our own API are stored only as a one-way bcrypt hash — we show you the key once, at creation, and cannot recover it afterwards. If you lose it, we can only issue a new one.
Billing information
Payments are processed by Stripe. Card numbers are entered directly with Stripe and never reach our servers. We store the subscription and customer identifiers Stripe gives us, your plan, and your subscription status, so we know what you are entitled to use.
Waitlist and campaign attribution
If you join our waitlist, we store the email address you give us. We also store how you
found us, where the inbound link carried that information: the UTM campaign parameters
on the URL (utm_source, utm_medium, utm_campaign,
utm_term, utm_content) and the referring page. This tells us
which of our announcements were worth making. Each value is truncated before storage.
Product analytics
We record how GitLaunch itself is used — pages visited, features used, and the outcome of actions such as a deploy being started — along with an identifier for the account and user involved, and a timestamp. We use this to find where the product is confusing or broken. This data is stored in our own database and is not transmitted to any third-party analytics or advertising provider.
Technical logs
Our servers and our hosting provider produce operational logs — requests, errors, and timings — which may include IP addresses. We use these to keep the service running and to investigate abuse and outages, and nothing else.
What we never collect
Stating this plainly, because it is the question engineering teams actually ask:
- Your source code. Our GitHub integration calls only the endpoints needed to identify you, list the repositories you have granted us, and trigger a workflow run. It does not request repository contents permission and cannot read your files, branches, or commit diffs.
- Any password in a form we can read. GitHub and Google authentication happen at those providers, and we receive only a scoped token — never a password. Where you set a password with us directly, we keep only a bcrypt hash of it, which cannot be reversed into the original.
- Your payment card details. Those exist between you and Stripe.
- Advertising or cross-site tracking identifiers. We run no third-party trackers, no advertising pixels, and no session-replay tooling. We do not build profiles of you across other websites, because we have no means of doing so.
- Special category data — health, biometrics, race, religion, political opinions. We have no use for it and do not ask for it.
How and why we use it
Where the EU or UK GDPR applies, we must have a lawful basis for each use. Ours are:
| What we do | Lawful basis |
|---|---|
| Provide the service: authenticate you, show your deployments, run deploys and rollbacks you request | Performance of a contract |
| Bill you and keep tax records | Contract; legal obligation |
| Keep the service secure, prevent abuse, and investigate incidents | Legitimate interests — running a service that is not compromised |
| Understand product usage and improve GitLaunch | Legitimate interests — improving a product people rely on, using first-party data only |
| Confirm that an email address used to sign up belongs to you | Contract; legitimate interests — stopping someone opening an account in your name |
| Send you service and account notices you cannot opt out of while you hold an account (security, billing, breaking changes) | Contract |
| Email you about the waitlist and product news | Consent, given when you submit the waitlist form — withdrawable at any time |
| Test which landing-page wording explains the product better | Legitimate interests — measuring our own marketing with a short-lived, first-party identifier |
| Comply with the law and respond to lawful requests | Legal obligation |
Where we rely on legitimate interests, we have weighed those interests against your rights, and you may object at any time under section 11.
We do not make automated decisions producing legal or similarly significant effects about you, and we do not use your data to train machine learning models.
International transfers
We operate from Puerto Rico and our infrastructure is located in the United States. If you use GitLaunch from the European Economic Area, the United Kingdom, or Switzerland, your information is transferred to and processed in the United States.
For those transfers we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum, where applicable), together with the technical measures described in section 10. You may request a copy of the relevant clauses by emailing us.
How long we keep it
We keep information only as long as it is doing a job, and no longer:
| Information | Kept for |
|---|---|
| Account and profile data | While your account is open, then deleted within 30 days of closure |
| Deployment and build history | While your account is open, then deleted with the account |
| Integration credentials | Until you disconnect the integration or close the account, then deleted |
| Email confirmation tokens | 24 hours, then expired and unusable |
| Billing and tax records | Seven years from the transaction, as US and Puerto Rico tax law requires |
| Product analytics events | 24 months, then automatically expired by the database |
| Waitlist entries | Until you unsubscribe or ask us to delete them, or 24 months after we stop operating a waitlist |
| Operational logs | Up to 90 days |
Backups are on their own cycle and are overwritten in the ordinary course, normally within 90 days. Deleted data can persist in a backup until that backup rolls over.
How we protect it
- All traffic to GitLaunch is encrypted in transit with TLS.
- Integration credentials are encrypted at rest with authenticated encryption, under a key that is not stored in the database. Key rotation is supported without downtime.
- API keys and account passwords are stored only as bcrypt hashes and cannot be recovered — only replaced or reset.
- Email confirmation tokens are 32 bytes from a cryptographically secure random source, are single-use, and expire after 24 hours.
- Session cookies are
HttpOnlyandSameSite-restricted; the sign-in flow is protected against cross-site request forgery. - Every query is scoped to an account, so one customer's data cannot be reached from another's session.
- Access to production data is limited to personnel who need it to operate the service.
No system is perfectly secure, and we will not claim otherwise. What we can tell you is what we have actually built, which is the list above.
Your rights
We extend the core rights below to every user, wherever you live. Some of them are legal entitlements only in certain places; we would rather not run two standards.
- Access — get a copy of the personal information we hold about you.
- Portability — receive it in a structured, machine-readable format.
- Correction — have inaccurate information fixed.
- Deletion — have your information erased, subject to records we must keep by law (chiefly tax records).
- Restriction and objection — ask us to pause a use, or object to processing based on legitimate interests, including our product analytics.
- Withdraw consent — unsubscribe from marketing email at any time, without affecting anything we did before you withdrew.
- Non-discrimination — we will not degrade your service or change your price because you exercised a right.
To exercise any of these, email support@gitlaunch.dev. We will verify your request against the email on your account and respond within 30 days, or tell you why we need longer. This is free of charge. You may use an authorised agent where the law allows it.
If you are in the EEA or UK, you also have the right to complain to your local supervisory authority. We would appreciate the chance to resolve it first.
If you are in California, the rights above satisfy your CCPA/CPRA rights to know, delete, correct, and opt out. Because we neither sell nor share personal information, there is no "Do Not Sell or Share My Personal Information" action for you to take — the answer is already no.
Children
GitLaunch is a tool for professional software teams. It is not directed to children, and we do not knowingly collect personal information from anyone under 18. If you believe a child has given us information, write to us and we will delete it.
Security incidents
If a security breach compromises your personal information, we will notify you without undue delay once we have established what happened and who is affected.
As a Puerto Rico entity we are also subject to the Citizen Information on Data Banks Security Act (Act No. 111 of September 7, 2005), which requires us to notify the Puerto Rico Department of Consumer Affairs within ten days of detecting a breach of protected personal information, and to notify affected individuals. Where the GDPR applies, we will notify the relevant supervisory authority within 72 hours as Article 33 requires. We will meet whichever obligations apply to you, and we will not wait to be asked.
Changes to this policy
When we change this policy we will update the effective date at the top. If a change materially affects your rights or meaningfully expands how we use your information, we will tell you by email or in the application before it takes effect, and give you a reasonable chance to object or close your account. We will not apply a materially expanded use to information we already hold without your consent where the law requires it.
Contact us
Privacy questions, rights requests, and everything else: support@gitlaunch.dev
GitLaunch LLC, Commonwealth of Puerto Rico, United States.