GETSSH Terms of Service
Effective Date: May 24, 2026
Last Updated: September 11, 2026
These Terms of Service (the “Terms”) are an agreement between you and RIESILING TECHNOLOGY LTD., which maintains GETSSH under the name Realmcloud Open Source Laboratory (“RIESILING,” “we,” “us,” or “our”), concerning the GETSSH software, official website, and related project resources.
By downloading, installing, accessing, or using GETSSH, you acknowledge that you have read and accepted these Terms. If you use GETSSH for an organization, you confirm that you have authority to accept these Terms on its behalf. If you do not agree, do not continue to use GETSSH.
1. Scope
These Terms apply to:
- official GETSSH software and preview releases published by RIESILING;
- the GETSSH official website, documentation, update information, and other project resources; and
- GETSSH-side conduct involved when you choose to connect, enable, or configure third-party functionality through GETSSH.
Third-party services, plugins, models, servers, and modified versions are the responsibility of their respective providers and may be governed by separate terms and privacy policies.
2. Open-Source License Takes Priority
GETSSH is free and open-source software. The GETSSH source code and official binaries released from it are licensed under the Apache License 2.0. Your rights and obligations to reproduce, use, modify, prepare derivative works of, sublicense, or distribute the Software are governed by that open-source license.
These Terms do not revoke, reduce, or replace rights granted to you under the Apache License 2.0. If these Terms conflict with that license on a software-licensing matter, the Apache License 2.0 controls. These Terms primarily address the official website and project resources, trademarks, third-party integrations, and matters not covered by the open-source license.
As of the Last Updated date, we do not offer a paid edition, commercial edition, subscription service, hosted account, or managed operations service. Any fee charged to you by a third party is not a fee charged or endorsed by RIESILING.
3. Official Builds, Modified Versions, and Trademarks
RIESILING identifies as an “official version” only a build expressly released through the GETSSH official website or official GitHub Releases page. Third-party builds, forks, modified versions, and derivative products created or distributed under the Apache License 2.0 may be lawful open-source uses, but they are not official RIESILING versions. We do not control their code, release process, security, availability, or data practices and provide no support or warranty for them.
The Apache License 2.0 does not grant a general license to use the GETSSH, RIESILING, or Realmcloud Open Source Laboratory names, marks, or logos. No person may falsely or misleadingly imply that a modified version, third-party product, or service was released, certified, sponsored, or endorsed by us. Reasonable use necessary to accurately describe the origin of a work is not affected.
4. Not a Hosted Service; No SLA
The official GETSSH client is a local open-source tool that runs on the user’s device. It is not an SSH, SFTP, AI, MCP, proxy, or cloud-account service hosted by us.
We provide no service-level agreement (SLA) or continuing-service commitment. Unless RIESILING signs a separate, express written agreement—which does not currently exist—we do not promise to:
- keep the Software, website, or any feature continuously available, uninterrupted, or error-free;
- respond to issues, provide support, fix defects, or disclose or patch security vulnerabilities within any period;
- continue maintaining any feature, platform, plugin interface, MCP interface, AI integration, or particular version; or
- follow a fixed release, compatibility, support, or lifecycle schedule.
Roadmaps, preview pages, estimated release dates, and feature descriptions are informational and are not guarantees. We may change, suspend, or discontinue any official version or project resource based on project capacity, security judgment, or technical direction, but doing so does not retroactively alter rights already received under the Apache License 2.0.
5. Authorized Use and User Responsibilities
You may connect to or administer only systems that you own, control, or have explicit authorization to access. You must comply with applicable law and the policies of target systems and must not use GETSSH for unauthorized access, attacks, malware distribution, credential theft, or other unlawful conduct.
You are responsible for:
- deciding whether GETSSH is suitable for your use and risk environment;
- protecting credentials, private keys, master passwords, local devices, and backups;
- verifying host fingerprints, download sources, versions, and the authenticity of updates;
- testing before use in production or important systems and maintaining recoverable backups of data and systems; and
- reviewing commands, file transfers, automations, AI suggestions, and the consequences of executing them.
This section describes general legal responsibilities and does not impose an additional field-of-use restriction on the license granted by the Apache License 2.0.
6. Local Data and Account Recovery
GETSSH connection profiles, credentials, keys, terminal content, history, and other client working data are processed locally by the Software on your device. We do not operate a GETSSH backend that receives or stores this client working data, and we cannot view, recover, reset, or back up that data for you.
If you enable a local encrypted vault, its protection depends on the version, configuration, device environment, and security of your master password. Loss of a master password or local data may make the data unrecoverable. You are responsible for safeguarding passwords and backups.
7. Network Connections and Third-Party Features
Depending on the features you use, GETSSH may connect directly from your device to servers you specify, code-hosting or update services, AI model providers, MCP servers, proxy services, plugin sources, or other external systems.
Third-party plugins, MCP tools and servers, AI models and vendors, proxies, packages, modified versions, and other external services are provided by independent parties. Unless we expressly state otherwise in writing, RIESILING:
- does not operate, control, audit, warrant, or endorse those third parties;
- does not determine their data practices, security measures, content, output, pricing, availability, or legality; and
- is not responsible for third-party code, model output, tool calls, data disclosure, service interruption, vendor conduct, or losses caused by modified versions.
Before enabling or connecting a third-party feature, you should review its permissions, code source, terms, and privacy policy. Data you send to a third party is governed by your relationship with that party.
8. Official Website and Privacy
The GETSSH official website does not provide user accounts and does not operate a proprietary business backend that stores GETSSH client working data. Network requests required to deliver the website, infrastructure logs, consent-enabled analytics, remote font requests, and similar technical data are processed on the systems of the relevant hosting, analytics, content, or network providers.
The GETSSH Privacy Policy governs how we handle website- and project-related data. Third-party providers may also process data independently under their own terms and privacy policies.
9. Preview Features and Security Risk
Preview releases, beta or experimental features, plugin interfaces, MCP, and AI features may be incomplete, unstable, materially changed, or affected by known and unknown defects. No software can be guaranteed to be free of vulnerabilities or completely protected against misuse.
Except where liability cannot lawfully be excluded, discovery of an issue, receipt of a security report, or public disclosure does not create a duty to provide continuing maintenance or monitoring, give notice, accept a patch, or fix the issue within a particular time. You should not use GETSSH in life-safety, critical-infrastructure, or other environments where failure could cause substantial personal injury or property damage without independent assessment and appropriate safeguards.
10. No Warranty
To the maximum extent permitted by applicable law, the GETSSH Software, website, documentation, and project resources are provided “AS IS” and “AS AVAILABLE,” with all faults. RIESILING, Realmcloud Open Source Laboratory, maintainers, authors, contributors, and licensors make no express, implied, statutory, or other warranty, including any warranty of title, non-infringement, merchantability, fitness for a particular purpose, security, accuracy, compatibility, availability, or freedom from error.
No documentation, roadmap, issue response, or community discussion creates a warranty or SLA unless RIESILING gives it in an express written agreement.
11. Limitation of Liability and Mandatory Exceptions
To the maximum extent permitted by applicable law, RIESILING, Realmcloud Open Source Laboratory, maintainers, authors, contributors, and licensors will not be liable for any direct or indirect loss arising from the use of or inability to use GETSSH, the website, project resources, unofficial versions, or third-party features. This includes loss of data, disclosure of credentials, compromise of systems, business interruption, loss of profit or revenue, replacement-service costs, and any incidental, special, consequential, punitive, or exemplary damages, regardless of the legal theory and even if advised that such damage was possible.
The exclusions and limitations above do not apply to liability that applicable law prohibits us from excluding or limiting, including liability for:
- fraud or fraudulent misrepresentation;
- knowingly making a contrary material security assurance despite a known serious risk;
- intentionally inserting malicious code or a vulnerability into an official release;
- death or personal injury caused by negligence; or
- gross negligence, wilful misconduct, or any other liability, to the extent it cannot lawfully be excluded.
If liability cannot be excluded entirely, it is limited to the greatest extent permitted by law and to loss directly caused by the relevant conduct that was reasonably foreseeable. These Terms do not create liability where applicable law would not otherwise impose it and do not make RIESILING jointly liable for the conduct of an independent third party, user, or unofficial distributor.
12. Intellectual Property and Contributions
Except for rights expressly granted by an open-source license, the respective rights holders retain their intellectual-property rights in the Software, website content, documentation, names, and marks. Code intentionally submitted to the GETSSH project is handled under the contribution rules published by the project at the time and the Apache License 2.0. You must have the rights necessary to submit any contribution.
13. Changes and Ending Use
We may update these Terms from time to time and will identify the “Last Updated” date on this page. We will provide reasonable notice of material changes through the website, Software, or project channels. A change applies only to use after it takes effect and does not retroactively revoke rights received under an open-source license.
You may stop using GETSSH at any time. A violation of these Terms may result in loss of access to the official website or project resources, but termination of a license to Software source code or binaries remains governed by the Apache License 2.0.
14. General Terms and Contact
If any part of these Terms is held invalid or unenforceable, the remaining parts remain effective, and the affected part will be interpreted as closely as the law permits to its intended effect. Failure to enforce a right is not a waiver. The English and Chinese versions are intended to express the same terms; if an inconsistency cannot be reconciled, the English version controls.
For questions about these Terms, contact us through the official repository:
Official Repository: https://github.com/JiangchenShen/GETSSH
GitHub issues are public. Do not submit passwords, private keys, personal data, or non-public vulnerability details there.