Guest Moments
Log inRegister

Draft for the operator and for legal review. It describes this application as it works today. It is not a statement that Guest Moments is GDPR-compliant, and a lawyer has not approved it.

Privacy policy

Who this notice covers

Guest Moments is a service for a couple to collect wedding photos and videos from guests. Guests do not create accounts. This draft notice describes the processing that the code actually performs.

The legal name, address, registration number, VAT number, and privacy contact email of the operator are not in the application. They are listed as unpublished on the legal notice. Until they are published, this page cannot name the controller.

Accounts

A couple provides a given name, a surname, an email address, and a password. The application stores the password only as a hash. It also stores whether the email is verified, the preferred language, the role, whether an administrator has activated the account, and the access end date.

A signed-in session stores a session token and its expiry. Better Auth also stores the IP address and user agent for that session. This application does not read those two fields. They are deleted when the session ends, when the person signs out, when the account is disabled, or when the account is deleted. Expired session rows are removed by the daily cleanup.

There is no payment or subscription record in this application.

Events and guest media

An event stores its name, date, welcome and instruction text, colours, fonts, privacy setting, download setting, and storage quota. The couple may upload a cover image, a logo, and a background image. The couple does not choose a separate retention period for an event.

A guest upload stores the file, its type, size, and original file name, an optional guest name, an optional message, and the random browser token. The application does not ask guests to create an account and does not ask for their age.

Hidden items are not shown to guests. With “full gallery”, anyone with the event link can see the items that are not hidden. With “only my uploads”, a browser sees the items uploaded with its own token. Downloads are available to guests only when the couple leaves downloads on. Preview links expire after 15 minutes. Download links expire after 60 seconds. Upload links expire after 15 minutes.

Why the information is used

The application uses account data to create the account, sign the person in, send verification and password-reset email when email delivery is configured, and let an administrator activate or disable access.

It uses event and media data to show the guest page, store uploads, let the couple manage the gallery, and remove files when the customer's access ends or someone deletes them.

It uses rate-limit records, which can contain an IP address and an event code, to slow abusive uploads. Those database rows are deleted about 24 hours after the window starts. If Upstash Redis is configured, the same limit is counted there and those keys expire after about 20 minutes.

Security and operational logs store event types, internal ids, and fixed reason codes. They do not store passwords, message text, file names, or email addresses. The current log periods are 30, 90, and 180 days depending on the event type. Those periods are engineering defaults and still need confirmation.

Legal bases

This draft does not assign a GDPR legal basis to any activity. The operator and a qualified lawyer need to confirm the basis for accounts, guest uploads, photographs of other people, security logs, and the session IP address before this notice is used as a final policy.

How long information is kept

An administrator sets how long a customer can use the service: 30, 60, 90, 180, or 365 days, or a custom end date. The couple does not choose a retention period for each event. After that access end date, guests cannot open the customer's events, even if the cleanup has not run yet. If the administrator does not extend access before then, the daily cleanup permanently deletes that customer's events, albums, media records, and the photos and videos stored for those events. The customer account remains and stays disabled. Operational, security, and authentication logs keep their own periods, which are separate from this deletion. This application has no archive for restoring a deleted event.

Deleting an event removes that event, its media records, its albums, and its stored files. Deleting one photo or video removes that item. A couple can delete their own account from the account page. An administrator can delete a customer account. Either deletion removes the account, the events, and the stored files from the application database and from object storage.

This deletion does not promise that a database backup, a hosting backup, or an object-storage backup is erased. Those backup periods are not recorded in this repository.

Who receives information

The couple can open their own events. An administrator can open customer and event records. Guests can open an event when they have its link, within the privacy setting above.

When the related service is configured, the application uses PostgreSQL for the database, Cloudflare R2 for private media storage, Resend for email, Upstash for rate limits, and the site is written to be hosted on Vercel. The repository does not record the production region of any of these. No analytics or advertising service is connected in this code.

The application does not sell personal information.

International transfers

The production regions are not in this repository, so this draft cannot say whether information stays in the European Economic Area. The operator needs to confirm the regions and, where a transfer needs a safeguard, which safeguard is used.

Rights and contact

People may have rights of access, rectification, erasure, restriction, objection, and portability, and the right to complain to a supervisory authority. For Cyprus, that authority is the Commissioner for Personal Data Protection. Which rights apply to which activity depends on the legal basis, which is not confirmed in this draft.

A signed-in couple can correct their name, delete media, delete an event, and delete the account. A guest cannot sign in. A person who appears in a photograph, or a couple who cannot sign in, needs the operator’s contact email. That email is not published yet. This draft does not promise a response time.

Other people and children

Photographs may show guests, including children. The application does not detect faces and does not check ages. The couple decides the event settings and who receives the link. A final policy needs the operator and a lawyer to describe who is responsible for the photographs and on what basis they may be collected.