Subprocessors
Everyone involved in delivering a migration, what they handle, and where they run it. Your own source and destination platforms are not listed here — they are your systems, and we act on your instructions when we touch them.
Last updated September 2026
Current subprocessors
| Provider | What it does | What it handles | Where |
|---|---|---|---|
| Supabase | Hosts the database holding job state, record states, mapping tables and reconciliation records. | Migration metadata and, where a mapping requires it, names and email addresses. | Customer region, pinned per engagement |
| Cloudflare | Protects public forms from automated abuse, and serves static assets. | Request metadata only. No migration content. | Global edge |
| Email delivery provider | Delivers transactional email — scoping confirmations and engagement notifications. | Names and email addresses of people who contact us. | Confirmed per engagement |
What is not on this list
Your source and destination platforms do not appear here. We access them with credentials you issue, on your instruction, and they remain your relationships rather than ours.
Where a migration stages media in cloud storage you own, that storage is not a subprocessor of ours either — it is your infrastructure, under your keys and your retention policy.
Changes
We will tell customers with an active engagement before adding a subprocessor that would handle their data, with enough notice to raise an objection.