Anyone who has lost photos, messages, or health records after a failed software installation knows the cost of skipping a backup. With Apple preparing its next major iOS release and millions of devices set to update, the gap between what iCloud preserves and what an encrypted local backup captures has real consequences for users who store sensitive data on their phones. Encrypted computer backups include categories of information, such as Health data, that standard and iCloud-only methods leave out, according to Apple’s own documentation.
Why encrypted backups protect data that iCloud alone does not
The difference between backup methods is not just about convenience. It is about what gets saved and what gets left behind. Apple notes that iCloud backups include on-device data that is not already synced to the cloud, but they are still constrained by storage limits and by a defined list of items that never make it into the backup at all. A user who relies solely on iCloud before installing a major update may discover afterward that certain sensitive categories were never copied.
Computer backups offer a second path. Users can create them through Finder on macOS 10.15 or later, or through iTunes and the Apple Devices app on Windows, following the steps in Apple’s iPhone backup instructions. The critical step is toggling encryption on. When a user enables encryption for a local backup, the resulting file captures Health data and other sensitive categories that unencrypted backups and iCloud copies do not contain. That single checkbox changes what survives a botched update or a full device reset.
The hypothesis here is straightforward: a user who creates an encrypted local backup before an OS update retains at least one category of data, specifically Health records, that an iCloud-only user loses if something goes wrong. No large-scale post-update recovery survey has tested this at population level, but Apple’s own support documentation confirms the underlying mechanism. Encrypted backups include sensitive information that standard copies omit. The gap is structural, not theoretical.
What federal security guidance says about single-copy risk
The stakes extend beyond personal inconvenience. The National Institute of Standards and Technology has issued guidance on mobile device security in BYOD settings, framing the primary risks of smartphones as data loss and privacy compromise. While the publication does not cite specific failure-rate statistics for update-related incidents, its guidance is clear: relying on a single backup location creates a single point of failure.
NIST’s framework applies most directly to organizations managing employee-owned phones, but the logic holds for individual users. A phone that holds years of health tracking, saved passwords for banking apps, and two-factor authentication tokens carries the same exposure whether its owner works in a federal agency or a coffee shop. Losing that data because of an incomplete backup strategy is a preventable outcome.
One boundary that even encryption cannot cross deserves attention. Face ID data, Touch ID fingerprints, and the device passcode itself are never included in computer backups, even when encryption is turned on. Apple states this explicitly in its encrypted-backup support material. Users who expect a backup to restore biometric settings after an update will need to re-enroll those features manually. That limitation is baked into the security architecture and is not a bug or an oversight.
Gaps in available evidence on backup failure rates
For all the clarity Apple and NIST provide on what backups should include, neither source offers hard numbers on how often updates actually cause data loss. The NIST practice guide contains no quantitative incident data or failure-rate statistics tied to OS installations. Apple’s support pages walk users through the steps but publish no metrics on how many people complete a backup before updating, or how many encounter data loss afterward.
This absence matters because the advice to “back up before you update” appears on every pre-installation screen, yet there is no public measurement of compliance or outcomes. Without recovery-success data, the difference between encrypted and unencrypted backups remains confirmed at the feature level but unmeasured at the population level. A controlled post-update recovery survey, comparing users who relied on iCloud alone against those who also created an encrypted local copy, would be the clearest way to quantify the gap. No such study has been published by Apple, NIST, or any academic institution referenced in available documentation.
Another open question involves Android. Every source in the current evidence set addresses Apple’s ecosystem exclusively. Google’s backup infrastructure operates differently, with its own set of inclusions and exclusions, and no equivalent federal practice guide isolates Android-specific update risks. Users on Samsung, Pixel, or other Android devices face a parallel decision about backup methods, but the documented guidance reviewed here does not cover their workflow.
What to do before the next update lands on your phone
The practical takeaway is specific and actionable. Before installing any major software update, create an encrypted backup on a computer. On a Mac running macOS 10.15 or later, connect the phone with a cable, open Finder, select the device in the sidebar, and choose the option to encrypt the local backup. On Windows, open iTunes or the Apple Devices app, select the iPhone icon, and enable encryption in the backup section before starting the process. In both cases, choose a strong, memorable password, because losing that password can make the backup unusable.
Relying on iCloud alone remains better than having no backup at all, particularly for users who move frequently between devices or who do not have regular access to a computer. iCloud can restore photos, messages, app data, and many settings, and it operates automatically once configured. But its limitations around certain sensitive categories mean that for users who track medical conditions, fitness regimens, or other health-related metrics on their phones, an encrypted computer backup is closer to a full snapshot of the device.
Users who want more redundancy can combine these methods. One approach is to confirm that iCloud Backup is turned on and up to date, then immediately create an encrypted local copy before accepting an OS update. This two-layer strategy addresses the single-point-of-failure concern raised in federal guidance while still preserving the convenience of cloud-based recovery if a device is lost or stolen.
None of these steps guarantee that an update will proceed flawlessly, and they do not change the fact that biometric templates and passcodes must be reconfigured after a restore. What they do change is the likelihood that critical personal information-especially health data that cannot be re-downloaded from an app provider-survives an unexpected crash or installation error. Until more comprehensive failure-rate statistics are available, the safest assumption is that devices can and do fail, and that the most complete protection comes from pairing iCloud with an encrypted local backup rather than trusting a single copy to carry everything that matters.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
