New phone launches happen on a predictable schedule, and each cycle brings the same advice: back up your old phone, restore to the new one, and you’re done. The transfer guides from Apple and Google are genuinely good. What they don’t cover is what happens to your data during that process — and the assumptions built into the “seamless” experience that most people never question.
Switching phones is one of the biggest personal-data events in a typical person’s year. Every photo, note, and stored file passes through a migration path. Understanding that path is how you decide whether you’re comfortable with what it involves.
What “Just Restore from Backup” Actually Means
When Apple prompts you to restore from an iCloud backup, or Android offers to copy your data from your old device, the experience feels simple. Under the hood, several things happen simultaneously:
For Apple: Your iCloud backup contains app data, settings, contacts, calendars, messages, photos (if iCloud Photos is on), and device configuration. Unless you’ve enabled iCloud Advanced Data Protection, Apple holds the encryption keys for that backup. That means Apple’s systems — and, in response to a lawful request, Apple’s legal team — can read the contents. The backup is encrypted in transit and at rest, but Apple can decrypt it.
For Android/Google: Android backups are tied to your Google account and similarly use encryption where Google holds keys. Your photos (if Google Photos backup is on), contacts, app data, SMS messages, and call logs are all included. Google can access these for legal compliance, and its systems process them for purposes like spam detection and service improvement.
The practical upshot: the moment you initiate a restore, a copy of your digital life exists on a server that a company controls, can decrypt, and has agreed to hand over under certain legal circumstances.
That’s not necessarily a reason to never use cloud backup. For most people, the convenience and data safety genuinely outweigh the privacy tradeoff. But it’s worth knowing what you’re accepting.
What Gets Transferred That You Didn’t Choose
Beyond the backup restore, phone-switching introduces several less-obvious data transfers:
Device fingerprinting. When you set up a new device on the same account, both Apple and Google log the event. This links your old device’s history to your new device and creates a persistent identity thread across hardware.
App re-installation and permissions. When apps reinstall on your new phone, many immediately request the same permissions they had before — and some silently re-enable data collection that was inactive because you rarely used the app. You don’t get a fresh permission audit; you get whatever you’d agreed to before.
Contacts and address book re-upload. If your contacts sync to a cloud provider, every phone number and email address in your address book gets re-uploaded during setup. Apps that access contacts (for “find your friends” features, spam filtering, etc.) will re-scan that list.
Cached data from previous AI indexing. If Google Photos or Apple’s photo library had been running AI recognition on your photos (face identification, object classification, location tagging), that index persists in the cloud. Switching phones doesn’t reset it — it transfers, updated, to your new device.
The Metadata Problem
Photo files are the most obvious transfer concern, but the metadata attached to them matters as much as the images themselves.
Every photo your phone has taken likely contains:
- GPS coordinates at the time of capture
- Device make and model
- Timestamp (creation, modification)
- Camera settings (aperture, shutter speed, ISO)
When your photos transfer through a cloud service during a device migration, that metadata travels with them. Cloud providers’ AI systems use this metadata for indexing, not just the image content. A year of location-stamped photos, transferred via backup, is a detailed log of where you’ve been.
If you’ve previously shared photos via a cloud link, that shared version may persist independently of any transfer you initiate now.
How to Make the Transfer More Private
You don’t need to avoid cloud backup entirely to do this more thoughtfully. A few specific choices materially reduce what your migration exposes.
Before you start
Audit what’s in your cloud backup. On iPhone: Settings → your name → iCloud → see which apps have iCloud backup on, and turn off anything you don’t need transferred. On Android: Settings → Google → Backup, and review what’s included. App data can carry more than you’d expect — chat histories, login tokens, browsing data from apps.
Review photo library before transferring. A phone migration is the best natural prompt to delete photos you’ve accumulated but don’t actually want: screenshots, accidental captures, duplicates. Fewer photos means less data transferred and less indexing activity on the new device.
Enable stronger backup encryption if available. Apple’s iCloud Advanced Data Protection extends end-to-end encryption to backups, photos, and most iCloud data — meaning Apple cannot decrypt them even if compelled. You must opt in explicitly. It’s one of the highest-leverage privacy switches available on iPhone, and a phone migration is a good time to enable it.
During the transfer
Consider a local backup option. Both iOS (via Finder on Mac) and Android (via various backup apps) support creating a full device backup on a computer rather than in the cloud. A local backup sits on your own hardware and doesn’t pass through a server. The tradeoff is that you’re responsible for keeping that computer secure and for not losing the backup file.
Use a direct device-to-device transfer where possible. Apple’s Quick Start and Android’s device-to-device transfer via cable let your old and new phones communicate directly, without routing everything through a cloud server as an intermediary. Data still passes through the same underlying systems once your accounts re-authenticate on the new device, but the initial transfer itself doesn’t require cloud upload/download of the full backup.
After the transfer
Do a permission audit on the new device. Once your apps are reinstalled, go through location, microphone, camera, contacts, and photos permissions in your phone’s settings. Treat this as a clean-slate review — only re-enable permissions that apps genuinely need and that you actively use.
Revoke lingering access on old device. Log out of your accounts on the old phone before you sell, trade in, or recycle it. Beyond factory reset (which most people do), actively revoke the device from your Google or Apple account, which prevents it from being recognized as a trusted device for account recovery.
Check shared cloud links from your photo library. If you’ve shared photos or files through Google Photos links or iCloud links, those links may still be active and accessible even after you’ve set up a new device. Review what’s shared and expire or revoke anything no longer needed.
What Your Personal Files Have to Do With It
The privacy exposure during a phone switch scales with how much of your personal life runs through the services that execute the backup.
If your photos, documents, journal entries, and voice memos all live in Google Drive or iCloud, a device migration means all of it passes through that service’s transfer infrastructure. The indexing, the metadata extraction, and the legal access window all apply to the whole library.
One way to reduce that exposure is to keep personal files in a service that isn’t also your device’s backup service. When your personal files live somewhere separate from your backup provider, switching phones doesn’t automatically expose them to the migration process. You transfer device settings and apps through your backup, then simply log into your personal file service on the new device and access your files there — the two events stay separate.
This is relevant to how daftei works: photos and personal files stored in daftei aren’t part of your iCloud or Google backup. They stay in daftei’s infrastructure, encrypted in transit (TLS 1.3) and at rest (AES-256), independent of whatever backup provider handles your device migration. Switching to a new phone means opening daftei, logging in, and your files are there — no migration event involved.
What You Can Reasonably Accept (and What You Can’t)
There’s no phone migration that touches nothing. Some degree of data transfer through platform infrastructure is unavoidable if you want a working phone.
What you can reasonably reduce:
- Which apps get iCloud/Google backup enabled
- How many photos transfer (audit first)
- Whether your personal files are caught in the backup sweep
- Which app permissions silently reactivate
- How long shared links remain active
What you probably can’t avoid:
- The device registration event (Apple/Google linking old and new hardware to your account)
- Some degree of cloud-side indexing on photo libraries, if those libraries are backed up there
- Account authentication events that create server-side logs
Understanding the distinction helps you make targeted choices rather than either ignoring the whole issue or getting overwhelmed by it. A phone switch is a finite, discrete event — doing it thoughtfully once is better than a vague ongoing concern that never gets addressed.
A Practical Checklist
Before switching:
- Audit iCloud/Google backup apps, disable ones you don’t need
- Delete photos you no longer want (screenshots, duplicates, accidental captures)
- Enable iCloud Advanced Data Protection if on iPhone
- Download any personal files you want local copies of
- Check and expire old shared links
During the transfer:
- Use device-to-device transfer over cable if possible
- Create a local encrypted backup as a secondary option if it matters to you
After:
- Full permissions audit on the new device
- Remove the old device from your trusted devices list in Apple ID / Google account settings
- Do a factory reset on the old phone before trade-in or resale
- Verify your personal file services are accessible on the new device (just log in)