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.
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...
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.
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.
Also note: at least on MacOS, the Backblaze backup install process creates a world-readable directory that contains a world-readable file that lists ALL files to be backed up across all users. This is a security issue if you have a multi-user setup and you don't want your filenames leaked across users. Any user on the system can read this file list.
Backblaze was uninterested in discussing this issue.
How do they even get some of this data they're proposing to sell?
"Geolocation Data: For example, information that can be used to determine a device’s physical location. "
And why would they need my device's location data to presumably access a backup?
I would guess they're giving signups and website visits to advertising networks, to link it to their ads and get discounts on future campaigns. They obviously shouldn't, and it may be worse than that, they shouldn't use such an opaque and hostile policy. But it doesn't include backups, and in practice I doubt if they're selling interactions from the desktop app at all?
There is a niche data selling industry sprung lately and offering millions of dollars to buy data. No wondering they are lured into it. It is free revenue.
To everyone here encrypting their data before sending it offsite.
How do you backup/store your encryption keys? How do you test restore?
Every single service turns to crap. It's just a matter of when. Every service you use, you always need to be on the lookout for an alternative.
I'm tired
Title has a typo
Such a shame enshittification has finally taken hold of BackBlaze.
It comes complete with vauge detail on what they're actually sharing and a dark pattern opt out (should be opt-in and toggled in your account settings, not a seperate form)
I remember back when they added facebook tracking code to there website that was totally accidentally sharing metadata.
https://www.bleepingcomputer.com/news/security/backblaze-mis...
This is why we need proper backup solutions, like cerabyte.
It's been over 2 hours now.
Where's the vibe-coded bring your own storage API key alternative?
Backup is a trust business. The entire product promise is "your data is safe with us for years", and customers pay monthly for that promise whether or not they ever restore anything. Monetising the same customer data for advertising reads, to many customers, as the opposite of that promise, whatever the legal fine print says.
The opt-out pattern makes it worse. When a company with a retention-based model introduces data sharing and hides the off switch, it converts a quiet pricing or growth problem into a visible trust problem. Churn in backup products is normally low and slow; moves like this give a loyal, low-maintenance customer base an active reason to shop around, and backup is exactly the kind of product where switching, once started, tends to complete.
If the ad revenue per user is small relative to lifetime value, the maths on this looks bad even before reputational damage.
[flagged]
[flagged]
I gave up on backblaze when they silently dropped support for truevrypt/veracrypt: https://old.reddit.com/r/backblaze/comments/1ol0pgf/backblaz...