Skip to content

Legal documents

Data processing agreement

Version 1.1, published 22 November 2026.

Version 1.1. Last updated 22 November 2026.

This data processing agreement ("DPA") forms part of the terms of service between Elements Marketing & Communications LTD ("Elements", the "Processor") and the organisation that subscribes to Engage by Elements (the "Customer", the "Controller"). It sets out the terms required by Article 28 of the GDPR and, where it applies, Article 28 of the UK GDPR.

1. Definitions

1.1 GDPR means Regulation (EU) 2016/679. UK GDPR means the GDPR as it forms part of the law of the United Kingdom. Data Protection Law means the GDPR, the UK GDPR where it applies, the Data Protection Acts 1988 to 2018 (Ireland), and any other law on the processing of personal data that applies to a party.

1.2 Controller, processor, data subject, personal data, personal data breach, processing and supervisory authority have the meanings given in the GDPR.

1.3 Customer Personal Data means personal data processed by Elements on the Customer's behalf in providing Engage, namely:

  • (a) Survey Data: the email addresses and segment attributes (such as team and location) of people the Customer invites to answer surveys, and their names where the Customer adds them to a saved list; the participation record; survey answers, including free-text comments; the Culture Compass answers and results of the Customer's users; and Culture Audit and pulse check responses;
  • (b) any other personal data the Customer or its users put into Engage as content, such as names in moment notes.

1.4 Sub-processor means a third party engaged by Elements to process Customer Personal Data.

1.5 SCCs means the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914.

1.6 Lapse Date means the day the Customer's organisation becomes read-only after its subscription ends or a payment remains unpaid after the grace period, as set out in the terms of service.

2. Roles and scope

2.1 For Customer Personal Data, the Customer is the controller and Elements is the processor.

2.2 For account, billing and contact data about the Customer's users, Elements is a controller, as set out in its privacy notice. This DPA does not apply to that data.

2.3 The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in Annex 1.

3. Instructions

3.1 Elements processes Customer Personal Data only on the Customer's documented instructions, unless required to do otherwise by EU or member state law, in which case Elements will tell the Customer before processing unless that law prohibits it.

3.2 The Customer's instructions are this DPA, the terms of service, and the Customer's use and configuration of Engage, such as creating a survey, adding respondents, choosing segment attributes and deleting data.

3.3 Elements will tell the Customer straight away if, in its opinion, an instruction infringes Data Protection Law.

4. The Customer's obligations

The Customer is responsible for:

  • (a) having a lawful basis for each survey and for the Customer Personal Data it puts into Engage;
  • (b) giving data subjects the information required by Articles 13 and 14, including telling employees about surveys before they are sent;
  • (c) not putting special category data (Article 9), criminal offence data (Article 10), or anyone's age or date of birth into segment attributes, uploads or other fields, and not asking respondents for it;
  • (d) not using Engage to identify, or try to identify, any respondent from their answers;
  • (e) carrying out any data protection impact assessment it needs, including for respondents under 18. Elements provides a template in the help centre;
  • (f) stating, when it sets up each survey, whether anyone invited could be under 18 or under 16, and giving those respondents information in clear and plain language they can understand (Article 12(1)).

5. Anonymity commitments

5.1 Engage is designed so that no person, including the Customer and Elements, can link a respondent to their answers. Elements will maintain, as a minimum, the following controls for the duration of this DPA:

  • (a) the participation record (who was invited and whether they responded) and the answers are stored separately, with no key or reference that joins them;
  • (b) a response link sent to one person by email is single-use and stored only as a one-way hash. Where the Customer chooses a shared link instead, the link is stored only as a one-way hash, each person who opens it is given a single-use response token, and no record is kept of who opened it;
  • (c) no IP address, user agent, or timestamp finer than the day is stored with answers, and no analytics or error reporting with user context runs on respondent pages;
  • (d) results are shown only where at least the score threshold of responses has been received. The default threshold is 5, it cannot be set below 3, it applies to every segment, and it locks when a survey opens;
  • (e) a segment result is hidden if the segment, or the remainder of its parent group, is below the threshold, and combining filters cannot narrow a group below the threshold;
  • (f) free-text comments are shown only for groups of 10 or more, are treated as personal data, and respondents are asked not to include names;
  • (g) Elements staff see aggregate results only, under the same thresholds, and impersonating a customer user does not reveal more;
  • (h) the email addresses of the people invited to a survey, and the record of whether each responded, are deleted 30 days after the survey closes. Names and email addresses the Customer keeps in a saved list stay there until the Customer removes them, or until the list has not been used for a survey or added to for 24 months, and a saved list never records who answered;
  • (i) Engage never asks respondents their age. Where the Customer states that a survey may include anyone under 18: the threshold cannot be set below 5; any group the Customer marks as possibly mostly under 18 needs at least 10 responses, and its complement is protected in the same way; comments are not shown for those groups; at most 2 reminders are sent; and respondents see an additional plain-language notice. Where a survey may include anyone under 16, it contains no free-text questions.

5.2 Elements will not change these controls in a way that weakens respondents' anonymity without giving the Customer at least 30 days' notice.

5.3 The controls in 5.1 apply to surveys answered through a response link. They do not apply to the Culture Compass taken by a signed-in user of the Customer: that take is stored against the user's account, only that user sees their own result, and a combined result is shown to the Customer's users once 3 or more of them have taken it.

6. Confidentiality

Elements ensures that everyone it authorises to process Customer Personal Data is bound by confidentiality, by contract or by law.

7. Security

7.1 Elements implements appropriate technical and organisational measures under Article 32, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing, and the risks to data subjects. The measures are described in Annex 2.

7.2 Elements may update the measures, provided the overall level of security is not reduced.

8. Sub-processors

8.1 The Customer gives Elements general written authorisation to engage sub-processors. The current list is published on the sub-processors page.

8.2 Elements will tell the Customer of any intended addition or replacement of a sub-processor at least 30 days in advance, by email to the Customer's owners and on the sub-processors page.

8.3 The Customer may object on reasonable data protection grounds within that notice period. The parties will discuss the objection in good faith. If it cannot be resolved, the Customer may end its subscription by notice before the change takes effect and receive a pro rata refund of any prepaid fees for the period after termination.

8.4 Elements imposes on each sub-processor, by contract, data protection obligations that give at least the same protection as this DPA, as required by Article 28(4). Elements remains fully liable to the Customer for each sub-processor's performance of those obligations.

9. International transfers

9.1 Elements stores Customer Personal Data in the European Union.

9.2 Where a sub-processor processes Customer Personal Data outside the European Economic Area, Elements ensures the transfer is covered by an adequacy decision or by the SCCs (Module 3, processor to processor) with any supplementary measures needed. For data subject to the UK GDPR, Elements relies on UK adequacy regulations, the UK Extension to the EU-US Data Privacy Framework or the UK International Data Transfer Addendum, as applicable.

10. Assistance with data subject rights

10.1 Taking into account the nature of the processing, Elements will help the Customer, by appropriate technical and organisational measures, to respond to requests from data subjects to exercise their rights.

10.2 Engage provides self-service tools for this, including data export and deletion.

10.3 Because survey answers are stored without any link to the respondent, neither party can identify an individual respondent's answers. The parties acknowledge that Article 11 of the GDPR applies to those answers.

10.4 If Elements receives a request from a data subject about Customer Personal Data, it will pass it to the Customer without undue delay and will not respond itself except to confirm it has been passed on.

11. Other assistance

Elements will help the Customer, taking into account the nature of the processing and the information available to Elements, to meet its obligations under Articles 32 to 36: security, notification of personal data breaches, data protection impact assessments and prior consultation with a supervisory authority.

12. Personal data breaches

12.1 Elements will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.

12.2 The notice will describe, as far as is known at the time, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Elements will provide further information as it becomes available.

12.3 Elements will take reasonable steps to contain and investigate the breach and reduce its effects, and will cooperate with the Customer.

13. Deletion and return

This section sets out the Customer's choice under Article 28(3)(g) between deletion and return of Customer Personal Data at the end of the service.

13.1 Return. The Customer's owners can export Customer Personal Data from Engage at any time while the organisation exists, including while it is read-only and during a deletion grace period. The export contains what the Customer's users can see in Engage, including aggregate results above the response thresholds and comments for groups at or above the comment threshold. Individual survey answers, results below the thresholds and participant lists are not exported, because they are stored without any link to respondents and releasing them could identify respondents.

13.2 End of the subscription. When the subscription ends, or a payment is still unpaid after the grace period, the Customer's organisation becomes read-only on the Lapse Date. The Customer instructs Elements to delete all Customer Personal Data, including stored files, 90 days after the Lapse Date unless the Customer subscribes again before then. Elements emails the Customer's owners and billing contact on the Lapse Date and 30, 60, 83 and 89 days after it.

13.3 Changing the instruction. Before deletion, the Customer can change the instruction in 13.2 by exporting its data, by an owner deleting the organisation (13.4), by subscribing again, or by an owner asking once in writing to info@elementsmarketing.ie for up to 90 more days.

13.4 Deletion by an owner. When an owner deletes the Customer's organisation, Elements deletes all Customer Personal Data, including stored files, after a 14-day grace period.

13.5 Backups. Copies in backups are deleted as those backups expire: database point-in-time backups within 7 days, and nightly backup copies of the database and of stored files within 36 days. Until then backups are used only to restore Engage after a failure, and a restore never brings back data that has been deleted.

13.6 Confirmation. Elements confirms to the Customer's billing contact by email, within 7 days of deletion under 13.2 or 13.4, that the deletion has been completed.

13.7 Survey emails. The email addresses of the people invited to a survey, and the participation record, are deleted 30 days after each survey closes, whatever the state of the subscription. Names and email addresses in a saved list are deleted when the Customer removes them, when the list has not been used for a survey or added to for 24 months, or with the organisation under 13.2 or 13.4, whichever comes first.

13.8 Storage required by law. Elements keeps Customer Personal Data after the dates in this section only where EU or member state law requires it to, or where the Customer instructs it in writing. Elements tells the Customer of any such legal requirement as soon as it is aware of it, unless the law prevents it.

14. Information and audits

14.1 Elements will make available to the Customer all information necessary to demonstrate compliance with Article 28, including this DPA, its security measures and its sub-processor list.

14.2 If the Customer reasonably needs more, it may request an audit or inspection by itself or an independent auditor bound by confidentiality, on at least 30 days' notice, no more than once in any 12-month period unless required by a supervisory authority or following a personal data breach. The audit is limited to what is needed to show compliance with Article 28, takes place during normal working hours without disrupting Elements' operations, and each party bears its own costs. Elements may satisfy a request with a current independent audit report or certification where one covers the point raised.

15. Records

Elements keeps a record of its processing activities as a processor, as required by Article 30(2).

16. Liability

Each party's liability under this DPA is subject to the limits in the terms of service, except where Data Protection Law does not allow it to be limited. There is no separate cap for claims under this DPA.

17. Term and order of precedence

17.1 This DPA applies for as long as Elements processes Customer Personal Data.

17.2 If this DPA conflicts with the terms of service, this DPA prevails for anything about personal data. If the SCCs apply and conflict with this DPA, the SCCs prevail.

18. Governing law

This DPA is governed by the laws of Ireland, and the courts of Ireland have exclusive jurisdiction, except where the SCCs require otherwise.

Annex 1: Description of the processing

Subject matterProviding Engage by Elements to the Customer
DurationThe term of the Customer's subscription, then until deletion under section 13 (90 days after the Lapse Date at the latest, unless extended under 13.3)
NatureCollection, storage, organisation, aggregation, display, transmission by email (invitations and reminders) and deletion
PurposeRunning the Customer's culture surveys and showing aggregate results, next best actions and plans
Data subjectsThe Customer's employees, workers and contractors invited to surveys, which may include employees under 18 where the Customer states so; the Customer's users who take the Culture Compass; other people named in content the Customer enters
Types of personal dataEmail addresses; names, where the Customer adds them to a saved list; segment attributes chosen by the Customer, such as team and location; participation status; survey answers, including free-text comments; Culture Compass answers and results of the Customer's users; any personal data in content the Customer enters, such as names in moment notes
Special category dataNot intended. Free-text comments could contain it if a respondent writes it, despite the prompt not to include names or personal details
RetentionEmail addresses of people invited to a survey, and participation records: 30 days after the survey closes. Saved lists: until the Customer removes a person, or 24 months after the list was last used for a survey or added to. Answers: life of the Customer's organisation unless the Customer sets a shorter period. Organisations whose subscription has ended: deleted 90 days after the Lapse Date. Organisations deleted by an owner: deleted after 14 days. Backups: expire within 36 days of deletion
Sub-processorsAs listed on the sub-processors page

Annex 2: Technical and organisational measures

  • Hosting and location. Database (PostgreSQL) and application servers in Dublin, Ireland. Files in EU-jurisdiction object storage, private by default and served only through short-lived signed links.
  • Encryption. All connections use TLS. The database and its backups are encrypted at rest by the database provider (PlanetScale, on AWS-managed encrypted storage). Files in object storage are encrypted at rest by Cloudflare R2 (AES-256). Nightly database copies are encrypted with a public key before they are stored, and the private key is held offline by Elements.
  • Access control. The browser never talks to the database. Every read and write goes through server code that checks the user's role and organisation. Permissions are defined in code and covered by automated tests.
  • Authentication. Passwords are checked against known breached passwords and stored only as one-way hashes. Multi-factor authentication (authenticator apps, passkeys, backup codes) and single sign-on are available, and owners can require MFA. Sessions use secure, httpOnly cookies and can be revoked. Sensitive actions require recent re-authentication. Sign-in and similar actions are rate-limited.
  • Elements staff. Staff sign in only through Elements' Microsoft 365, with multi-factor authentication enforced by Microsoft. Leaving staff lose access at the next session check. Support access to a customer account requires a reason, is read-only by default, lasts no more than 60 minutes, and is recorded in the audit log and shown in the user's security log.
  • Audit. An append-only audit log records staff actions, security events and billing events, kept for 3 years.
  • Survey anonymity. The controls in section 5.
  • Secure development. Every change passes automated checks before it can be merged, including tests, secret scanning and dependency vulnerability audits. Secrets are held only in the hosting provider's and CI provider's secret stores.
  • Backups and recovery. Database backups every 12 hours with 7 days of point-in-time recovery, a nightly encrypted copy of the database kept for 35 days under a bucket lock and removed within a day after that, and a nightly copy of stored files to a second bucket under the same lock, from which deleted files are removed within 36 days. Every restore replays the record of deleted organisations before it is used.
  • Deletion. Scheduled jobs delete data on the dates in section 13, delete stored files under the organisation's own storage prefix, and check weekly that nothing remains for a deleted organisation.
  • Monitoring and incidents. Error monitoring (without user context on respondent pages), uptime checks, and a documented incident and breach response procedure.