Several features of the platform show who did what: work-level outcomes count completed items per person, the Microsoft 365 connection keeps per-person Copilot activity, provider usage can be attributed to the person or key that made the requests, timed runs name the person who timed them, and the recorder notes the pages and controls a person used while they chose to record a workflow. Before any of these is switched on, the Terms, section 5, require the customer to give its staff the notice the law where they work requires, and to consult or inform a works council where one must be. This page gives a notice to adapt and the facts a works council, a data protection officer or a data protection impact assessment asks for. It is a template, not legal advice; local counsel decides what the law where the staff work requires.
Notice: measurement of AI implementations at [Company]
[Company] uses Track AI ROI, a service operated by Track AI ROI in the United States, to measure whether the AI tools and automations it introduces pay off. The service measures implementations, not people, and [Company] will not use any figure from it as the basis for a decision about an individual's hiring, pay, discipline or dismissal.
What the service records about you, if you are involved in a measured workflow:
Who sees it: [Company]'s administrators, [the consulting firm engaged, if any] while its engagement is open, and the operator of the service to run and support it. Per-person Microsoft 365 activity is visible to administrators and the engaged firm only. Wages, where entered, are visible to [Company]'s administrators only.
How long: for the life of [Company]'s workspace, after which identifiers are removed; short-lived records (recordings, import drafts, assistant exchanges) are deleted on fixed windows stated in the service's Privacy Policy.
Your rights: you may ask [contact at Company] to see, correct or delete what is held about you, and you may opt out of timing, sampling and check-in emails in each email or in the service's settings. [Where applicable: you may also complain to the data protection authority.] Questions about the service itself: elijah@trackairoi.com.
[Date] [Signature of the person responsible]
| Item | Fact |
|---|---|
| Purpose | Measuring the adoption, outcomes and cost of AI implementations and computing a verdict per implementation. Per-person data serves attribution and adoption counts only; the verdict is about the implementation. |
| Controller and processor | The customer is the controller; the operator is its processor under the Data Processing Addendum. A consulting firm engaged by the customer acts within that engagement. |
| Legal basis (customer's choice) | Typically the customer's legitimate interest in measuring its own operations, balanced by the limits below; consent where the law requires it (and always for the recorder, which only the person starts). In Germany and similar jurisdictions, a works-council agreement under the applicable co-determination rules. |
| Data subjects | Staff involved in measured workflows; administrators and users of the workspace. |
| Data categories | Identity and role; per-person work items, labor tickets from a connected ERP (job, work center, date, hours), AI usage and Copilot activity where connected; timings and answers a person gives; the recorder's page, control and field labels; wages where an administrator enters them. |
| Never processed | Prompt or response content; typed values; screenshots; special categories of personal data; government identifiers, card or bank numbers. |
| Recipients | The customer's authorised users by role; an engaged firm while the engagement is open; the sub-processors listed at /subprocessors; nobody else unless the customer publishes. |
| Location | United States (Oregon); transfers under the standard contractual clauses (DPA, section 11). |
| Retention | The life of the workspace; erasure on account or workspace deletion; fixed windows for short-lived data (webhook events 7 days, delivery bodies 30 days, timer records 365 days, recordings and assistant exchanges as the Privacy Policy, section 10, states). |
| Automated decisions | None. No figure produces a legal or similarly significant effect on an individual by itself; the Terms forbid employment decisions on per-person figures. |
| Limits on use | Administrators see per-person figures to run the measurement; plain viewers see counts. The customer may keep the Microsoft 365 connection off, attribute usage to keys rather than people, and leave the recorder uninstalled. |
| Security | The measures on the Security page: encryption in transit and at rest, database-enforced isolation, append-only records, daily integrity check, named operators. |
| Rights handling | Access, correction, erasure, restriction, portability and objection through the customer, with the operator's help (DPA, section 7); the person's own account can be deleted by the person. |
See also Terms of Service, Privacy Policy, Data Processing Addendum, Acceptable Use Policy, Sub-processors, Security, how verification works and how adoption is measured. All documents: /legal.