Data processing agreement
A data processing agreement (DPA) is the contract that governs how a software provider handles personal data on a customer's behalf. This page explains the structure of a recruitment-software DPA that incorporates the 2021 EU Standard Contractual Clauses and the UK International Data Transfer Addendum, and gives controllers a practical way to review it before signing. Where a first-party legal or commercial term depends on the publishing entity, the page shows an {{OWNER_...}} placeholder so the term can be filled in accurately.
What a DPA does and where it sits
A DPA sits alongside the main service agreement and is treated as part of it. Where the two documents disagree, the DPA controls to the extent of the conflict. Its duration mirrors the service agreement, and the provider may revise the terms periodically, alerting active subscribers by email or through an in-app message. Readers should treat any version number, effective date and issuing entity as details to confirm against the signed contract rather than as fixed facts on this page. The document has two layers. The first is the commercial DPA: scope, processing instructions, personnel, third-party disclosure, assistance, audit, incidents, international transfers, termination, deletion and definitions. The second is the Standard Contractual Clauses exhibit, which reproduces the EU model clauses and the UK addendum so that transfers outside the EEA and UK rest on a recognised safeguard.
Controller and processor roles
The customer is the controller and the provider is the processor. The processor handles personal data only on the controller's documented instructions and must keep a secure, complete and accurate record of any individual instructions. If an instruction would take processing outside the DPA, for example by adding a new purpose, the parties must agree first and follow the service agreement's change procedure. The processor must tell the controller in writing if it believes an instruction infringes data protection law, and it is not liable for losses that arise from processing carried out on the controller's instructions after that warning.
Personnel access is restricted to authorised staff under confidentiality, data protection and data security obligations. The processor will not disclose personal data to a third party, including a government agency or court, except as the DPA allows, with the controller's written consent, or where mandatory law requires it. Where a law-enforcement or third-party request arrives, the processor gives the controller reasonable notice before granting access so the controller can seek a protective order, and if notice is legally prohibited it takes reasonable measures to protect the data and informs the controller once the prohibition lifts.
Data subject requests and assistance
When a data subject contacts the processor, the processor must not answer directly. It forwards the request to the controller within three business days of identifying it as controller-related and then assists as instructed. The controller may also ask for cooperation on a data protection impact assessment where the law requires one and the controller does not already hold the information. Assistance that cannot reasonably be absorbed within normal service delivery is chargeable at rates the parties agree.
The processor also assists the controller with Articles 32 to 36 GDPR obligations, taking account of the nature of the processing and the information available to it.
Information rights and audits
The processor supplies the information needed to demonstrate compliance and, on written request, its most recent third-party certifications or audits. A controller reviewing a DPA should ask which certifications are currently held and check that they cover the services actually used. Inspections of processing and of technical and organisational measures are permitted on reasonable notice during business hours, with minimal disruption, by the controller, its affiliates or an independent third party that is not a competitor and is bound by confidentiality. The controller bears reasonable costs where it wants more than one audit or inspection in a 12-month period; the exact allowance should be read from the signed DPA. Requests from national data protection authorities relating to the processor's processing are referred to the controller immediately, and the processor cooperates with those authorities. On written request the processor also explains how personal data is processed through AI features, including the identity of applicable sub-processors.
Data incidents: who reports what
The processor notifies the controller of a personal data breach involving the processor or a subcontractor without undue delay and within the deadline stated in the signed DPA after becoming aware of it. It then makes reasonable efforts to find the cause and remediate it within its control, and gives the controller the information, cooperation and assistance needed for breach response, including communications to data subjects and authorities. A useful distinction: the Section 7 obligations do not apply to incidents caused by the customer or the customer's users. In practice, a controller reviewing an incident should separate (a) a breach originating in the processor's systems or a sub-processor, which triggers the notice obligation, from (b) a breach caused by the controller's own configuration, credentials or user behaviour, which falls outside that clause.
International transfers and the SCCs
Personal data may be transferred to countries other than the one in which the data subject lives, including the United States. The provider and its associated entities have entered into Standard Contractual Clauses among themselves for transfers from the EEA, UK and Switzerland. Where the client is in the EEA, the client is the data exporter and the provider is the data importer. Where the exporter is outside the US or EEA, the transfer involves onward transfer to the EEA, the US and other jurisdictions where the provider and its sub-processors are registered. The parties agree to process European data in line with Commission Implementing Decision (EU) 2021/914 and, where applicable, the UK IDTA issued by the UK Information Commissioner's Office. A controller should confirm in the signed DPA which transfer mechanism applies to its own route. If the provider cannot meet its SCC obligations, the client agrees to give reasonable notice to allow a cure and to cooperate on additional safeguards. If the non-compliance is not cured, the client may suspend or terminate the affected part of the service under the terms of service without liability to either party, without prejudice to fees already incurred.
Sub-processors and the right to object
Sub-processing is governed by Annex III of the Standard Contractual Clauses. The data importer has general authorisation to engage sub-processors from an agreed list and must inform the data exporter in writing of intended additions or replacements within the advance-notice window set in the signed DPA, giving enough time to object. If the controller objects to an appointment or replacement, the processor will either not appoint or replace that sub-processor, or, if that is not possible, the controller may suspend or terminate the service without prejudice to fees already incurred. The table below lists the sub-processors named in this DPA. Vendor names and purposes can change, so check the current list before relying on it for a transfer assessment.
Retention, export and deletion
The controller may export all customer data before the account terminates. After termination, customer data is retained for the post-termination export window stated in the signed DPA so the controller can contact the processor to export it. Where the controller does not use a custom mailbox and uses the email feature, emails forming part of customer data are automatically archived for three months. Logs are archived for 30 days in the log management systems and then moved to restricted archived cold storage for 11 months. Each of these is a Data Retention Period. After the relevant period the processor may delete all customer data in the normal course of operation, except where needed to meet legal obligations, keep accurate financial and other records, resolve disputes or enforce agreements. Deleted customer data cannot be recovered. Workflow automation runs through the AI and automation sub-processor named in the signed DPA. The Workato retention period is configurable, defaults to 90 days and cannot exceed 90 days. Users can opt not to store data for specific recipes, though that is not recommended because the records help troubleshoot recipe errors. Where the customer connects an email account, the provider may synchronise and store emails related to records, including emails matched through email fields or manually associated, to provide display, search and email-history functionality.
AI features and controller responsibilities
Optional AI features are enabled through the integration provider named in the signed DPA and are used at the controller's sole discretion. The controller keeps ownership of inputs and outputs, but AI-generated outputs may be the same or similar to those provided to other users. Processing may involve that integration provider and its authorised sub-processors. The controller must not use AI features to build competing models or present AI outputs as human-generated, and is solely responsible for lawful use, including notices and consents for personal data. The controller indemnifies the provider for claims arising from misuse of AI features. AI outputs are provided as is without warranty, and the provider and its integration provider disclaim liability for inaccuracies or reliance on them. Technical usage data and voluntary feedback may be collected to improve the features. The provider may amend the DPA to reflect the introduction or modification of AI features, with notice by email or in-app notification; continued use of AI features constitutes acceptance.
Term, termination and miscellaneous terms
The DPA becomes effective on signature and continues while the processor processes personal data under Annex I, then ends automatically. The controller may terminate the DPA and the service agreement for cause, with or without notice as it selects, if the processor materially breaches the DPA. Where amendments are needed for legal compliance, the parties agree on them at the controller's request with no additional cost to the controller; if they cannot agree, either party may terminate the service agreement and the DPA on the notice period stated in the signed DPA. On conflict, the DPA prevails over other agreements with the processor. The service agreement's limitation of liability applies to DPA breaches. No party receives remuneration for performing DPA obligations except as expressly set out. A required written notice may be sent by email to the contacts in Annex I. Supplementary agreements and amendments must be in writing and signed by both parties. If one provision becomes void or invalid, the rest remains valid.
Technical and organisational measures
Annex II describes the security programme as of the date of signature. Rather than restating each control, read it as five categories and check that your own requirements are met in each. Governance and people: a named owner for the information security programme, privacy and security awareness training at hire and annually thereafter, and a controller right to review an overview of the programme before service and annually on request. Data handling: encryption of personal data in transit over public networks, media sanitisation to a recognised forensic standard before disposal, need-to-know access, individual accounts with password complexity and duration rules, password storage that resists recovery in isolation, encrypted and audited access sessions, logical separation between customers, and isolation of test or development environments from production. Network and communications: firewalls and threat detection, physical networking designed to resist attack, and encrypted transit. Physical and resilience: secure encrypted backup media, data-centre access controls with CCTV and audit logs, fire detection and suppression, redundant generators and HVAC with N+1 and N+2 redundancy. Assurance: at least annual third-party penetration and vulnerability testing with remediation and revalidation, and an annual SSAE 18 (or equivalent) audit whose results are provided on written request. A controller should ask which certifications and audits are currently held and confirm they cover the services in use. The provider's use of information from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
The Standard Contractual Clauses exhibit
Exhibit 1 reproduces the EU Standard Contractual Clauses. Clause 1 sets purpose and scope; Clause 2 preserves the clauses as unmodified except for module selection and appendix updates; Clause 3 gives data subjects third-party beneficiary rights with listed exceptions; Clause 4 requires interpretation consistent with the GDPR; Clause 5 makes the clauses prevail over conflicting related agreements; Clause 6 points to Annex I.B for transfer details; and Clause 7 allows a new entity to accede by completing the appendix and signing Annex I.A. The obligations section covers documented instructions, purpose limitation, transparency, accuracy, duration and erasure or return, security, sensitive data, onward transfers and documentation and compliance. Clause 9 covers sub-processors, including advance notice of changes and a written contract with equivalent obligations. Clause 10 covers data subject rights. Clause 11 covers redress. Clause 12 covers liability, including joint and several liability where more than one party is responsible. Clause 13 covers supervision. Clause 14 covers local laws and practices affecting compliance. Clause 15 covers public-authority access, including notification, review of legality and data minimisation. Clause 16 covers non-compliance and termination. Clause 17 selects the governing law, and Clause 18 selects the forum; both should be read from the signed DPA. Clause 18 also preserves a data subject's right to sue in the Member State of habitual residence.
Annex I: parties, transfer description and authority
Annex I.A identifies the data exporter as the customer under the terms of service or master service agreement, acting for itself and permitted affiliates, with the address and contact details in that agreement or the customer's account. The customer's role is controller. The data importer is the provider, with the address and contact details in the DPA, and its role is processor. Annex I.B describes the transfer. The customer decides the extent of personal data submitted and it may include data about the exporter's end-customers, group employees and merchants. Categories may include contact data such as name, date of birth, address, email and phone number; identifiers such as PNO or social security number; payment data such as card number, invoice data and bank account number; purchase and payment history; device data such as IP address and geolocation; log data; and email and communications data including sender and recipient information, subject, content, attachments, timestamps and record associations. The transfer is continuous for the duration of the service agreement. Personal data is processed as necessary to provide the services under the terms of service or master service agreement, as specified in the service order form and as instructed by the customer. Data is retained during the agreement and for the post-termination period stated in the signed DPA. Annex I.C identifies the competent supervisory authority: the authority responsible for the customer where it is established in an EU Member State; the authority of the Member State where the customer's representative is established where the customer is outside the EU but within the GDPR's extra-territorial scope and has appointed a representative; or the authority of the Member State where the data subjects are predominantly located where no representative is required. For UK GDPR or Swiss DPA data, the competent authority is the UK Information Commissioner or the Swiss Federal Data Protection and Information Commissioner, as applicable.
Key definitions
Data Protection Laws means the data protection laws of the country where the controller is established, including the GDPR and UK GDPR, plus any data protection laws applicable to the controller in connection with the service agreement. Where the controller is not established in an EU Member State, the California Consumer Privacy Act applies in addition. DP Losses covers liabilities including costs, legal costs, claims, demands, actions, settlements, charges, procedures, expenses, losses and damages, whether material or non-material and including emotional distress. GDPR means Regulation (EU) 2016/679. UK GDPR means the GDPR as retained in UK law by the European Union (Withdrawal) Act 2018 and as amended by the Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019. Personal Data means information relating to an identified or identifiable natural person as defined by the GDPR or UK GDPR and processed by the processor as part of providing the services described in Exhibit 1. Service Agreement means the terms of service or a master services agreement executed between the parties. Standard Contractual Clauses means the clauses set out in Exhibit 1 in the form in the Annex of Commission Implementing Decision (EU) 2021/914 of 4 June 2021, as amended by incorporating the transfer description and technical and organisational measures in the Appendix. UK International Data Transfer Addendum or UK IDTA means the addendum issued by the UK Information Commissioner's Office under S119A(1) Data Protection Act 2018, as amended, updated or replaced from time to time, applying to transfers of personal data subject to the UK GDPR to third countries without a UK adequacy decision. Controller, Data Subject, Personal Data Breach, Processor and Process/Processing have the meanings given in the GDPR or UK GDPR.
Pre-signing checklist for controllers
Use this checklist to turn the DPA into review questions. Each item maps to a section above. 1. Role and scope: confirm the DPA names the customer as controller and the provider as processor, and that the processing description in Annex I.B matches your actual use, including candidate and client data. 2. Instructions: check how you will communicate changes to processing instructions and who keeps the record of them. 3. Sub-processors: review the sub-processor list, confirm the advance notice for changes in the signed DPA, and decide how you will exercise the right to object. 4. Transfers: identify whether you are an EEA, UK, Swiss or other exporter, and confirm the SCC module and UK IDTA apply to your transfer route. 5. Incidents: record the breach notice period in the signed DPA and agree who on your side receives it; separate processor-caused incidents from customer-caused ones. 6. Retention: map the post-termination export window, the three-month email archive, the 30-day plus 11-month log retention and the 90-day automation default against your own record-keeping duties, and confirm the periods in the signed DPA. 7. Audit and assistance: note the audit allowance in the signed DPA and the chargeable assistance and additional audits. 8. AI features: decide whether you will enable AI features, and if so confirm your notices, consents and restrictions on use, and the integration provider named in the signed DPA. 9. Security: review Annex II against your own security requirements and request the most recent certifications or audits. 10. Exit: confirm the export process, the deletion rules and the termination route for unresolved amendment disputes in the signed DPA.
Worked example: one candidate record across the chain
A recruitment agency in Berlin (the controller) stores a candidate's name, email, phone number and CV in the recruitment platform (the processor). The agency connects its email account, so emails matched to the candidate record are synchronised and stored. The agency enables an AI feature that drafts a candidate summary; the request is processed through the integration provider named in the signed DPA and may involve an AI inference sub-processor listed in Annex III. The agency remains the owner of the input and output, but the generated summary may resemble output produced for another user, so the agency should not treat it as unique or verified. If the candidate asks the agency to delete the record, the agency sends the instruction to the processor, which corrects, deletes or blocks the data as instructed. If the candidate instead contacts the processor directly, the processor forwards the request to the agency within three business days and does not answer it itself. If a breach occurs in the AI sub-processor's systems, the processor notifies the agency within the breach notice period stated in the signed DPA of becoming aware. If the breach is caused by the agency's own user sharing credentials, the Section 7 notice obligations do not apply. After the agency terminates its account, it has the post-termination export window stated in the signed DPA to export the data; the connected emails remain archived for three months and logs for 30 days plus 11 months in cold storage before deletion.
| Vendor | Purpose |
|---|---|
| Amazon Web Services, Inc. | Primary cloud infrastructure provider. Almost all data stored, processed and transmitted resides on AWS data centres. |
| SendGrid, Inc. | Email service provider to deliver emails triggered programmatically from the products. |
| Twilio Inc. | Platform to programmatically initiate and receive calls, call recordings, and SMS. Text messages sent and received are stored at Twilio's end. |
| Beamer | In-product announcements regarding new features or offers. |
| Google, Inc. | Regional Data Processing, APIs. |
| Intercom | Conversation & Chat Functionality. |
| Nylas | Connect and sync mail, calendar, and contact data from any email service provider. |
| AWS CloudWatch | Application and infrastructure log management. |
| Elastic Search | Log indexing and search. |
| OpenAI, L.L.C. | Generative AI capabilities: note taking, call log summarisation, job description generation, candidate summary generation, email drafting, call transcripts. |
| Workato, Inc. | Automation and integration platform for custom integrations, workflows, and data mappings. |
| Userpilot | Product experience software for contextual onboarding experiences. |
| Singlestore | Real-time data analytics platform to speed up search queries. |
| Datadog, Inc. | Observability and security platform for application performance monitoring, real-user monitoring, and application security. |
| VONQ Inc. | Job advertising and job distribution partner for multiposting to 3000+ job boards. |
| Metabase, Inc. | Advanced analytics partner for custom reporting and business intelligence. |
| Unipile | LinkedIn Messages feature — syncs LinkedIn messages to the provider's CRM profile. |
| Geoapify | Location Services. |
| MongoDB | Capturing audit logs. |
| Amplitude | App usage tracking and gathering relevant insights. |
| Aha | Tool to manage roadmap and customer feedback. |
| Hubspot | Capture and manage Customer data. |
| Retool | Capture and manage Customer data. |
| Custify | Capture and manage Customer data. |
| ElevenLabs | AI onboarding experience software. |
| Stripe | Used for processing payments. |
| RocketReach LLC | Data Enrichment |
| Full Enrich | Data Enrichment |
| Cerebras | AI inference and processing of AI model requests. |
| Groq | AI inference and processing of AI model requests. |
| Gemini (Google) | Generative AI capabilities, including processing prompts and generating AI-powered responses. |
| CubeAPM | Application performance monitoring, error tracking, and observability for troubleshooting and improving application reliability. |
Vendor names and purposes can change; check the current sub-processor list before relying on it.
Frequently asked questions
Who is the controller and who is the processor under this DPA?
The customer is the controller and the provider is the processor. The processor handles personal data only on the controller's documented instructions and must tell the controller in writing if it believes an instruction infringes data protection law.
How quickly must a personal data breach be reported?
The processor notifies the controller without undue delay and within the deadline stated in the signed DPA after becoming aware of a personal data breach involving the processor or a subcontractor. The Section 7 obligations do not apply to incidents caused by the customer or the customer's users.
What happens to customer data after the account terminates?
The controller may export all customer data before termination. After termination, customer data is retained for the post-termination export window stated in the signed DPA so the controller can export it. Emails in the email feature are archived for three months, and logs are archived for 30 days and then held in restricted cold storage for 11 months. After the relevant Data Retention Period, the processor may delete the data in the normal course of operation, subject to legal, financial, dispute and enforcement exceptions. Deleted data cannot be recovered.
How much notice is given before a sub-processor changes?
The data importer must inform the data exporter in writing of intended additions or replacements within the advance-notice window set in the signed DPA, giving enough time to object. If the controller objects and the change cannot be avoided, the controller may suspend or terminate the service without prejudice to fees already incurred.
Which law and courts govern the Standard Contractual Clauses?
The governing law and the courts with jurisdiction are set out in the signed DPA. A data subject may also bring proceedings in the Member State where they habitually reside.
Does the DPA cover AI features?
Yes. Optional AI features are enabled through the integration provider named in the signed DPA and used at the controller's sole discretion. The controller owns inputs and outputs but AI outputs may resemble those provided to other users. The controller must not use the features to build competing models or present outputs as human-generated, and is responsible for lawful use, notices and consents. The provider may amend the DPA for AI changes with email or in-app notice, and continued use constitutes acceptance.