About this notice
This Product Telemetry Notice explains the usage telemetry that the Augmentus software (the Augmentus desktop application and the Perception Server, the “Software”) collects, why we collect it, where it is processed, and the controls available to you. It is provided by Augmentus Pte. Ltd., together with its subsidiaries and affiliates (“Augmentus”, “we”, “us”).
This Notice is referenced by our End User License Agreement (the “EULA”), which incorporates it as updated from time to time, and should be read together with our Privacy Policy. It is a versioned document: we may issue new versions as our instrumentation changes, and the version shown above is the current one.
Our core principle
The Software is instrumented so that telemetry contains no personal data and none of your design content. In particular, telemetry payloads do not include personally identifying information, workpiece geometry, scan data, CAD content, or file contents or file paths. This is enforced by an allowlist applied where events are assembled, and is covered by automated tests, so that only the specific, non-personal fields listed below can be sent.
What we collect
The Software emits a defined set of usage events. The current allowlist is:
| Group | Events and allowlisted payload |
|---|---|
| Session | App launched (including the total number of stations and projects at start); session ended (including session duration). |
| Station & project | Station created; station imported; robot model assigned to a new station (robot brand and model); external axis assigned (type); project created. |
| Import | Workpiece mesh imported (file format and success/failure result); custom tool imported (file format and success/failure result). The file format and outcome are recorded — never the file or its contents. |
| Path generation | An AutoGenerate module (AutoPattern, AutoEdge, AutoSurface, AutoScan) added to the treeview (module name); a module generates a path (module name and result: success / completed with errors); a path optimizer added; a path optimizer run (result); path planning completed (result); script generation (robot brand and result). Script-generation events can be analysed by licence tier. |
On every event we also attach a small technical envelope: the app version, the licence tier, and an anonymised installation / organisation identifier (see section 5). [Confirm: a session identifier, operating system / platform, and telemetry schema version may also be attached.]
Scan-workflow events are out of scope in this version. Events relating to deployment endpoints (for example, sending a program to a controller or exporting a script) are [to be confirmed — tracked separately] and are not part of this version unless listed above.
What we do not collect
Telemetry does not include your name, email address or credentials; workpiece geometry, scans or CAD content; toolpath or file contents; or file names or paths. The Software does not record your screen or keystrokes. (Website analytics and session replay are separate, do not run inside the Software, and are described in our Privacy Policy and Cookie Policy.)
How we identify installations
So that we can count installations and derive metrics such as time-to-first-successful-path without identifying you, each event carries an anonymised installation / organisation identifier produced by a one-way (non-reversible) hash. We do not use it to identify you or any individual.
Where telemetry is processed
Product telemetry is processed and stored on PostHog’s European Union (EU) region infrastructure. PostHog acts as our processor for this data.
Legal basis
Because the telemetry described here is non-personal and de-identified, we collect it on the basis of our legitimate interests in operating, securing, supporting and improving the Software. No consent is required for this non-personal telemetry. Any collection that would involve personal data is carried out only with consent, as described in our Privacy Policy.
Your controls
- For standard licences, telemetry is enabled by default; where offered, you can manage it through a setting in the Software.
- For defense customers, telemetry can be switched off by default and controlled per licence entitlement.
- Where telemetry is disabled — including air-gapped installations and installations provisioned with telemetry off — the Software collects and buffers nothing at all, and it remains fully functional.
- If a connected installation is temporarily offline — for example, a laptop that loses its connection — events are held on your device up to a capped limit and sent once connectivity is restored; if that limit is reached, the oldest events are discarded rather than stored indefinitely.
How we use telemetry
We use this telemetry to operate, secure, support and improve the Software — for example, to see where users encounter friction in path generation, to inform our roadmap, and to understand trial engagement and conversion. In de-identified, aggregated or derived form, we also use it to develop, train and improve our models and algorithms, as licensed under the EULA. We do not use it to identify you.
Changes to this notice
This is a versioned notice, and the EULA references it as updated from time to time. Disclosure-only changes — such as adding a telemetry event, changing a processor or hosting region, or making a new use of already-de-identified data within the grant in the EULA — are made by issuing a new version of this Notice with a new effective date. A material change — such as collecting personal data, using your raw content, or sharing data with new categories of third parties — is handled through the EULA’s re-acceptance mechanism, not by a notice update alone.
Relationship to other documents
This Notice covers only in-product telemetry. Our Privacy Policy covers personal data generally, including website analytics; the EULA contains the software licence and the data-rights grant; and our Cookie Policy covers website cookies.
Contact
Questions about this Notice can be sent to legal@augmentus.tech.