Privacy

GuestCam collects photos and videos from guests at an event and shows them on a screen and in one album. This page says exactly what is stored, who can see it, and when it is deleted. If anything here is unclear, email [email protected].

What is stored

• The photos and videos guests send, along with the time the photo was taken and its file size.
• The name a guest types when they join an event.
• A guest's email address, only when the organiser requires Google sign-in. If the event allows a first name instead, no email is stored.
• Face groupings, only for an album whose host switched on finding people by face — see below.
• A record of every approval, hide and delete, with the account that did it. This is what lets a school show that a person checked each photo.
• Technical notes when an upload fails — the file name, size and the error — so failures can be fixed rather than silently lost.
• Account details for organisers: name and email address, from signing in with Google.
• When you send an enquiry or a booking: what you type, plus the internet (IP) address and the type of device and browser it came from. These are used only to spot duplicate or fake requests, such as one person asking for several free trials, and are kept with the enquiry or booking.

What is never done

• No facial recognition unless the host switches it on — see Finding people by face — and never on school events. Faces are never given names.
• Photos are never sold, shared with advertisers, or used to train anything.
• No advertising or analytics trackers. The site uses a sign-in cookie for organisers, and your browser remembers your event on your own device. Cloudflare, which sits in front of the site, may set a cookie to block attacks.

Finding people by face

A host can switch this on for their own event's album. It is off unless they do, and it is never used on a school event. When it is on:

• GuestCam's own server finds the faces in each approved photo and turns each one into a list of numbers, so faces that look alike can be grouped together. The numbers cannot be turned back into a picture, and no names are attached.
• No photo is sent to any other company or service to do this.
• Guests are told on the join screen. In the event's gallery and the album, anyone who can see the photos can tap a face to see the ones that person is in.
• Any guest can take their own face out of it from the album, and the host cannot undo that. The host can also hide anyone.
• The face data is deleted with the photos, or straight away if the host switches it off.

Who can see the photos

The organiser of the event, anyone they add to approve photos, and anyone they give the album link to. Photos waiting for approval are seen only by the organiser and their approvers. A guest can always see and delete their own photos. The album link can only be used to view and download — it can never be used to upload.

How long it is kept

Everything from an event is permanently deleted one month after the event closes — photos, videos, the album and any downloads. An event with no closing date is deleted 90 days after it is created. If an organiser asks me to keep an event for longer, I can, and I will tell them.

Download what you want to keep before then. Every event has a ZIP download, and organisers can back up to their own Google Drive.

Where it is kept

Photos are stored on my own server in Orange, New South Wales. To make them load quickly, they are delivered through Cloudflare's network, which means copies are held temporarily on servers in other countries while people are viewing them. Backups stay in Australia.

Other services GuestCam uses

• Google sign-in, when an event requires it, or when an organiser signs in. Google provides the person's name, email address and an account identifier — nothing else.
• Google Drive, only if an organiser chooses to back an event up to their own Drive, and only for the files they send.
• Email for notices such as an album link or an alert, sent through Google's mail servers.

Photos of children

At a school event, the school decides who may take part, whether guests must sign in, and who approves photos. Approval cannot be switched off for school events. If a family asks for a photo to be removed, the school can hide or delete it immediately, or email me and I will.

Your choices

• Remove a photo: guests can delete their own; organisers can delete any photo in their event.
• Ask what is stored about you, or ask for it to be deleted: email [email protected] and I will answer within a few days.
• Delete an entire event: the organiser can do this at any time, and every photo goes with it.

How the photos are protected

The security page explains, in plain English, how photos are kept away from people who should not see them — including the extra protection for schools.

If something goes wrong

If photos were ever exposed to someone who should not have seen them, I will tell the affected organisers directly and promptly, and explain what happened.

Who runs GuestCam

GuestCam is built and run by one person in Orange, New South Wales, Australia. Contact: [email protected].