Privacy Notice

01Who we are

Revivre is operated by Revivre, the company you contract with. Revivre is the data controller for the account data of photographers who sign up, and for the analytics described below. For the wedding content a photographer uploads (photos, video, names, messages), the photographer is the controller and Revivre acts as their processor, handling that content only to provide the service.

You can reach us about privacy at contact@revivre.app.

02What we collect

Photographer accounts

• Your email address, used to sign in and to contact you.
• A password, which we store only as a salted bcrypt hash. We never see or store the password itself.
• The stories you build: titles, captions, and the settings of each project.

Wedding content you upload

• Photos and video clips, and any text you add to a scene.
• Details you choose to enter, such as the couple's names, the date, and the venue.
• Photo files can carry embedded data (for example the time a photo was taken), which we may read to help order a timeline.

Couples and guests who view a story

• Messages left in a guestbook, and answers submitted through an RSVP, booking, or contact form. These go to the photographer who owns the story.
• If a guest allows it, a single random identifier stored on their device so we can count views without profiling anyone. See section 06.

03Why we use it, and our legal basis

• To provide the service (build, publish, and show stories): performance of our contract with the photographer.
• To keep the service secure and working (sign-in sessions, preventing abuse of our AI features): our legitimate interest in a safe, reliable product.
• To measure how many people view a story: the viewer's consent, which they can decline with no loss of access.
• To generate draft copy and scenes with AI: at your request, as part of providing the service.

04Who processes data for us

We use a small set of trusted providers to run Revivre. Each handles data only on our instructions and under a data processing agreement.

Some providers may process data outside your country. Where that happens, we rely on appropriate safeguards such as the European Commission's standard contractual clauses.

05How long we keep it

• Account data and stories: for as long as your account is active. Delete a project to remove its content, or close your account to remove your account data.
• Guestbook messages and form entries: until the photographer deletes them or deletes the project.
• Client access details, and what a client chose or hid: until the photographer removes that client or deletes the project.
• View counts: kept in aggregate. The device identifier that allows counting is stored only on the guest's own device and can be cleared at any time.

06Cookies and local storage

We keep this simple. We use one strictly-necessary cookie to keep a photographer signed in. It is required for the app to work, so it does not need consent.

For everything else we ask first. One choice covers both counting views on a published story and understanding how the app is used (product analytics). If you allow it, we store a small identifier so activity is not double counted; if you decline, we store nothing and the product works exactly the same. You can change your mind by clearing your browser storage for this site. We do not use advertising cookies or third-party trackers.

A story embedded on another site (in an iframe) works differently: we count views there without asking for consent, because nothing is stored on your device. Each view gets a fresh, temporary identifier that exists only for that page load and is never written to a cookie or local storage, so there is nothing to opt out of.

6bRSVP and lead data

Some stories are wedding invites with an RSVP form. When a guest fills it in, the details they enter (such as name, email, phone, whether they are attending, and how many guests) are collected as a lead for the photographer who owns that story. The photographer decides what happens next: they may receive it by email, have it sent to a system of their own through a secure webhook, or share a read-only list with the couple via a private link they can revoke.

The photographer is the controller for that RSVP data and is responsible for handling it lawfully and for honoring any request to be removed. Revivre processes it on their behalf to provide these features.

6bbClient access (the couple)

A photographer can invite their clients, usually the couple, to their own gallery. To do that we store the email address the photographer enters, a name if they give one, and a record of which wedding that address may open and when it was last opened. The invitation itself is a single-use link sent by email; we store only a one-way hash of it, never the link.

Signing in this way sets a cookie so the couple can come back without the link. It is used only to recognise them on their own gallery. What they do there, such as hiding a photo from guests or choosing photos for an album, is stored against that gallery so the photographer can act on it.

The photographer is the controller for their clients’ details and decides who to invite and when to remove access. Revivreprocesses them on the photographer’s behalf. Removing a client’s access stops any existing link and cookie from working.

6cBusiness contact details we collect for outreach

We look for photography studios that Revivreis built for, and we contact them once to introduce it. For that we collect business contact details from public sources: a studio’s own website, business listings, and professional directories. We record the studio name, the business email address, the website, and the page the address was read from. Our crawler identifies itself and can be excluded; see the crawler page for how.

Our basis is legitimate interest in reaching businesses whose work our product serves. Every message says who we are and includes a link that stops all further contact immediately. Addresses that opt out stay on a do-not-contact list so a later round of outreach cannot reach them again. If we hear nothing back, the record is deleted within 18 months.

To see what we hold about you, correct it, or have it deleted, email contact@revivre.app. We act on removals the same day we receive them.

07Your rights

Under the GDPR and similar laws you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or provide it in a portable format. Where we rely on consent, you can withdraw it at any time.

If your data sits inside a photographer's story (for example a guestbook message), the quickest route is often the photographer, who controls that content. You can also contact us at contact@revivre.app and we will help. You have the right to complain to your local data protection authority.

08Children

Revivre is a tool for professional photographers and is not directed to children. We do not knowingly collect data from children. Photos of children may appear in a wedding story; the photographer is responsible for having the right to use them.

09Changes to this notice

If we change how we handle data, we will update this page and the date above. For significant changes affecting account holders, we will also reach out by email.

10Contact

Questions or requests: contact@revivre.app. This notice is governed by the laws of the Netherlands.