SaaS Ranking

Notice before subprocessors change in Data warehouses and databases

A list is a snapshot. Art. 28(2) GDPR gives you a right to object, and that needs advance notice.

12 of 42 companies we measured here publish it, that is 29%. Last checked 2026-10-17.

29% here against 10% across every category we measure. Data warehouses and databases sits above the overall share for this criterion.

This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.

Back to Notice before subprocessors change across all categories, or to Data warehouses and databases.

The evidence at a glance
  • Found12
  • Not found at checked addresses30
  • Not measured3

45 companies in total. Unmeasured companies are excluded from the published share.

Published

The vendor commits publicly to giving notice before the list changes.

VendorWhat we found
Aiven https://aiven.io/subprocessorsChecked
Databricks https://www.databricks.com/legal/databricks-subprocessorsChecked
InfluxData https://www.influxdata.com/legal/data-processing-agreement-legacy-version/Checked
MongoDB Atlas https://www.mongodb.com/legal/data-processing-agreementChecked
Neon https://www.databricks.com/legal/databricks-subprocessorsChecked
PlanetScale https://planetscale.com/legal/data-processing-addendumChecked
Redis https://redis.io/legal/subprocessors/Checked
ScyllaDB https://www.scylladb.com/data-processing-agreement/Checked
Supabase https://supabase.com/legal/customer-resources/subprocessor-listChecked
SurrealDB https://surrealdb.com/legal/subprocessorsChecked
Tinybird https://www.tinybird.co/dpaChecked
Weaviate https://weaviate.io/subprocessorsChecked
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.

VendorWhat we found
ClickHouse 8 addresses checkedChecked
CockroachDB 8 addresses checkedChecked
Convex 8 addresses checkedChecked
Crunchy Data 8 addresses checkedChecked
DoubleCloud 8 addresses checkedChecked
Dragonfly 8 addresses checkedChecked
Dremio 8 addresses checkedChecked
EDB 8 addresses checkedChecked
Exasol 8 addresses checkedChecked
Firebolt 8 addresses checkedChecked
Gel 8 addresses checkedChecked
Instaclustr 8 addresses checkedChecked
Materialize 8 addresses checkedChecked
MotherDuck 8 addresses checkedChecked
Nile 8 addresses checkedChecked
Percona 8 addresses checkedChecked
PingCAP TiDB Cloud 8 addresses checkedChecked
Prisma 8 addresses checkedChecked
Qdrant 8 addresses checkedChecked
SingleStore 8 addresses checkedChecked
Snowflake 8 addresses checkedChecked
StarRocks 8 addresses checkedChecked
Teradata 8 addresses checkedChecked
Tiger Data 8 addresses checkedChecked
Turso 8 addresses checkedChecked
Ubicloud 8 addresses checkedChecked
Vertica 8 addresses checkedChecked
Xata 8 addresses checkedChecked
Yellowbrick 8 addresses checkedChecked
YugabyteDB 8 addresses checkedChecked
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.

VendorWhat we found
Couchbase The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Cybertec The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
QuestDB The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked

Other criteria in Data warehouses and databases

Notice before subprocessors change in related categories

Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.