Data Processing Agreement
Version 1 · effective 21 November 2026
1. Parties and roles
1.1 The Venue (customer) is the controller of personal data about couples contained in enquiries, replies, bookings and related messages ("Couple Data").
1.2 Benjamin Potts, a sole trader trading as SolerMedia, of 26 Ark Royal Avenue, Exeter, Devon, EX2 7GP, which provides Venquire, is the processor of Couple Data on the Venue's behalf.
1.3 The processor remains responsible for its own obligations under UK GDPR and the Data Protection Act 2018 (including security, records of processing, sub-processor contracts and breach notification), and is the controller of Venue account and billing data (see the Privacy Notice).
2. Subject matter and duration
2.1 Processing: - receiving forwarded enquiry emails; - extracting contact details, names, wedding date and guest numbers; - automatically drafting replies from the Venue's confirmed information (rules and templates, no third-party AI service); - scheduling and sending the messages the Venue approves; - viewing bookings and reminders; - storage; - deletion on the Venue's instruction.
2.2 Data subjects: couples (and others) who send enquiries to the Venue.
2.3 Categories of data: names, email addresses, phone numbers if included, wedding date, guest numbers, message contents and viewing times. Special category data isn't required, and the Venue should avoid forwarding it.
2.4 Duration: for the term of the Venue's account, then deletion under clause 6.
3. Processor obligations
3.1 Process Couple Data only on the Venue's documented instructions (these terms, the Venue's settings, approvals and deletions), unless the law requires otherwise.
3.2 Ensure people with access are bound by confidentiality.
3.3 Apply appropriate technical and organisational security measures (Annex A).
3.4 Assist the Venue with data subject requests. The Venue can do this itself in the app: - export all data (Settings → Download or delete your data); - delete one couple's data (the enquiry page → "Delete couple's data"). This deletes immediately that couple's enquiries at the Venue (all of them, unless the Venue unticks that option), every message (including drafts and anything scheduled, so nothing further is sent), viewing bookings, stored email copies, delivery records and related log entries; - correct names on the enquiry page.
3.5 Notify the Venue without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Couple Data. The notice will include the information the Venue needs to decide whether to report it to the ICO. A controller must report within 72 hours where a breach is likely to result in a risk to people.
3.6 Assist with DPIAs and regulator consultations where reasonably required.
3.7 Make available the information needed to demonstrate compliance with this DPA, and allow reasonable audits on 30 days' notice (normally by written questionnaire).
4. Sub-processors
4.1 The Venue gives general authorisation for these sub-processors: - Cloudflare, Inc. (hosting, database in Western Europe, email routing); - Resend (email sending; sending domains in Resend's EU (Ireland) region; US-headquartered); - GitHub, Inc., only if encrypted backup files are stored there (encrypted backup files only; we hold the key).
Stripe processes Venue billing data only, not Couple Data, so it isn't a sub-processor of Couple Data.
4.2 We'll give 30 days' notice of new sub-processors by email, so the Venue can object.
5. International transfers
5.1 Where Couple Data is transferred outside the UK, it's protected by an approved mechanism: - Cloudflare: the UK Extension to the EU-US Data Privacy Framework where applicable, otherwise the EU Standard Contractual Clauses with the UK International Data Transfer Addendum (Cloudflare DPA). - Resend: the EU Standard Contractual Clauses as amended by the UK Addendum (Resend DPA).
6. Deletion and return
6.1 One couple: deleted immediately when the Venue uses "Delete couple's data" (clause 3.4).
6.2 Whole account: the Venue can delete everything at any time from Settings. When an account ends (cancellation, full refund, a Founding Year not renewed, or termination for non-payment), the Venue has 90 days to export. At the end of the 90 days, all Couple Data is deleted.
6.3 What deletion can't reach immediately, and how it's handled: - Encrypted database backups expire within 30 days. If a backup taken before a couple's deletion is ever restored, that deletion is re-applied as part of our restore procedure: deletion records (enquiry reference numbers and one-way codes, with no personal data) are kept for 25 months, both in the database and as a copy outside it, and the system re-applies them every night. (Corrected 20 Nov evening: "automatically" overstated the case for a restore made after the live database is lost; see launch-verification doc 02 §6.) - The same original email delivered again is not re-imported. Only a one-way code of its Message-ID is kept. - Copies in the Venue's own mailbox are the Venue's to delete. - Resend may hold delivery logs of sent emails for its own limited retention period.
6.4 After deletion we keep only a minimal record that it happened (date, who requested it, counts). It has no names, addresses or message content.
7. Retention (current product settings)
| Data | Retention |
|---|---|
| Forwarded email copies | 90 days |
| Enquiries and their messages and bookings | 24 months after receipt |
| Test data | 14 days |
| Unfinished sign-ups | 6 months (we email the Venue first) |
| After the account ends | 90 days to export, then deletion; backups expire within 30 days after that |
| Deletion records (reference numbers and one-way codes only) | 25 months |
Annex A: security measures (summary)
- Encryption in transit (TLS). Data stored in Cloudflare D1 with provider-level encryption at rest. Backups are encrypted (AES-256) with a key held by the processor.
- Passwordless sign-in with single-use, hashed, time-limited links. Sessions are stored hashed, with secure, HTTP-only cookies.
- Strict separation of each Venue's data in every query, covered by automated tests.
- Private booking links use long random tokens. Pages aren't indexed and don't leak links via referrers.
- Staging uses an email allowlist and can't email real couples.
- Logs are redacted (email addresses masked, tokens removed). Error monitoring and operator alerts. A health check watched by an external uptime monitor.
- An audit log of key actions, without couple personal data after a deletion.