ReliveWeddings
Menu
How it worksPricingSignature demoSign inCreate your wedding
Service providers

Who helps us provide Relive

Relive uses a small number of carefully chosen providers to run the wedding service. This register explains what each provider does, the information it may handle, and where that processing may take place.

A deliberately short list

A subprocessor may process customer-controlled wedding data for us. For wider transparency, this page also names providers that handle visitor, sign-in or payment information. Their role is described below.

Currently included

  • AWS · wedding-data subprocessor
  • Cloudflare · status-service processor
  • Stripe · payment service provider
  • Google · optional sign-in provider

How provider changes work

Before a material new or replacement subprocessor begins handling personal data, we assess its security, privacy terms, deletion support, incident duties, processing locations, and transfer safeguards. We update this page before the change takes effect.

We normally give active customers at least 30 days' advance notice by email. A shorter period may be necessary for an urgent security, legal, or service-continuity reason; if so, we explain why and give as much notice as reasonably possible.

Questions or objections

Email security@relive.wedding before the stated change date with the wedding and the data-protection concern. We will consider a reasonable objection in good faith and explain the available safeguard, alternative, or route to export and end the affected service.

This register forms part of the transparency provided with our customer data processing terms. The privacy notice explains Relive's wider handling of account, wedding, guest, and operational information.