Notice before subprocessors change in MLOps and model serving
A list is a snapshot. Art. 28(2) GDPR gives you a right to object, and that needs advance notice.
2 of 12 vendors we measured here publish it, that is 17%. Last checked 2026-09-02.
17% here against 10% across every category we measure. MLOps and model serving sits above the overall share for this criterion.
Back to Notice before subprocessors change across all categories, or to MLOps and model serving.
Published
The vendor commits publicly to giving notice before the list changes.
| Vendor | What we found |
|---|---|
| Anyscale | https://trust.anyscale.com/?tab=subprocessors |
| Baseten | https://www.baseten.co/dpa/ |
No commitment to give notice before subprocessors change found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| BentoML | 8 addresses checked |
| ClearML | 8 addresses checked |
| Comet | 8 addresses checked |
| CoreWeave | 8 addresses checked |
| DataRobot | 8 addresses checked |
| Evidently | 8 addresses checked |
| Flyte | 8 addresses checked |
| Genesis Cloud | 8 addresses checked |
| Iterative | 8 addresses checked |
| Kedro | 8 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us and the next run picks it up.