1. Parties and scope
This Software License Agreement is between PatientLock, LLC and the person or organization authorized to install or use PatientLock software. It applies to Rusty agents, PatientLock-provided client software, and related documentation made available under an evaluation or commercial engagement.
2. License
Subject to the applicable commercial documents and payment of required fees, PatientLock grants a limited, non-exclusive, non-transferable license to install and use the software on systems the customer owns, controls, or is authorized to administer, solely for the authorized service purpose.
3. Customer authority and actions
The customer is responsible for defining who may deploy software, what systems are in scope, and what actions are authorized. Rusty does not create its own authority. Customer-approved actions may be performed only within the capabilities, policies, and permissions enabled for the applicable environment.
4. Restrictions
You may not sell, sublicense, distribute, tamper with, defeat access controls for, or reverse engineer the software except to the limited extent applicable law expressly prohibits such a restriction. You may not use the software to access systems without authorization or to provide a competing service except as expressly permitted in writing.
5. Telemetry and service data
The software may generate device identity, software inventory, security-control state, configuration, action, diagnostic, and evidence records needed to operate VitalSec. Data handling is governed by the applicable MSA, Privacy Policy, DPA, BAA, and customer configuration.
6. Ownership
PatientLock and its licensors retain ownership of the software and PatientLock-owned intellectual property. Customer ownership of Customer Data and customer-specific deliverables is governed by the applicable MSA, Service Order, or SOW.
7. Updates and support
PatientLock may provide updates, patches, or replacement versions. Support commitments, maintenance obligations, and version requirements are those stated in the applicable Service Order, SOW, or service terms; this public license does not create a separate support SLA.
8. Security outcomes
Cybersecurity software can reduce and manage risk but cannot guarantee that every threat, vulnerability, outage, or security event will be prevented. RCI and related modeled outputs are not insurance, actuarial, or regulatory determinations unless an executed agreement expressly states a defined use.
9. Term and termination
The license continues for the authorized evaluation or commercial term. On expiration or termination, use must cease and software must be removed where required by the applicable commercial documents.
10. Commercial precedence
For paid services, the Master Services Agreement and applicable Service Order or SOW control commercial terms, liability, indemnity, fees, and service-specific obligations. If this license conflicts with an executed customer-specific document, the order of precedence stated in those executed documents controls.
11. Governing law and contact
This Agreement is governed by Kansas law unless an executed commercial document states otherwise. Questions may be sent to legal@patientlock.net.