Paper Trust: A 2026 Privacy Reading of the Manchester 2013 Delegate Register

A sheet with consequences

At a conference, the delegate list looks administrative. It is printed, checked, amended and sometimes discarded. Yet the register from the Manchester 2013 congress is not a neutral schedule of attendance. It is a collection of personal data gathered at a particular moment, under particular expectations, and later inherited by an archive with different public responsibilities. The IUAES 2013 Archive exists to preserve the intellectual and organisational record of the Manchester dialogue; it does not exist to turn past delegates into a searchable directory.

That distinction is the starting point for any serious privacy reading. This article does not reproduce names, email addresses or other contact details from the register. Instead, it treats the document as a case study in consent, retention and archival judgement for UK conveners preparing events in 2026. The question is not whether attendance records have value. They plainly do. The question is how that value can be kept without exposing the people whose presence created it.

What the register records

A conference register is usually composed of several layers. The public-facing layer may include a delegate's name, institution and country. The administrative layer may include email address, phone number, fee category, payment status, attendance days, badge name and notes on access or dietary requirements. Some of these fields are mundane; others can reveal more than a delegate intended. Access requirements may hint at disability or health needs. Dietary notes may point towards religious observance. A contact email may be personal rather than institutional. Even a seemingly simple affiliation can identify a person in a small specialist field.

In 2013, the norms around conference data were less settled than they are in 2026. Printed delegate lists were often circulated as a convenience, and online registration systems were not always designed with granular permissions. That historical context matters, but it does not suspend present obligations. The UK GDPR and the Data Protection Act 2018 govern how personal data is processed now, including data held in archives. Archiving in the public interest can provide a lawful basis and safeguards, but it is not a blanket exemption from care.

Consent is not a single box

One of the most common weaknesses in conference registration is the all-purpose permission box. A form may ask whether the organiser may 'share your details', without specifying whether that means sharing with fellow delegates, sponsors, partner organisations, future conference teams or an archive. A single tick cannot meaningfully cover all of those purposes. Nor should consent be treated as the only lawful basis for every processing activity. Conference administration may rest on contract or legitimate interests; electronic marketing has its own rules under PECR; publication of a programme may require a different assessment again.

The lesson for 2026 conveners is to separate purposes at the point of collection. A delegate should be able to understand, without legal training, which fields will appear in the printed programme, which will be visible to other attendees, which will be shared with sponsors, and which may be retained by an archive. Where consent is used, it should be specific, informed and easy to withdraw. Where it is not used, the lawful basis should be recorded and explained. 'Consent' is not a word that can be stretched to cover every later use.

Retention and the archival turn

Archives are often tempted by completeness. A full register feels more useful than a redacted one. But retention is not the same as preservation. A conference archive can preserve the fact of attendance, the shape of a programme and the distribution of institutions without retaining every contact field. The Manchester 2013 record can support research into disciplinary participation, international representation and session attendance while keeping personal identifiers to a minimum.

A workable retention policy distinguishes between operational need, financial need and archival value. Operational records may be kept for a short period after the event; financial records follow accounting requirements; archival records are selected for enduring historical value. At the point of transfer to an archive, fields should be reviewed rather than inherited wholesale. Email addresses, phone numbers, payment details and free-text notes are rarely necessary for the public record. Affiliation-only data, role categories or aggregate counts may serve research better and expose less.

A 2026 checklist for UK conveners

• Map every registration field to a stated purpose. If a field has no clear use, do not collect it.
• Separate public programme data from administrative data. Publish only what the programme genuinely requires.
• Write a plain-language privacy notice at the point of registration. Name the recipients, retention periods and any archival transfer.
• Use granular choices for sharing with sponsors, partners and future event teams. Do not bundle permissions.
• Record the lawful basis for each processing activity. For marketing emails, use PECR-compliant consent.
• Set retention periods before the event, not after it. Include a redaction rule for archival copies.
• Restrict access to full registers. Log downloads and use pseudonymised copies for research.
• Provide a clear route for objections and erasure requests, and explain any archival limits honestly.
• Before transfer to an archive, remove unnecessary contact fields and treat access, dietary and payment notes as sensitive in practice.
• Document decisions. For large or complex events, a data protection impact assessment is prudent.

What can remain useful

Privacy is not the enemy of research. A conference archive can still record how many delegates attended, which institutions were represented, how sessions were distributed and how participation changed across the programme. It can preserve anonymised co-attendance patterns, aggregate affiliation data and the organisational history of the event. What it should not do is convert a 2013 registration form into a permanent public directory simply because the technology makes that possible.

The Manchester 2013 register is therefore a test of archival discipline. It asks whether an archive can preserve context without converting trust into exposure. For 2026 conveners, the practical answer is to design for the archive from the beginning: collect less, explain more, separate purposes and redact before deposit. The delegates of 2013 could not foresee every later use of their details. The least we can do is apply a standard of care that they would recognise as fair.