how-to

How to Share Photos Privately: A No-Hype Practical Guide

Permanent public links, no-expiry albums, and EXIF metadata make photo sharing a privacy risk by default. Here's how to share files safely for each common situation.

Every time you share a photo using a cloud storage link, you’re making a decision that may be harder to reverse than you expect. Most photo sharing links are permanent by default. Many are accessible to anyone who has the URL, not just the people you sent it to. Most preserve the metadata embedded in the image file — including the GPS coordinates of where the photo was taken.

Photo sharing is genuinely useful. The goal isn’t to never share a photo. The goal is to understand what each sharing mechanism actually does — and choose the right one for what you’re trying to accomplish.

This guide covers the practical mechanics of how major sharing approaches work, their failure modes, and which situations each is appropriate for.


When a cloud storage or photo service gives you a sharing link, that link is typically one of three things:

Anyone with the link can view. The most common default. The link grants access to whoever has it. There’s no authentication — no login, no invitation acceptance. If the recipient forwards that link to someone else, the new person can also view the content. If the link appears in a screenshot, an email thread, or a group chat that gets shared further, every person in that chain gains access. Most Google Drive and Dropbox shares work this way by default.

View with authentication required. The link requires the recipient to log into an account — either their own Google, Apple, or Dropbox account, or an account with the sharing service. This adds a meaningful layer: you can see who viewed the content, and you can revoke access for specific people. Apple iCloud shared albums work this way. Google Drive folder sharing to specific email addresses works this way.

Time-limited or expiring links. The link becomes invalid after a set period. This is available on Dropbox (as a configurable option) and on some other services, but it is not a universal default and it’s often a paid-tier feature. After the link expires, even someone who bookmarked it can’t use it.

Password-protected links. The recipient needs both the URL and a separately communicated password to access the content. This adds friction that limits casual forwarding — someone would need to share both the link and the password. Password protection is not the same as encryption; the content may still be decryptable by the service itself.

Understanding which of these you’re creating before you create it prevents the most common photo sharing privacy mistakes.


The EXIF Metadata Problem

Before discussing sharing mechanisms, there’s a separate issue that applies regardless of how you share: the metadata embedded in image files.

Every photo taken with a smartphone contains EXIF data — a block of technical information that includes, depending on your phone’s settings, the GPS coordinates of where the photo was taken, the exact timestamp, the device model, and sometimes the camera settings used.

When you share a photo file directly — as an email attachment, a direct message file, or via a cloud service that doesn’t strip metadata — that EXIF data travels with the file. The recipient can extract it using any free EXIF viewer. Your home address, if the photo was taken at home, is readable by anyone who receives the original file.

Services that strip EXIF on upload: Most social media platforms strip or alter EXIF data when photos are uploaded, including Instagram, Twitter/X, and Facebook. This is good for metadata privacy but the trade-off is that the platform itself processes and retains the original.

Services that preserve EXIF intact: Google Drive, Dropbox, and most generic cloud storage services preserve files exactly as uploaded, including all metadata. If you share a Drive link to a photo taken at your home, the GPS coordinates in the file are accessible to anyone who opens it.

Sharing services that preserve EXIF on direct file sharing: WhatsApp when photos are sent as files (rather than compressed images). Telegram when files are sent in file mode. Email attachments. Any link to the original file rather than a processed thumbnail.

If you want to share a photo without location metadata, the cleanest approach is to strip the EXIF data before sharing. On iPhone, the Photos app has a native option: when sharing, tap “Options” at the top and toggle off “Location.” On Android, the default Camera app doesn’t offer this — you’ll need to use a dedicated EXIF editor app. On desktop, most image editing apps can save without metadata.


Sharing Situations and What to Use

Sharing one or a few photos with a specific person

Best approach: direct message via an E2EE app.

Sending photos through Signal or through WhatsApp (in standard image mode, not file mode) to a specific person gives you end-to-end encryption in transit, and the photos go directly to that person’s device rather than to a cloud service that the recipient can link and re-share.

The limitation is that the recipient has the photo on their device and can screenshot, copy, and share it from there. This is true of all sharing mechanisms — you cannot prevent a determined recipient from capturing what they can see. But for one-to-one trusted sharing, direct message via encrypted messaging is the simplest option.

What to avoid: Google Drive or Dropbox “anyone with link” shares for personal photos sent to one person. The link is valid indefinitely, can be forwarded easily, and goes to a server you have less control over.

Sharing an album with a few trusted people

Best approach: invite-based sharing with a service that requires recipient login.

Most dedicated photo services — Apple iCloud Shared Albums, Google Photos albums shared to specific accounts — allow you to invite specific people by email or phone number. The recipient has to accept the invitation and have an account. You can see the list of people with access and remove individuals.

The tradeoff is that the recipient has an account with the same service, which means they have the full feature access that comes with that. On Apple Shared Albums, recipients can add their own photos to the album. On Google Photos, invited viewers may see AI-generated summaries depending on your settings.

For an invite-only photo album with family or close friends, invite-based sharing within a trusted service is the right approach — more controlled than “anyone with link” and more convenient than managing encryption yourself.

What to avoid: Sharing albums publicly or via “anyone with link” to people who will share the link further.

Sharing photos temporarily — for an event, a trip, a project

Best approach: password-protected link with expiration.

If you need to share a set of photos with a group for a defined period — photos from a wedding, a team event, a trip — a link with both a password and an expiration date gives you the most control.

Dropbox allows link-level passwords and expiration dates on paid plans. Some dedicated photo sharing services offer these options. After the expiration date, the link stops working. The password limits casual forwarding.

The content is still on the service’s servers, decryptable by the service, and accessible to anyone who has both the link and the password during the active period. This isn’t a privacy solution for highly sensitive content — it’s a practical access management approach for temporary sharing with a known group.

After the sharing period ends: delete the album or shared folder if it’s no longer needed. Most services retain content indefinitely unless you explicitly delete it.

Best approach: end-to-end encrypted file transfer.

For documents and photos that you’d categorize as sensitive — medical images, identity documents, legal evidence, anything where you need assurance that the content is not accessible to the service provider — generic cloud storage links are the wrong tool.

Options include:

  • Signal: end-to-end encrypted file transfer to a specific recipient. Files up to 100MB can be sent directly. This is the highest-assurance option for one-to-one sensitive file sharing.
  • ProtonDrive shared folders: Proton offers zero-knowledge encryption where Proton doesn’t hold the keys, and shared folders can be accessed by recipients without a Proton account (though with somewhat reduced guarantee levels for those without accounts).
  • pCloud Crypto: pCloud’s zero-knowledge encrypted folder with client-side key management. Sharing requires the recipient to have a pCloud account and the shared folder key.
  • Tresorit: designed specifically for secure file sharing, with end-to-end encryption and specific controls for professional document sharing. More expensive, targeted at professional use.

For sharing with professionals — your doctor, lawyer, accountant, or an insurance adjuster — the secure file transfer approach is worth the extra setup, particularly if the files contain health information, identity documents, or financial records.

Sharing photos with a large group where you don’t know everyone personally

Honest answer: this is risky by design, and no sharing mechanism fully resolves it.

Event photos shared with a conference attendee list, a sports team’s season photos, neighborhood association archives — any situation where you’re sharing with a large group of people you don’t all know personally creates risks that technical controls only partially address.

Members of the group can download photos and share them further. People photographed in group photos may not have consented to being shared with the broader group. Metadata in files may reveal information about individuals who are photographed.

For this use case, the most reasonable approach is:

  1. Use a service that requires individual account authentication (not “anyone with link”).
  2. Set explicit download controls where the service allows it.
  3. Strip metadata from photos before sharing.
  4. Communicate clearly to members what they should and shouldn’t do with the photos.
  5. Set a time limit for access and remove the album when the event’s purpose has passed.

This isn’t a guarantee — it’s risk reduction. If you have a large group of people who all need access to photos, some level of downstream sharing is likely regardless of what controls you set.


The Screenshot Problem

Every sharing mechanism has the same fundamental limitation: a determined recipient can always screenshot or photograph the content they can see.

No encryption prevents a screenshot. No expiring link prevents someone from downloading a photo before it expires. No watermark prevents someone from cropping it out. No “view only, no download” mode prevents a screen recording.

This is why the strongest privacy posture for sensitive content is controlling who sees it in the first place, not relying on technical restrictions on what recipients do with it once they have access. Technical controls reduce casual oversharing. They don’t prevent intentional re-sharing by a recipient who wants to.

The realistic question for any photo you’re sharing is: who am I sharing this with, do I trust them with the content independently of what technical restrictions I’ve set, and am I comfortable with the possibility that it could travel further than I intend?


Reviewing What You’ve Already Shared

The photos you’ve already shared are worth auditing, not just future ones.

On Google Photos, Settings → Shared Albums shows all albums you’ve created with sharing enabled. Check whether any are set to “Anyone with the link” rather than specific people. Review whether albums you created for temporary purposes are still active.

On Dropbox, the “Links” section shows all shared links you’ve created and their settings. Expired links appear here for reference. Any link still active with no expiration date is still working.

On iCloud, Shared Albums in the Photos app shows your active shared albums and who has access.

Regularly reviewing and cleaning up active shared links and albums is a straightforward practice that limits your ongoing exposure. A photo album from three years ago that’s still accessible via a link you shared in a group chat is a data point you’d probably prefer to control.


What Happens to Files After You Stop Sharing

Revoking a sharing link or deleting a shared album typically removes access for recipients going forward. It does not delete any copies that recipients may have already downloaded.

If you shared a Google Drive link to a folder and then remove the link, the photos are no longer accessible via that link. Any person who downloaded a copy while the link was active has their own copy — in their Google Drive, on their device, or wherever they saved it.

This is the right mental model for shared content: sharing is more like making a copy than lending something. Revoking access stops future access; it doesn’t retrieve copies that were made.

For content you’re truly trying to share on a temporary basis — a photo set for a short-term purpose where you’d like the content to essentially disappear afterward — Services like daftei let you store and share files with the expectation that the content is yours and persists under your control. Content that exists only in your own private storage and is shared only as needed through explicit sharing acts is easier to keep under control than content distributed via open links across multiple services.


A Quick Reference

SituationRecommended Approach
One photo to one trusted personEncrypted direct message (Signal)
Small album with family/friendsInvite-based sharing, login required
Temporary event photosPassword-protected link with expiration
Sensitive documents or medical photosE2EE file transfer (Signal, ProtonDrive)
Large group access, unknown individualsAuthenticated access only, time-limited

The right approach is rarely “use the default link” and almost always slightly more deliberate than whatever the sharing button suggests by default.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts