BRANCH TERMS

Branch End User License Agreement (Beta)

Effective: 20 October 2026
Language: English · 한국어 (prevails)
Contact: support@paldyn.com

1. Purpose and acceptance

This Agreement sets out the terms on which you may use the executable files, updates and accompanying documentation (together, the "Software") of "Branch", a desktop Git client provided by Paldyn (팔딘; "PALDYN", "we" or "us").
By installing or using the Software, you agree to this Agreement. If you do not agree, do not install or use the Software.
If you use the Software on behalf of a company or other organization, you confirm that you are authorized to accept this Agreement on its behalf.

2. Definitions

"Beta Period" means the period until PALDYN announces, by a notice on PALDYN's website (paldyn.com/branch) and in the update release notes, the general release of the Software or the end of the beta.
"Paid Plan" means any form of use of the Software that PALDYN provides for a fee, such as a subscription, a one-time purchase or paid features.
"Update" means a revision, new version or patch of the Software provided by PALDYN.
"Third-Party Components" means open-source software, fonts, icons and other components included in the Software in which third parties hold rights.
"Feedback" means comments, suggestions, bug reports and similar input about the Software that you provide to PALDYN.

3. Beta license grant

Subject to this Agreement, PALDYN grants you, during the Beta Period, a free of charge, non-exclusive, non-transferable, non-sublicensable and revocable license to use the Software.
You may use the Software for both personal and commercial purposes, including managing work repositories.
This license is limited to installing and using the Software, in the executable form distributed by PALDYN, on devices that you own or lawfully control. No rights in the source code are granted.
All rights not expressly granted in this Agreement are reserved by PALDYN.

4. Introduction of paid plans

PALDYN may introduce Paid Plans, subscriptions or paid features in the future.
If PALDYN introduces a Paid Plan or changes what is offered free of charge, it will announce the change and its effective date by a notice on PALDYN's website (paldyn.com/branch) and in the update release notes at least 30 days before that date.
Some or all features offered free of charge during the Beta Period may, after the beta ends or when a Paid Plan is introduced, become available only under a Paid Plan. PALDYN does not guarantee that features offered during the Beta Period, or free use, will continue.
PALDYN will not charge you unless you expressly accept separate paid terms and complete the payment process. Paid Plans are governed by those separate paid terms together with this Agreement, and your statutory rights, such as the right to withdraw from a purchase, are governed by those terms and applicable law.
The Software works with standard Git repositories through Git: the Git included with the Software or, if you choose it in the settings, the Git installed on your computer. Whether or not a Paid Plan is introduced or your license ends, you can therefore keep using your repositories with other Git tools.

5. Restrictions

You must not:

copy the Software beyond what is needed for its normal installation and operation and for backups of your devices, or distribute, redistribute, sell, rent, lease, sublicense or make the Software available to the public;
modify, translate or adapt the Software, or create derivative works of it;
reverse engineer, decompile or disassemble the Software, or otherwise attempt to derive its source code, except to the extent that applicable law expressly permits this despite this restriction;
circumvent, disable or defeat any technical protection or license-management measure of the Software, such as license checks, paid-feature restrictions or update signature verification;
remove or alter any copyright, license or trademark notice included in the Software; or
use the Software in violation of law or in a way that infringes the rights of others.

6. Updates

PALDYN may provide Updates but has no obligation to provide Updates or to maintain any particular feature.
The Software includes a built-in updater that works as follows:
1. When "Automatically check for updates" in the Updates settings is on (the default), the Software checks for a new version when it starts. When this setting is off, it checks only when you ask it to.
2. When "Automatically download updates" in the same settings is on (the default), the Software downloads a new version it finds in the background and verifies its signature. When this setting is off, it downloads an Update only when you choose to.
3. An Update is installed only after you confirm, and the Software then restarts to complete the installation.
4. The Software installs only Updates signed with PALDYN's signing key and does not install an Update whose signature cannot be verified.
You agree that Updates may be downloaded and installed through the built-in updater. This Agreement applies to Updates, except where an Update comes with separate terms, in which case those terms apply.
PALDYN may stop supporting, or providing Updates for, earlier versions.

7. Data practices

PALDYN does not use the Software to collect your personal information, repository contents, files, commits, credentials or usage history, or to send them to PALDYN's servers. The Software contains no usage analytics, telemetry, advertising or crash reporting.
Updates and author photos. The only network communications that the Software starts without your request are the update check and the automatic update download described in Section 6.2 and the author photo requests described at the end of this paragraph. Update checks and update downloads use HTTPS only and request the update information file and update files that PALDYN publishes in its public paldyn/Branch-releases repository on GitHub (github.com, operated by GitHub, Inc.). These requests contain no user identifier, account information or repository information added by the Software. As with any internet request, however, ordinary request information such as your IP address, the time of the request and the updater's identification string (User-Agent) reaches GitHub and is handled under GitHub's privacy statement. PALDYN can see the aggregate download count of each file that GitHub provides, which does not identify individual users. While "Author photos" is turned on in the settings (it is on by default), the Software loads, over HTTPS through its built-in web view, the photo of each commit author it shows: when the author's email address is a GitHub no-reply address (number+name@users.noreply.github.com), from GitHub (avatars.githubusercontent.com), sending only the account number in that address; for any other author email address, from Gravatar (gravatar.com, operated by Automattic Inc.), sending only the SHA-256 hash of that email address. These requests contain nothing else added by the Software. The hash does not make the email address anonymous, however: Automattic can recognize addresses registered with Gravatar, and anyone who knows or guesses an address can compute its hash and match it. Ordinary request information, such as your IP address, the time of the request, and the web view's identification string (User-Agent) and language preferences, reaches GitHub or Automattic with each request and is handled under their privacy statements, so these services can tell which commit authors are being viewed from your connection. Turning off "Author photos" in Settings → Appearance stops these requests.
Git remote operations. Git remote operations, such as cloning, fetching, pulling, pushing, listing remote references (including the connection check in Settings → Git) and adding or updating submodules, run only when you request them. The Software performs them by running a Git program (the Git included with the Software or, if you choose it in the settings or the included Git cannot run, the Git installed on your computer) and connects only to remote addresses that you enter or that are configured in the repository, including submodule addresses. The permitted transports are file, https, http, ssh and git. Authentication is handled by your Git configuration, SSH keys and credential helpers; the Software itself does not store passwords, tokens or other credentials. When the included Git is used, the macOS keychain credential helper of Git that is included with the Software is configured by default (your Git configuration can replace it). Like the helper of Apple's Git, it stores the HTTPS credentials with which Git has signed in successfully in the login keychain on your computer and reads them from there; they are not sent to PALDYN. If you include credentials in a remote address, however, Git may record that address in the repository configuration. Information exchanged with a remote service (for example GitHub, GitLab, Bitbucket or Azure DevOps) is subject to that service's terms and privacy statement. Git behaves as your Git and repository configuration directs, for example when running Git hooks or when Git automatically downloads missing objects in a partial clone. The Software periodically re-reads repository status to keep its display current, but it does not run Git commands that contact remote repositories, such as fetch, for this purpose.
Information stored on your device. The Software stores the following information only on your device and does not send it to PALDYN:
1. settings (such as theme, accent color, language, keyboard shortcuts, the update settings and the external editor you chose, which is an application name or the path of an application you selected), workspace information (local paths of the repositories you opened, tabs and groups), the version and release notes of an Update recorded right before it is installed (used to show release notes after the restart; this temporary entry is deleted once shown or no longer needed), the most recently installed version's release notes retained for reopening in Settings regardless of the automatic-popup setting (replaced by the next installed version's notes and excluded from backups), and, for each repository, commit message drafts in progress, layout, the name of the branch to return to after you check out a specific commit, and the commit ID at which a detached HEAD began: in the local storage of the Software's built-in web view (on macOS, ~/Library/WebKit/com.paldyn.branch/);
2. window position and size, the choice of Git executable and the system-level Git configuration generated for the included Git: in .window-state.json, git-executable.json and bundled-git/gitconfig in the application settings folder (on macOS, ~/Library/Application Support/com.paldyn.branch/);
3. Git author name and email: written to your Git configuration (global or for the repository) only when you save them in the settings;
4. temporary working files needed for an interactive rebase: inside that repository's .git folder;
5. recovery references: before a reset, a rebase or an interactive rebase, the Software records the commit that HEAD points to, and before it deletes a branch or tag in a remote repository, it first fetches the commit or tag that the remote branch or tag points to. Before a force push, it records the remote commit confirmed for replacement. It keeps each of these in that repository as a Git reference under refs/branch/recovery/, with a reflog entry, so that the previous state can be recovered. When a new checkpoint is created, the Software keeps the newest 20 references it can identify as its own or those created less than 14 days ago; older references that satisfy neither condition are eligible for automatic cleanup. It does not automatically delete references used by active sessions or references it cannot identify as created by the Software, and it skips cleanup if it cannot read session information from any worktree of the repository. Some references may therefore remain longer. You can also delete them yourself, for example with git update-ref -d <reference name>, or all at once with git for-each-ref --format='delete %(refname)' refs/branch/recovery/ | git update-ref --stdin. While they remain, Git's garbage collection does not remove the commits they point to, even after a reset has removed those commits from your branches. Ordinary pushes and clones do not transfer these references, but commands that copy every reference of a repository, such as git push --mirror or git clone --mirror, do; and
6. if settings saved under the identifier of an earlier version exist, the Software copies them to the new location on your device the first time it runs;
7. author photos loaded under paragraph 2 and their addresses, which contain the email hashes or GitHub account numbers: in the built-in web view's cache in ~/Library/Caches/com.paldyn.branch/ (on macOS). They can remain there after you turn off "Author photos".
This information may remain on your device after you delete the Software. You can delete the files in the locations above, and the recovery references in item 5, yourself.
Other local integrations. When you ask it to, the Software opens a repository in Finder, Terminal or the external editor you choose in Settings → External apps (Visual Studio Code unless you choose another application), opens the official release notes page in your default browser, copies text to the clipboard and opens file selection dialogs. Previews of repository contents, such as image previews, are processed entirely on your device.
If PALDYN intends to process information differently from this Section, for example for license checks of a Paid Plan, it will first amend this Agreement, announce the change by a notice on PALDYN's website (paldyn.com/branch) and in the update release notes and, where applicable law requires, obtain your consent.

8. Ownership

The Software is licensed, not sold. All intellectual property rights in the Software, its copies and Updates, including copyrights, patents, trademarks and trade secrets, belong to PALDYN or its licensors.
Rights in the repositories, files, commits and other content you work with in the Software remain with you or their rightful owners, and PALDYN acquires no rights in that content under this Agreement.

9. Feedback

You are not required to provide Feedback.
If you provide Feedback, PALDYN has a worldwide, perpetual, irrevocable and royalty-free right to use, modify, publish and commercialize it in the Software and in PALDYN's products and services, without payment or attribution to you.
Do not include confidential information or content in which others hold rights in your Feedback. PALDYN has no duty of confidentiality regarding Feedback; however, personal information provided with Feedback is handled in accordance with applicable law.

10. Third-party components and services

The Software includes Third-Party Components. Their list and full license texts are in THIRD_PARTY_NOTICES.md, provided with the Software. For the Git programs included with the Software, THIRD_PARTY_NOTICES.md names the license texts and the offer of their source code, which are provided together with those programs (in the macOS app, in Contents/Resources/git/share/doc/branch-bundled-git/). Third-Party Components are governed by their own licenses, and nothing in this Agreement, including Section 5, limits the rights you have under those licenses.
Services operated by third parties, such as GitHub, are governed by those third parties' terms. PALDYN is not responsible for the availability, content or information handling of third-party services.
The names and logos of GitHub, GitLab, Bitbucket and Azure DevOps shown in the Software are trademarks of their respective owners and are used only to identify the service that hosts a remote repository. Their use does not imply any affiliation with, sponsorship by or endorsement by those owners.

11. Beta software and disclaimer of warranties

The Software is a beta version. It may contain errors, defects or missing features and may change without notice.
The Software is provided "AS IS" and "AS AVAILABLE". To the maximum extent permitted by applicable law, PALDYN makes no warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy and uninterrupted operation.
Some Git operations, such as reset, discarding changes, rebase and deleting branches or tags, may be irreversible. You should back up important data regularly.
This Section does not apply to any of your rights that cannot be excluded or limited under applicable law. Any part of this Section that is invalid under the Act on the Regulation of Terms and Conditions of the Republic of Korea or other applicable law does not apply, and applicable law governs that part instead.

12. Limitation of liability

To the maximum extent permitted by applicable law, PALDYN is not liable for any indirect, special, incidental, consequential or punitive damages, or for any loss of profits, revenue, data or business opportunities, arising from the use of or inability to use the Software, whether or not PALDYN was aware of the possibility of such damages.
To the maximum extent permitted by applicable law, PALDYN's total liability arising from or relating to this Agreement or the Software will not exceed the greater of the amount you paid PALDYN to use the Software and KRW 100,000.
Sections 12.1 and 12.2 do not apply to damages caused by PALDYN's willful misconduct or gross negligence, to damages to life or physical health, or in any other case in which liability cannot be excluded or limited under applicable law. Any part of this Section that is invalid under the Act on the Regulation of Terms and Conditions of the Republic of Korea or other applicable law does not apply, and applicable law governs that part instead.

13. Term and termination

This Agreement takes effect when you install or use the Software and remains in effect until terminated.
You may terminate this Agreement at any time by ceasing to use the Software and deleting all copies of it.
If you materially breach this Agreement, PALDYN may terminate your license immediately by notifying you.
PALDYN may end the beta license, for reasons such as the end of the beta or discontinuation of the Software, after announcing it by a notice on PALDYN's website (paldyn.com/branch) and in the update release notes at least 30 days in advance. If a Paid Plan is introduced, the end of the beta license and any transition are governed by Section 4.
When your license ends, you must stop using the Software and delete all copies of it. Your repositories remain intact, and you can keep using them with other Git tools.
Sections 5, 8 to 12, 15 and 16 survive termination of this Agreement.

14. Changes to this Agreement

PALDYN may change this Agreement to the extent permitted by applicable law.
PALDYN will announce the changes and their effective date by a notice on PALDYN's website (paldyn.com/branch) and in the update release notes at least 30 days before that date.
If you continue to use the Software after the effective date of the changed Agreement, you are deemed to have accepted the changes. If you do not accept them, you may stop using the Software and terminate this Agreement.

15. Governing law and jurisdiction

This Agreement is governed by and construed in accordance with the laws of the Republic of Korea.
The court with jurisdiction over disputes arising from or relating to this Agreement or the Software is determined under the Civil Procedure Act of the Republic of Korea and other applicable law.

16. General

This Agreement is the entire agreement between you and PALDYN regarding the Software and supersedes any prior agreement or representation on that subject, except that separate terms for Paid Plans apply to those plans.
If any provision of this Agreement is invalid or unenforceable, the remaining provisions remain in effect.
PALDYN's failure or delay in exercising a right under this Agreement is not a waiver of that right.
You may not assign this Agreement or your rights under it without PALDYN's prior written consent. PALDYN may transfer its position under this Agreement in connection with a merger, business transfer or similar transaction.
This Agreement is written in Korean and English. If the two versions differ, the Korean version prevails.

17. Contact

For questions about this Agreement or the Software, contact:

Company: Paldyn (팔딘)
Representative: Wonmo Lee (이원모)
Email: support@paldyn.com

Effective date

This Agreement takes effect on 20 October 2026.