Pouring something cute…
Pouring something cute…
Privacy
The short version: we use your details to reply to you about your event, and nothing else.
Last updated 6 August 2026
When you send an enquiry through the booking form we collect the details you type into it: your name, email address, phone number, event type, date, guest count, city, whether the event is indoor or outdoor, your budget range, and any notes you add.
We don't run analytics, advertising pixels, or third-party trackers on this site, and we don't set any cookies of our own.
Only to reply to you and to quote for your event. We don't add you to a mailing list, and we don't sell, rent or share your details with anyone for marketing.
Enquiries are delivered to our own inbox, and — depending on how the site is configured — may pass through our email provider and our hosting provider on the way. Those providers process the message on our behalf and don't use it for anything else.
Our site is hosted on Vercel, whose servers keep short-lived request logs (including IP addresses) for security and abuse prevention.
We keep enquiry emails for two years so we can pick up a conversation about a repeat booking, then delete them. Ask us to delete yours sooner and we will.
You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Email hello@tezzy.ca and we'll action it within 30 days.
If you're in Canada and you're not happy with how we've handled a request, you can raise it with the Office of the Privacy Commissioner of Canada.
This site isn't aimed at children, and we don't knowingly collect information from anyone under 13. If a booking is being arranged for a child's party, we only need the details of the adult organising it.
If we change this notice we'll update the date at the top. Material changes will be flagged on the booking form itself.
Questions about any of this go to hello@tezzy.ca, or through the contact page.
This notice is a starting point written for a small Canadian business and is not legal advice. Have it reviewed before launch, and update the provider names above to match what you actually deploy.