Privacy Policy

Last updated: August 21, 2026

        TL;DR: Voltrus SCADA is a self-contained binary that runs on your server. All industrial data (tags, alarms, historical data, dashboards) stays on your machine. No telemetry, no analytics, no phone-home. We never see your SCADA data.
      

What Voltrus SCADA Does

Voltrus SCADA is a single-binary industrial monitoring application. It connects to Modbus TCP, MQTT, OPC-UA, Siemens S7, Allen-Bradley EtherNet/IP, DNP3, and BACnet/IP devices on your network. It stores data in an embedded SQLite database, serves a web dashboard, and provides REST APIs. It runs entirely on your infrastructure: on-premises, in your data center, or on a VPS you control.

Data Collection

Voltrus SCADA does not collect, transmit, or store any personal data on our servers. Specifically:

No industrial data leaves your network. All tag values, alarms, historical data, dashboard configurations, and event logs exist only in the embedded database on your server.
No connection details are collected. Device IP addresses, register addresses, credentials, and configurations are stored in your server's filesystem and never sent anywhere.
No usage analytics. The binary does not include any analytics SDK, tracking pixels, or telemetry. We do not know how you use the software.
No crash reporting. The binary does not send crash reports automatically. If you report a bug, you choose what information to share.

Network Communication

The binary makes network connections only to the industrial devices you explicitly configure:

Industrial protocols: Modbus TCP (port 502), MQTT (port 1883/8883), OPC-UA (port 4840), and other protocol-specific ports, all to IPs you configure
License activation: Contacts activate.voltrus.id to validate your license key. Sends only your license key and a device identifier, no other data.
Update checks (optional): If you enable auto-update checks, the binary contacts activate.voltrus.id for version info. No data is sent. This is a one-way version query.

After initial license validation, the binary works fully offline.

Local Data

The binary stores the following data on your server:

Configuration (YAML): device IPs, register mappings, alarm thresholds, dashboard layouts
Embedded SQLite database: historical tag data, alarms, events, OEE calculations
License activation data: stored locally, validated against our server on startup

All data can be deleted by removing the binary and its config directory. No residual data is left after deletion.

License Purchase

Licenses are processed through Polar.sh. We receive only your email address and purchase details. We do not receive or store payment card information. License keys are managed by Polar.sh.

Third-Party Services

Polar.sh: Payment processing and license key management.
Cloudflare: Hosts the license activation and update server. No industrial data is stored on Cloudflare beyond temporary request logs.

Data Retention

We retain your email address (from Polar.sh purchases) for as long as necessary to provide license support. We do not maintain any database of users, devices, or usage patterns. You can request deletion of your purchase data by emailing us.

Your Rights

Depending on your jurisdiction, you may have the right to:

Request access to the personal data we hold about you
Request deletion of your personal data
Object to processing of your personal data
Request a copy of your data in a portable format

Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated revision date. Continued use of the software after changes constitutes acceptance.

Contact

For privacy-related questions or data requests, contact [email protected].