Establishing secure connection…Loading editor…Preparing document…

Data Processing Agreement 2024

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

DATA PROCESSING AGREEMENT 2024

This Data Processing Agreement ("Agreement") is entered into as of Day: Month: Year: (the "Effective Date") by and between Controller Name: , principal address: ("Controller") and Processor Name: , principal address: ("Processor").

RECITALS

WHEREAS, Controller determines the purposes and means of processing Personal Data and engages Processor to perform certain services that require Processor to process Personal Data on behalf of Controller; and

WHEREAS, Processor will process Personal Data only on documented instructions from Controller, subject to the terms of this Agreement, and will implement appropriate technical and organizational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, disclosure or access; and

WHEREAS, the parties intend to ensure compliance with applicable data protection laws and to set out the respective obligations and responsibilities of Controller and Processor in relation to Personal Data processed under the parties' principal agreement:

NOW THEREFORE, in consideration of the mutual covenants and agreements herein, the parties agree as follows:

1. DEFINITIONS

1.1 "Personal Data" means any information relating to an identified or identifiable natural person that is provided to or collected by Processor on behalf of Controller in connection with the services described in Schedule A.

1.2 "Processing", "controller", "processor" and "data subject" shall have the meanings given to them under applicable data protection law and shall include any successor definitions thereto.

2. DETAILS AND SCHEDULE OF PROCESSING

2.1 The subject-matter, duration, nature and purpose of the Processing, the types of Personal Data and categories of Data Subjects are set forth in Schedule A attached hereto. Schedule A forms an integral part of this Agreement.

3. PROCESSOR OBLIGATIONS

3.1 Processor shall process Personal Data only on documented instructions from Controller, unless required to do otherwise by applicable law; in such case Processor shall inform Controller of that legal requirement unless prohibited by law from doing so.

3.2 Processor shall ensure that persons authorized to process Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

3.3 Processor shall implement and maintain appropriate technical and organizational measures to ensure a level of security appropriate to the risk, including as set forth in the technical measures checklist below and in any additional security specifications agreed between the parties.

Encryption of data at rest and in transit
Role-based access controls and least privilege
Audit logging and monitoring of access
Pseudonymization where feasible
Regular backup and business continuity procedures

4. CONTROLLER OBLIGATIONS

4.1 Controller represents and warrants that it has all necessary rights and lawful grounds to transfer Personal Data to Processor for Processing under this Agreement and that Controller's instructions comply with applicable data protection law.

4.2 Controller shall respond to requests from Processor for instructions, consents or authorizations reasonably necessary for Processor to comply with applicable legal obligations.

5. SUB-PROCESSORS

5.1 Controller authorizes Processor to engage the sub-processors listed in the initial sub-processor list below and to replace or appoint additional sub-processors provided that Processor: (a) gives Controller prior written notice of the intended addition or replacement, and (b) enters into a written contract with the sub-processor imposing obligations no less protective than those imposed on Processor under this Agreement.

6. INTERNATIONAL TRANSFERS

6.1 Where Personal Data is transferred to jurisdictions that do not provide an adequate level of protection under applicable law, the parties shall ensure that appropriate safeguards are implemented, such as contractual safeguards, binding corporate rules, or other measures required by law.

7. DATA SUBJECT RIGHTS AND ASSISTANCE

7.1 Processor shall assist Controller, taking into account the nature of Processing and the information available to Processor, by appropriate technical and organizational measures, insofar as this is possible, for the fulfillment of Controller's obligation to respond to requests for exercising data subject rights.

8. SECURITY BREACHES AND INCIDENT NOTIFICATION

8.1 Processor shall notify Controller without undue delay after becoming aware of a Personal Data breach. Such notification shall: describe the nature and scope of the breach, the categories and approximate number of Data Subjects affected, the likely consequences, and the measures taken or proposed to address the breach.

9. AUDIT AND INSPECTION

9.1 Processor shall make available to Controller all information necessary to demonstrate compliance with the obligations laid down in this Agreement and allow for and contribute to audits, including inspections, conducted by Controller or an auditor mandated by Controller, subject to reasonable confidentiality protections for Processor's business information.

10. RETURN OR DELETION OF PERSONAL DATA

10.1 Upon termination or expiration of the services under the parties' principal agreement, Processor shall, at Controller's choice, return all Personal Data to Controller and delete existing copies unless retention of Personal Data is required by applicable law. Processor shall certify in writing the completion of such return or deletion.

11. CONFIDENTIALITY

11.1 Each party shall keep confidential any Personal Data and any information received from the other party that is designated confidential and shall not disclose such information except as permitted under this Agreement or required by law.

12. LIABILITY AND INDEMNITY

12.1 Each party's liability for breaches of this Agreement arising from its negligence or willful misconduct shall be governed by the liability provisions of the parties' principal agreement. To the extent such principal agreement does not address liability for data protection breaches, the parties agree that each party shall be liable for direct damages caused by its breach of this Agreement.

12.2 Processor shall indemnify and hold harmless Controller for losses arising from Processor's breach of its obligations under this Agreement, subject to any limitations set forth in the parties' principal agreement.

13. GOVERNING LAW; JURISDICTION

13.1 This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified below. Any dispute arising out of or in connection with this Agreement shall be subject to the exclusive jurisdiction of the courts of that jurisdiction, except where mandatory law requires otherwise.

14. ENTIRE AGREEMENT; SEVERABILITY; AMENDMENT; WAIVER

14.1 This Agreement, together with any schedules and the parties' principal agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior proposals, agreements, representations and understandings. If any provision of this Agreement is held invalid or unenforceable, the remainder of the Agreement shall remain in effect. Any amendment or waiver of any provision of this Agreement must be in writing and executed by authorized representatives of both parties.

15. NOTICES

15.1 Any notice required or permitted under this Agreement shall be in writing and delivered to the notice contact details set out below or to such other address as a party may designate by notice in accordance with this Section.

16. COUNTERPARTS

16.1 This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures delivered by electronic means shall be effective as original signatures.

Controller

Printed Name:

By:

Date:

Title:

Processor

Printed Name:

By:

Date:

Title:

Enter text✕

What the Data Processing Agreement 2024 Covers

A Data Processing Agreement 2024 (DPA) is a contract between a data controller and a data processor that defines how personal data is handled, protected, and processed on behalf of the controller. The DPA allocates responsibilities for data security, sets limits on processing purposes, describes technical and organizational safeguards, and establishes procedures for incident response, audits, and return or deletion of data. In U.S. contexts the DPA also clarifies HIPAA obligations where protected health information is involved and documents whether a Business Associate Agreement (BAA) is required.

Why a Clear DPA Matters for Compliance and Risk Management

A well-drafted DPA reduces legal and operational risk by documenting roles, legal bases, and security expectations. It supports regulatory compliance (HIPAA, specific state privacy laws, ESIGN/UETA for execution), enables consistent incident handling, and clarifies liabilities and indemnities between parties.

Why a Clear DPA Matters for Compliance and Risk Management

Who Typically Prepares or Signs a Data Processing Agreement

Organizations that collect, transfer, or process personal data use DPAs: vendors, cloud providers, SaaS platforms, and enterprise legal or privacy teams commonly prepare or request them.

  • In-house Legal Teams — Draft and approve contractual language protecting the controller and ensuring enforceable obligations.
  • Privacy/Compliance Officers — Verify technical controls, data flows, and regulatory alignment such as HIPAA or state privacy statutes.
  • Vendor Contracts Managers — Negotiate operational terms, subprocessors, and audit rights for procurement and vendor management.

Controllers should ensure authorized signatories execute the DPA and keep a signed copy in procurement and privacy records for evidence of compliance.

Who Signs and What Their Roles Are

Authorized Signatory

Typically a corporate officer or delegated contract manager with binding authority. This person certifies that their organization accepts the processor obligations and can commit to indemnities or limitations of liability.

Data Protection Officer

When present, the DPO reviews data transfer mechanisms, ensures the DPA aligns with privacy policies, and confirms security and breach notification clauses meet regulatory requirements such as HIPAA or state data breach statutes.

Core Sections to Include in a Professional DPA

A concise DPA balances legal precision with operational detail; include clauses that allocate responsibilities, define data categories, and set security and audit terms.

Processing Scope

Describe permitted purposes, categories of personal data, affected data subjects, and duration of processing so obligations are narrowly tailored and enforceable.

Security Measures

List technical and organizational safeguards, encryption expectations, access controls, and incident detection procedures to align with industry standards.

Subprocessor Controls

Require prior notice or approval for subprocessors, mandate flow-down obligations, and preserve audit or inspection rights to verify compliance.

Breach Notification

Set maximum notification windows, required content, and cooperation steps for investigation and remediation following a security incident.

Audit Rights

Define audit frequency, scope, and format (on-site or remote); specify remediation timelines and handling of audit findings.

Data Return or Deletion

Require secure return or destruction of controller data at contract end, including acceptable methods and verification of secure deletion.

Step-by-Step: Completing the DPA

Follow these steps to assemble, review, and execute the Data Processing Agreement 2024 in a compliant, auditable way.

  • 01
    Gather Documents: Collect controller policies, security summaries, and vendor addenda before drafting.
  • 02
    Draft Terms: Customize processing scope, security, and breach clauses to match operational reality.
  • 03
    Review Internally: Have legal, privacy, and IT teams review for legal and technical alignment.
  • 04
    Execute and Archive: Obtain authorized signatures, save a signed copy, and record the execution date.

How to Configure an Online DPA Workflow

Set up an eSignature workflow to ensure correct routing, authentication, and auditability when executing a DPA online.

Field Configuration
Signature Block Require full name, title, and MM/DD/YYYY date field.
Authentication Use email verification or SMS code; consider stronger auth for HIPAA records.
Document Versioning Lock the DPA PDF before sending to preserve the signed text.
Audit Trail Capture IP, timestamp, and signer events for evidentiary support.

Digital Signing and eSubmission Requirements

Ensure the chosen eSignature platform supports the authentication, audit trail, and security features required by the DPA and any applicable regulations.

  • Authentication Options: Email, SMS, KBA, or stronger methods supported.
  • File Formats: Accepts PDF, DOCX, and preserves signature metadata.
  • Integrations: Connects to CRM, storage, and workflow systems.

Choose a solution that yields a tamper-evident signed file and stores an auditable certificate of completion to meet ESIGN/UETA evidentiary tests.

Typical Online Execution Flow for a DPA

An efficient online execution follows a predictable sequence from upload to final archive; ensure each step produces evidence of action.

  • Upload Document: Sender uploads the finalized DPA PDF to the platform.
  • Place Fields: Insert signature, name, title, and date fields for each party.
  • Send for Signature: Platform emails signers or generates secure signing links.
  • Archive Evidence: Store signed PDF and audit trail for retention and audits.

Key Timing Considerations When Executing a DPA

Certain dates and deadlines influence obligations and records; ensure the execution date, notice periods, and retention triggers are clearly recorded.

Effective Date:

MM/DD/YYYY — determines start of processing obligations.

Breach Notification Window:

Specify maximum days for notification; common windows are 72 hours or 30 days depending on sector.

Subprocessor Notice:

Specify lead time for notice or consent before onboarding a subprocessor.

Audit Scheduling:

Define notice period for audits, commonly 30 days.

Data Return Deadline:

Set timeline for return or deletion after termination, e.g., 30–90 days.

Milestones and Review Stages for a DPA Lifecycle

Track these milestone stages from negotiation through post-termination to maintain compliance and readiness for audits.

01

Negotiation

Drafting and redlines between legal teams before signature.

02

Execution

Authorized signatures and recording the effective date.

03

Ongoing Oversight

Periodic security reviews and subprocessor checks.

04

Termination

Trigger data return or secure deletion obligations.

Common Preparation Errors to Avoid

  • Overbroad processing language that fails to specify categories and purposes, creating compliance exposure and unclear limits.
  • Missing or vague breach notification terms that delay response and may violate HIPAA or state breach laws.
  • No subprocessor controls or notification mechanism, making it difficult to manage third-party risk and audits.
  • Failing to record the effective date and signed version, which complicates retention, enforcement, and audit trails.

Consequences of an Incomplete or Incorrect DPA

Regulatory Fines: Civil penalties from HIPAA or state data protection statutes.
Contract Liability: Indemnity and damages claims between parties.
Operational Disruption: Inability to use or transfer data during remediation.
Audit Findings: Corrective actions from internal or regulator audits.
Reputational Harm: Loss of customer trust and business opportunities.
Tax/Record Issues: Retention failures that affect tax or compliance evidence.

Security and Compliance Facts to Document

Encryption: AES-256 at rest; TLS 1.2/1.3 in transit
Certifications: SOC 2 Type II; ISO 27001
HIPAA Support: BAA required for PHI handling
21 CFR Part 11: Compliant controls available
Audit Trail: Captures IP, timestamps, signer events
Accessibility: WCAG 2.0 Level AA support

eSignature Vendor Comparison Relevant to a DPA

Compare baseline pricing and key capabilities that matter for executing and managing Data Processing Agreements. signNow is listed first per vendor comparison conventions.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About the Data Processing Agreement 2024

Answers to common execution, validity, and compliance questions for DPAs executed electronically in the United States.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users