ArchForge Desktop Software Terms

Application and publisher

ArchForge Desktop is a desktop Git interface intended for Arch Linux/KDE Plasma and connects to https://archforge.nl. Product credit: Made by Jeffrey Services. Identify the legal software publisher and licensing details before publication: Jeffrey Services, License Identifier: MIT. This document supplements, and does not replace, the applicable source-code license included with each distribution.

Local data and permissions

The application operates on local Git working directories chosen by the user and may invoke the system Git binary. It can stage, commit, clone, fetch, pull and push; batch operations process repositories independently. A push affects a remote repository only when authorized by the server and user. Review changed files, remotes and branches before committing or pushing. The operator cannot guarantee recovery of overwritten local changes or force-pushed history.

Credentials and security

Personal access tokens and SSH credentials must be handled using supported OS security facilities where available, such as a suitable KDE Wallet/Secret Service integration. A temporary-session token may be offered when persistent storage is unavailable. Do not store passwords or API tokens in a repository. Signed release packages should be verified with a trusted public key. Installation and updates via pacman require user-controlled authorization for privileged operations.

Updates and support

The application may check for updates but should not install privileged updates without informed confirmation. Version availability, platform compatibility, signed releases, support contact and any warranty terms must reflect actual operations: **Our desktop application receives periodic updates to improve security, performance, stability, and functionality. Security vulnerabilities and critical bugs are addressed as soon as reasonably possible.

Users are encouraged to install the latest available version of the application to maintain security and compatibility.

Technical support is available through our official support channels. Updates are distributed through our official website or other authorized distribution channels.

Support and updates are provided on a best-effort basis, and no specific update frequency or resolution time is guaranteed.**. Upstream dependencies may have their own open-source licenses.

Licenses, warranties and mandatory rights

Software copyright and license permissions come from the actual distribution license and third-party notices, not just this policy. No statement here overrides mandatory consumer law or licenses granted under an applicable open-source license. The user retains ownership of their local repositories and work.

Changes and version history

This policy applies from its stated effective date once published. Material changes are dated and versioned. Earlier versions remain available to administrators for audit, and any notice or renewed agreement required by applicable law is handled separately. Questions and legally valid notices may be sent using the contact details in the Legal Notice.