Privacy Policy

1. Data Stored by the Application
TRGS is designed to record operational equipment information relating to tanks and regulators. This may include tank numbers, serial numbers, barcodes, gas contents, inspection dates, hydro dates, service dates, equipment status fields, notes, and related operational identifiers entered by the user.

2. Local Device Storage
TRGS is designed around an offline first model. Operational records may be stored locally on the user’s device so the application can function in environments with limited or inconsistent internet connectivity.

3. Personal Data
TRGS is not intended as a consumer social platform and does not require public user profiles. The application is designed primarily for operational equipment governance. To the extent that users choose to enter names, notes, or other identifiers into free text fields, that information is entered at the discretion of the operator using the application.

4. Cloud Sync and Remote Storage
TRGS is being developed with a structured path toward wider sync capability. Where cloud sync, authentication, or remote database services are introduced in future releases, this policy will be updated to reflect what data is transmitted, where it is stored, and what operational controls apply.

5. Advertising
TRGS does not use in app advertising.

6. Analytics and Third Party Services
TRGS is not intended to rely on advertising based analytics. If analytics, crash reporting, authentication, or cloud sync services are introduced in future releases, this policy will be revised to reflect those integrations.

7. Data Sharing
Operational records stored within TRGS are not intended to be sold to third parties. Any future sync, export, or reporting features remain under operator control and are intended for operational governance purposes.

8. Data Retention and Deletion
Because TRGS is designed for operational record control, data retention depends on the operator’s own use, exports, and deletion practices. Users may remove records from the application according to operational need and software permissions.

9. Security
TRGS is being developed with a structured security hardening path appropriate to its release stage. No software system should be treated as risk free, and operators remain responsible for their own device security, access control, and data handling practices.

10. Children
TRGS is not directed to children.

11. Changes to This Policy
This Privacy Policy may be updated as the application develops, particularly if cloud sync, authentication, analytics, subscriptions, or additional data handling functions are introduced.

12. Contact
For general or privacy related enquiries, contact: assetgovernance@outlook.com