Every November through January, the same pattern plays out across millions of families: people take hundreds of photos, share them through whatever channel is easiest, and then forget that those channels often keep the photos long after the gathering ends.
The result is that holiday photos — which frequently include children, home interiors, elderly relatives, and location data — end up in places nobody explicitly chose.
This isn’t a hypothetical concern. It’s a structural feature of how the most popular sharing methods work.
The Four Sharing Methods and What They Actually Do
Group chats
A family group text or WhatsApp thread is probably the most common place holiday photos end up. They feel private because only the people in the thread can see them — but that assumption has several gaps.
Every recipient saves photos to their own camera roll with a single tap. Once saved, a photo is subject to whatever backup and sync settings that person has enabled. A photo you sent to seven relatives may now live in four different cloud accounts, two of which are set to back up automatically to a third-party service.
On WhatsApp specifically, your messages and photos — including backed-up media — are stored in a system governed by Meta’s privacy policies. If any recipient backs up their WhatsApp to Google Drive or iCloud, the photos are then subject to the terms of that platform as well.
You sent the photo once. It potentially lives in five different places with five different privacy policies.
AirDrop and Quick Share
AirDrop (Apple) and Quick Share (Android) are the closest thing to handing someone a physical print: no accounts, no servers, direct device-to-device transfer. Once the file lands on the recipient’s device, though, it is treated like any other file — which means it gets included in iCloud backup, Google Photos upload, or whatever backup process runs on that phone.
AirDrop’s “Everyone for 10 minutes” mode, introduced specifically for situations like crowded family gatherings, creates a different risk: other people nearby can attempt to send you photos or files, and your name (or Apple device name) becomes briefly visible to anyone looking.
Shared albums
Google Photos Shared Albums and iCloud Shared Albums feel like a more considered approach. You create an album, invite specific people, and the photos stay in one place.
The privacy problem with shared albums is access management over time. People you invited years ago may still have link access. Someone who left the family group may still be in the shared album. Shared albums in iCloud let contributors add their own photos — so the album you created as a private archive may now contain photos added by others that you didn’t take and can’t fully control.
In Google Photos, when you share an album with a link (rather than by email), anyone with that link can access it — and links can be forwarded.
Cloud links
Sending a link to a Google Drive folder, iCloud shared album, or Dropbox folder is common when sharing many photos at once. A link can be forwarded to anyone. That’s usually fine when you trust everyone who has it — but family contexts often include mixed levels of tech sophistication and mixed levels of caution.
The person who asked for the link so they could print some photos may have also forwarded it to the family group text, which now has 22 people in it, some of whom you haven’t spoken to in three years.
What Holiday Photos Actually Reveal
The contents of holiday photos create specific privacy considerations beyond the photos themselves:
Location data. Most phones embed GPS coordinates in photo metadata. A photo taken at your parents’ home includes their address. A photo taken at a child’s school holiday performance includes the school’s location. This metadata survives in the file unless you strip it before sharing.
Home layout. Holiday photos are often taken indoors, showing home interiors: where valuables are displayed, the layout of the house, security equipment, and window locations. These details have been used by people planning burglaries, typically pulled from social media but potentially from any shared photo.
Children’s faces and routines. Holiday gatherings concentrate family photos of children in predictable ways — what they received as gifts, what the family’s routines are, what the child looks like now. Faces combined with school performance events and schedules create a profile that, if it reaches AI training datasets or facial recognition systems, is very hard to walk back.
Family structure and relationships. Who is and isn’t at the gathering, who is or isn’t in photos — this information is sensitive in some family situations (estranged relationships, custody arrangements, people fleeing domestic situations) even when it seems like ordinary holiday documentation.
The Persistent Metadata Problem
When you photograph someone and share the image, you are also sharing a file that contains structured data about:
- The exact time and date (accurate to the second)
- GPS coordinates (if location access was granted to the camera app)
- The make, model, and serial number of the device
- Camera settings: aperture, ISO, shutter speed
- In some cases, the face detection confidence score the camera computed
This metadata travels with the file unless explicitly stripped. Most sharing channels do not strip it. Google Photos and iCloud strip it from some shares and not others, depending on settings that most people have never reviewed.
Stripping EXIF metadata before sharing is a simple step that most people never take because they don’t know the metadata is there.
A Better Holiday Sharing Strategy
For immediate sharing at the gathering
AirDrop and Quick Share are still the cleanest options for device-to-device transfer. The file lands on the recipient’s device with no cloud intermediary. If you want to avoid the “Everyone for 10 minutes” mode’s exposure, use “Contacts Only” and have people add you to their contacts before the transfer.
For sharing with the broader family after
Instead of group chats or public cloud links, a private album in a service that requires recipients to authenticate (not just have a link) is significantly more controlled. Daftei’s file storage is designed for exactly this: you store files privately, encrypted at rest and in transit, and share them only with people who have authenticated access.
The alternative — a shared Google Photos link or a Dropbox folder — creates an access control problem that grows over time. A link sent in November is still valid next November unless you remember to revoke it.
For archiving
The family member who takes the official holiday photos and wants to preserve them for the long term should be storing them somewhere that:
- Is not AI-training-opt-in by default
- Does not use your photos to personalize ads (as Google recently updated its policy to potentially do when users opt into “Personal Intelligence” features)
- Gives you a clear path to deletion if you change your mind
The archive copy you keep should be yours — not a convenience feature of a platform whose business model is orthogonal to your interests.
Stripping Metadata Before Sharing
On iOS: Share the photo to your Files app, then use a shortcut or an app like Metapho to remove EXIF data before sharing the file.
On Android: Some Android launchers and gallery apps have a “Remove location” toggle in the share sheet. If yours doesn’t, apps like Scrambled Exif work before you share.
On desktop: Preview on Mac and Photos on Windows both allow you to export photos with location data removed.
For a family gathering, stripping metadata from every photo before sharing is impractical. A reasonable approach: strip it from photos you post anywhere semi-public, and store a metadata-intact copy privately for your own archive.
The Consent Problem Nobody Talks About
Holiday gatherings include people who did not consent to being photographed, including children who are old enough to have preferences but young enough that parents often override them, elderly relatives who may not understand what “shared to Google Photos” means, and people who may have reasons to not want their location, presence, or appearance documented.
None of the major sharing platforms has a mechanism for managing consent among people in the photos — only from the person who took the photo.
The practical implication: what you share broadly carries no consent signal for the people in the frame. What you archive privately gives you the ability to make sharing decisions later, with more context, rather than locking in broad sharing in the moment.
What to Actually Change This Holiday Season
Three concrete steps that take under ten minutes:
1. Review who’s still in your shared albums. Open Google Photos or iCloud Shared Albums and look at who has access. Remove anyone who shouldn’t still be there.
2. Check your group chat membership. If your family group text includes people you’ve added over the years and never removed, that is the list of people who will receive every photo you send this holiday season.
3. Pick one private archive destination. Decide before the gathering where your personal copies are going. Not your employer’s cloud, not a link anyone can forward, not the same shared family drive where last year’s photos already are.
Holiday photos are worth keeping. The default sharing methods just weren’t designed with that goal in mind.