SaaS Ranking

Notice before subprocessors change in Cloud storage

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

2 of 23 companies we measured here publish it, that is 9%. Last checked 2026-10-19.

9% here against 10% across every category we measure. Cloud storage sits below 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 Cloud storage.

The evidence at a glance
  • Found2
  • Not found at checked addresses21
  • Not measured5

28 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
IDrive https://www.idrive.com/dpaChecked
Proton Drive https://proton.me/legal/dpaChecked
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
Backblaze 8 addresses checkedChecked
Degoo 8 addresses checkedChecked
Dropbox 8 addresses checkedChecked
Egnyte 8 addresses checkedChecked
Filen 8 addresses checkedChecked
Filestash 8 addresses checkedChecked
Icedrive 8 addresses checkedChecked
Internxt 8 addresses checkedChecked
Jottacloud 8 addresses checkedChecked
Koofr 8 addresses checkedChecked
Livedrive 8 addresses checkedChecked
luckycloud 8 addresses checkedChecked
Mega 8 addresses checkedChecked
ownCloud 8 addresses checkedChecked
pCloud 8 addresses checkedChecked
RushFiles 8 addresses checkedChecked
Seafile 8 addresses checkedChecked
Storj 8 addresses checkedChecked
Sync.com 8 addresses checkedChecked
Tresorit 8 addresses checkedChecked
Wasabi 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
Box The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Kiteworks The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Nextcloud None of the addresses could be reached, so this was not measured.Checked
SpiderOak The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked
TeamDrive The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked

Other criteria in Cloud storage

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.