Privacy, in plain English
Last updated September 2026
What we collect
When you use the booking form, reply to our emails, or scan one of our QR codes, we store:
- Your event date, guest count, event type, venue and town, service style, meals and add-ons, dietary notes, kids note, service time, and how you found us
- Anything you type into the free-text "anything else" field
- Your name, email and phone number
- UTM parameters and which pages of the site you came from, if you arrived via a tracked link
- The full text of any reply you send to our emails
- The browser user-agent and referrer of a QR-code scan
- Sign-in IP addresses for the owner account (Aimee's login only, never yours)
If you start the form and stop partway, we keep what you entered so far (a date and a headcount) so Aimee can still help if you come back.
What we do with it
We use it to answer your inquiry and run your event: at most three automated emails (a copy of your request, one follow-up after 72 hours if you go quiet, and one review request after your event) plus Aimee's own replies. Email goes only to addresses that ticked the consent box. We do not send text messages. Aimee uses the phone number you give to call you about your inquiry and pricing. There is no newsletter and no advertising list.
Who else sees it
Cloudflare hosts the site, our database and our inbound/outbound email routing. Resend delivers our emails. A copy of every email we send and every reply you send back also goes to Aimee's own Gmail, so she sees inquiries on her phone. We never sell or rent your information to anyone.
How long we keep it
We keep your information for three years after your event date, then delete it. Ask us to delete yours sooner and we will, unless the law says we have to keep it.
Your choices
Email aimee.strevay@gmail.com to see, correct or delete what we hold about you. Deletion requests are honored within 30 days.
Cookies
The public site sets no tracking cookies. The booking form remembers your progress in your own browser only. The owner dashboard uses one strictly-necessary session cookie for sign-in.