Cookies and storage
The whole answer
We count page views, searches and the filters used on the directory on our own servers, and only if you switched site analytics on when we asked. The things below are stored so the product works, and not one of them is sold or shared.
- The one exception is a link someone shared: opening it adds one to that link’s own counter, and nothing in that identifies you or your visit.
- Nothing about any of it leaves this domain: there are no third-party requests on this page, there is no advertising code, and the typeface is served from our own domain.
- We record only whether a visit was signed in, never which account.
- If you arrived from another site we keep that site’s name for ninety days, never the page or the link you followed, and read it as a list of where our visits come from.
- If you are signed in we also keep the home country and the specialty you chose yourself, so an organiser can see who their listing reaches; never your address, and never which account the visit was.
- When you share a listing, the link carries a short random code so we can count how often each way of sharing is used and opened; the code is not made from anything about you.
Your choices
The banner offers three kinds of storage and requests. Only the last two are a choice, and both start off.
- If you never press anything on the banner and never sign in, neither is ever switched on.
- Signing in counts as Accept all when you have not chosen yet, as the sign-in page says; a choice you already made, Reject all included, stays as it is.
Necessary
Always onKeeps the site working: your sign-in session, your theme and currency, your compare list, the area you last used, the sessions you pick into a day while signed out, a half-filled organiser form or claim, how far down each page you had scrolled in this tab, and your answer to the banner.
- These are the cookies marked Necessary below.
- Nothing here is used for counting or advertising, and there is no switch for it because the site cannot do these things without it.
Site analytics
Off by defaultCounts page views with the time spent on them, searches, the filters used, searches and filters that found nothing, listing opens, shortlist saves, clicks out to an event’s own site (and whether the button said register), clicks on map, source, speaker, area-guide and calendar links, and shares.
- Each event is sent to our own servers, at an address on this domain, with a random number for this browser tab that is kept in session storage.
- Kept for 90 days.
- Switch it off and no event is sent from then on, and the tab’s number is cleared.
Google sign-in
Off by defaultLoads Google’s sign-in script from accounts.google.com on the sign-in page and the home page, so Sign in with Google works and the home page can offer Google’s own one-tap prompt.
- Google receives the request for the script, which carries your address and browser details like any other web request, and its script can set a cookie of its own, for instance to remember that you dismissed its prompt.
- With this off, nothing is requested from Google, with one exception: if you press Continue with Google on the sign-in page, the script loads then, for that visit, because you asked for it. That press does not change your choices.
- Signing in with an email code never uses Google.
What we store
- cookieNecessary
themeWhether you chose the light or the dark theme.
So the page does not change under you on the next visit.
- cookieNecessary
conferra.token / conferra.emailYour sign-in session, once you sign in.
So you stay signed in across visits, and the site knows which name to show in the header.
- cookieNecessary
conferra.compareThe listings you put side by side, up to three.
So the comparison page and every Compare button agree on the first paint, with no account needed.
- cookieNecessary
conferra.areaWhich of Attending, Organising or Sponsoring you last used.
So you land back where you were. It is a view preference, not a permission.
- cookieNecessary
conferra.currencyThe currency figures are read in. It starts from your home country if you have set one, otherwise from your browser’s language, and changes when you pick a currency.
So an estimate beside a fee or a price is in the server render rather than appearing after it. Nothing is charged in it.
- cookieNecessary
conferra.consentYour choices on the banner: whether site analytics is on and whether Google sign-in is on. It is a short code such as v2.a1.g0 and holds nothing else.
So the question is asked once rather than on every visit, and not at all once you are signed in, and your choices are there when you open Cookie settings.
- Signing in sets it to everything on if it was not set, and leaves it alone if it was.
- Until site analytics is on in it, none of your reading is counted and the session entry below is never written.
- The one exception is opening a link someone shared, which adds one to that link’s own counter and stores nothing in your browser. Links you share, below, says exactly what.
- session storageSite analytics
conferra.session / conferra.referredA random number identifying this browser tab’s visit, so page views can be counted, and a note that the page you arrived from has already been counted once.
Thrown away when you close the tab, or at once if you switch site analytics off. Neither is ever sent as a cookie.
- If you are signed in we record that a visit was signed in, and never which account it was, alongside the home country and the specialty you chose on your own profile so an organiser can see who their listing reaches.
- Signed out, neither of those is recorded at all.
- cookieNecessary
conferra.agendaSessions you have picked into a day, while you are signed out.
So the day view works with no account. When you sign in, these picks are moved into your account and this cookie is cleared.
- session storageNecessary
conferra.submit-draft / conferra.claim-draftWhat you have typed into the organiser’s submit form, or into the form to claim a listing, while it is half filled in. The submit draft also notes the step you are on and whether you had picked a photo. The photo itself is not stored.
So a trip through sign-in does not lose what you typed. It is cleared when you send the form or start it again, and thrown away when you close the tab. It is never sent as a cookie.
- session storageNecessary
react-router-scroll-positionsHow far down each page you had scrolled in this tab.
So Back returns you to where you were. Thrown away when you close the tab, and never sent.
- session storageNecessary
conferra.triage.placeTeam console only: the filters, open rows, folded groups and shown-row counts a reviewer had on the triage screen. It never holds which rows were ticked.
So a trip to a listing and back lands on the same view. Thrown away when you close the tab, and never sent.
Clear either by clearing site data in your browser; signing out clears the session cookies directly.
Who else your browser talks to
Google sign-in is the only one. Nothing else on the site is served from another company.
- Its script loads on the sign-in page and on the home page only if you switched Google sign-in on, and otherwise only when you press Continue with Google on the sign-in page.
- A reader who has done neither never asks Google for anything.
Still to settle
This page covers what the site does today. These points are written down so they are a decision rather than a discovery:
Page views, searches and filter choices are counted only if you switched site analytics on, and no such event is sent before you do.
- The one thing counted regardless is the arrival count on a shared link, described above, which carries no identifier.
- They are counted on this domain, kept for 90 days, and tied to a number that dies with your browser tab rather than to you.
- Anything older is deleted by a sweep that runs on the next visit rather than on a clock, so on a quiet week a row can outlive the 90 days by a few days.
A reviewer’s name will be published deliberately, once reviews exist, and is the one piece of personal data here meant to be public.
- That should be said at the point of writing, and again in the privacy notice.
Email addresses collected at sign-in are personal data held by us, with a retention and deletion route that still needs settling.
- Emailing a listing to a colleague collects a second kind, and the more sensitive one: a third party’s address, given to us by somebody else, kept under no retention rule at all and without the knowledge of the person it belongs to.