Backblaze has reportedly ceased backing up data residing in cloud sync folders like OneDrive and Dropbox without informing users directly. This unilateral policy shift breaks the implied trust users place in an unlimited backup service, especially since sync providers offer inferior versioning and retention compared to dedicated backup solutions.

This change surfaced when users discovered omissions, such as `.git` folders and now major cloud directories, were mysteriously excluded from backups. The company buried this modification within release notes, classifying the exclusion of services like Dropbox and OneDrive as a performance 'Improvement' to avoid unintended uploads.

For many, including long-time advocates, this move feels like a fundamental service downgrade. Backblaze's original 2015 pitch promised to back up *all* user data with no restrictions, making absolute file coverage the core value proposition. The lack of proactive communication erodes confidence in Backblaze’s commitment to data safety.

Operating under the assumption that every file is covered is now dangerous. If the provider can silently drop support for common directories like Git or entire cloud sync folders, users must audit exclusions constantly. The service has shifted from backing up everything to performing selective backup based on internal criteria.