Skip to main content

Archive Deployer

Deploy archives to GitHub

Terms of Service

Last updated:

1. Scope and about these terms

These Terms of Service (“Terms”) govern the use of the hosted Archive Deployer instance at https://push.leunos.com (the “Service”). Archive Deployer lets you unpack an archive, folder, or individual files in your browser and create a Git commit with the files you selected in a GitHub repository, including optional branch creation and pull requests.

Additional information on data processing is available in the Privacy Policy.

2. Eligibility and your responsibility

You may use the Service if you have a GitHub account and its use is lawful in your jurisdiction. You are responsible for your use of the Service, for the accuracy of the deployment configuration you enter, and for ensuring that your use of the Service complies with these Terms, GitHub’s terms, and applicable law.

3. GitHub authentication and your credentials

The Service authenticates you against GitHub using GitHub OAuth or a GitHub Personal Access Token (PAT) that you provide. OAuth tokens are obtained with the repo, read:user, and workflow scopes; for PATs, you choose the scopes yourself.

You are solely responsible for maintaining the confidentiality of your GitHub credentials and for their appropriate permission scope. Do not sign in with credentials that grant broader access than you intend. You can revoke the Service’s access at any time: by disconnecting in the application or removing the authorized OAuth application in your GitHub settings, or by deleting a PAT in your GitHub settings. The Service processes your token only to perform the GitHub operations you request while you are signed in.

4. Repository permissions

The Service acts only on GitHub repositories for which your supplied GitHub credentials hold the required permissions. The repository and branch selection lists are derived from your credentials, and GitHub rejects operations your credential is not permitted to perform. You remain responsible for ensuring that you are authorized to modify every repository, branch, and path you target.

5. User-supplied archives, folders, and files

All content you deploy (“User Content”) is your responsibility. You retain ownership of your User Content. You grant the operator only the technical permission necessary to process and transmit your User Content in order to create the commit you requested — a limited, temporary right of use for performing the requested deployment.

You confirm that you hold the necessary copyrights, licenses, and permissions for the content you deploy and that deploying it into the target repository does not violate the rights of third parties or any license that applies to the target repository.

6. Prohibited use

You must not use the Service to:

  • deploy or distribute unlawful material, malware, phishing content, or content designed to steal credentials or compromise systems;
  • gain or enable unauthorized access to accounts, repositories, systems, or networks, or deploy content into repositories you are not authorized to modify;
  • abuse GitHub, the Service, or the underlying infrastructure, including circumventing rate limits, processing limits, or security measures, or generating load that degrades the Service for others;
  • use the Service destructively against repositories, for example overwriting content without authorization;
  • interfere with or disrupt the integrity or performance of the Service, or share, resell, or broker access to the Service in violation of these Terms; or
  • misrepresent your identity or your relationship to a repository or organization.

7. Processing limits and safety behavior

The Service applies processing limits and an archive safety policy to protect you, GitHub, and the infrastructure. Unsafe, ignored, or oversized archive entries may be skipped or rejected and are reported to you before deployment. Limits may change as the Service evolves.

  • Total source size: 500 MiB; up to 1,000 extracted files per source.
  • Per-file limits: 5 MiB, or 3 MiB when a file is sent straight through the API without intermediate object storage.
  • Rejection or skipping of unsafe paths (such as path traversal patterns), sensitive defaults (.env files), and system directories (.git, node_modules).

Branch updates are performed without force: if the target branch has moved since a deployment was prepared, the update is rejected instead of overwriting the branch. This safety behavior is described for information; it is not a substitute for your own review under section 10.

8. Third-party services

The Service depends on third-party services — in particular GitHub (API, authentication) and the selected hosting platform (Vercel or another compatible host, or OpenAI ChatGPT Sites with Cloudflare) — and may use Redis, D1, and object storage providers configured by the operator. Your use of those services is additionally governed by the respective provider’s terms and privacy statements, which are outside the operator’s control. The operator is not responsible for third-party services beyond the scope of its own responsibility for the Service.

9. Availability; uploaded files are not stored permanently

The Service is provided on the basis of the functionality described on this website. There is no guarantee of uninterrupted availability, error-free operation, permanent storage of any uploaded data, or a successful deployment. Deployments can fail, for example because of GitHub rate limits, repository state, or infrastructure availability.

Where temporary object storage is used, uploaded file contents are working space only: they are deleted after the deployment is confirmed, retained for a short recovery window after terminal failures, and expire when an upload is abandoned. These uploads are not backups, and the Service must not be used as a storage location.

10. Your deployment configuration

A deployment creates a real commit in a real repository. Before you execute a deployment, you are responsible for reviewing the target repository, branch, target path, commit message, and pull request configuration. You are also responsible for using a suitable target — for example creating a new branch or pull request when you do not intend to commit directly to an existing branch.

11. Suspension and termination

You can stop using the Service at any time; disconnecting the application’s GitHub access ends your session. The operator may restrict, suspend, or terminate access to the Service where reasonably necessary to prevent or address abuse, security threats, prohibited use under section 6, or violations of law or of these Terms, or to protect the Service, its users, or third parties. Where reasonably possible and lawful, the operator will inform you of a measure and its reason.

12. Changes to the Service and these Terms

The operator may develop, change, or discontinue features of the Service, and may update these Terms for legal, security, or technical reasons. Material changes will be published on this website, for example by publishing the updated Terms with a new “Last updated” date. Continuing to use the Service after publication of changes constitutes acceptance; if you do not agree with the changed Terms, you must stop using the Service.

13. Warranty

To the extent permitted by law, no guarantee of specific features, of uninterrupted availability, or of successful deployments is given. The statutory warranty and liability rights that cannot be excluded under applicable law — in particular your rights as a consumer — remain unaffected.

14. Limitation of liability

The operator is liable without limitation for damage caused intentionally or by gross negligence, for injury to life, body, or health, in accordance with any guarantee expressly given, and under mandatory statutory liability regimes (such as the German Product Liability Act).

In the case of a slightly negligent breach of a material contractual obligation — an obligation whose fulfilment is essential for the proper performance of these Terms and on whose compliance you may regularly rely — liability is limited to the damage typically foreseeable at the time of using the Service and typical for this type of service. Beyond that, liability for slight negligence is excluded to the extent permitted by law. The above limitations do not shift the burden of proof where mandatory law provides otherwise.

15. Governing law and jurisdiction

These Terms are governed by the laws of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG). These choice-of-law provisions do not deprive you, as a consumer with habitual residence in the EU or EEA, of the protection of mandatory provisions of the law of your country of residence.

Statutory jurisdiction rules apply. In particular, as a consumer you may bring proceedings before the courts of your place of residence where applicable law so provides, and mandatory consumer protections remain unaffected.

16. Contact

The operator of the Service is the controller identified in the Privacy Policy, section 1.