Your wedding is not our content.
We use personal information to provide the service a couple asks us to run. We do not sell guest lists, use wedding photographs to train AI models or add enquirers to marketing without a separate choice.
Who is responsible?
The intended operating arrangement is that Yours, Dearest handles website enquiries and its direct work with couples. For guest replies, menus, table assignments and wedding uploads, the couple normally decides why the information is collected and Yours, Dearest runs the agreed service for them. The final controller and processor roles for each flow still require review before a paying wedding. Contact: privacy@withyoursdearest.com.
What we collect and why
- Enquiry contact details, wedding date if known, guest range and any optional venue or wedding-country details so we can respond and check the service fit. The country you enter can differ from the site market you selected.
- A short first-party referral label, such as a service page or venue code, when it is present in the enquiry link. The enquiry record does not store the referring page URL.
- Cookie-free Vercel Web Analytics on public marketing and fictional demonstration pages. This can record the public page viewed, a referring page, approximate region and general browser or device details in anonymised form. Analytics is disabled for every private wedding and administration route, and query strings are removed before a public page event is sent.
- Guest names, attendance, menus, dietary notes and table assignment to run the booked wedding service.
- Photographs a guest deliberately confirms for upload, plus uploader name when they choose to provide it.
- Security and delivery records needed to prevent abuse, diagnose failures and prove important actions.
Our legal reasons
The launch plan expects steps requested before a contract and contract performance to support couple enquiries and booked services, with legitimate interests considered for proportionate service security and reliability. Marketing email uses a separate choice and is never required to make an enquiry. Dietary information can reveal health or belief information, so the Article 6 basis for each flow and the Article 9 condition for dietary details must be confirmed before a paying wedding.
Who receives information?
The couple and authorised wedding operators can access their wedding. Relevant guest and menu information may be exported for the venue. Vercel hosts the website and provides public-page analytics. Supabase hosts application data and private image storage; Resend delivers service email. We will document international-transfer safeguards in the final supplier record before launch.
How long we keep it
The current operating schedule places enquiries that do not become customers into deletion after 12 months. Wedding guest records and gallery files enter a 90-day deletion schedule after the wedding unless the couple agrees a shorter period or asks for an export first. This process still needs final rehearsal evidence. Essential invoices and contract records follow the retention period confirmed for the business. Short-lived security counters expire automatically. They contain a one-way code derived from the connecting address supplied by our hosting provider, never the address itself.
Your choices and rights
You can ask for access, correction, deletion, restriction, portability or object to particular uses where those rights apply. You can withdraw marketing consent at any time. Contact us first so we can help; you may also complain to the UK Information Commissioner's Office.