Customer and platform responsibilities
Couples normally control wedding content and decide what is collected and shared. Wedding Guest Gallery processes that content for them, while separately controlling account, security, support, and audit data.
Wedding galleries can include personal moments, guest names, dietary notes, account details, and support messages. This page explains the product controls and operational rules used to handle that data carefully.
Couples normally control wedding content and decide what is collected and shared. Wedding Guest Gallery processes that content for them, while separately controlling account, security, support, and audit data.
Customers can ask for help with data access, correction, export, or deletion from inside their wedding console, where the request is attached to the right event.
Event records include retention dates so galleries can be closed, exported, archived, or deleted under the package and any agreed hosting extension.
Event content is scoped by event, guest access uses private QR sessions, operator access is separate, and sensitive support/operator actions are audited.
The product now has an internal data map, processing record, lawful-basis assessment, retention schedule, AWS subprocessor register, draft processor terms, and a 72-hour breach-response runbook. They are kept with the product so implementation and customer wording can be reviewed together.
Legal entity details, solicitor review, dietary-data consent evidence, automated retention warnings, the guarded deletion executor, and dedicated breach-register tooling remain required before taking payment.
Sign in, open your wedding console, and choose Support. You can download account data or send a tracked access, correction, wedding deletion, or account deletion request with the right context attached.