COMPANY
Personal Data Processing Addendum (DPA)
pursuant to art. 28 of Regulation (EU) 2016/679 (“GDPR”)
Version: 2026.11 — Effective Date: November 2, 2026
This version supersedes version 2026.03 of March 31, 2026 and version 2026.02.02 published on the website.
1. Parties, incorporation and precedence
1.1 Parties
This Personal Data Processing Addendum (“DPA”) is concluded between:
1) the Customer/Organizer who accepts an Order and/or uses the Services (“Customer” or “Client”), acting as data controller (“Controller”) or, in the cases referred to in Section 3.3, as processor on behalf of an End Client;
and
2) the Eventboost company that provides the Services as the Contracting Entity indicated in the Order and/or on the invoice (“Eventboost” or “Processor”), acting as processor or, in the cases referred to in Section 3.3, as sub-processor.
1.2 Incorporation
The DPA is incorporated by reference and constitutes an essential part of the Contract between the Parties (Master Terms + Order), in the version published on the date the Order is accepted. Previous versions are archived and available on request.
1.3 Precedence
In the event of a conflict between the DPA and other contractual documents, the DPA prevails only on matters related to the processing of personal data.
1.4 Scope
The DPA exclusively governs the processing where Eventboost acts as a Data Processor on behalf of the Client.
2. Definitions
2.1 The terms “personal data”, “processing”, “personal data breach”, “data subject”, “controller”, “processor”, “supervisory authority” have the meanings defined by the GDPR.
2.2 Customer Data: data and content provided or created by the Customer through the Services, including personal data of Participants (attendees) processed by Eventboost on the Customer’s behalf.
2.3 Services: The Eventboost SaaS platform and related modules, as described in the Order/Documentation.
3. Roles and categories of processing
3.1 Roles
For Participants’ personal data processed in the context of Client events:
- the Customer acts as the Data Controller;
- Eventboost acts as Data Processor pursuant to art. 28 GDPR.
For events organised on behalf of an End Client, Section 3.3 applies.
3.2 Processing as Eventboost Controller. For data related to the Customer concerning its account, administration, billing, security, support, and management of the business relationship, Eventboost may act as a Controller according to its own Privacy Policy (not governed by this DPA).
3.3 Agencies and End Clients
3.3.1 Roles. Where the Customer uses the Services for events organised on behalf of its own client that is the controller of the data (“End Client”), the Customer acts as processor on behalf of the End Client and Eventboost as sub-processor pursuant to Article 28(2) and (4) GDPR. For data that the Customer processes for its own purposes (e.g. its own contact databases), the Customer remains the controller and Section 3.1 applies. Where the Customer and the End Client jointly determine the purposes and means of the processing, they set out their respective roles under Article 26 GDPR; vis-à-vis Eventboost, instructions are in any case given by the Customer.
3.3.2 Identification of the controller in the Services. For each event or workspace, the Customer specifies in the settings of the Services who the controller is (the Customer itself or the End Client) and keeps this information up to date. This indication constitutes a documented instruction under Section 5.1 and determines the controller shown in communications to Participants, in the preference centre and in exports.
3.3.3 Customer warranties. The Customer warrants that: (a) the processing on behalf of the End Client is governed by a contract or other legal act compliant with Article 28(3) GDPR; (b) the End Client has authorised in writing, specifically or generally, the engagement of Eventboost and of Eventboost’s sub-processors referred to in Section 8; (c) the instructions given to Eventboost comply with those received from the End Client; (d) data processed on behalf of an End Client are not used for events of other End Clients or for the Customer’s own purposes, unless authorised by the End Client and supported by an appropriate legal basis.
3.3.4 Equivalent obligations. For the purposes of Article 28(4) GDPR, this DPA constitutes the contract binding Eventboost as sub-processor. If the contract between the Customer and the End Client provides for additional or stricter obligations (e.g. shorter notification deadlines, data location, specific security measures), the Customer notifies them to Eventboost in writing before processing begins; such obligations bind Eventboost only if accepted in writing.
3.3.5 Communications along the chain. Eventboost provides the Customer with all communications required by this DPA (incidents and breaches, changes to sub-processors, requests from data subjects and authorities); the Customer forwards them to the End Client without undue delay. The first notification within 48 hours under Section 10.1 is given to the Customer also to enable it to inform the End Client promptly. Objections to sub-processors (Section 8.4) and audit requests (Section 12) of the End Client are exercised through the Customer; on-site audits are allowed once per calendar year for each End Client, in aggregate between the End Client and the Customer.
3.3.6 Return and erasure at the request of the End Client. If the Customer has ceased to exist in law, is subject to insolvency proceedings or has factually disappeared, the End Client may request Eventboost directly to return or erase the data processed on its behalf. Eventboost may make this subject to verification of the identity and powers of the requesting party. The End Client may enforce this Section 3.3.6 as a third-party beneficiary.
3.3.7 End of the End Client engagement. If the relationship between the Customer and the End Client ends while the Contract continues, the Customer exports and/or erases the data processed on behalf of that End Client, in accordance with the instructions received from it; the Services allow export and erasure separately for each controller. Eventboost is not required to verify the termination of relationships between the Customer and End Clients.
3.3.8 Liability and tripartite addendum. Without prejudice to Section 3.3.6, Eventboost assumes no direct obligations towards the End Client, except under an addendum signed by the Customer, the End Client and Eventboost. The Customer remains fully liable to the End Client under Article 28(4) GDPR. In any case, liability caps and audit rights remain single and aggregate between the Customer and the End Client and are not cumulative.
4. Subject matter, duration, nature, and purpose (Art. 28(3) GDPR)
4.1 Subject matter
Provision of Eventboost SaaS services and related activities (hosting, maintenance, support, security, backup).
4.2 Duration
For the duration of the Contract and, after termination, for the necessary technical period for return/export and erasure, in accordance with Section 11.
4.3 Nature and purpose
Processing necessary for: providing the Services, managing events and registrations, transactional communications related to the event (email and, where enabled, SMS), measurement of email opens and clicks according to the settings chosen by the Customer (Annex E), check-in/accreditation, reporting, functionalities requested by the Customer, and technical support.
4.4 Categories of data subjects and data
As per Annex A.
5. Documented Customer Instructions
5.1 Eventboost processes personal data only following documented instructions from the Customer, including platform configurations, event settings, and written requests.
5.2 If Eventboost considers that an instruction violates the GDPR or other applicable laws, it shall notify the Customer accordingly (Art. 28(3)(h)).
5.3 Prohibition of autonomous purposes. Eventboost does not use Participants’ data processed on behalf of the Customer for its own purposes (e.g., marketing to Participants), unless otherwise and lawfully instructed by the Customer and within the limits permitted by law. Furthermore, Eventboost does not use Customer Data to train, develop or improve artificial intelligence models, its own or third parties’, unless instructed in writing by the Customer.
5.4 Special categories and judicial data. The Client must not process special categories of data (art. 9 GDPR) or judicial data (art. 10 GDPR) unless: (i) it is strictly necessary for the event; (ii) there is a legal basis and the Client fulfills information or consent obligations; (iii) configurations are minimized. The Customer remains responsible for the lawfulness of the provision.
5.5 Artificial intelligence features. As at the date of this DPA, the Services do not include artificial intelligence features. If the Customer enables such features when they become available, Eventboost will process Customer Data only to provide the requested feature, will notify in advance any model providers with access to Customer Data (sub-processors under Section 8) and will provide the information needed for the impact assessment and for informing data subjects.
5.6 Email tracking. The processing of data collected through tracking pixels or similar techniques in communications sent by the Customer through the Services is governed by Annex E.
6. Authorized personnel and confidentiality
6.1 Eventboost ensures that the personnel authorized to process the data are bound by confidentiality obligations and receive appropriate instructions (Art. 28(3)(b)).
7. Technical and organizational measures (Art. 32 GDPR)
7.1 Eventboost implements technical and organizational measures appropriate to the risk, including (but not limited to): access controls, environment segregation, logging, encryption in transit, backup, hardening, and vulnerability management.
7.2 The minimum measures are outlined in Annex B. Eventboost can revise them for technical and safety improvements, maintaining a level suitable for the risk.
7.3 Security incidents. Eventboost informs the Customer without undue delay and, where reasonably possible, within 48 hours of internal confirmation, of significant security incidents affecting the availability, integrity or confidentiality of the Services, even where they do not involve a personal data breach. Eventboost provides the available information to enable the Customer to comply with any notification obligations it may have (e.g. under Italian Legislative Decree 138/2024 implementing the NIS2 Directive).
8. Sub-processors (Art. 28(2)–(4) GDPR)
8.1 The Client grants Eventboost overall authorization to appoint sub-processors for providing the Services.
8.2 The updated list of sub-processors (with indication of role, location and safeguards for any transfers) is available upon request to be sent to: privacy@eventboost.com.
8.3 Eventboost imposes obligations on sub-processors no less stringent than those provided for in this DPA.
8.4 Objection
Eventboost notifies the Customer of any addition or replacement of sub-processors at least 30 days in advance, by email to the administrative contact indicated in the Order or in the account; within that period the Customer may object on reasonable grounds related to data protection. If the Parties do not find a reasonable alternative, the Client may terminate the affected part of the Services, within the limits and according to the rules of the Agreement.
9. Assistance to the Customer
9.1 Rights of the data subjects
Taking into account the nature of the processing, Eventboost assists the Customer with appropriate technical and organizational measures to respond to the requests of data subjects (Articles 15–22 GDPR). If a data subject contacts Eventboost directly in relation to data processed on behalf of the Customer, Eventboost forwards the request to the Customer without undue delay and does not respond on the merits, unless instructed by the Customer.
9.2 DPIA and consultations
Eventboost provides reasonable assistance in relation to DPIA and consultations with the Authority (Articles 35–36 GDPR), within the limits of available information and, if applicable, on reasonable economic terms.
10. Data Breaches
10.1 Eventboost notifies the Customer, without undue delay, of a personal data breach related to Customer Data pursuant to Art. 33(2) GDPR, providing the reasonably available information on the nature of the incident, the measures taken, the possible impact and mitigation actions.
Where reasonably possible, based on the nature of the incident and the information available at the time of the initial qualification, Eventboost undertakes to make the first notification to the Customer within 48 hours of the internal confirmation of the breach of personal data relating to Customer Data, it being understood that further information may be provided subsequently in a progressive manner.
10.2 Eventboost does not communicate directly to the data subjects unless required by law or lawful instruction by the Customer.
11. Return, erasure and retention
11.1 Upon termination of the Contract, Eventboost shall make the Customer Data available to the Client for export according to the standard functionalities of the Services and in accordance with the provisions of the Contract.
11.2 After the post-termination availability period provided for in the Contract/Privacy Policy, Eventboost proceeds with the deletion or anonymization of Customer Data, except for legal obligations or cyclical backups.
11.3 Switching (Regulation (EU) 2023/2854 – Data Act). If the Customer exercises the right to switch to another provider or to data portability under Section 11-bis of the Master Terms, the periods set out therein apply (transition period and data retrieval period of at least 30 days). At the end of the data retrieval period, Eventboost erases all Customer Data, including data in backups upon completion of the rotation cycle indicated in Annex B6, except where required by law.
12. Audit and accountability (Art. 28(3)(h) GDPR)
12.1 Eventboost provides the Client with the information necessary to demonstrate compliance with the obligations of the DPA.
12.2 Upon reasonable request, the Customer may carry out documentary checks. On-site audits are allowed only: (i) subject to appropriate notification; (ii) once a year; (iii) during business hours; (iv) with respect to confidentiality and security; (v) at the Customer’s expense; and (vi) unless Eventboost provides equivalent reports (e.g., certifications, attestations, independent audit reports) that are reasonably sufficient.
13. International transfers
13.1 If Customer Data is transferred out of the EU/EEA to countries not covered by an adequacy decision, Eventboost applies appropriate safeguards pursuant to Chapter V GDPR, including the Standard Contractual Clauses adopted by Decision (EU) 2021/914 (as amended): Module 3 (processor to sub-processor) for transfers to sub-processors; Module 2 (controller to processor) where a Customer established in the EEA uses an Eventboost entity established in a third country without an adequacy decision; Module 4 for the return of data to a Customer established in a third country. For recipients established in the United States and certified under the EU-U.S. Data Privacy Framework, the transfer may rely on adequacy Decision (EU) 2023/1795; the SCCs remain available as an alternative safeguard.
13.2 United Kingdom. Where the UK GDPR applies, Eventboost applies the UK Addendum to the EU SCCs or the IDTA, according to the mechanism indicated in the transfer documentation.
13.3 Switzerland. Where Swiss law (nFADP/FADP) is applicable, the SCCs are supplemented with the adaptations required by Swiss law (e.g. references to the Federal Data Protection and Information Commissioner, data subject rights, forum/law).
14. Additional regulations (UK / Switzerland)
Where the processing also falls under the UK GDPR/Data Protection Act 2018 or nFADP/FADP, the Parties undertake to comply with the applicable legislation and the related transfer and transparency requirements.
15. Liability
Responsibilities and limitations are governed by the Agreement (Master Terms/Order). This DPA does not extend Eventboost’s liability beyond what is provided for in the Agreement and mandatory law.
16. Privacy contacts
The privacy contacts/DPO (if appointed) and the channels for privacy requests are indicated in the Eventboost Privacy Policy.
ANNEX A
DETAILS OF THE PROCESSING (art. 28(3) GDPR)
1. Subject matter of the processing
Provision of Eventboost Services in SaaS mode for the management of Customer events (e.g.: event creation, registration pages, registration management, invitations and communications, check-in, badge printing, reporting, integrations/APIs, sending of SMS where enabled, any ticketing where required by the Order).
2. Duration of processing
For the duration of the applicable Contract/Order, and thereafter for the expected retention periods:
- Event Data (Single Event): usually available in the reserved backend for 12 months from the conclusion of the event (unless otherwise agreed in writing).
- Post-expiration account/event data: usually up to 6 months from the expiration of the relationship (including trial) to allow export/reactivation, except for legal obligations and/or cyclical backups according to DPA and Privacy Policy.
3. Nature and purpose of the processing
Collection, recording, organization, structuring, storage, consultation, use, communication (limited to sub-processors), erasure/destruction, necessary to:
- provide the functionality of the Service;
- ensure security, business continuity, support and maintenance;
- execute documented instructions from Customer (including in-platform configurations and support requests).
4. Categories of data subjects
- Participants/Attendees (guests, registrants, event participants);
- Speakers/sponsors/exhibitors/suppliers of the Client;
- Authorized users of the Customer (admins, staff, check-in operators);
- Customer’s contacts/import lists (invitations and communications), where uploaded.
5. Categories of personal data (typical; depend on Customer configuration)
- Identifiers and contacts: name, surname, email, telephone, company, role, country/city;
- Event registration data: responses to forms, preferences, sessions, badge fields, check-in status;
- Technical data: access logs, account identifiers, audit logs, IP (where collected), device/browser info;
- Communication data: emails and SMS sent, telephone number, RSVPs, bounces and delivery status (where applicable); email opens and clicks according to the Customer’s tracking settings (Annex E);
- Ticketing (if enabled): transaction and ticket information (note: full payment data is typically processed by the third-party payment processor as an independent controller or processor).
- Special categories (art. 9 GDPR): not provided for by default. The Client is responsible for avoiding the inclusion of special categories, except for strict necessity and adequate legal bases; if used, they must be specified in the Order and managed with additional measures.
6. Processing operations
Hosting, backup, recovery, sending of email and SMS communications (if enabled), measurement of opens and clicks according to Annex E, technical support, incident management, security monitoring, access and authorization management.
7. Roles
- Client: Controller of the data of Participants and other data subjects in the context of the events.
- Eventboost: Processor on behalf of the Client, according to documented instructions.
- Events organised by an agency on behalf of an End Client (Section 3.3): End Client as controller; Customer as processor; Eventboost as sub-processor.
Eventboost may operate as a Data Controller for account/billing/business relationship data, as described in the Privacy Policy.
ANNEX B
TECHNICAL AND ORGANISATIONAL MEASURES (TOM)
The Security Measures are risk-adjusted (Art. 32 GDPR) and apply to the processing of Customer Data within the scope of the Services.
B1. Security Governance (ISMS / ISO 27001)
Eventboost maintains a security governance framework aimed at protecting data confidentiality, integrity, and availability. Eventboost’s Information Security Management System (ISMS) is certified to ISO/IEC 27001:2022 by Scandinavian Certification AS (certificate no. ITA-10382-ISMS, first issued on 28 August 2026, valid until 28 August 2029), for the following scope: “Design, development, maintenance, delivery and support of the Software as a Service (SaaS) platform for the management of events and related digital services” (English translation of the scope stated in Italian on the certificate). The certificate is issued to Eventboost S.A. and covers the sites of Eventboost S.r.l. and Eventboost Inc.; it is available on request.
It is understood that the obligation to implement and maintain appropriate measures exists regardless of certification; the certification has informative value and does not automatically expand contractual obligations or remedies.
B2. Access Control and Identity Management
- Access to systems limited to authorized personnel according to the principle of least privilege.
- Strong authentication for administrative accounts; credential management and role rotation/segregation where applicable.
- User provisioning/deprovisioning process (joiner/mover/leaver).
- Separation between environments (e.g. production/testing) where applicable.
B3. Application Security and SDLC
- Secure development practices, vulnerability management, and remediation (patching) according to risk priorities.
- Deployment and change management controls; approval logic and change tracking where applicable.
- Hardening and secure configuration of components.
B4. Encryption and data protection
- Encryption in transit via TLS/HTTPS.
- Encryption at rest (AES) or equivalent protections for systems and backups where applicable (depending on technology/vendor).
- Logical segregation of data between tenants/customers, where applicable.
B5. Logging, monitoring and audit trail
- Logging of relevant security and administrative events; log retention according to internal policies.
- Monitoring for anomalies and alerting; observability tools for availability and performance.
B6. Availability, backup and disaster recovery
- Regular backups and tested/validated recovery procedures with reasonable periodicity.
- Measures for business continuity and resilience; incident response and recovery plans.
- Scheduled maintenance windows and urgent interventions for security/stability.
- Backups stored in the EEA on a 60-day rotation cycle; at the end of the cycle, deleted data can no longer be recovered.
B7. Incident and data breach management
- Internal process of incident management, triage, containment, remediation and post-mortem.
- Notification to the Customer of personal data breaches without undue delay and, where reasonably possible, within 48 hours of internal confirmation (Section 10), and of significant security incidents under Section 7.3; reasonable cooperation.
B8. Security of suppliers (sub-processors)
- Selection of suppliers with appropriate measures and equivalent contractual obligations (Art. 28 GDPR).
- Reasonable assessments and documentary control of critical sub-processors, based on risk.
B9. Training and confidentiality
Confidentiality commitments for staff; periodic security and privacy training where appropriate.
B10. Physical measures
Data centers/hosting typically managed by cloud providers with industry-standard physical and environmental controls.
B11. Vulnerability management and mobile applications
- Vulnerability reporting channel: security@eventboost.com.
- For mobile applications of which Eventboost is the manufacturer, notification to the competent CSIRT and to ENISA of actively exploited vulnerabilities and severe incidents, pursuant to Article 14 of Regulation (EU) 2024/2847 (Cyber Resilience Act).
B12. Data location
Customer Data is hosted on Amazon Web Services in the AWS Europe (Ireland) region, eu-west-1; hosting and backups do not involve transfers outside the EEA.
Note: The list describes categories of controls; specific details (tools, configurations, thresholds) may vary over time for continuous improvement, as long as the overall level of security is not materially reduced compared to the risks addressed.
ANNEX C
SUBPROCESSORS
C1. General Authorization
The Client gives a general authorization to the use of sub-processors for the provision of the Services (art. 28(2) GDPR), according to the updated list.
C2. List and updates
Eventboost maintains and makes available an up-to-date list of subprocessors upon request. The list shall indicate, as far as reasonably practicable:
- name of the sub-processor;
- country of processing/hosting (or regions);
- description of the service (hosting, email, SMS, support, analytics, etc.);
- safeguards adopted for any transfers outside the EEA.
C3. Notification and right to object
Eventboost will notify any addition or replacement of sub-processors at least 30 days in advance, in accordance with Section 8.4. The Customer may object in writing on reasonable grounds relating to data protection; In such a case, the parties shall cooperate in good faith to identify a commercially reasonable alternative or mitigation measure. If not possible, Eventboost may (at its discretion) allow the termination of the impacted module/service according to the remedies provided for in the Agreement, limited to the affected party.
C4. Contractual obligations towards sub-processors
Eventboost imposes data protection obligations on sub-processors that are substantially equivalent to those of the DPA, including security and support obligations.
ANNEX D
INTERNATIONAL TRANSFERS
D1. General principle
Eventboost processes and/or allows access to personal data in accordance with the rules on international transfers provided for by the applicable legislation (GDPR, UK GDPR, Swiss law).
D2. EU/EEA mechanisms (GDPR)
For transfers to countries not subject to an adequacy decision, Eventboost applies (where relevant) the EU Standard Contractual Clauses (Decision (EU) 2021/914), with the modules indicated in Section 13.1, and appropriate supplementary measures based on the risk. For US recipients certified under the EU-U.S. Data Privacy Framework, adequacy Decision (EU) 2023/1795 may apply.
D3. United Kingdom
Where the UK GDPR applies, Eventboost applies the UK Addendum to the EU SCCs or the IDTA, as applicable, as provided in the DPA.
D4. Switzerland
Where applicable, Eventboost adopts the clauses/adjustments required by Swiss law (nFADP/FADP) for cross-border transfers, according to recognized practices and models.
D5. Documentation and transparency
At the reasonable request of the Client, Eventboost makes available information on the transfer mechanism applied (e.g. SCC/UK Addendum reference) and on the relevant sub-processors, within the limits of confidentiality and security.
ANNEX E
EMAIL COMMUNICATION TRACKING
E1. Subject matter
This Annex governs the processing of data collected through tracking pixels and, where enabled, through links containing a recipient identifier, included in email communications sent by the Customer through the Services. This processing falls under Article 122 of Italian Legislative Decree 196/2003 and is governed by the Guidelines of the Italian Data Protection Authority (Garante per la protezione dei dati personali) adopted by decision no. 284 of 17 April 2026, or by equivalent applicable law.
E2. Roles
The Customer, as Controller, decides whether and for which purposes to enable tracking. Where the Customer uses the Services on behalf of an End Client under Section 3.3, the Controller is the End Client and references to the Controller in this Annex are to be read as references to the End Client; the Customer warrants that the settings configured for each End Client reflect the instructions received from it. The Controller is responsible for informing recipients and for collecting and documenting consent; Eventboost provides a template privacy notice.
E3. Instructions through the settings of the Services
- Before enabling any form of tracking, the Customer completes, for each Controller, the privacy settings of the Services, specifying at least: the identity of the Controller and the applicable privacy notice, whether individual tracking with consent is enabled, whether read receipts are enabled for service communications, and the retention period. Until these settings are completed, communications are sent without pixels or tracked links.
- The settings constitute documented instructions under Section 5.1. Each change is recorded with its date, version and the user who made it.
- The Customer instructs Eventboost to enable individual tracking for promotional purposes only for recipients for whom the Customer declares, through the settings of the Services, contact import or the APIs, that it holds valid consent, specifying its date and source. Registration for an event, purchase of a ticket or consent to receive promotional communications are not, in themselves, considered consent to tracking, unless the privacy notice provided by the Controller expressly so provides.
- Consent is recorded and used only for communications of the Controller that collected it. Eventboost does not combine consent status or open and click data across different Customers or Controllers and does not use them for its own purposes (Section 5.3).
E4. Classification of communications
For the purposes of this Annex, what matters is the purpose of the tracking, not the name of the communication. The Services assign each communication to one of the following categories:
| Category | Examples | Tracking allowed |
|---|---|---|
| Security | Password reset, access codes, account sign-in alerts | No pixels or tracked links |
| Service | Registration confirmation; delivery of tickets, QR codes or badges; reminders and logistics updates sent to registrants; receipts and payment confirmations; certificates of attendance; event materials promised to registrants; notices of meeting and voting communications | Aggregate and anonymous statistics; individual only if the Customer enables read receipts, under the conditions of Section E6 |
| Promotional | Invitations and save-the-dates; reminders to register; newsletters, offers and announcements of new events; satisfaction surveys | Aggregate and anonymous statistics; individual only with the recipient’s consent |
A service communication that also contains promotional content (e.g. offers, sponsor banners, promotion of other events) is treated as promotional. For communications addressed to employees of the Controller, the Controller also assesses whether tracking is compatible with the rules on remote monitoring of workers (Article 4 of Italian Law 300/1970 or equivalent legislation).
E5. Features provided by Eventboost
- individual tracking disabled by default in the absence of an indication of consent;
- recording of the tracking consent status for each contact and each Controller, with date, source and version of the privacy notice;
- a link in every communication to opt out of tracking only while continuing to receive emails, and sending of pixel-free emails to recipients who have opted out;
- a separate preference centre for each Controller, showing its identity and privacy notice;
- an aggregate and anonymous statistics-only mode, with a pixel that is the same for all recipients and anonymisation of IP address and email client data;
- a summary, before each send, of the number of recipients tracked individually and in statistical form;
- a layered privacy notice accessible from communications and from the preference centre.
E6. Service communications
Open data from service communications are processed only for technical, security or service-delivery purposes for the recipient. If the Customer enables read receipts, the opening of an individual message is visible only in the participant’s record, to verify delivery and provide assistance, and is not used for promotional purposes, segmentation, automations, profiling or export to marketing systems. The Controller informs recipients accordingly.
E7. Non-compliant instructions
The Services do not allow configurations contrary to this Annex. Eventboost does not execute instructions, including those given through support, aimed at enabling individual tracking for promotional purposes without consent, inserting pixels in security communications or using data from service communications for promotional purposes, and informs the Customer in accordance with Section 5.2.
E8. Technical measures
Eventboost uses non-intelligible, non-sequential identifiers, linked to the email address in a separate internal layer of the platform with restricted access, so that the email address does not appear in the technical request generated when the pixel is loaded. In statistics mode, technical data are anonymised. Withdrawal of consent takes effect immediately, including for pixels contained in communications already sent.
E9. Sub-processors and retention
Email delivery providers are sub-processors under Section 8 and apply configurations consistent with this Annex. Open and click data are retained for the period set by the Customer for each Controller in the settings of the Services and in any case for no longer than twelve months, after which they are deleted or anonymised.
E10. Assistance
Eventboost assists the Customer, in accordance with Section 9, in responding to data subject requests relating to tracking, including by providing an export of consent status and opt-outs. Requests received directly by Eventboost are handled in accordance with Section 9.1.
E11. Transitional provision
Until 31 December 2026, or until any earlier date on which Eventboost notifies the Customer that the privacy settings referred to in Section E3 are available in the Services, individual tracking of opens and clicks is disabled for all communications, including read receipts for service communications. By way of derogation from Section E3, during this period only the aggregate and anonymous statistics mode described in Section E5 is permitted. At the end of the transitional period, Section E3 applies in full.
Intelligent event management for modern organizations
Product & Solutions

ISO 27001 Certified

GDPR Compliant

256-bit SSL Encryption





