MetalOps

LEGAL / SECURITY

Security for the work behind every estimate.

MetalOps is built around business information that fabrication teams do not want exposed. This page explains the security practices we use to protect the platform and customer information.

Last updated: September 2026

Our approach

Security is considered across the application, infrastructure, access controls and operational processes used to provide MetalOps.

We work to minimise unnecessary access to customer information and to protect information while it moves between systems.

Access control

  • Access to workspace information is controlled through user accounts and workspace permissions.
  • Team roles can be used to separate responsibilities within a workspace.
  • Administrative access is restricted to authorised personnel.
  • We work to review and remove access that is no longer required.

Customer data

Customer drawings, estimates, parts and rate information are treated as business information and are protected through the controls available within the MetalOps platform and its supporting infrastructure.

Application security

  • Authentication and authorisation controls are used to protect account and workspace access.
  • Input handling and application controls are used to reduce common security risks.
  • Changes to the application are reviewed and tested as part of the development process.
  • Dependencies and infrastructure components are monitored as part of ongoing maintenance.

Monitoring and response

We monitor the service and relevant infrastructure for operational and security issues. When an issue is identified, we investigate it and take appropriate steps to contain and resolve it.

Security incidents

If we confirm a security incident that materially affects customer information, we will assess the situation and communicate with affected customers as appropriate.

Report a security issue

If you believe you have found a security issue affecting MetalOps, please contact us at hello@metalops.in with enough information for our team to investigate.

Security practices evolve as MetalOps grows. This page describes our current approach and is not a certification or guarantee of any particular security standard.