Backblaze customers worried of personal data sale/sharing after policy update
Backblaze's updated privacy policy has customers reeling, as new language suggests personal data may be sold or shared for targeted advertising. This move, clarified by Backblaze to exclude backed-up files, still raises alarms about privacy practices and corporate trust. Hacker News dissects whether this is a defensive legal maneuver or a shift towards data monetization, prompting many to consider switching services or reinforcing their own data encryption strategies.
The Lowdown
Cloud backup provider Backblaze has sparked significant concern among its user base after updating its privacy policy. The new terms, effective December 1, 2026, indicate that certain categories of personal information may be sold or shared with third parties for cross-context behavioral advertising.
- Policy Change: The updated policy now explicitly states that tracking technologies may involve selling or sharing personal information for targeted advertising.
- Data Categories: Information that may be shared includes identifiers (name, IP, email), commercial information (purchase history), internet/network activity (browsing history), and geolocation data.
- Key Distinction: Backblaze clarifies that this policy concerns customer account information and website interaction data, not the files users backup to their servers. Backed-up files are explicitly stated as not being sold or shared.
- Previous Stance: The prior policy, updated in April 2026, stated the company would not rent, trade, or share customer addresses or email for marketing purposes without consent.
- Opt-Out Options: Customers can opt-out via a "Your Privacy Choices" link on Backblaze's website or by using browser-based signals like Global Privacy Control (GPC).
Despite the clarification that user files are exempt, the perceived shift in data handling practices has ignited a debate about privacy, data monetization, and the evolving landscape of user trust in cloud services.
The Gossip
Privacy Policy Panic: Encryption as a Panacea
Many commenters express dismay and a sense of betrayal over Backblaze's policy update, even with the clarification that actual backed-up files are not included. The prevailing sentiment is that companies will eventually exploit any data they can. A strong consensus emerged around the necessity of client-side encryption for *all* data sent to cloud providers, with tools like Restic, Rclone crypt, Cryptomator, and `age + rclone` frequently recommended as essential safeguards against shifting privacy policies and potential data exploitation.
Motives & Maneuvers: Legal Shields or Lucrative Shifts?
The discussion delves into the potential reasons behind Backblaze's policy change. One camp argues it's primarily a defensive legal maneuver, reacting to California's stringent privacy laws (like CIPA) and the risk of lawsuits over common website tracking (e.g., Google Analytics for remarketing). This view suggests it's about compliance and avoiding litigation. Conversely, others suspect a profit motive, suggesting Backblaze might be looking to monetize user data for AI training, or even subtly encourage consumer users to leave to free up storage for more lucrative AI-related enterprise uses.
Service Struggles & Seeking Sanctuaries
Beyond the privacy debate, several users aired grievances about Backblaze's service quality. Complaints included performance issues (especially at night), unresponsive or problematic support, and poorly maintained client libraries that cause API compatibility problems. These existing frustrations, combined with the privacy policy update, are pushing users to actively seek alternative storage providers. Options like S3 or Bunny are mentioned for those needing non-self-hosted solutions, while others emphasize the importance of robust encryption tools regardless of the chosen backend.