Every third party that handles personal data on the operator's behalf in running Track AI ROI, what each is for, and what it receives. Each is bound by a written contract that limits it to the purpose listed and, where the data leaves the European Economic Area, the United Kingdom or Switzerland, carries the standard contractual clauses. The operator remains responsible for each of them.
Each processes personal data on the operator's behalf under a written contract that limits it to the purpose listed.
| 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) |
Not sub-processors: the customer, or the reader's browser, deals with each directly under its own terms. Listed so that nothing is hidden.
| Provider | Location | Purpose | What it handles |
|---|---|---|---|
| Google LLC | United States | Optional sign-in with a Google account | Name, email address and account identifier at sign-in, under Google's own terms |
| Google Fonts (Google LLC) | United States | Typefaces on the sign-in and sign-up pages and in proof-report documents | The reader's browser requests the font files from Google, which sees the reader's IP address, browser and the page's address. No platform data is sent |
| Microsoft Corporation | United States | Optional sign-in with a Microsoft account; optional Microsoft 365 Copilot usage report, only after a Microsoft 365 administrator consents | Name, email address and account identifier at sign-in; the usage report is read from Microsoft, not sent to it |
| Anthropic, OpenAI, Google Cloud (usage endpoints) | United States | Reading usage figures with the API keys a customer connects | The connected key and a date range go to the provider's usage endpoint; usage figures come back. No workspace content is sent for this |
| ECI Software Solutions (JobBOSS² Cloud API) | United States | Reading JobBOSS² Cloud records with the API user a customer connects | The API user's client ID and secret go to ECI's sign-in endpoint, and the token it returns, with the record type and the time of the last change already read, to ECI's data endpoint; the customer's records come back. No workspace content is sent |
The AI providers whose usage a customer connects (Anthropic, OpenAI, Google) receive the customer's own key and a date range so the platform can read usage figures; they are the customer's providers under the customer's contracts. Google and Microsoft as sign-in providers, and Microsoft 365 as the source of the Copilot report, act under the customer's or the person's own account with them. Google Fonts serves typefaces to the reader's browser on a few pages and sees the reader's IP address. Business systems a customer connects send data to the platform; for a scheduled pull the platform sends them only the customer's own credential and the query that selects the records (ECI's API, for JobBOSS² Cloud, is listed above). They are the customer's providers under the customer's contracts. The JobBOSS Classic agent runs on the customer's own machine under the customer's control and is not a third party. Consulting firms a customer engages are the customer's own processors or controllers, chosen by the customer.
See also Terms of Service, Privacy Policy, Data Processing Addendum, Acceptable Use Policy, Security, Workforce notice and processing summary, how verification works and how adoption is measured. All documents: /legal.