Legal
Data Processing Addendum
This Data Processing Addendum (“DPA”) forms part of the agreement between Eventlink Technologies LTD, a company registered in England and Wales with its registered office at 71-75 Shelton Street, Covent Garden, WC2H 9JQ, London, United Kingdom (“Eventlink”, “we”, “us”), and the customer that accepted our Terms & Conditions or signed a separate agreement with us (“Customer”, “you”). Together they are the “Agreement”.
This DPA applies when we process Customer Personal Data on your behalf while providing the Eventlink platform at https://app.eventlink.co and related services (the “Service”). It takes effect on the date the Agreement does, and stays in force for as long as we process Customer Personal Data. To request a countersigned copy, email support@eventlink.co.
1. Definitions
Terms not defined here have the meaning given in the Agreement.
- “Data Protection Laws” means all laws that apply to the processing of Customer Personal Data, including Regulation (EU) 2016/679 (“EU GDPR”), the UK GDPR, the UK Data Protection Act 2018, and the Swiss Federal Act on Data Protection, each as amended.
- “Customer Personal Data” means personal data that we process on your behalf through the Service. This includes registration data about event attendees, contact and guest lists, content you place on event pages, and the data of your workspace members.
- “Controller”, “Processor”, “Data Subject”, “Personal Data Breach”, “Processing” and “Supervisory Authority” have the meaning given in the EU GDPR or the UK GDPR, as applicable.
- “Subprocessor” means a third party we engage to process Customer Personal Data.
- “Restricted Transfer” means a transfer of Customer Personal Data to a country that is not covered by an adequacy decision under Data Protection Laws.
- “SCCs” means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914.
- “UK Addendum” means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner’s Office under section 119A of the Data Protection Act 2018.
2. Roles of the parties
2.1 Processor and controller. For Customer Personal Data, you are the Controller (or a Processor acting for your own customer) and Eventlink is the Processor (or your Subprocessor). You are responsible for deciding why and how the data is used, including for the attendees whose data you collect through your event pages.
2.2 Eventlink as controller. We act as an independent controller for the personal data we need to run our business, such as account and billing details of workspace members, security and abuse monitoring, and analytics on our own website. That processing is described in our Cookie Policy and is not covered by this DPA.
2.3 Your responsibilities. You confirm that you have a lawful basis for the processing you ask us to carry out, that you give attendees the notices Data Protection Laws require, and that you obtain any consent needed, for example for marketing emails. Your instructions must comply with Data Protection Laws.
3. Details of the processing
The subject matter, duration, nature, purpose, data types and data subjects are set out in Annex I. We process Customer Personal Data for as long as the Agreement is in force, and then as described in section 11.
4. Our obligations as Processor
We will:
- process Customer Personal Data only on your documented instructions. The Agreement, this DPA, and your use and configuration of the Service are your complete instructions. We will tell you if we think an instruction breaks Data Protection Laws, unless the law forbids us to;
- process Customer Personal Data in another way only where required by law, and tell you first where the law allows us to;
- make sure everyone authorised to process Customer Personal Data is bound by a duty of confidentiality;
- not sell Customer Personal Data, and not use it for our own marketing or to build profiles of individuals;
- not combine Customer Personal Data with data from other sources, except as needed to provide the Service to you.
5. Security
5.1 We maintain technical and organisational measures that are appropriate to the risk, as described in Annex II. We may update these measures as long as the overall level of protection is not reduced.
5.2 Personal Data Breach. We will notify you without undue delay, and in any event within 72 hours, after we become aware of a Personal Data Breach affecting Customer Personal Data. The notice will describe, as far as we know them, the nature of the breach, the categories and approximate number of records affected, the likely consequences, and the measures we have taken or propose to take. We will keep you updated as we learn more and will help you meet your own notification duties. Our notification is not an admission of fault.
6. Subprocessors
6.1 Authorisation. You give us general written authorisation to engage Subprocessors. The Subprocessors we use at the date of this DPA are listed in Annex III.
6.2 Changes. We will give you at least 30 days’ notice before we add or replace a Subprocessor that processes Customer Personal Data, by email to your workspace owners or through the Service. Subprocessors that you switch on yourself through an integration (see section 6.5) are not covered by this notice.
6.3 Objection. You may object to a new Subprocessor on reasonable data protection grounds within that 30-day period by emailing support@eventlink.co. We will work with you in good faith to find a solution. If we cannot, you may terminate the affected part of the Service, and we will refund any prepaid fees for the period after termination.
6.4 Our liability. We impose written data protection obligations on each Subprocessor that are no less protective than those in this DPA, and we stay responsible for their performance of those obligations.
6.5 Integrations you enable. When you connect a third-party service to your workspace (for example HubSpot, Salesforce, Slack, Notion, Typeform or Livestorm), you instruct us to send data to that service. That service acts under your own agreement with it, not as our Subprocessor.
7. International transfers
7.1 Where we host. Our application services run on Google Cloud in the europe-west1 region (Belgium). We also use Cloudflare for networking, edge compute, queues and object storage. Some Subprocessors, listed in Annex III, may process data outside the UK and the European Economic Area (“EEA”).
7.2 Transfer mechanisms. We transfer Customer Personal Data outside the UK and EEA only where permitted by Data Protection Laws: under an adequacy decision (including the UK–US and EU–US data bridges where the recipient is certified), or under the SCCs and, for UK transfers, the UK Addendum.
7.3 SCCs between you and us. Where a Restricted Transfer happens between you and us, the SCCs are incorporated into this DPA as follows: Module Two (controller to processor) or Module Three (processor to processor), as applicable; clause 7 (docking clause) applies; in clause 9(a) Option 2 (general authorisation) applies with the notice period in section 6.2; in clause 11 the optional language does not apply; in clause 17 Option 1 applies and the governing law is the law of Ireland; in clause 18 the courts of Ireland have jurisdiction. Annexes I to III to this DPA serve as Annexes I.A, I.B, II and III to the SCCs. The competent Supervisory Authority is the one identified in Annex I.
7.4 UK and Switzerland. For Restricted Transfers subject to the UK GDPR, the UK Addendum is incorporated, with the SCCs above as its “Approved EU SCCs”, and the tables completed from Annexes I to III. The “Exporter” and “Importer” may each end the UK Addendum as set out in its section 19. For Restricted Transfers subject to the Swiss Federal Act on Data Protection, the SCCs apply with references to the EU GDPR read as references to that Act, and the Swiss Federal Data Protection and Information Commissioner is the competent authority.
7.5 Conflict. If this DPA conflicts with the SCCs or the UK Addendum, the SCCs or the UK Addendum prevail.
8. Data subject requests
Taking into account the nature of the processing, we will help you respond to requests from Data Subjects to exercise their rights under Data Protection Laws, using the tools in the Service where possible. If a Data Subject contacts us directly about Customer Personal Data, we will redirect them to you and will not respond to the request ourselves unless the law requires it. We may charge a reasonable fee for help that goes beyond the normal functionality of the Service.
9. Assistance
Taking into account the nature of the processing and the information available to us, we will give you reasonable help with your obligations on security, breach notification, data protection impact assessments and prior consultation with Supervisory Authorities. We may charge a reasonable fee for help that requires significant effort.
10. Audits and information
10.1 We will make available the information reasonably needed to show that we comply with this DPA, including written answers to a security questionnaire.
10.2 If that information does not satisfy you, or a Supervisory Authority requires it, you may audit our compliance with this DPA no more than once a year, and more often only after a Personal Data Breach or where required by Data Protection Laws. You must give us at least 30 days’ written notice, agree the scope and timing with us, keep the audit to normal business hours without disrupting our operations, and keep what you learn confidential. You bear the costs of the audit, and any auditor must be bound by confidentiality. Audits cover our own systems and processes only, not the facilities of our Subprocessors, whose reports we will share where we can.
11. Return and deletion
11.1 You can export and delete Customer Personal Data yourself through the Service at any time.
11.2 When the Agreement ends, we will, on your written request made within 30 days, return your Customer Personal Data in a common machine-readable format. After that, we will delete Customer Personal Data from our systems within 90 days, and from backups when they expire in the ordinary course, unless the law requires us to keep it. Until it is deleted we will keep protecting it under this DPA.
12. Liability
Each party’s liability under this DPA is subject to the limitations and exclusions in the Agreement. Nothing in this DPA limits liability that cannot be limited by law, or any rights of Data Subjects under the SCCs.
13. General
13.1 Order of precedence. If this DPA conflicts with the Agreement on the processing of Customer Personal Data, this DPA prevails.
13.2 Changes. We may update this DPA to reflect changes in Data Protection Laws, in our Subprocessors, or in the Service. We will give you at least 30 days’ notice of material changes. Changes to the list of Subprocessors follow section 6.
13.3 Governing law. This DPA is governed by the law that governs the Agreement, except where the SCCs or the UK Addendum require otherwise.
13.4 Contact. Questions about this DPA or our data protection practices go to support@eventlink.co.
Annex I: Details of processing
Data exporter: the Customer, as a Controller (or Processor). Contact details are those of the workspace owner on the Eventlink account.
Data importer: Eventlink Technologies LTD, 71-75 Shelton Street, Covent Garden, WC2H 9JQ, London, United Kingdom, as Processor. Contact: support@eventlink.co.
Subject matter and nature of processing: hosting, storing, organising, transmitting and deleting data in order to provide the Eventlink platform: event pages and registration forms, guest and contact management, check-in, email sending, integrations, and AI-assisted features that you choose to use.
Purpose: to provide the Service to you as described in the Agreement, and to follow your instructions.
Duration: for the term of the Agreement, plus the return and deletion period in section 11.
Frequency of transfer: continuous, for as long as you use the Service.
Categories of Data Subjects:
- event attendees, registrants and guests of your events;
- your contacts and prospects, for example people you email or import;
- your workspace members and other users you invite.
Categories of Customer Personal Data:
- identity and contact details: name, email address, phone number, job title, company;
- registration answers and any other information you ask for in a form or that attendees choose to submit;
- event activity: registration status, check-in, ticket and attendance records, email delivery and engagement events;
- content you provide, such as names and photos on event pages;
- technical data: IP address, device and browser information, and workspace member sign-in records.
Sensitive data: the Service is not designed to collect special categories of personal data (as defined in Article 9 of the EU GDPR) or data about criminal convictions. You must not ask attendees for such data through the Service unless you have confirmed with us in writing that the safeguards below are enough for your use. If you do, the measures in Annex II apply.
Competent Supervisory Authority: the authority of the EU Member State where you are established, or where your EU representative is established. For UK transfers, the UK Information Commissioner’s Office.
Annex II: Technical and organisational measures
We apply the following measures, and review them as the Service changes.
Encryption. Data is encrypted in transit using TLS. Data at rest in our managed databases and object storage is encrypted by our infrastructure providers.
Access control. Access to production systems and Customer Personal Data is limited to personnel who need it for their role, and is protected by individual accounts and multi-factor authentication. Workspace members sign in with accounts that support single sign-on and two-factor authentication, and workspace access is controlled by roles. Administrative actions are recorded in audit logs.
Tenant separation. Each workspace’s data is logically separated from other workspaces and is accessed through the application using the workspace’s own permissions.
Secrets management. Credentials and API keys are held in a dedicated secrets manager, not in source code, and integration tokens are stored server-side.
Network and application security. Traffic passes through Cloudflare’s edge, with rate limiting on our API. Our services run in managed containers and edge workers, and our code goes through peer review and automated tests and checks before it is deployed.
Monitoring. We monitor availability and errors, and investigate security events and abuse reports.
Backups and resilience. Our managed databases are backed up, and we can restore from those backups after an incident.
Incident response. We keep a process for detecting, assessing, containing and reporting security incidents, including notice to customers as described in section 5.2.
Personnel. People with access to Customer Personal Data are bound by confidentiality obligations.
Vendor management. We review Subprocessors for data protection before we engage them and put written terms in place with them.
Data minimisation and deletion. We process only the data needed to provide the Service. Customers can export and delete their data, and we delete data after the Agreement ends as set out in section 11.
We do not currently hold third-party security certifications such as SOC 2 or ISO 27001, and we do not claim them.
Annex III: Subprocessors
The Subprocessors below process Customer Personal Data to provide the Service. The list is current as of the “Last updated” date on this page. A longer public disclosure, including processing activities and data categories, is at eventlink.co/sub-processors. If that page and this Annex differ, this Annex controls for the Agreement until both are updated together.
| Subprocessor | Purpose | Location |
|---|---|---|
| Google Cloud (Google Cloud EMEA Limited) | Application hosting (Cloud Run), secrets, container registry | Belgium (europe-west1) |
| Cloudflare, Inc. | Network and edge compute, DNS, queues, object storage, database connection proxy | Global edge network |
| Neon, Inc. | Managed PostgreSQL database for the Service | European Union (eu-central-1) |
| Resend, Inc. | Sending transactional and event emails on your behalf | United States |
| Stripe Payments Europe, Ltd. | Subscription billing and payments for workspace owners | European Union and United States |
| Functional Software, Inc. (Sentry) | Error and performance monitoring | United States |
| PostHog, Inc. | Product analytics for the dashboard and event pages, using PostHog’s EU region | European Union |
| AI model providers, via an AI gateway: OpenAI, Anthropic, Google | Generating content when you use AI features. Only the data you submit to a feature is sent. | United States |
Where a Subprocessor is based outside the UK and EEA, the transfer mechanisms in section 7.2 apply.
To receive notice of changes to this list, write to support@eventlink.co with the subject “Subprocessor updates”.
Questions about this page? Email support@eventlink.co.
