How Relive processes wedding data for you
These terms form part of the customer agreement when a customer decides why and how personal data in their wedding is used and Relive processes it to provide the service.
Version 2026-09-26
Customer as controller. Relive as processor.
The customer remains responsible for their purpose and lawful basis. Relive follows documented instructions, protects the data, assists with rights and incidents, and deletes or returns it as agreed.
1. Parties and scope
The controller is the customer identified by the Relive account or order. The processor is Christopher Duke, a sole trader trading as Relive Group, at 14 Berrisford Avenue, Sheffield, S21 4LJ. These terms cover guest upload, gallery, guest-information, moderation, export, support, retention, and deletion functions.
2. Processing details
Processing lasts for the service term, closure/recovery period, and documented deletion process. Its purpose is to collect, secure, organise, display, moderate, export, support, retain, and delete wedding data. People may include guests, the couple, invited admins, uploaders, and people appearing in media. Data may include names, contact details, event details, photos, videos, guestbook messages and recordings, transcripts, captions, reactions, access records, meal choices, and dietary or allergy information, song requests, optional requester names, and anonymous vote records when the customer enables those features.
3. Documented instructions
Relive processes wedding data only on instructions expressed through the agreement, product settings, authorised account actions, support requests, and agreed retention or deletion choices, unless UK law requires otherwise. We will tell the customer before legally required processing unless the law prohibits it, and will flag an instruction we reasonably believe infringes data-protection law.
4. Confidentiality and security
People authorised to process wedding data are bound by confidentiality. Relive maintains measures appropriate to the risk, including encryption in transit and at rest, restricted access, secure authentication, access records, retention and deletion controls, and arrangements to respond to security incidents. Controls evolve with risk and the service.
5. Subprocessors
The customer gives general authorisation for the subprocessors on Relive's published register. Relive will assess providers, impose equivalent data-protection duties, remain responsible as required by law, and give reasonable advance notice of a material addition or replacement with a route for a reasonable data-protection objection. Amazon Web Services currently provides the wedding-data infrastructure. Cloudflare runs the separate public status page but is not intended to receive customer-controlled wedding data. Stripe provides payment services and has both processor and independent-controller responsibilities as described in the register.
6. Rights and compliance assistance
Taking account of the processing and information available, Relive will reasonably assist with access, correction, erasure, restriction, objection, and portability requests, as well as security duties, breach notifications, impact assessments, regulator consultation, and information needed to demonstrate compliance. The customer remains responsible for verifying requesters and making controller decisions.
7. Personal data breaches
Relive will notify the customer without undue delay after becoming aware of a personal data breach affecting customer-controlled wedding data. Available information will cover the nature of the incident, affected people and data, likely consequences, mitigation, and a contact point, and may be provided in phases. The customer decides whether controller notification is required, with reasonable assistance from Relive.
8. Return, deletion, and recovery
Relive provides configured download and export tools during the service. At the end of the agreed hosting and recovery period, or after a valid deletion instruction, Relive will delete wedding data and copies through the deletion process, unless law requires narrow retention. Recovery controls must not restore data that was already validly deleted. Any legally retained data is isolated, purpose-limited, and removed when no longer required.
9. Audits and information
Relive will provide information reasonably necessary to demonstrate compliance and permit proportionate audits or inspections on reasonable notice. Existing control evidence may be used first. Audits must protect security, confidentiality, and other customers, avoid unreasonable disruption, and be limited to relevant processing. Relive will cooperate with the ICO where legally required.
10. International transfers
Our primary hosting is in the United Kingdom, while global delivery and provider support may involve processing elsewhere. Relive will not initiate a restricted transfer without a permitted UK transfer mechanism and any required data-protection test or supplementary measures. Current provider, location, and safeguard details are maintained in the subprocessor register and privacy notice.
11. Customer duties
The customer must give required privacy information, have a lawful basis, collect only necessary data, keep access appropriate, and provide lawful instructions. Special-category dietary or allergy information must only be used with a valid Article 9 condition, such as properly recorded explicit consent where appropriate. The product records the customer's confirmation that the information came from the guest, or their parent or guardian, for the wedding hospitality purpose; the customer remains responsible for the validity of that confirmation and for any onward disclosure to the venue.
12. Priority and ending
These terms take priority over conflicting customer terms about processor obligations. They end when Relive has returned or deleted the covered data, except for provisions that must continue for confidentiality, legally retained evidence, or liability. Nothing removes either party's direct duties under data-protection law.
Questions or audit requests
Contact security@relive.wedding with the account, wedding, and requested information. Please do not send guest personal data unless it is necessary.