Browse conferences
Fields
All fields →
Health & Medicine
Engineering & Technology
Computing & Data
Social & Behavioural Sciences
Earth & Environment
Education
Physical Sciences
Arts & Humanities
Business & Economics
Life Sciences
Law & Criminology
Politics & Public Policy
Agriculture & Veterinary
Mathematics & Statistics
Open callsBlogFor organizersAdd your event — freeLog inSign up

Privacy policy

Version 1.8 · last updated

This policy sets out what we collect, why, who else sees it, how long we keep it and what you can do about it. It describes what the software actually does rather than what a policy of this kind usually says, so where the two differ, this follows the software.

This text has not been reviewed by a solicitor or a data-protection specialist. It is a plain description of how this service actually works, published because operating with nothing written down is worse than publishing an unreviewed statement. A reviewed version will replace it. Where a fact is genuinely undecided, this document says so in the place the fact would have gone rather than filling the space with a plausible sentence.

The cookie policy covers cookies and browser storage specifically, and the terms of service cover the service itself.

1. Who is responsible for your data

Conference2Go is the data controller for everything described here.

We serve people in the United Kingdom and across Europe, so UK GDPR and EU GDPR both apply, and this policy is written to satisfy the stricter reading of either.

Not settled yet. The legal entity behind Conference2Go is not named here, and neither is a dedicated data-protection address. Neither has been confirmed for publication and neither is invented on this page. Until they are, everything about your data goes through the contact page, which reaches a person and gives you a reference.

Not settled yet. Whether we are required to appoint a data protection officer, and whether we have appointed one, are not decided. Whether we need an EU representative under Article 27, and who it is, is likewise not decided. Both are questions for the specialist reviewing this document.

2. The short version

3. What we collect, and why

While you are signed out

Unless you accept analytics or advertising cookies, nothing about your visit is written down. For our own record this is enforced in the code rather than promised: the function that records behaviour cannot be called without a signed-in person, so an anonymous visit has nothing to record.

The exceptions, and only if you choose them. If you accept analytics in the cookie banner, Google Analytics' tag runs in your browser and records the pages you visit here, without what you search for, and Microsoft Clarity records how the pages are used, with the text you type into forms hidden. If you accept advertising measurement and arrived from one of our advertisements, we keep a random identifier in a cookie in your browser and the advertisement's own reference from the link you followed — not the pages you read and not what you searched for — and Google's advertising tag, and Meta's if we advertise there, may keep cookies of their own. Clause 6 says what happens with each.

Two things are stored inside your own browser and sent nowhere: your answer to the cookie banner, and the conferences you have opened recently, as identifiers only. Both are listed in the cookie policy, and both are yours to clear.

If you fill in the contact form without an account, we keep what you sent us and the address you gave, so we can answer.

Newsletter and reminders without an account

You can subscribe to our monthly email, or to date reminders for a conference, without creating an account. We store your email address, the fields and options you chose, where and when you signed up, and when you confirmed. We send one confirmation email, and nothing else until you confirm. Unconfirmed sign-ups are deleted after 30 days. Every email has a one-click unsubscribe link and a link to change your choices. Legal basis: your consent. We keep your subscription until you unsubscribe or ask us to delete it.

When you hold an account

Our own statistics

We also keep our own usage statistics (for example which fields and destinations are popular, and which searches find nothing). They are recorded only if you accept Analytics cookies, are never linked to your name or account, are only reported in aggregate, and are deleted after 400 days.

Behavioural analytics, only if you agree

If, and only if, you turn analytics on for your account, we record what you did on the site: which conference pages you opened and the field and country of each, what you searched for and how many results came back, how you arrived as a class such as "search engine" or "academic", the country the request came from, your browser's primary language, and whether the screen was a phone, a tablet or a desktop.

Three limits on that are worth stating because they are unusual:

Separately from all of this we keep two counters against each listing — how many times its card was shown and how many times somebody acted on it. Those carry no identifier of any kind: no account, no session, no country. They exist because search ranking normalises engagement by impressions, and gating them on consent would make a listing's position depend on how many of its viewers happened to opt in.

What we never collect

We do not ask what kind of user you are. There is no "researcher or organizer" question, no role on your account and nothing that infers one, because whether somebody presents or attends changes per conference and per year.

We do not collect special category data. Do not send us any.

4. Why we are allowed to hold it

Three switches, and they gate data rather than access:

The product works completely for somebody who refuses everything. Search, browse, conference pages, saving, ticked dates, reminders, submitting a listing and managing one all behave identically. We checked that rather than asserting it: analytics consent decides one thing in the code, whether an event may be recorded at all, and marketing consent decides the three named above. Advertising measurement decides whether a conversion is recorded and reported, and nothing else. None of the three is read anywhere that grants or withholds access to a feature.

Refusing the cookie banner, and dismissing it without answering, are the same thing: capture stays off until somebody actively accepts.

You can change any of them at any time from your settings, and the answer to the banner from Cookie preferences in the footer of any public page.

Signed in, every answer you give on the banner is also kept on your account: what you chose, when, and which version of the banner's wording you saw. Withdrawing from Cookie preferences is kept too, with the time and what you turned off.

6. Who else sees it

Organizers see counts for their own listings, in aggregate, never an individual. Daily views, saves, clicks out to their own website, the countries requests came from and the kind of source that brought them. No name, no address, no account, and nothing about anybody's activity on a listing that is not theirs.

One thing about that is worth being exact about. Every figure we show, on our own screens and on an organizer's, suppresses any cell resting on fewer than 5 events, because an "aggregate" of three people is not an aggregate — and where a line is withheld the screen says so, so a suppressed country is never read as a country nobody came from. Version 1.0 of this policy recorded that the organizer's own screen did not yet apply that floor. It applies it now, in the same function that defines the threshold, which is why this version says something different. The figures carry no identifier of any kind, so the most any of them can tell an organizer is that somebody in a given country opened their listing, and nothing further.

There is one exception, and it is the thing marketing consent exists for. An organizer holding an access key can resolve the name and email address of a person who has ticked a date on one of that organizer's own conferences — and only where that person has given marketing consent. Without the consent the key gets an identifier and a sentence saying the details are not available. Without the ticked date on that organizer's own conference, it gets nothing at all.

We do not sell personal data, and we do not tell an organizer who looked at their listing.

Analytics and advertising measurement

With your consent, we use tools that help us understand how Conference2Go is used and how well our advertising works.

Legal basis: your consent (Article 6(1)(a) GDPR). You can change your choice at any time with "Cookie preferences" in the footer. Declining does not limit any feature of Conference2Go.

What Google Analytics is given, besides those actions: a random identifier for this browser, the pages you visit on Conference2Go, the campaign that brought you if there was one, or the website that sent you, your device and browser, and an approximate location worked out from your network address.

What an advertising platform is given: that someone who arrived from one of its advertisements went on to act, with the time, the value and the advertisement's own reference. We do not tell it your name, which conferences you looked at, or anything you have saved.

We do not sell your data.

Code on these pages

Another company's code runs on these pages only once you accept the kind it belongs to: Google Analytics and Microsoft Clarity with analytics; Google's advertising tag, and Meta's if we advertise there, with advertising measurement. Google Analytics is given each page's address without anything you typed — no search words — and, of a page on another website that sent you, only that website's name, never the page's own address. There is no social widget, no font loaded from somebody else's server and no map tile service. The browser is instructed, by a content security policy the server sets on every response, that it may load scripts, styles, fonts, images and connections only from this site and our own image store — and, while one of those tools is switched on, from that tool's own addresses. Nothing else could run here even if it were added by mistake.

Processors. We use service providers to run the platform: hosting, an email delivery provider, a payment provider for card payments, Google where you choose to sign in with a Google account, Google and Microsoft as our analytics providers where you accept analytics, Google — and Meta, if we advertise there — as our advertising providers where you accept advertising measurement, and the customer-relationship and email tools described below. Search runs on our own infrastructure and is not a processor arrangement at all. Each provider acts on our instructions, and a written data processing agreement with each one is a condition of using it.

Not settled yet. Where the platform itself is hosted, which email delivery provider and which customer-relationship tools we use, and the transfer mechanism for any of those outside the UK or the EEA, are not named here. This document will not name a provider we have not confirmed for publication or a safeguard we have not put in place. The specialist reviewing this will need those decisions first.

International transfers

Some providers (Google, Microsoft, Meta) may process data outside the European Union. These transfers are covered by the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses.

Our CRM and marketing tools

To manage our relationships with researchers and organizers, we may pass account and subscription information (such as your email address, account type, the fields you follow and your subscription status) to the customer-relationship and email tools we use. We only do this with providers who have signed a data processing agreement with us, and only for people who have confirmed a subscription or agreed to marketing. When you unsubscribe or ask us to delete your data, we pass that on to these tools too.

How the platform holds that line. Each tool that receives our events is set up by our staff with one of three levels of detail: an identifier only, a per-recipient pseudonym that is salted so two receivers cannot join their data, or full contact details. Full contact details are blocked outright until a data processing agreement is recorded against that tool, and then still degrade per person to an identifier for anybody who has not confirmed a subscription or, for an account, given marketing consent.

7. Your search queries

The matching that understands "cancer" means oncology runs on our own servers, not through a hosted AI service. No query is sent to a third party, there is no API key, and there is no outbound call when you search. Google Analytics, where you accept it, is given the search page's address with the words removed, and that a search found nothing — never what was searched for.

We built it the harder way on purpose, and it was not a requirement anybody gave us: a search query can reveal what somebody is working on before they have published it, and for an academic that is genuinely sensitive.

It is protected structurally as well as by intention. The code that configures the search index refuses any configuration that would send a query to another host, and refuses at the point of the edit rather than after it ships. If we ever change this — a hosted model may one day rank better — this section changes with it, and it will be a decision taken with the privacy cost named rather than a default that arrives with a configuration change.

The same care applies to the artificial-intelligence features the platform is able to run, such as reading a conference's own website to pre-fill a listing. What any of them reads is listing text and the conference's own public website — never your account, your saves, your reminders or your searches, none of which is passed to a model by any code path here. None of those features is switched on today, and each has a manual alternative it falls back to, so the product does not depend on one being on.

8. Email

We send:

Every non-transactional email carries an unsubscribe link that works immediately and without logging in. The link does not contain your email address — not in plain text and not encoded — because an unsubscribe link travels through mail gateways, link scanners and proxy logs, and any of those would then hold it. It carries a random token instead, which reveals nothing and can be revoked.

Transactional email stops in two cases only: when you delete your account, and when your address hard-bounces. A dead address is dead, and continuing to mail it damages the delivery of every other stream.

9. Your rights

You can exercise the first three yourself, without asking us and without waiting.

We do not make automated decisions that produce a legal effect about you.

Ask through the contact page. We answer within one month, which is the limit the law sets, and we aim to be quicker than that.

One thing we do not do, said plainly: we do not email you when a copy of your data is downloaded. An export is the quietest way for somebody with a stolen session to take everything at once, and a notice at your address is what would make that visible. It is not built. We do send that notice when an email address is changed, to the old address, with a link to cancel the change.

10. What deletion actually does

Deletion is not reversible, so export first if you want a copy.

Removed outright: saved conferences, ticked dates, follows, recently viewed, your lists, your saved searches, your travel regions, any pending email change, every session, every access key, every outstanding password-reset or verification token, your password hash, any Google connection, any second-factor secret and recovery codes, and everything kept for advertising measurement — the browsers joined to your account, the advertisement references, and every conversion not yet sent.

Detached rather than deleted: behavioural analytics rows, where the link to you is removed and the row stays. They describe the catalogue rather than the person, and by then there is nothing tying one to an account.

What survives, and why each one has to:

Two things can stop a deletion, and the settings page names whichever applies: an unpaid invoice, and a listing that would be left with nobody able to correct it.

Support tickets are not currently erased or pseudonymised by deletion, so the address you wrote in from can survive on a ticket. We would rather record that here than describe an erasure that is more complete than the one the code performs. If you want a ticket removed as well, ask us and we will do it by hand.

Google Analytics holds no name or address to delete. Its records are tied to a random identifier in your browser, not to your account; withdrawing analytics deletes that identifier and stops them.

Deleting your data

When you ask us to delete your data, we delete it from Conference2Go and tell the tools that received it (such as our CRM) to delete it too. Data already sent to Google Analytics or Google Ads is not linked to your name and is deleted by those providers under their own retention periods.

If you have given your details to a conference organiser directly, ask them as well.

11. How long we keep things

Not settled yet. Three retention periods are not decided and none of them is invented here: how long the audit log is kept — nothing deletes from it today and it is currently permanent; how long support tickets are kept — nothing deletes them either; and backup and server-log retention, which depend on hosting decisions that have not been taken. A retention schedule that has not been agreed is not published as though it had been.

12. Security

Passwords are hashed with Argon2id and never stored in a form we could read. Sessions expire. Cookies are httpOnly, restricted to this site, and marked secure in production. Every permission is checked on the server, per object, and every refusal is logged. Uploaded images have their metadata containers stripped before storage, so a location tag inside a photograph does not end up published. Staff accounts require a second authentication factor.

One thing that is asked for and is not built: we do not check a new password against lists of passwords known to have been breached. It is a real protection and it is not here yet.

Rate limits are keyed with a secret so that nothing identifying — an address, an email — is written into the rate-limit store in the clear.

No card details reach our servers. Card payments, where they are available, go directly to a payment provider.

13. Children

This service is aimed at researchers and conference organisers and is not directed at children. We do not knowingly hold data about anybody under 16. If you believe we do, tell us and we will remove it.

14. Complaints

If you are unhappy with how we have handled your data, tell us first through the contact page and we will answer in writing.

You can also complain to a supervisory authority. For the UK that is the Information Commissioner's Office.

Not settled yet. Which EU supervisory authority is our lead authority, and whether an Article 27 representative is required, are not decided. Meanwhile, if you are in the EU you may complain to the supervisory authority in the country you live in.

15. Changes to this policy

If this policy changes materially we will publish the new version, say so, and keep the earlier version readable. A version is never edited in place, and the version number and date are at the top of this page.

Version 1.8 adds Microsoft Clarity, Google Ads and Meta to clause 6, with our CRM and marketing tools and international transfers; adds the newsletter and reminders without an account, and our own statistics, to clause 3; and adds what deleting your data tells the tools that received it to clause 10. It removes the statements that Google Analytics was the only other company's code that could run here, that the platform sends no event to another system, that such events would go only to an organizer's own system, and that deletion does not reach outside this platform.