Policy Document

Privacy Policy

Last Updated: 2026-02-27

1. Information Collection

Twinise collects the data necessary to operate and maintain the platform. This includes:

  • Hardware Telemetry: Sensor readings, device attributes, and connection events.
  • 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:

  • Delivering telemetry from your devices to your dashboards and Unreal clients, live and as stored history.
  • Evaluating the threshold alarms you configure, and raising the alerts that follow from them.
  • Operating, supporting, and billing the service, including account administration.

3. Data Protection

Telemetry is stored in a managed Postgres database on managed cloud infrastructure. Platform APIs and client streams run over TLS; device MQTT over TLS is available on port 8883 while the fleet migrates, and plaintext port 1883 is still open. Access to telemetry is bound to your organization — every resource carries an organization identifier and every query is filtered by it. Full detail sits in the Security Overview.

4. Third-Party Sharing

We do not sell telemetry data. It is shared only with the sub-processors that deliver the service: DigitalOcean (managed cloud hosting and managed Postgres), Cloudflare (network edge in front of the API), Vercel (website hosting and analytics), Stripe (payments), and Brevo (transactional email). If you connect your own AI assistant to Twinise, what it may read is limited to what you approve on the consent page, and that assistant's provider is your processor, not ours. The list is maintained in the Data Processing Addendum.

Twinise runs as a managed cloud platform today. Data-residency and dedicated-instance requirements are scoped per engagement — talk to us.