Who is responsible for personal data

The customer normally decides why and how wedding content, guest uploads, meal choices, and guest information are used, so they normally act as controller for that event data. Wedding Guest Gallery processes it to provide the service. Wedding Guest Gallery separately controls account, authentication, security, operator-audit, support, and future billing records.

What information is collected

The service stores customer account details, event settings, guest uploads, captions, optional guest names, guest information entered by the customer, upload/reaction metadata, and operational records needed to run the service.

Why it is used

Information is used to provide the event gallery, protect QR access, process uploads, prepare downloads, show guest information when enabled, moderate content, send account or event emails, and support the customer when something goes wrong.

Account and service processing is generally necessary to provide the requested service. Proportionate security, abuse-prevention, and audit processing relies on legitimate interests. Any future accounting records may also be retained to meet legal obligations. Wedding customers remain responsible for the lawful basis applying to the guest information they choose to enter.

Dietary and allergy information

Dietary notes can reveal health, religion, or belief information and may receive extra legal protection. Customers should only add what is necessary after telling the guest and identifying both a lawful basis and an appropriate special-category condition, commonly the guest's explicit consent for the wedding purpose.

Who can see event content

Customers and invited event admins can manage event content. Guests can see guest-facing pages only where the customer has enabled access, usually through the private QR code. Platform operators should only use support tooling where needed to diagnose issues or protect the service.

Deletion and retention

Hosting periods depend on the chosen package and any extension. Customers can download original files where available and delete uploads from the event console. When retention ends, galleries can be closed first; archive or deletion steps should only happen under the published retention process.

Guest review requests

Guests can ask the couple to review an upload. A review request moves the upload out of the guest gallery until an event admin approves, hides, or deletes it.

Cookies and browser storage

The product uses cookies and browser storage for sign-in sessions, QR guest access, upload progress, duplicate-upload prevention, reactions, and remembering useful event state.

Service providers and international processing

Amazon Web Services provides the current hosting, storage, databases, processing queues/functions, email, logs, DNS, and certificate services. The primary workload is configured in the AWS London region. AWS contractual terms and transfer safeguards still require final legal review before paid launch. Stripe, analytics, advertising, and external error monitoring are not currently active subprocessors.

Your choices and rights

Depending on the circumstances, people may ask for access, correction, deletion, restriction, objection, or portability. Customers can download account data and submit tracked requests from their account. Guests can contact the wedding organiser or support. Identity and event ownership may need to be confirmed before a request is completed.

Questions and complaints

Contact support@dukeweds.comfirst so the request can be examined. People also have the right to complain to the UK Information Commissioner's Office. Legal provider identity, postal address, and registration details will be added before the paid service launches.