Privacy
Your event is not our content.
Relive exists so a night can be photographed by the people who were in it. That only works if everyone trusts where those photographs end up. This page says exactly what we store, who can reach it, and how to make it all disappear.
Last updated
The short version
Photos taken at your event belong to you and your guests. They are not public, not searchable, and not used to advertise anything. We do not sell data, we do not run ad networks, and we do not train anything on your photographs.
What a guest gives us
A guest joins by opening a link or scanning a QR. They are not asked for an account, an email address or a phone number. What we keep is:
- The name they type. Whatever they enter — a first name, a nickname — so their photos can be labelled in the album.
- A random device token. A string generated in their browser and stored on their own device. It is how we recognise the same phone returning to the same event. It is not tied to a person and it tells us nothing about them.
- The photographs they take, and the time each was taken.
- A push subscription, but only if they tap “Notify me” and their browser then grants permission. It is used for one notification: the album is open.
We do not collect location, contacts, or the rest of the camera roll. The camera is opened for one frame at a time and nothing else on the device is read.
What a host gives us
A host has an account, so we hold the name and email address it was created with, the events created, and a record of payment — the amount, the method and the reference. Card and wallet details are handled by the payment provider; they never reach our servers and we never store them.
Who can see the photographs
An event album lives at a private, unguessable link. It is visible to the host and to the guests who joined that event on that device. It is marked no-index, so search engines are instructed not to list it, and there is no public feed anywhere in the product.
While the event is running, a guest sees only their own frames. When it ends, everyone who took part sees everything. That is a deliberate design decision, not an accident of permissions.
Anyone you give the link to can open the invite screen. Treat it the way you would treat the address of the venue: share it with the people you want there.
Where it is kept, and for how long
Photographs are stored on object storage, and the database holds the records that tie an album together. Albums are kept indefinitely — storage is part of the one-time price, and the point of the product is that you can come back to the night years later.
If you would rather not keep it: a host can delete an event and its photographs from the app, and that removes the originals, every generated size, and the album itself. Deletion is not reversible.
What lives on the guest’s own phone
The guest PWA stores a small amount of data in the browser, on the device, and never sends it anywhere: which events this phone has joined, the device token for each, the number of shots left, and any photograph that has been taken but not yet uploaded. Clearing the browser’s site data removes all of it — including the identity, which is why a guest who clears it will be asked for their name again.
We do not use advertising cookies or third-party analytics trackers on the guest screens.
Children
Relive is intended for adults organising and attending events. We do not knowingly create host accounts for children under 13. Children do appear in event photographs, as they do at any family wedding; those photographs are governed by the same private album rules as every other frame, and a host can remove any of them.
Your rights
You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to hello@relive.cam and we will reply to you, not to a ticket number.
Changes
If this policy changes in a way that affects what we do with your photographs, we will say so on this page and update the date at the top.
Something here unclear? Write to hello@relive.cam and a person will answer. Or go back to the home page.