rConfig Web Terminal Preview Addendum

Version, Parties and Scope

Version 0.1 (Preview)
Last Updated: 31st October 2026
Proposed Effective Date: 31st October 2026

This rConfig Web Terminal Preview Addendum ("Addendum") is made between:

OS Informatics Limited, trading as rConfig, a company incorporated in Ireland under company number 751053, with its registered office at 44 Longshore Drive, Jacobs Island, Cork, Ireland ("rConfig"); and

the customer identified in the applicable software licence agreement, order form, subscription agreement, invoice or other contract ("Customer").

This Addendum governs the Customer's access to and use of the rConfig Web Terminal. It supplements and forms part of the software licence agreement, order form, subscription agreement or other contract under which the Customer is authorised to use the applicable rConfig product (the "rConfig Licence Agreement").

If there is a conflict between this Addendum and the rConfig Licence Agreement, this Addendum governs only in relation to the Web Terminal. The rConfig Licence Agreement governs in all other respects. Any Data Processing Agreement governs to the extent of a conflict concerning the processing of personal data.

Core architecture commitment. Web Terminal sessions, Device Credentials, keystrokes and device output pass only between the User's browser, the Customer's local rConfig installation and the Managed Device. They never pass through an rConfig-operated service.

Acceptance

The Web Terminal is disabled by default. It may be enabled only after this Addendum has been expressly accepted by an Authorised Administrator through the activation workflow, and after the Web Terminal has been switched on in the local rConfig configuration.

The person accepting this Addendum represents that they have authority to bind the Customer. An ordinary page view, passive access, continued use of rConfig, or failure to disable the feature does not constitute acceptance.

1. Definitions

"Applicable Law" means all laws and binding regulatory requirements applicable to a party, the Customer Environment or the relevant use of the Web Terminal, including data protection, cybersecurity, telecommunications, export control and sanctions laws.

"Authorised Administrator" means a person authorised by the Customer to accept contractual terms on its behalf and to enable, configure or administer the Web Terminal.

"Customer Environment" means the Customer-controlled systems, networks, hosts, web servers, reverse proxies, load balancers and local rConfig installation in which the Web Terminal operates.

"Device Credentials" means usernames, passwords, keys, enable secrets and other authentication material stored in the Customer's rConfig installation and used to authenticate to Managed Devices.

"Generally Available" means a version of the Web Terminal that rConfig has expressly designated in its release notes as generally available and no longer Preview.

"Managed Device" means a network device, server or other system that is configured in the Customer's rConfig installation and reachable by it.

"Preview" means pre-release functionality supplied for evaluation, whether described as preview, beta, early access, experimental or similar.

"Session" means an interactive terminal session opened through the Web Terminal between a User's browser and a Managed Device, including all keystrokes, pasted content, commands and device output within it.

"Session Records" means records of Session start, end, duration, User, Managed Device and end reason generated by the Web Terminal within the Customer Environment.

"Usage Metadata" means technical and administrative information about licensing, feature activation, software version, acceptance events and security events. It expressly excludes Device Credentials, keystrokes, commands, device output and Session content.

"User" means an individual authorised by the Customer and granted the Web Terminal permission in the Customer's rConfig installation.

"Web Terminal" means the rConfig functionality, including the terminal gateway, per-Session processes, browser terminal interface and related configuration, that allows a User to open an interactive Session with a Managed Device from within rConfig using stored Device Credentials.

2. Preview Status

2.1 Pre-release functionality

The Web Terminal is Preview functionality. It is supplied for evaluation and feedback only and is not a Generally Available feature of any rConfig product edition.

2.2 Security testing not complete

The Customer acknowledges that the Web Terminal:

• has not completed rConfig's full security testing programme, including independent penetration testing;
• may contain undiscovered vulnerabilities affecting the Web Terminal, the rConfig installation, Device Credentials or Managed Devices;
• has not been certified or assessed against any security standard, framework or regulatory scheme; and
• may behave unexpectedly with some devices, operating systems, terminal types, character sets, proxies or network paths.

2.3 No commitment to release

rConfig makes no commitment that the Web Terminal will become Generally Available, in its current form or at all. rConfig may at any time, with or without notice, change, restrict, replace, suspend or permanently withdraw the Web Terminal.

Withdrawal of the Web Terminal does not entitle the Customer to any refund, credit, fee reduction or other remedy. No purchase decision should rely on the Web Terminal being made Generally Available.

2.4 Changes between versions

Preview versions may change behaviour, configuration, permissions, data formats and interfaces without backwards compatibility, migration path or notice. Settings or Session Records from a Preview version may not carry forward to a later version.

2.5 Feedback

The Customer may provide feedback on the Web Terminal. The Customer must not include Device Credentials, device output containing secrets or personal data in feedback. rConfig may use feedback without restriction or obligation, provided it does not identify the Customer publicly without consent.

2.6 Recommended use

rConfig recommends that the Web Terminal is evaluated first in a non-production or lab environment, with a limited set of Users and Managed Devices, before any use against production infrastructure.

3. Licence Dependency, Enablement and Access

3.1 Licence dependency

Use of the Web Terminal is permitted only while the Customer holds a valid licence for an eligible rConfig product edition and complies with the rConfig Licence Agreement. Eligible editions are those stated in rConfig's documentation or release notes for the relevant Preview version. Suspension, expiry or termination of the underlying licence automatically suspends or terminates the right to use the Web Terminal.

3.2 Disabled by default

The Web Terminal is supplied switched off. It is enabled only by an explicit change to the local rConfig configuration, made by a person with administrative access to the rConfig host. The Customer is responsible for controlling who can make that change, and for switching the Web Terminal off when it is no longer needed.

3.3 Access control

The Customer must:

• grant the Web Terminal permission only to named, trained Users who need interactive device access for their role;
• review that permission regularly and remove it promptly when no longer required;
• protect rConfig accounts with strong authentication, and multi-factor authentication where available; and
• ensure that every User is also authorised under the Customer's own policies to access each Managed Device they connect to.

The Customer is responsible for all activity carried out through its rConfig accounts and the Web Terminal, whether or not authorised by the Customer.

3.4 Effective access of Users

The Customer acknowledges that a Session authenticates using the Device Credentials stored in rConfig, not the User's personal credentials. A User with the Web Terminal permission can therefore act on a Managed Device with the full privilege of those Device Credentials, which may exceed the User's own access rights on that device. The Customer is solely responsible for assessing and accepting this effect before granting the permission.

4. Architecture, Credentials and Records

4.1 Local data path

The Web Terminal is designed so that a Session runs only between the User's browser, the Customer's rConfig installation and the Managed Device. The browser connects to the rConfig installation over an encrypted connection using the Customer's existing web server and certificate. The rConfig installation then connects to the Managed Device.

4.2 No rConfig intermediary

Sessions, keystrokes, commands, device output and Device Credentials are never received, routed, proxied, relayed, stored, logged or inspected by any infrastructure or service operated by or on behalf of rConfig. The Web Terminal does not send Session content to rConfig for support, telemetry, licensing, diagnostics or product improvement.

4.3 Device Credentials

Device Credentials are retrieved only inside the Customer's rConfig installation at the start of a Session. They are not sent to the User's browser. The Customer acknowledges that:

• Device Credentials remain subject to the security of the rConfig host, its database, backups and administrators;
• anyone able to open a Session can use the access those Device Credentials grant, even without seeing them; and
• the Customer is responsible for scoping Device Credentials to the minimum privilege its use of rConfig requires.

4.4 Session Records

The Web Terminal records Session start and end events within the Customer Environment. In this Preview version, keystrokes, commands and device output are not recorded. Session Records are stored only in the Customer Environment, and the Customer controls their access, retention, export and deletion.

The Customer must not rely on Session Records as a complete audit trail of actions taken on a Managed Device. Where a full audit trail is required, the Customer must use device-side logging, AAA accounting (such as TACACS+ or RADIUS) or other controls of its own.

4.5 Architecture commitment

rConfig will not change the Web Terminal under this Addendum so that Session content or Device Credentials pass through an rConfig-operated service. Any future offering involving such a data path must be separately identified, optional, governed by a separate written agreement and enabled by an explicit action of an Authorised Administrator. It will not be enabled by default, by a software update or by a general update to this Addendum.

4.6 Usage Metadata

rConfig may process Usage Metadata for licensing, entitlement, feature activation, security and acceptance records, in line with the applicable rConfig privacy notice and any Data Processing Agreement. Usage Metadata never includes Device Credentials or Session content.

5. Customer Security and Operational Obligations

5.1 Host and network security

The Customer is solely responsible for the security of the Customer Environment, including:

• patching, hardening and monitoring the rConfig host, its operating system, web server and database;
• keeping the terminal gateway bound to the local host only, and not exposing it directly to any network;
• configuring TLS, certificates, reverse proxies, load balancers and firewalls in front of rConfig, including any WebSocket support they require;
• restricting network access to the rConfig web interface to trusted networks; and
• verifying Managed Device host keys and protecting against interception of the connection between rConfig and Managed Devices.

5.2 Changes to Managed Devices

The Web Terminal gives Users direct, interactive command-line access to Managed Devices. Commands entered or pasted in a Session take effect immediately, with no review, approval, validation or rollback by rConfig. The Customer acknowledges that a single command can cause loss of connectivity, service outage, configuration loss or security exposure.

The Customer must ensure that Sessions used to change production devices follow its normal change management, approval, maintenance window, backup and rollback procedures. The Web Terminal is not a change approval authority, and a paste confirmation or other safeguard in the interface does not replace those procedures.

5.3 Session availability

Sessions may end without warning, including on idle timeout, maximum duration, gateway restart, rConfig upgrade, network interruption or Preview defect. The Customer must not rely on a Session staying open to complete a change, and must not start a change it cannot safely recover from if the Session drops.

5.4 Incident response

If the Customer suspects compromise or misuse of the Web Terminal, an rConfig account or Device Credentials, it must promptly disable the Web Terminal, revoke affected access, rotate the affected Device Credentials and review device-side logs. The Customer should report suspected vulnerabilities in the Web Terminal to rConfig under its published security policy.

6. Restricted Use

6.1 Prohibited use

The Customer must not use the Web Terminal:

• to access any device or system without lawful authority, or beyond the scope of that authority;
• as a safety component, or the sole means of control, for systems whose failure could reasonably cause death, personal injury, environmental harm or serious property damage;
• to circumvent licensing, entitlement, authentication, authorisation or security controls in rConfig or on a Managed Device;
• to expose the terminal gateway, or Sessions, to persons who are not Users;
• to probe, scan, attack or disrupt third-party systems; or
• in breach of Applicable Law or the rConfig Licence Agreement.

6.2 Automation and AI

The Web Terminal is for interactive use by a human User. The Customer must not script, automate or drive Sessions through browser automation, AI agents or other tools, and must not paste AI Output into a Session against a production device without the review required by the rConfig AI Center Terms of Use Addendum, where that Addendum applies.

6.3 Managed service providers and third-party devices

Where the Customer uses the Web Terminal to access devices owned by, or operated for, a third party (including an End Client under an rConfig MSP or Vector licence), the Customer must:

• hold written authority from that third party for interactive access to its devices;
• inform that third party that access is made through a Preview feature; and
• remain fully responsible for all Sessions against those devices.

Use of the Web Terminal does not create any relationship between rConfig and that third party.

6.4 Devices reached through agents

Unless rConfig documentation for the relevant Preview version states otherwise, the Web Terminal supports only Managed Devices reachable directly from the rConfig installation. It does not support Sessions routed through an rConfig Vector Agent.

7. Warranties and Disclaimers

Any warranty in the rConfig Licence Agreement does not apply to the Web Terminal while it is Preview. To the maximum extent permitted by law, the Web Terminal is provided "as is" and "as available", with all faults, and without warranty of any kind, whether express, implied or statutory, including any warranty of merchantability, fitness for a particular purpose, security, non-infringement or uninterrupted or error-free operation.

Without limiting the above, rConfig does not warrant that the Web Terminal is free from vulnerabilities, that it will protect Device Credentials or Managed Devices from unauthorised access, that it will work with any particular device, proxy or browser, or that Sessions will be complete, accurate or uninterrupted.

Nothing in this Addendum excludes a warranty or remedy that cannot lawfully be excluded.

8. Support

The Web Terminal is excluded from any support entitlement, service level and response target under the rConfig Licence Agreement while it is Preview. rConfig may, at its discretion, respond to reports and feedback, but has no obligation to fix defects, provide workarounds or release updates. Support for the rest of the rConfig product is not affected.

9. Operational Responsibility

The Customer remains solely responsible for all commands entered or pasted in a Session, all changes made to Managed Devices through the Web Terminal, and the consequences of those changes, including outages, configuration loss, security incidents and impacts on third parties.

10. Limitation of Liability

All exclusions and limitations of liability in the rConfig Licence Agreement apply to this Addendum and the Web Terminal. Liability relating to the Web Terminal forms part of, and does not add to, the aggregate liability cap in the rConfig Licence Agreement.

To the maximum extent permitted by law, rConfig will not be liable for any loss or damage arising from:

• the Preview status of the Web Terminal, including any undiscovered vulnerability or defect;
• commands entered, pasted or executed in a Session, or changes made to a Managed Device;
• the scope or privilege of Device Credentials configured by the Customer;
• access granted to Users, or misuse of rConfig accounts within the Customer's control;
• the Customer Environment, including hosts, web servers, proxies, load balancers and network paths;
• Sessions ending, failing or being interrupted; or
• the change, suspension or withdrawal of the Web Terminal.

Nothing in this Addendum limits liability that cannot lawfully be limited.

11. Customer Indemnity

Subject to the indemnity procedures in the rConfig Licence Agreement, the Customer will defend and indemnify rConfig against third-party claims, damages, liabilities and reasonable costs to the extent caused by:

• the Customer's use of the Web Terminal against devices it was not authorised to access;
• Sessions against third-party or End Client devices;
• misuse of rConfig accounts, Device Credentials or the Web Terminal within the Customer's control; or
• the Customer's breach of this Addendum.

This indemnity does not apply to the extent a claim is caused by rConfig's breach of contract, negligence, wilful misconduct or breach of Applicable Law.

12. Suspension and Withdrawal

rConfig may suspend the Customer's use of the Web Terminal, or require the Customer to disable it, where rConfig reasonably believes that continued use presents a material security risk, breaches this Addendum or Applicable Law, or threatens the integrity of the rConfig software. Where practicable, rConfig will give notice and the reason. rConfig may withdraw the Web Terminal entirely under section 2.3.

Where rConfig notifies the Customer of a security issue affecting the Web Terminal, the Customer must disable it or apply the update rConfig specifies within the period rConfig reasonably sets.

13. Updates to this Addendum

rConfig may update this Addendum to reflect changes to the Web Terminal, its Preview status, security requirements, law or commercial terms. Material changes that adversely affect the Customer will require express reacceptance by an Authorised Administrator before the Web Terminal can be used under the new version, unless required immediately by law or to address a security risk. The architecture commitment in section 4.5 cannot be changed by general update.

If the Web Terminal becomes Generally Available, rConfig may replace this Addendum with terms for the Generally Available version, which may require new acceptance.

14. Termination and Survival

This Addendum terminates when the Web Terminal is withdrawn, when the Customer's right to use it or the underlying licence ends, or when the Customer disables the Web Terminal and notifies rConfig that it no longer accepts this Addendum. On termination, the Customer must disable the Web Terminal in its rConfig configuration.

Termination does not delete Session Records held in the Customer Environment. Sections concerning architecture, warranties, liability, indemnity, acceptance records and governing law, and any provision intended by its nature to survive, survive termination.

15. General and Governing Law

This Addendum does not amend pricing, payment, confidentiality, governing law, jurisdiction, dispute resolution, assignment, notices or other general provisions of the rConfig Licence Agreement, except where it expressly says so. If a provision is unenforceable, it will be modified to the minimum extent needed, and the rest continues in effect. This Addendum is governed by the law and dispute resolution provisions of the rConfig Licence Agreement.

Acceptance Confirmation

By completing the acceptance process as an Authorised Administrator and enabling the Web Terminal, the Customer confirms that it has read, understood and agrees to be bound by this Addendum, and that it accepts the risks of using Preview functionality that has not completed full security testing and may never be released.