Opsnap focuses on decision readiness — not equipment control.

Enterprise Data Handling

Opsnap enhances operational readiness without directly interfacing with or controlling equipment.

1. Overview

Opsnap is designed for enterprise use in operational environments.

2. Data isolation

Each company's data is isolated
There is no cross-company visibility of customer data

3. Site-level data segmentation

Data is scoped to site where the product model supports it
Access is controlled by roles and membership

4. Role-based access control

Typical roles in the product include:

Operator — access to assigned scenarios and personal run history
Manager — access to site-level performance and assignments as configured
Admin — broader visibility for administration where enabled

5. Data processing model

Opsnap acts as a processor on behalf of the customer
The customer retains ownership of their data

Personal data practices are described in our Privacy Policy.

6. No equipment control

Opsnap does not connect to or control industrial systems by default. Training and readiness views are separate from live control systems.

7. Secure architecture

HTTPS for traffic in transit
Controlled API access for application features
Database isolation appropriate to the deployment model

8. Analytics and aggregation

Insights may be generated from usage and performance data
Aggregated or anonymized metrics may be used to improve the product where applicable

9. Customer control

Customers can:

Export data where the product provides export paths
Request deletion subject to agreement and law
Manage access through roles and site membership

10. Future integrations (optional)

Roadmap capabilities may include APIs for sensors, controllers, or other systems. Any such integration would only be enabled with explicit customer consent and appropriate contractual safeguards.