What this notice covers
It covers conclavedesk.com — the pages you are reading now — operated by ZEBIQ TECHNOLOGY LLP.
It does not cover the Conclave product. That is a separate application on separate infrastructure, and when a customer self-hosts it, it runs on machines we have no access to at all. The registrations, phone numbers and entry passes belonging to somebody’s conference never touch this website. If you registered for an event and want to know what happens to your details, the organisation running that event is the one to ask; data residency explains why they, and not we, are the ones who can answer.
What we collect when you read this site
Nothing you type, because there is nothing to type into. There is no contact form, no newsletter box, no chat widget and no account for visitors.
The server that answers your request writes an ordinary web log — the IP address the request came from, the page asked for, the time, and the browser string your browser volunteered. That is how the site is kept running and how abuse is spotted. We do not join those logs to anything else, and we do not use them to build a picture of an individual reader.
Cookies: there is one, and it is probably not for you
A single cookie, conclave_admin, is set when a member of our team signs in to write or edit a blog post. It holds a signed session identifier and nothing else — no name, no email, no preferences. It is marked HttpOnly, so page scripts cannot read it, it expires after seven days, and signing out deletes both the cookie and the session record behind it.
If you never sign in — which is everybody except a handful of us — you are never given a cookie. That is also why there is no consent banner on this site: a banner asking permission for nothing would be theatre.
Analytics and third parties
There is no analytics on this site today. No Google Analytics, no ad pixel, no heatmap recorder, no embedded social widgets, no chat bubble phoning a vendor.
The typefaces are downloaded when the site is built and served from this domain, so reading a page here does not quietly make a request to a font provider on your behalf.
If we ever add measurement, this page changes before it goes live, and we will pick something that counts page views rather than something that follows you to other websites.
Email you send us
Mail to hello@conclavedesk.com arrives in a mailbox and is read by a person. We keep it while we are dealing with what it is about, and for as long afterwards as a sensible business record requires. We do not add senders to a marketing list.
Please do not send us other people’s personal data — delegate lists, member spreadsheets, phone numbers. Contact says the same thing at more length, and means it.
The blog
Posts carry the name of the person who wrote them. Authors are our own staff; there is no public sign-up, and no comments to moderate.
Where this data is held
The website and its small database run on infrastructure we operate. It is a handful of blog posts and a couple of staff accounts. The interesting question — where participant data sits — is answered on data residency, and for a self-hosted deployment the answer is: wherever you put it.
Asking us about your data
Write to hello@conclavedesk.com and ask. Given what this site holds, the honest answer for most readers will be that we have nothing of yours beyond a line in a web log we cannot connect to your name.
If your question is about an event you registered for, we may not be the controller of that data at all — often the organiser is, and on a self-hosted deployment we cannot reach it even if we wanted to. Tell us which event and we will point you at the right people.
Changes
When this notice changes, the date at the top changes with it. There is no archive of previous versions; if that matters to you, keep a copy.