Essential
Private access stays private
Secure sessions and QR access are needed to provide the service you ask for.
Cookies and privacy
Cookies & browser storage
Relive remembers only what helps keep your wedding private, your uploads recoverable and your experience effortless. We do not use advertising cookies or track you across other websites.
Last reviewed 26 September 2026
Respectful
No advertising profiles
No marketing pixels, cross-site tracking or sale of browser activity.
In your hands
Helpful details are optional
You can stop remembered preferences or anonymous service analytics at any time.
Your choice
Privacy choices
Keep useful details effortless and decide whether this device contributes anonymous service insight.
Helpful preferencesRemembers a guest name and data-saving gallery choice on this device.
Anonymous service analyticsContributes aggregate visits, journey outcomes and performance without a visitor profile.
What we store
A clear, practical inventory
“Browser storage” includes local storage, session storage and the protected device database used for upload recovery.
Private report status
A random security reference remembers this browser’s photo reports, prevents duplicate submissions and lets you see whether a report has been reviewed. It does not contain your report or identity and is not used for advertising.
Relive · Secure, HTTP-only cookie__Host-relive_safety_reporter
Kept forUp to 180 days
Google sign-in security
Where Google sign-in is available, protects the sign-in or account confirmation you choose to start. These cookies contain random references, not Google tokens.
Relive · Secure cookies__Host-relive_google_flow, __Host-relive_google_pending, __Host-relive_google_reauth
Kept forUp to 10 minutes
Account session
Keeps a couple or wedding-team member securely signed in.
Relive · Secure cookiewedding_customer_session
Kept forUp to 14 days
Wedding setup
Carries the new wedding safely between the setup steps you requested.
Relive · Secure cookiewedding_event_setup
Kept for15 minutes
Private guest access
Remembers that this browser used a valid wedding QR code. Rotating the QR code invalidates old access.
Relive · Secure cookiewedding_guest_access_<wedding>
Kept forUp to 60 days
Song request voting
Uses a random, event-specific identifier to combine duplicate requests and prevent repeated votes from this browser.
Relive · Secure cookierelive_song_voter_<wedding>
Kept forUp to 400 days or until cleared
Account and form security
Protects sign-in, account recovery and safety report forms against unauthorised submissions.
Relive · Secure, HTTP-only cookie__Host-relive_unauth_account_csrf
Kept forUp to 30 minutes
Upload recovery
Keeps an interrupted photo or video upload available so it can continue after a refresh.
Relive · Local storage and protected device databaserelive-upload-recovery:v1:<wedding>, relive-upload-files
Kept forUsually 24 hours or less
Guest and download controls
Supports duplicate prevention, upload limits, deletion rights, reactions, guestbook editing and download progress.
Relive · Local and session storagewedding-photo-*, guestbook-edits-v1:<wedding>, wedding-download-export:<wedding>, wedding-auto-download:<wedding>
Kept forUntil the task expires or is cleared
Helpful preferences
Remembers an optional guest name, data-saving display choice and whether this device should remember them.
Relive · Local storagewedding-photo-uploader-name, wedding-photo-low-data-mode, relive:browser-preferences:v1
Kept forUntil cleared or switched off
Anonymous service analytics choice
Remembers if this device should contribute aggregate visits, journey outcomes and performance measurements.
Relive · Local storage and first-party preference cookierelive:service-analytics:v1, relive_service_analytics
Kept forUntil cleared or switched off
Why essential storage is always on
Without it, Relive could not keep you signed in, recognise valid private guest access, resume an upload or preserve controls such as deleting something you contributed. It is used only for those service and security purposes.
Payments
If you choose to buy a package, the checkout may use Stripe storage needed to complete and protect that payment. Stripe is loaded only when you open checkout, not while you browse ordinary Relive pages.
Our promise
Insight without following people
Relive may use anonymous, daily aggregate measurements solely to improve the service. We do not create visitor profiles or use this information for advertising. If that purpose changes, the new technology will stay off until the appropriate choice has been offered.