Draft: not yet reviewed by counsel
This is a working draft. It has not been approved and is not final, and it should not be relied on as the agreement between you and us. 3 items are still to be confirmed, highlighted where they occur.
Subprocessors
The companies that help us run the Data Migration Agent, and what each one receives. This list is part of the Data Processing Agreement.
Last changed 24 September 2026
The AI assistant sends data to a third-party AI provider. That includes what you type into it, and names from your workspace. The entry for DigitalOcean GenAI Platform below says exactly what.
In use
DigitalOcean
HostingCan see workspace contentDigitalOcean, LLC
Hosts the application, its background workers, the PostgreSQL database that holds every workspace, the job queue and cache, and, where data export is switched on, the private object storage (Spaces) that holds a data export until it is downloaded or its link expires.
What it receives
- Everything stored in a workspace, including migrated data, flow definitions and settings
- Account details: name, work email address, role, hashed password
- ERP connection credentials, stored encrypted
- Job and activity logs
- Temporary job and session data held in the queue and cache
- Data exports a customer requests: a copy of the workspace data, kept only until downloaded or the link expires
Where
New York, United States (App Platform region nyc). [[TO CONFIRM: region of the production database and cache, and any backups]]
DigitalOcean GenAI Platform
AICan see workspace contentOnly if you use itDigitalOcean, LLC
Runs the AI model behind the AI assistant (chat, SQL suggestions, field-mapping and action-flow suggestions, conversion suggestions and migration error explanations), and a knowledge base of our own product documentation.
What it receives
- What you type into the AI assistant, and the last few messages of that conversation
- The names of the tables and columns in your workspace, and the names of the fields and IFS entities in the flow you are working on
- Example source values, only when you include them in a request for conversion suggestions
- The error text of a failed migration job, when you ask the assistant to explain it. This can contain values from your data as reported back by IFS
- Search queries sent to our documentation knowledge base
Where
[[TO CONFIRM: region where DigitalOcean runs the inference service and knowledge base]]
Microsoft 365 (Microsoft Graph)
EmailMicrosoft Corporation
Sends our transactional email: workspace verification, invitations and plan notices.
What it receives
- The recipient’s email address
- The organisation name and the content of the message being sent
Where
[[TO CONFIRM: Microsoft 365 data location of the Change8 tenant that sends the email]]
Google sign-in
Sign-inOnly if you use itGoogle LLC
Lets a person sign in with their Google account instead of a password. Only used if they choose it.
What it receives
- The email address and basic profile of the Google account being used to sign in
Where
Determined by Google
Microsoft sign-in
Sign-inOnly if you use itMicrosoft Corporation
Lets a person sign in with their Microsoft account instead of a password. Only used if they choose it.
What it receives
- The email address and basic profile of the Microsoft account being used to sign in
Where
Determined by Microsoft
Google Fonts
Your browserGoogle LLC
Serves the icon font used across the interface. Your browser requests it directly from Google, so this is not something we send data to, but Google does see the request.
What it receives
- Your IP address and browser details, as part of the font request
Where
Determined by Google
Not subprocessors
Some services are often assumed to be subprocessors. These are not, and why:
- Your IFS environment. It is your own system. Data moves to and from it because you told the tool to, using the credentials you provided.
- GitHub. Holds our source code. Customer data is never stored there.
How this list changes
We tell your organisation’s Owner before we add or replace a subprocessor, as the Data Processing Agreement describes. Every change is recorded below.
| Date | Change |
|---|---|
| 24 September 2026 | Where data export is switched on, DigitalOcean also holds requested data exports in private object storage (Spaces) until they are downloaded or their link expires. |
| 21 September 2026 | Initial publication of the subprocessor list. |
