Eventphoto.io
Wedding · Privacy · Who sees what

Are wedding photo sharing apps private?

Private to the room, not to the world: everyone who holds the event’s QR code, its six-character event code or its link can see the photos, and nobody else. An Eventphoto.io gallery is shared by design: guests see each other’s photos as they arrive, which is why they upload. It is not public: the page is never indexed by search engines, the host’s own link is separate and private, a PIN is on by default (4 to 6 digits, chosen when the event is created, can be switched off), the host can delete any photo and a guest can delete their own, and when the event expires, after 14 days on the free plan or 12 months on the paid plan, every file is deleted.

What it costs

  • Free: 20 photos per guest, kept 14 days from when you create the event
  • Paid: $19.99 (£15.99 in the UK) per event for unlimited photos and videos per guest, kept up to 12 months
  • One-time payment. No subscription and no fee per guest.

Who can open the gallery?

Anyone with the way in. The QR code on the table, the six-character event code typed at Eventphoto.io and the plain link all open the same page, and that page is the gallery: the photos everyone has uploaded so far, newest first, plus the upload button. No app, no account, no email address; the only thing a guest types is a name, so the photos carry one. If the event has a PIN, the page asks for it the first time a phone opens it and remembers it on that phone for a week.

The host holds a second, private link, sent in the confirmation email. It opens the same gallery but signs that browser in as the host, which adds the controls: delete any photo, download everything. Nothing about the host link is printed on a sign or shown to a guest. A guest who turns out to be the host on another phone taps “Are you the host?” and types a one-time code emailed to the host address.

What this means in plain terms: the gallery is as private as the code and the PIN. Whoever you hand them to, on a table card or in a group chat, can see every photo in it, and so can anyone they forward them to. It is the right level for a wedding, where the people in the room are the people who should see the room, and it is why there is a PIN for the cases where the card might walk out of the venue.

Can I lock it with a PIN?

It is locked by default. When you create an event the PIN is switched on, you choose it, and it has to be 4 to 6 digits; a guest-created quick event gets a random one. You can switch it off at creation if the venue is private enough that the code alone is fine. The PIN appears in your confirmation email, and it has to go on the sign next to the QR code, or be said from the microphone, because a guest who scans and meets a PIN prompt otherwise has to come and ask.

A guest types the PIN once per phone, and the phone opens the gallery without asking again for a week. Changing or removing the PIN later is done from the dashboard, which means signing in with a one-time code sent to the host address; the host link on its own does not change it. A found link without the PIN opens nothing, which is the whole purpose: a card left in a taxi is a square of ink, not an album.

Is it searchable on Google?

No. Every event page tells search engines not to index it and not to follow its links, and the site’s robots file disallows the whole event area on top of that, so neither Google nor Bing nor an answer engine lists a gallery, a photo or an event name. There is no public directory of events anywhere on Eventphoto.io; the address of a gallery contains its six-character code and nothing else, and nothing links to it except the things you print and send.

If a guest pastes the link into a chat, the preview the messaging app shows is a card with the event’s name and one line of text, never a photo from the gallery. The photos themselves are served from storage through short-lived signed addresses, not from a public folder, so a picture cannot be reached by guessing a file name.

Can I remove a photo?

The host can remove any photo or video, at any time: the trash icon on its tile, the same in the full-size view, or Select to pick several and delete them together. A deleted file is removed from the gallery and from storage, and the next Download all packs a fresh archive without it. A guest can delete their own uploads, from the phone they uploaded from, and nobody else’s.

There is no approval queue: photos appear as they are uploaded. For a wedding that is what you want, because guests upload for the pleasure of seeing their pictures land next to everyone else’s, and a queue would kill that in the first hour. For an event where every image has to be checked before anyone sees it, this is not the right tool, and we would rather say so here than on the night.

What happens to the photos when the event ends?

They are deleted. A free event expires 14 days after it was created, a paid one 12 months after the upgrade, and the day after that date the event, every file in it and the ZIP archive are removed from storage. It is permanent on both plans, and it is a privacy feature as much as a storage one: nothing from your wedding sits on a server indefinitely waiting to be found.

The host gets a reminder email two days before and another the day before, so the sequence is: download everything with Download all, keep the ZIP, let the event expire. Upgrading a free event, $19.99 (£15.99 in the UK) once, restarts the clock to 12 months from the moment of the upgrade; the download guide covers the ZIP and Save to this phone step by step. Files are stored with Supabase in London (UK); the privacy policy has the rest.

How does this compare with a public album or a hashtag?

A wedding hashtag is the opposite model. Only public posts count. Instagram’s own line: “Place and hashtag pages on Instagram include public photos and videos that were shared with the corresponding location or hashtag.” A guest whose posts are not public can tag all night and nothing shows on the tag page. Meanwhile a guest with a public account is publishing your wedding to anyone who searches the tag, and you never hold a file, only other people’s posts (Instagram’s own help page, read in October 2026).

A shared Google Photos album sits in between. The link is the key. Anyone who gets it can view and add unless Collaborate is off, and turning link sharing off and on resets the link, so the old one stops working for everyone. (Google’s album-controls page, read in October 2026.) Adding to the album takes a Google Account, and there is no PIN. An Eventphoto.io gallery asks for no account, is never indexed, is behind a PIN by default, and deletes itself at the end. The methods comparison puts all seven ways side by side.

Privacy questions, answered

Can other guests see my photos?

Yes, that is the point of the gallery: every photo a guest uploads appears in the shared gallery for everyone who has opened the event with its QR code, its event code or its link, and the PIN if there is one. It is a shared album for the people at the wedding, not a private upload box. A guest who would rather not share a picture simply does not upload it.

Can guests download the photos?

No. Guests can look, including at full size. The Download all button is on the page for everyone, but it only opens “Are you the host?” and asks for a one-time code emailed to the host address; without it there is no ZIP and no save-to-phone. If the couple wants guests to have the full set, the host downloads it and shares it as they see fit.

Does the host see who uploaded what?

Each photo shows the name the guest typed before uploading, in the gallery, for everyone who can see the gallery. The name is not written into the files of the ZIP download. There is no account behind the name and nothing else is asked of a guest: no email, no phone number, no login.

Is there an approval step before a photo appears?

No. Photos appear in the gallery as they are uploaded; there is no queue to approve them from. What there is: the host can delete any photo the moment it appears, from its tile, from the full-size view or several at once, and a guest can delete their own. A host who wants to screen uploads before anyone sees them should know that this is not that.

Where are the files stored?

With Supabase, in London (UK). Payments run through Stripe and no card is asked for on the free plan. The privacy policy has the details, and the about page lists the company behind Eventphoto.io.

What happens to the photos when the event expires?

They are deleted, with the ZIP, the day after the event expires: 14 days after creation on the free plan, 12 months after the upgrade on the paid plan. Reminder emails go to the host two days before and the day before. Download everything first; the deletion is permanent.

Related pages