Links last opened 29 October 2026. Record confirmed by a person on 2 October 2026. 2 recorded changes, listed below.
Merge API contracts through Merge API Inc., registered in United States. Transfers of personal data out of the EEA are covered by EU-US Data Privacy Framework (DPF). Its trust center is published at https://trust.merge.dev/. Its customer data processing agreement, also called a data processing addendum, is published by Merge API itself; the link is below. Its sub-processor list is published by Merge API itself; the link is below. We open those pages every day — last on 29 October 2026 — and a person last went through this record on 2 October 2026.
A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope.
A ready row. Replace the purpose with what your client actually uses Merge API for.
| Subprocessor | Legal entity | Country | Purpose | Transfer | DPA |
|---|---|---|---|---|---|
| Merge API | Merge API Inc. | US | AI providers | DPF | https://www.merge.dev/legal/data-processing-agreement |
Changes we noticed on Merge API's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.
29 October 2026
Merge API added SMS Terms to their data processing agreement, expanding the scope of services covered by the DPA.
Seen on https://www.merge.dev/legal/data-processing-agreement
30 September 2026
We recorded changes to the transfer mechanism, the UK transfer mechanism.
Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.
Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.
Six of them. All ai providers in the registry · others that transfer the same way.