About & Legal

EdgeConnect Privacy and Data Use Notice

Last updated: June 2026

EdgeConnect is an appliance and server application for connecting to MTConnect Agents and displaying machine monitoring data. This notice is a practical summary for operators, customer IT, and support teams. It is not a substitute for any applicable written agreement with True Analytics Manufacturing Solutions.

Data EdgeConnect reads

EdgeConnect reads MTConnect device, component, data item, current, sample, event, condition, asset, and stream information from the Agents configured by the operator. The exact data depends on the connected equipment and the MTConnect Agent implementation.

Data EdgeConnect stores locally

Depending on configuration and enabled features, EdgeConnect may store:

• application configuration and visualization settings;
• Agent connection settings;
• dashboard, section, and data binding configuration;
• application logs;
• in-memory or file-backed observation cache data used by live visualizations, Program Replay, and Program Map history;
• Program Replay screenshots or replay packages;
• configuration archives;
• guided workflow packages;
• provisioning package staging data, validation reports, and provisioning state.

Logs, support bundles, replay exports, .ecrp packages, .mep packages, and screenshots can contain operational machine data, timestamps, program names, device identifiers, and configuration details. Review exported files before sharing them outside your organization.

Cloud and TAMS services

Most appliance deployments can operate locally after configuration. EdgeConnect may communicate with configured TAMS or cloud endpoints when those features are configured and available, including Account Portal, subscription/licensing, Smart Dashboard ChatGPT relay, deployment manager, or other support services.

EdgeConnect does not require customer-managed DNS, public certificates, or cloud services for the default kiosk-only local mode. Customer IT is responsible for customer-managed DNS records, certificates, trust chains, renewal procedures, and access policies when those options are used.

Offline and local deployments

In mostly-offline deployments, data remains local to the appliance or server unless an operator exports files, configures a cloud endpoint, installs a provisioning package that points to external services, or otherwise shares logs/support artifacts.

Support contact

For support or privacy questions, contact TAMS support at support@tams.ai or the contact listed in your applicable TAMS agreement.