Policy Document
Privacy Policy
Last Updated: 2026-02-27
1. Information Collection
Twinise collects telemetry data strictly necessary for the operation, maintenance, and enhancement of the digital twin control loop. This includes:
- Hardware Telemetry: Sensor readings, gateway status, and network diagnostics.
- System Interactions: API calls, user interface activity within the Twinise Cloud, and Unreal Engine Connector utilization.
- Account Data: Contact information, billing details, and facility metadata required for deployment provisioning.
2. Usage Protocols
Collected data is utilized for:
- Maintaining bi-directional control integrity between physical sensors and virtual representations.
- Generating predictive insights and automated anomaly detection alerts.
- Aggregating anonymized performance metrics to improve the core Twinise analytics engine.
3. Data Protection
Twinise employs AES-256 encryption for data at rest and TLS 1.3 for data in transit. Access to tenant-specific telemetry is strictly gated utilizing Role-Based Access Control (RBAC).
4. Third-Party Sharing
We do not sell telemetry data. Data is only shared with verified sub-processors (e.g., AWS, Azure) essential to the delivery of the Twinise platform.
For enterprise-specific data residency requirements, refer to your dedicated Service Level Agreement.