How we handle your details
What we keep when you book a visit, why, for how long, and what you can ask us to do about it. Last updated .
Who we are
What we collect and why
Your booking request
Your name, email address, phone number if you give one, the date, start time and length of the visit, how many of you are coming, whether you are bringing your own drinks, whether you want dinner, served by us or your own, any notes, and a coupon code if you use one. We use them to answer your request, confirm or decline it, send you the address, and deal with any change or cancellation. The legal basis is taking steps at your request to enter into, and then carry out, the booking (GDPR Article 6(1)(b)).
Each booking has a private cancellation link, sent only to you. We store a one-way fingerprint (a hash) of it, not the link itself.
Coupons and referral codes
If you tick the box asking for one when you book, we email you a code to share with friends after your visit, and store it with your email address and phone number so that it is yours. The legal basis is your consent (Article 6(1)(a)), which you can withdraw at any time by writing to us: we then delete your code, with your email address and phone number, and send you no more. When someone uses a referral code, we check that they have not booked before by comparing their email address and phone number with our bookings. A friend’s visit earns you a one-time code, emailed to you without their name. The legal basis for these checks is our legitimate interest in keeping each code to what it offers (Article 6(1)(f)).
Technical data
To stop the booking form being flooded, Cloudflare counts recent requests from your IP address and refuses them past a limit. So that one connection cannot hold many times at once, we also keep your IP address with a request while it waits for the owner (for an IPv6 address, only its first half, which names your network), and delete it once the request is confirmed, declined, cancelled or lapses. On the booking page, Cloudflare Turnstile checks that a person, not a script, is sending the form. By Cloudflare’s account, it processes your IP address, browser (user agent) and connection details for that purpose, and it does not read what you type into the form. Cloudflare also uses those signals, as a controller itself, to improve its bot detection.
Our server records each request it handles, including page views: when it came, the address requested, the response, and technical details Cloudflare attaches, which can include your IP address and browser. We use these logs to keep the site running and to find faults. The cancellation link never appears in them: the page sends it in the body of the request, not in the address.
The legal basis for this technical data is our legitimate interest in keeping the site and the booking form secure and working, and free of spam (Article 6(1)(f)).
The admin pages
The admin pages are protected by Cloudflare Access. Only the owner and the people the owner lets in, such as artists keeping their own pieces, sign in to them; guests never do.
No-shows and late cancellations
Cancelling is free until 6 hours before your visit. A later cancellation, or not coming at all, is a no-show: no bookings for 6 months. Any other bookings on the same email or phone are cancelled too.
When that happens we record the booking’s email address and phone number, the reason and the date the ban ends. While it lasts, a new request from that email address or phone number is refused automatically, and other upcoming bookings on them are cancelled. The ban lasts 6 months, and we delete its record on the day it ends. If you think a ban is wrong, write to us and the owner will look at it.
The legal basis is our legitimate interest in protecting a small room, which hosts one party at a time, from bookings that are not kept (Article 6(1)(f)).
How long we keep it
- Your name, email address, phone number, notes and cancellation link fingerprint are erased after the date of your visit. What remains is anonymous: the date, time and length of the visit, the party size, whether drinks were brought, the dinner chosen, any percentage taken off, whether a referral code was asked for, whether it went ahead, and when the request was sent and last changed.
- The IP address kept with a request is deleted once the request is confirmed, declined, cancelled or lapses.
- A ban record is deleted on the day the ban ends.
- A referral code is deleted once none of your bookings still holds your details. A code a friend’s visit earned you, which holds your email address and phone number too, is kept until its last valid day, after it was made, even if your bookings’ details are erased before then.
- Request logs are kept for at most .
- Cloudflare keeps a rolling history of the database for recovery, for at most , so erased details leave that history within that time.
- The emails about your booking are in our mailbox as well as yours. We delete ours on the same schedule.
Who handles it for us
Cloudflare runs the site for us, as our processor under its data processing addendum: it hosts the pages and the server code, stores the booking database (placed in its Western Europe region), sends our emails, and provides Turnstile and Access. Your own email provider receives the emails we send you. We do not sell your details or share them with anyone else.
Outside the European Economic Area
Cloudflare’s network spans the world, so a request may be handled in a data centre outside the EEA, and Cloudflare is a US company. Its data processing addendum covers such transfers with safeguards: the EU Standard Contractual Clauses, and Cloudflare’s certification under the EU–US Data Privacy Framework.
Cookies
This site sets no cookies, and uses no analytics or advertising trackers. The Turnstile check on the booking page runs in a frame served by Cloudflare and hands the form a one-time token rather than a cookie. When someone signs in to the admin pages, Cloudflare Access sets the sign-in cookies it needs; guests never sign in, so that never happens for them.
When you follow a link, the page also leaves the point you clicked in your browser’s storage for that tab, for the next page to start its transition from; the next page deletes it as it opens, and it is never sent to us.
On a laptop or desktop, your browser also downloads one music file from this site in the background while the page is idle, so it can play at once if you press and hold on the page. It is a static file from our own server; nothing about you is sent with it beyond what any page request carries.
The Uni-Q guide shows three short films from KEF that play from YouTube. Nothing is loaded from YouTube until you press play on one. Then that film plays in YouTube’s privacy-enhanced player (youtube-nocookie.com), and Google, which runs YouTube, receives your IP address and browser details and may store data on your device, as a controller in its own right under its own privacy policy.
Your rights
You can ask us for a copy of your details, to correct them, to erase them, to restrict how we use them, or to have them in a portable form, and you can object to the uses that rest on our legitimate interests. Email from the address you booked with, and we will answer within a month. Erasing the details of an upcoming visit means cancelling it.
If you are unhappy with how we handle your data, you can complain to the Portuguese supervisory authority, the Comissão Nacional de Proteção de Dados (CNPD), at www.cnpd.pt (opens in a new tab).