Privacy and data in plain language
Reverie collects your guests’ photos and videos in a private gallery. This page explains where the files live, who can see them, how long they stay and how you take them with you. The privacy policy has the full legal detail.
Hosted in the EU.
Reverie’s application, database and file storage run on Railway in an EU region. Photos and videos sit in private object storage.
Cloudflare handles DNS, Resend delivers email, Polar processes payments, and Google powers optional sign-in and the Drive export. The privacy policy names every provider and explains international transfers. Reverie does not sell personal data.
Originals, kept as sent.
Photos and videos are stored exactly as guests send them, up to 250 MB per file. Nothing is resized, re-encoded or watermarked. Previews for browsing are separate copies.
Because originals stay untouched, they keep any metadata the phone added, such as camera or location details.
Hosts download the originals of an event, one by one or as an archive. Guests upload and, when the host allows it, browse the gallery.
Guests scan the QR code or open the event link and upload from their browser. They need no app, no account and no password. Hosts sign in with their own account.
Unlisted galleries.
A gallery opens through one of its event links, or for the signed-in hosts of the event. Event pages ask search engines not to index them.
Guests see the gallery only while the host has switched the guest gallery on. Uploading works either way.
Create separate links for different parts of the event and revoke any of them whenever you like. A revoked link no longer opens the event.
Anyone holding a link can open the event, so keep the QR code off public posts. Guests keep the rights to their photos and videos.
A clear timeline.
Uploads close 28 days after the last upload, or as soon as the first export is made.
12 months after the last upload, an event’s photos and videos are due for deletion. A daily check removes the files and their records.
Hosts can delete an event in its settings at any time. That deletes the uploaded media, exports, hosts, event links, prompts and billing state.
Files you downloaded or exported to your own Google Drive belong to you and stay where you put them. Logs and backups are kept for limited periods, which the privacy policy describes.
Take everything with you.
Hosts can export every original as one ZIP archive, stored exactly as uploaded. Reverie emails the host who requested it when the archive is ready.
Hosts can also export to a new folder in their own Google Drive. Reverie sees only the files it creates there, through Google’s drive.file permission.
The first export, to an archive or to Drive, finalizes the event: nobody can upload anymore, and downloads stay available.
Analytics only with your consent.
Reverie uses cookies and browser storage for login, sessions, security, event context and language. These keep the service working.
Usage analytics stay off until you agree in the cookie banner. You can withdraw consent at any time on the privacy policy page, and every feature keeps working.
Consented page visits carry a pseudonymous browser identifier, plus your account ID while you are signed in. Names and email addresses are never sent, and there are no session recordings.
Run from Lübeck, Germany.
Reverie is operated by Christoph Schmatzler, trading as Leuchtturm Software, Bornhövedstr. 17, 23554 Lübeck, Germany. For an event’s photos and videos, the host is usually the controller and Reverie processes them on the host’s instructions. The imprint has the legal notice and contact details, and the privacy policy names the controller for each kind of data.
Every guest. Every photo.
One gallery.
Create your event for free and print the QR code. The gallery fills itself while you enjoy the party.
Create your event for free
