Effective Date: October 15th, 2026 Last Updated: October 15th, 2026
This Addendum applies where the GitHub repository delivery option — under which the Company provides Outputs via a private GitHub repository mirror — is provided as part of the User's plan and the User uses it. It applies equally to all Users worldwide. Where the Company delivers Outputs by other means (such as downloadable archives or deployment bundles), this Addendum does not apply. In this Addendum, "User" includes the owner and members of a project who join the repository under Section 2. Terms not defined in this Addendum have the meanings given in the BackendX Terms of Use (the "Terms").
1. Repository Ownership
All repositories, including GitHub mirror repositories, are owned or controlled by BackendX Inc. under GitHub accounts or organizations managed by the Company. A transfer of the ownership of a project to another User does not change who owns or controls the repository.
2. Access Rights
The Company provides read-only collaborator access to the private mirror repository for viewing, cloning, and downloading Outputs. The mirror reflects the project's main branch only.
-
A User who has permission to access the project's source code (the project owner and members in a role with that permission) may request to join the repository after connecting a GitHub account to the Service and accepting this Addendum, and the Company invites the requesting User's GitHub account as a read-only collaborator.
-
The User may stop participating in the repository at any time.
-
Access may be revoked in the following cases:
- where, following a plan change, the GitHub repository delivery option is no longer provided;
- where the User leaves or is removed from the project, or loses permission to access the project's source code, for example because of a change of role or the loss of a Seat;
- where the project is deleted, or the User disconnects their GitHub account or deletes their Account; or
- where access to the Service is suspended, restricted, or terminated under Section 14 of the Terms. In that case access may be revoked without prior notice in accordance with Section 14.1 of the Terms, and where circumstances permit the Company will notify the User of the reason.
-
A User whose access has been revoked and who again has permission to access the project's source code may request to join again under paragraph 1.
3. Mirror Updates and Deletion of Content
The mirror repository is force-updated when the project is regenerated, and its history may be rewritten at any time (Section 7.2 of the Terms). In accordance with Sections 7.2 and 7.3 of the Terms, the Company may delete repositories, branches, or commits where the delivery method or repository structure changes, where the project is regenerated, or where operationally necessary, and is not obligated to restore deleted content. Upon project deletion, the mirror repository is deleted. Copies the User has already cloned or downloaded are not affected. The User may copy the Outputs to their own devices or to repositories they control. However, a copy made with GitHub's fork feature may, under GitHub's policies, be deleted when access to the mirror repository is revoked or the mirror repository is deleted; a User who wishes to keep the Outputs should clone the repository and push it to a repository the User controls.
4. GitHub Account Information
To provide collaborator access, the Company processes the GitHub account information registered with the Service by a User who requests to join the repository, as described in the Privacy Policy. The User may disconnect their GitHub account at any time, which ends collaborator access to every repository the User has joined. Reconnecting a GitHub account does not automatically rejoin the User to any repository previously joined; the User must request to join again under paragraph 1 of Section 2.
5. Disclaimer
Repository content is AI-generated and may contain errors, inaccuracies, or security vulnerabilities. In accordance with Section 15.7 of the Terms, the Company provides no warranty regarding its quality, legality, or fitness for purpose.
6. User Obligations
Users must not:
- Attempt unauthorized access to repositories owned or managed by the Company
- Attempt to modify the mirror repository or its settings beyond the granted read-only permission
- Use repository collaboration features available to a read-only collaborator (such as issues or pull requests) to post malicious, unlawful, or infringing content, or personal or sensitive information
- Circumvent, or attempt to circumvent, the read-only nature of the access, including by sharing collaborator access with third parties
7. Intellectual Property
Repository access does not grant rights to the Company's internal models, algorithms, source code, or infrastructure. Rights in the Outputs themselves are governed by Section 15 of the Terms.
8. Governing Law and Jurisdiction
- This Addendum is governed by the laws of the Republic of Korea.
- Disputes shall be resolved as set out in Section 19 of the Terms (including the consumer-forum provisions of Section 19.4).