Responsibility Statement
Effective date: April 18, 2026
This Responsibility Statement describes the allocation of operational responsibility between MyRuns and each customer using the platform.
1. Customer Responsibility
The customer is responsible for the correct use of the platform, the assignment of permissions, the supervision of internal users, and the validation of any action taken based on system information. This includes stock operations, incident handling, hardware deployment, and the interpretation of reports or alerts.
2. Credential and Device Protection
Users must protect their login credentials, approved devices, and access methods. Any suspected compromise, misuse, or unauthorized access must be reported promptly to the responsible administrator so the relevant access can be revoked or updated.
3. Data and Configuration Accuracy
The customer is responsible for keeping installations, readers, devices, users, and imported datasets correctly configured. Incorrect mappings, outdated metadata, or incomplete operational processes may affect the quality of the resulting information.
4. Physical and Operational Controls
MyRuns supports monitoring and traceability, but the customer remains responsible for physical inventory controls, device placement, stock movements, local procedures, and compliance with site-specific safety or security obligations.
5. Incident Handling
The customer must review alerts, anomalies, and incidents using appropriate internal criteria. Platform notifications are support tools and do not replace escalation procedures, approval workflows, or legal reporting obligations established by the customer.
6. Platform Responsibility
MyRuns is responsible for providing the contracted software service with reasonable professional care, maintaining the platform, and implementing corrective or preventive measures when service issues are identified within the product scope.
7. Liability Boundary
Unless otherwise agreed in writing, MyRuns is not responsible for losses derived from incorrect customer configuration, unauthorized account sharing, omitted operational controls, third-party infrastructure failures, or business decisions taken without human validation.
8. Acceptance
Continued use of the platform implies acknowledgement of this responsibility model and acceptance that the service must be operated under the customer’s own governance, validation, and control procedures.