Operational Disclosures

These disclosures explain the intended role, operating boundaries, and current limitations of TRGS Application.

Effective date: 21 July 2026
Last updated: 21 July 2026

1. Operational Support Tool
TRGS is an equipment-record, tracking, and governance support application designed for dive centres, liveaboards, training facilities, technicians, managers, and related operational personnel.

TRGS supports the recording and review of tank and regulator information. It does not replace competent inspection, servicing, maintenance, supervision, technical judgement, or legal compliance.

2. No Inspection, Certification, or Approval Function
Use of TRGS does not itself inspect, test, certify, approve, service, quarantine, or determine whether any tank, regulator, valve, component, or other item is safe or legally compliant.

Equipment condition and serviceability must be determined by appropriately competent and authorised personnel using applicable inspection procedures, manufacturer guidance, technical standards, and local requirements.

3. User-Entered Information
Information displayed by TRGS depends on records entered, changed, synchronised, imported, exported, or maintained by authorised users.

TRGS does not independently verify that tank numbers, serial numbers, barcodes, inspection dates, hydrostatic test dates, regulator-service dates, equipment locations, condition fields, status selections, or notes are accurate, complete, current, or legally sufficient.

Users must verify important records before relying on them for an operational, inspection, maintenance, or safety-related decision.

4. Inspection and Service Warning Limitations
TRGS provides visual warning logic based on dates and intervals entered by users.

The main dashboard is designed to highlight equipment that is overdue or approaching an entered inspection or service date within the application’s current warning period. It should not be relied upon as a complete long-range maintenance forecast.

Operators should review full equipment records and reports when planning inspections, hydrostatic testing, servicing, replacements, or other work beyond the immediate warning period.

5. Inspection History Limitations
TRGS records current inspection and service information and may retain previous inspection-related values in its available audit or history functions.

The application should not be treated as a complete permanent technical history unless the operator has confirmed that all required historical records are present and has maintained suitable external records or exports where necessary.

6. Offline-First Operation
TRGS is designed to continue operating when internet access is unavailable. Records may be created or updated locally on an authorised device.

Information created or changed while offline is not visible on another device until the relevant records have been successfully synchronised.

Users remain responsible for checking synchronisation status and confirming that important changes have reached the cloud-linked account.

7. Cloud Synchronisation and Recovery
Successfully synchronised records may be stored through TRGS cloud-linked services and may be recoverable on another authorised device.

Records that exist only on a device may be lost if that device is lost, damaged, reset, cleared, removed, or becomes unusable before successful synchronisation.

TRGS does not guarantee recovery of records that were never successfully synchronised.

8. Equipment Location Records
TRGS location and movement functions depend on authorised users manually recording or updating equipment movements.

TRGS does not provide physical GPS tracking of tanks or regulators. A displayed location represents the most recent location information entered and successfully synchronised by users.

Equipment may therefore be physically located somewhere other than the location shown if a movement was not recorded, was recorded incorrectly, or has not yet synchronised.

9. Barcode and Identifier Use
Barcodes, QR codes, tank numbers, regulator numbers, serial numbers, or other identifiers are used to retrieve records entered into TRGS.

Scanning an identifier does not itself confirm the physical identity, ownership, condition, contents, serviceability, or inspection status of the equipment. Staff must confirm that the identifier and displayed record correspond to the correct item.

10. Shared Operational Access
An operation may permit authorised staff to access the same operational TRGS account.

The account holder or operating entity remains responsible for controlling credentials, restricting access to authorised personnel, removing access when appropriate, and monitoring changes made through the account.

11. Reports and Exports
Reports and exported files reflect information available to TRGS at the time they are generated.

Reports may be incomplete or outdated if records have not been entered, updated, or successfully synchronised. Users must review exported information before relying on or distributing it.

Once an export is shared through email, messaging, cloud storage, or another external service, its handling is outside the control of TRGS.

12. No Sole Reliance
TRGS must not be relied upon as the sole basis for safety-critical, inspection, servicing, maintenance, legal, supervisory, equipment-release, or business-continuity decisions.

TRGS should operate as one information and governance layer within a wider system of competent staff, physical inspections, maintenance procedures, technical documentation, supervision, and management control.

13. Operator Responsibility Remains Primary
The owner, operator, manager, technician, inspector, or other responsible person remains accountable for:

14. External Standards and Local Requirements
TRGS does not replace manufacturer instructions, recognised inspection practices, training-agency standards, engineering requirements, statutory duties, workplace-safety rules, insurance conditions, or local legal requirements.

Users remain responsible for determining which requirements apply to their equipment, location, organisation, and activities.

15. Application Availability
TRGS may occasionally be unavailable or operate with reduced functionality because of device problems, internet failure, software defects, maintenance, cloud-service interruption, subscription status, application updates, security controls, or other technical conditions.

No guarantee is made that the application, account, cloud services, synchronisation, reports, or other functions will always operate without interruption, delay, conflict, or error.

16. Product Development and Changes
TRGS is publicly available through Google Play and may continue to receive updates, corrections, security improvements, workflow changes, feature additions, or feature removals.

Screens, functions, data structures, subscription arrangements, supported devices, synchronisation behaviour, and technical requirements may change between versions.

17. Contact
For enquiries regarding these disclosures, contact: assetgovernance@outlook.com