Built for private wedding memories

Who provides Relive

Relive is provided by Christopher Duke, a sole trader trading as Relive Group. The public correspondence address is available by contacting security@relive.wedding.

Who is responsible for personal data

The customer normally decides why and how wedding content, guest uploads, meal choices, and guest information are used, so they normally act as controller for that event data. Relive processes it to provide the service. Christopher Duke, trading as Relive Group, separately controls account, authentication, security, safety-report and review records, access records, support, and billing records.

What information is collected

Where Google sign-in is available and you choose to use it, we receive your name, email address and a Google account identifier to create or connect your account. We do not request access to your Gmail, contacts, photographs or files, and do not retain Google access or refresh tokens. Google handles its own sign-in service under its privacy policy.

The service stores customer account details, event settings, guest uploads, captions, guestbook messages, voice and video recordings and any requested transcripts, optional guest names, guest information entered by the customer, including RSVP contact emails, attendance, table and meal choices, optional dietary or allergy details, song titles and artists requested for the DJ, optional requester names, invitation and reminder delivery status, upload/reaction/vote metadata, and operational records needed to run the service.

Why it is used

Where automatic Guestbook transcription is enabled, recording guests can choose to have Amazon Transcribe turn their voice or video recording into text and captions. These are labelled as automatic, may contain mistakes, and follow the recording's event-access, moderation and deletion settings. Choosing not to transcribe does not prevent posting a recording.

Information is used to provide the event gallery, protect QR access, process uploads, prepare downloads, show guest information when enabled, collect private RSVP responses, send account, invitation, and reminder emails, combine duplicate song requests into anonymous votes, provide the private DJ queue, moderate content, and support the customer when something goes wrong.

Account and service processing is generally necessary to provide the requested service. Proportionate security, abuse-prevention, and audit processing relies on legitimate interests. Billing and accounting records may also be retained to meet legal obligations. Wedding customers remain responsible for the lawful basis applying to the guest information they choose to enter.

Dietary and allergy information

Dietary or allergy details can reveal health, religion, or belief information and may receive extra legal protection. The organiser must confirm that the details came from the guest, or their parent or guardian, for managing food and hospitality at that wedding. Relive records that confirmation and keeps these details inside the organiser workspace and protected venue service plan. Guest-facing Find Your Place pages receive only the name, table and meal choices selected by the organiser.

Organisers should enter only what the venue needs, correct or remove it when asked, and securely share the service plan only with people who need it. The customer remains responsible for identifying the lawful basis and special-category condition that applies to their wedding.

Who can see event content

Customers and invited event admins can manage event content. An invited party can use its private RSVP link to see and change only that party's response. Guests can see other guest-facing pages only where the customer has enabled access, usually through the private QR code. Guestbook entries are shared with everyone who has access to the event. Authorised staff may access information when needed to provide support, investigate safety concerns or protect the service.

Deletion and retention

Hosting lasts for 30 days, 12 months, or 24 months after the wedding date, depending on the chosen package, plus any extension. Customers can download original files where available and delete uploads from the event console. We warn 14 and 3 days before expiry, close guest access at expiry, allow a 30-day recovery/export window, and then delete the wedding data and stored copies, subject to the limited retention described below.

Guest photo, video, and guestbook contributions open seven days before the wedding date. Date changes can be made directly before opening; afterwards our support team reviews requests while the existing date remains active. Approved requests update the wedding and hosting dates.

Photo safety checks and reports

Where automatic photo screening is enabled, new photos are temporarily hidden while Amazon Rekognition checks a processed copy for potentially harmful visual content, such as explicit sexual content or violence. A clear result can allow publication; a concern or an unavailable check keeps the photo hidden for review. This photo check does not scan videos, identify people, determine consent or establish whether content is lawful. Automated checks can miss problems or flag harmless photographs.

Safety reports are handled by Relive. You can report a concern even if a photo has passed an automated check. Please provide only the details needed to locate and understand the concern; do not send copies of suspected illegal material. A clear visual check cannot settle privacy, consent, harassment or child-safety concerns, which need human consideration.

Some visual-content reports may be resolved automatically after a clear photo check. Privacy, consent, harassment and child-safety concerns require human review. You can ask us to reconsider an automated result.

Authorised safety staff may view reported content to investigate a concern, and that access is recorded. This does not make hidden content visible to guests. Safety checks support our legitimate interests in protecting guests and preventing misuse of the service.

Safety records include the report, relevant upload identifiers, screening results, decisions and access history. They are kept separately from the guest gallery with restricted access. Retention depends on resolving the concern, handling challenges, preventing repeat abuse and any applicable legal preservation requirement; deleting gallery content does not necessarily delete these records at the same time.

To question a restriction or automated result, request a human review, or object to this processing, contact security@relive.wedding with the wedding and item or case reference if you have one. A reference is helpful, not required. See our service-provider information for AWS processing details. Reports are not monitored continuously; call 999 if someone is in immediate danger.

Cookies and browser storage

The product uses cookies and browser storage for sign-in sessions, QR guest access, upload progress, duplicate-upload prevention, reactions, and remembering useful event state. See the full cookies and browser storage inventory and manage privacy choices there. We also use anonymous aggregate service measurements, which you can switch off on that page.

Service providers and international processing

Amazon Web Services provides hosting, storage, processing and email delivery. Our primary hosting is in the United Kingdom. AWS services may use global delivery locations and support providers; restricted transfers must use an applicable UK transfer mechanism and any required supplementary measures. Current details are maintained in our customer data processing terms and service-provider and subprocessor register. Cloudflare runs the separate public status service but does not receive private wedding content. Stripe provides checkout, receipts, refunds, and dispute handling. We do not use third-party advertising trackers.

Your choices and rights

Depending on the circumstances, people may ask for access, correction, deletion, restriction, objection, or portability. Customers can download account data and submit tracked requests from their account. Guests can contact the wedding organiser or support. Identity and event ownership may need to be confirmed before a request is completed.

Where processing relies on your consent, you can withdraw it at any time by contacting us. This does not affect processing that was lawful before you withdrew consent. You can also object to processing based on legitimate interests; we will consider your circumstances and explain our response.

Questions and complaints

Contact security@relive.wedding for privacy questions, data-rights requests, or security concerns. People also have the right to complain to the UK Information Commissioner's Office. You can find guidance and raise a complaint at ico.org.uk.