(www.neowin.net)
- Rclone crypt: https://rclone.org/crypt/
- Cryptomator: https://cryptomator.org/
- (for incremental backups) Restic: https://restic.net/
This should be a hard requirement for anyone storing data on someone else's computer. Barring vulnerabilities, you can essentially disregard the service's privacy policy, and select purely based on price and reliability.
I used veracrypt for a long time, but the encrypted vault is just one gigantic blob, which makes incremental backups hard, i recently switched to https://github.com/rfjakob/gocryptfs which encrypts the files and the filenames, as a results it's way easier to sync with any tool, even something like Dropbox.
Agreed.
With regard to rclone, remember that there is a very interesting and useful workflow which combines rclone and restic to produce append-only backups at the destination of your choice:
https://www.rsync.net/resources/notes/2025-q4-rsync.net_tech...
rclone serve restic --stdio ...
... is the form of this workflow and the howto linked above is NOT rsync.net specific - it can be used anywhere.At some point the obvious step for these services is to disallow storage of encrypted data, yes?
If you upload an uncompressed 10MB markdown file to Amazon S3, Amazon will charge you for 10MB of storage, but is almost certainly going to use some internal compression so that they only have to commit 500KB to disk. Given enough scale, and you can project that every x TB of customer data only actually requires y TB of storage space. If all ingested data is already encrypted, x now equals y and that savings ratio disappears, so you are going to have to provision x storage hardware.
No, Backblaze doesn't. Their personal and business plans have "Unlimited data backup": https://www.backblaze.com/cloud-backup/pricing
Been using rclone on B2 for ever, only ever push encrypted files there, with encrypted filenames so good luck using them for marketing or whatever.
I reposted because after the rename of the thread above, the problematic nature of these changes are lost using the generic privacy policy page title.
Backblaze Notice at Collection and Privacy Policy: https://www.backblaze.com/company/policy/privacy
The table feels confusing with the spanned center cell but if I'm reading it correctly, all of the following fall under "Sold or Shared for Targeted Advertising: Yes"
* Identifiers: For example, a name, address, Internet Protocol address, email address, or other similar identifiers.
* Commercial Information: For example, records of personal property, products or services purchased, obtained, or considered, or other purchasing or consuming histories or tendencies.
* Internet or Other Similar Network Activity: For example, browsing history, search history, and information regarding a consumer’s interaction with an Internet Web site, application, or advertisement.
* Geolocation Data: For example, information that can be used to determine a device’s physical location.
Opt out at https://preferences.backblaze.com
Can anyone say whether it's third party sharing (i.e. using Google analytics) or selling of personal data? (The article says "sale or sharing")
Because I've got little problem with the former, and a big problem with the latter.
I'm particularly interested because I had a TODO item of my own for setting up backblaze as an alternate restic backend, but now I'd probably like a little more clarity before going ahead.
People previously felt like they could trust the Backblaze client to faithfully mirror their data. No longer. That client may decide that it has the right to inspect some "harmless" metadata that would be valuable to advertisers. Will the software start scanning browser cookies of recently visited sites? Pull GPS coordinates of recently acquired photos?
From this moment, running Backblaze software is an unacceptable risk, and the convenience of the service is now negligible. Privacy focused individuals will have to setup their own encryption pipeline using trusted software to dump encrypted blocks onto Backblaze servers.
What We Sell to Third Parties or Share with Third Parties for Cross-Context Behavioral Advertising and Right to Opt-Out
We have sold or shared with third parties for cross-context behavioral advertising (e.g., targeted advertising) the following categories of personal information to advertising networks and analytics providers in the preceding 12 months: Identifiers; Internet or Other Similar Network Activity; Commercial Information; Geolocation Data. We do not sell or share sensitive personal information.
Don't be fooled by "identifiers" either: Identifiers: For example, a name, address, Internet Protocol address, email address, or other similar identifiers.
I feel that utilising a few quite normal advertising third parties would match that description, and so would selling data to some shady data brokers. Can anyone infer which it is?
They also explicitly said they weren’t going to sell my data, only to change that with this update. When will they “alter the deal” to allow also selling my actual stored data?
Anything I store on not-my-computer is encrypted tyvm.
Privacy Notice
Updated to improve clarity and organization, and to reflect current legal requirements.Normal communication to normal people doesn't involve sending diffs. I feel like I'm practically shilling for these guys just by having to point out obvious stuff.
Just to be clear - no affiliation with backblaze, not even a customer. Just have to deal with privacy policy updates all the time for customers. Poke around in google or run these comments through an LLM of choice. This is really pretty benign stuff lots of companies are being forced to do because of legal trolls running wild in California over the last year or so.
No, there is profit motive in this.
Begging the question.
> not doing so opens them up to a lawsuit.
Evidence that these adjustments are not minor.
* Having legally compliant policy safeguards against lawsuits from legal trolls who focus on low hanging fruit. The wording requirement to meet that standard changes from time to time, necessitating minor adjustments to stay compliant.
I miss when hacker news was filled with intellectually curious people instead of quasi-clever types. This place has become exhausting.
You guys win. Normal privacy policy adjustments are all actually EvilCo secret plans to sell your cat photos to the highest bidder for AI. Couldn't possibly be anything else. Certainly it's not the sort of thing you could put literally 3 minutes of research into instead of just arguing from a starting position of "must be malice".
It does not surprise me that they would do this as their priority seems to be cashing in on AI and not delivering a decent service to customers.
I'm looking at S3 or Bunny - I need something I don't self-host, as I use it for Terraform (OpenTofu) state, among other things.
I've had zero issues, ever. But I'm not a heavy user. Just backups to b2 via restic. Never any issues with uploads or downloads or service availability.
Post the problematic parts of updated terms if you want a discussion. Don't turn this into yellow press tabloid.
I doubt you are going to see a commentary from Bruce Schneier or the EFF about the security implications of this. Which leaves randos on the internet, whose name is meaningless to the rest of the audience.
The policy changed, as a rando user of the internet, I think it is a terribly worrying policy decision.