Backblaze's New Privacy Policy Says It May Sell Your Data for Targeted Ads

BlackBlaze now explicitly states selling your data for advertisement

Backblaze's updated privacy notice, effective December 1, 2026, marks identifiers, commercial information, browsing history, and geolocation data as "sold or shared for targeted advertising." The backup and cloud storage provider says its tracking technologies may count as a sale or sharing of personal information under state law, and offers opt-outs through a "Your Privacy Choices" link or the Global Privacy Control signal.

Our use of tracking technologies may be considered a "sale" or "sharing" of personal information with third parties for cross-context behavioral advertising (e.g., targeted advertising) under applicable state law.
  1. cjboco

    You can opt out of most of everything here. Sure, it appears to be a dark pattern opt out process. Sucks, been using these guys for years, hate to see them go this route.

    https://preferences.backblaze.com/

  2. olalonde

    I know it sucks but it's worth pointing out that Backblaze explicitly distinguishes personal information from the files customers upload. Their CCPA FAQ[0] says that uploaded files are not included in the definition of personal information and that they do not sell or share those files.

    [0] https://help.backblaze.com/hc/en-us/articles/360040703654-Ca...

  3. munch-o-man

    good thing all my data with this is encrypted from my end haha. Also, just gonna pimp out https://github.com/afreidah/s3-orchestrator shamelessly here...if you put it between your clients and the backend it is easy to have your data in multiple places and a cloud migration is as simple as having your clients make requests to b2 through s3-orchestrator, add your new backend you want to migrate to in the config and set the replication-factor to 2, your clients keep writing with no idea what is going on, meanwhile a replication worker is copying everything from b2 to the new backend without taking downtime. Once replication reaches zero just drain the b2 backend so write stop going to it, and let it safely unwind itself, then remove it from the config. migration done, basically zero downtime other than a quick service restart.

  4. fluxusars

    I gave up on backblaze when they silently dropped support for truevrypt/veracrypt: https://old.reddit.com/r/backblaze/comments/1ol0pgf/backblaz...

  5. throwaway_ab

    Is the data the info about your account and computer environment details? (Location, name, os, apps running on your computer, etc...)

    Or is it actually the data you are backing up? Are they reading your files to mine for data to sell?

    Or both?

    I think selling any of this data, account, environment, actual files, all of this is abhorrent.

More from this day

2026-11-21