This addendum applies whenever the operator processes personal data on a customer's behalf in providing Track AI ROI: the people in a workspace, the records connected systems and imports bring in, the usage attributed to people, the recordings they make, and everything else in customer data that relates to an identified or identifiable person ("customer personal data"). It forms part of the Terms of Service for every customer without separate signature, and where a signed data processing agreement exists between the parties that agreement prevails.
For customer personal data the customer is the controller (or, where the customer is itself a processor for another company, a processor, in which case the operator is its sub-processor and the customer warrants that its own instructions are authorised) and the operator is the processor. For account, billing and security data the operator is an independent controller under the Privacy Policy, and this addendum does not apply to it.
A consulting firm engaged at a client company processes that client's personal data as the client's processor or, where it determines purposes of its own, as a controller; that relationship is between the firm and the client, and the operator processes for each of them on their respective instructions as these documents describe.
"Data protection law" means every law that applies to the processing of customer personal data under this addendum, including the EU General Data Protection Regulation 2016/679 (the "GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended (the "CCPA") and the other United States state privacy laws. "Controller", "processor", "data subject", "personal data", "personal data breach", "processing" and "supervisory authority" have the meanings data protection law gives them; under the CCPA "controller" reads as "business" and "processor" as "service provider". "Standard contractual clauses" means the clauses in Commission Implementing Decision (EU) 2021/914, module two (controller to processor) and, where the customer is a processor, module three. "UK addendum" means the International Data Transfer Addendum issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018.
Every person the operator authorises to process customer personal data is bound by a duty of confidentiality, has access only to the extent their role requires, and is listed by name in the platform's configuration as an operator; the same people hold the hosting and database accounts. Contractors are bound by written terms no less protective than this addendum.
The operator implements and maintains the technical and organisational measures in Annex 2, appropriate to the risk, and may update them provided the overall level of protection does not fall. The customer is responsible for the security of its own accounts and credentials, for the roles it assigns, for the credentials it issues to connected systems, and for deciding whether the service's measures are adequate for the data it chooses to put in it. The service is not designed for special categories of personal data (health, biometric, genetic, racial or ethnic origin, political, religious, union, sexual life), for criminal-conviction data, or for government identifiers, card numbers or bank details; the customer must not put them in a workspace, and the recorder is built to skip fields that look like them.
The service lets a customer answer most requests itself: administrators can see, correct and export a workspace's data and remove or erase a person, and each person can see and delete their own account. If a data subject contacts the operator directly about customer personal data, the operator refers the request to the customer within five business days and does not answer it on the customer's behalf unless the customer asks or the law requires. The operator gives the customer the help it reasonably needs to answer requests for access, correction, erasure, restriction, portability and objection, and to honour an opt-out of sale or sharing (none occurs).
The operator notifies the customer's administrators of a personal data breach affecting customer personal data without undue delay after becoming aware of it, and in any case within 48 hours of becoming aware, with what is then known: the nature of the breach, the categories and approximate number of people and records concerned, the likely consequences, the measures taken or proposed, and a contact. Information is supplemented as it becomes available. The operator cooperates with the customer in investigating and remedying the breach and in the notifications the customer must make, and does not name the customer in any notification of its own without the customer's agreement unless the law requires. A notification is not an admission of fault.
Taking into account the nature of the processing and the information available to it, the operator helps the customer meet its obligations on security, breach notification, data protection impact assessments and prior consultation with a supervisory authority. The Privacy Policy, the Security page, the workforce notice and processing summary, this addendum and the methodology pages are the first source for that assistance; the operator answers further written questions within a reasonable time. Assistance beyond what the service and these documents provide may be charged at a reasonable rate agreed in advance.
The operator makes available the information needed to show compliance with this addendum: these documents, the security measures in Annex 2, the daily integrity check published at /verification, and answers to a reasonable written security questionnaire once a year. Where that is not enough to meet a legal requirement, the customer or an independent auditor bound by confidentiality may audit the operator's processing of customer personal data, once in any twelve months and additionally after a personal data breach affecting it or on a supervisory authority's demand, on 30 days' written notice, during business hours, in a way that does not disrupt the service or expose other customers' data, at the customer's cost. The operator will make a recognised third-party assessment (such as a SOC 2 report) available in place of an on-site audit once it holds one.
Customer personal data is processed in the United States (the application and database in the United States (Oregon); the sub-processors where Annex 3 says). Where data protection law restricts a transfer to the United States, the parties rely on the following, in this order: an adequacy decision covering the operator or the transfer, where one applies; otherwise the standard contractual clauses, which are incorporated into this addendum and completed as follows: module two (or module three where the customer is a processor); clause 7 (docking) included; clause 9 option 2 (general authorisation) with the notice period in section 6; clause 11 optional language not included; clause 13 and the supervisory authority, the governing law under clause 17 and the courts under clause 18 those of the EU member state in which the customer is established (or Ireland where it is not established in the EU); Annex I and II of the clauses completed by Annexes 1 and 2 of this addendum; for transfers from the United Kingdom, the UK addendum, with the tables completed from the same information and either party able to end it as its section 19 provides; for transfers from Switzerland, the clauses adapted as the Swiss Federal Data Protection and Information Commissioner requires, with the Commissioner as the competent authority and Swiss law for Swiss data. The operator will notify the customer if it can no longer comply with the clauses, and the customer may then suspend the transfer and end the affected service.
During the agreement the customer can export its workspace as JSON from Settings at any time, and for 30 days after it schedules the workspace for deletion. After that window, or at the end of the agreement, the operator erases customer personal data as the Privacy Policy, section 10, describes: identifiers are removed or replaced with anonymous labels, connected credentials are destroyed, and the short-lived stores are deleted on their windows. What remains is anonymised: verdicts, confirmed figures and the hash-chained change log, which the Terms require the service to keep and which no longer relate to an identifiable person, apart from the older audit entries the Privacy Policy discloses, which are kept as written because the chain cannot be rewritten. Backups age out on the hosting provider's window of at most seven days; after a restore the operator re-runs the scheduled workspace erasures and repeats the account deletions recorded on the audit trail since the backup. On written request the operator confirms deletion in writing and lists anything retained with the reason.
Where the CCPA or another United States state privacy law applies (among them the laws of Virginia, Colorado, Connecticut, Utah, Texas and Oregon), the operator is the customer's service provider or processor, processes customer personal data only for the business purposes of providing the service as these documents describe, and certifies that it understands and will comply with the restrictions in section 3: no selling, no sharing, no retention, use or disclosure outside the direct business relationship or for any purpose other than the specified business purposes, and no combining except as permitted. The operator notifies the customer if it can no longer meet these obligations, and the customer may take reasonable steps to stop and remediate unauthorised use. The operator gives the same level of privacy protection the law requires of the customer, deletes or returns the data at the end of the services as section 12 provides, makes available the information needed to demonstrate compliance, allows and cooperates with reasonable assessments as section 10 provides, and flows these duties down to its sub-processors by written contract.
Each party's liability under this addendum is subject to the exclusions and limits in the Terms of Service, section 18, except where data protection law or the standard contractual clauses do not permit a limit towards data subjects or supervisory authorities. Where this addendum and the Terms differ, this addendum prevails for the processing of customer personal data; where this addendum and the standard contractual clauses differ, the clauses prevail. This addendum ends with the agreement and survives until every obligation under section 12 is performed.
| Item | Detail |
|---|---|
| Data exporter / controller | The customer: the company or consulting firm that holds the workspace, acting through its administrators. Contact: the administrators' email addresses recorded in the service. |
| Data importer / processor | Track AI ROI, operator of Track AI ROI, United States. Contact: elijah@trackairoi.com. |
| Subject matter and purpose | Providing the service: mapping workflows, measuring the adoption, outcomes and costs of AI implementations, computing forecasts and verdicts, producing reports, drafting import mappings and workflow steps, sending the requests and notices the service involves, and publishing what the customer chooses to publish. |
| Nature of processing | Collection, storage, structuring, matching to the customer's roster, computation, display to the customer's authorised users and engaged firms, transmission to the sub-processors in Annex 3, erasure and anonymisation. |
| Duration | The life of the workspace, the 30-day deletion window, and the retention windows the Privacy Policy, section 10, states. |
| Categories of data subjects | The customer's employees, contractors and other staff added to a workspace, named as participants or roster members, named in connected systems' records or imports, asked for timings or check-ins, or using the recorder; a client company's staff where the customer is a consulting firm; the customer's administrators and users; counterparts in a marketplace introduction. |
| Categories of personal data | Names, work email addresses, job titles and departments, roles in the service, the identifier a sign-in provider returns; the credentials the customer gives for connected systems (held encrypted); who completed which work item and when, from connected systems and imports, and any further field the customer's configured pull or webhook returns; from a connected manufacturing ERP such as JobBOSS, labor tickets naming the employee, their department, the job and work center, the work date and the hours worked; per-person AI usage figures and Microsoft 365 Copilot activity where connected; timings, check-in and questionnaire answers, suggestions, comments and messages a person writes; hourly wages where an administrator enters them; the pages, controls and field labels a person used while they recorded a workflow, with their notes (never typed values); the names of imported files; session and timer records; the content of assistant exchanges for 30 days. |
| Special categories | None intended. The customer must not put them in a workspace (section 5). |
| Frequency | Continuous while the workspace is active; connected pulls on the schedule the customer sets, normally daily; the JobBOSS Classic agent sends hourly from the customer's own machine. |
| Recipients | The customer's authorised users; consulting firms the customer has engaged, within the engagement; the sub-processors in Annex 3; the public, only for what the customer publishes or consents to. |
| Retention after the end of the services | Erasure and anonymisation as section 12 describes. |
| Competent supervisory authority (EU transfers) | That of the EU member state in which the customer is established; otherwise the Irish Data Protection Commission. |
The technical and organisational measures the operator maintains, as the code and the hosting implement them. The Security page carries the same list with how to report a vulnerability.
As of 2026-11-09; the current list is at /subprocessors.
| Provider | Location | Purpose | What it handles |
|---|---|---|---|
| Render Services, Inc. | United States (Oregon) | Hosting the application and the PostgreSQL database, including managed backups | All platform data, encrypted in transit and at rest; request logs (IP address, path, status, timing); automated backups kept for at most seven days |
| Resend, Inc. | United States | Sending transactional email | Recipient address, subject and body of every email the platform sends (Privacy Policy, section 3), including sign-in links; Resend keeps a copy of sent email under its own retention settings |
| Stripe, Inc. | United States | Subscription payments, when a customer subscribes | Billing contact and payment details, entered on Stripe's own pages. When it opens the checkout the platform sends Stripe the administrator's email address and the company's reference; it never receives card numbers |
| Anthropic, PBC | United States | The platform assistant: the import assistant (proposing how the columns of an imported file or webhook feed map to the platform's fields) and the workflow recorder's draft steps | For an import: the file's name, the column names and, unless "Send column names only" is ticked, up to 40 sample rows, which can include the names and email addresses of the people in them; the company's task names and implementation titles; any instruction the person importing types. For a recording: the recorded events condensed into a log of page titles, sites, button and field labels, step marks, notes and times (never typed values); the department's name; any instruction the person reviewing types. Each exchange is stored with its action record and emptied after 30 days. Anthropic's commercial API terms apply: no training on the data, and deletion of inputs and outputs within 30 days (zero retention on request) |
Third-party services the customer or the reader's browser deals with directly (sign-in providers, the usage endpoints read with the customer's own keys, Microsoft Graph, Google Fonts) are not sub-processors and are listed on the same page for completeness.
See also Terms of Service, Privacy Policy, Acceptable Use Policy, Sub-processors, Security, Workforce notice and processing summary, how verification works and how adoption is measured. All documents: /legal.