Security & procurement
What is data processing agreement?
A contract that sets out how a vendor processes personal data on a customer's behalf, required under GDPR for processors.
Also called: dpa, data processing addendum
A data processing agreement, often called a DPA or data processing addendum, governs how a vendor handles personal data it processes for you. Under GDPR Article 28, controllers must have one in place with every processor. It covers the purpose and duration of processing, security measures, confidentiality, subprocessors, assistance with data subject requests, breach notification and deletion at contract end.
Event platforms process large amounts of attendee data, so procurement and legal teams almost always request a DPA. International transfers are usually covered by standard contractual clauses or an adequacy framework.
When reviewing, check breach notification timelines, the subprocessor list and change notice process, audit rights and data return or deletion terms.
Why it matters for event marketers: Without a signed DPA, most legal teams won't approve an event tool that handles attendee data.
How it works
A data processing agreement sits alongside the main contract with an event software vendor. Your company is usually the controller, deciding why attendee data is collected; the vendor is the processor, handling it on your instructions.
GDPR Article 28(3) lists what the contract must cover: the subject matter, duration, nature and purpose of processing, the types of personal data and categories of people, processing only on documented instructions, staff confidentiality, security measures, rules for using subprocessors, help with data subject requests, deletion or return of data at the end of the service and information for audits. Under Article 28(2), a processor can't engage another processor without the controller's written authorization, and with general authorization must give notice of changes so the controller can object.
Many vendors publish a standard DPA you can sign online, often with standard contractual clauses attached for transfers outside the EU.
What to look for in software
When reviewing a vendor's DPA, check the subprocessor list and how you'll be told about changes, the breach notification timeline to you, where data is stored and how international transfers are covered, audit rights and the deletion timeline after termination.
For event platforms specifically, check how the DPA treats data shared with exhibitors and sponsors (often a separate controller relationship), AI features and model providers, and onsite vendors such as badge printing partners.
Practically, a published DPA, a public subprocessor list and a trust center make security review faster.
Examples
Cvent publishes a data processing addendum with EU standard contractual clauses plus UK and Swiss addenda, and a public subprocessor list with locations. Zuddl publishes a DPA with SCCs and a subprocessor list in its trust center. Swapcard includes a DPA as an appendix to its organizer terms. EventMarketingSoftware.com's security check tool compares which vendors publish DPAs, subprocessor lists and other documents.