Establishing secure connection…Loading editor…Preparing document…

Data Processing Agreement & Information Disclosure Document

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

DATA PROCESSING AGREEMENT & INFORMATION DISCLOSURE DOCUMENT

This Data Processing Agreement & Information Disclosure Document (the Agreement) is made and entered into as of Day: Month: Year: by and between Controller Name: principal place of business: (Controller) and Processor Name: principal place of business: (Processor).

RECITALS

WHEREAS, Controller determines the purposes and means of Processing personal data in connection with its business operations and desires to engage Processor to process certain personal data on Controller's behalf; and

WHEREAS, Processor provides services that involve access to and Processing of personal data and is willing to process such personal data subject to the terms and conditions set forth in this Agreement; and

WHEREAS, the parties intend by this Agreement to set forth the parties' respective rights and obligations with respect to the Processing of personal data and any required disclosures under applicable data protection law.

NOW, THEREFORE, in consideration of the mutual covenants set forth herein, the parties agree as follows:

1. DEFINITIONS

1.1 For purposes of this Agreement, the following terms have the meanings set forth below: "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; "Processing" means any operation or set of operations performed on Personal Data; "Sub-processor" means any Processor engaged by Processor to carry out Processing activities on behalf of Controller; and "Applicable Data Protection Law" means any law applicable to the Processing of Personal Data under this Agreement.

2. SCOPE AND DETAILS OF PROCESSING

3. PROCESSOR OBLIGATIONS

3.1 Processor shall process Personal Data only on documented instructions from Controller, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Applicable Data Protection Law. Controller's documented instructions (if any) are detailed as follows:

3.2 Processor shall implement appropriate technical and organizational measures to protect Personal Data against unauthorized or unlawful processing and against accidental loss, destruction or damage. Processor describes the measures it will implement as follows:

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

4. CONTROLLER OBLIGATIONS

4.1 Controller shall ensure that it has all necessary rights and lawful basis to provide Personal Data to Processor for the Processing and to instruct Processor for such Processing. Controller shall provide timely written instructions where required by Applicable Data Protection Law.

5. SECURITY MEASURES

5.1 Processor represents that it will maintain and regularly test technical and organizational measures appropriate to the risk, including measures to ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services.

6. SUB-PROCESSING

6.1 Controller hereby authorizes Processor to engage Sub-processors as necessary to perform the Services. Processor shall provide Controller with prior written notice of any intended changes concerning the addition or replacement of Sub-processors and shall allow Controller the opportunity to object for reasonable grounds. Notice period in days:

7. INTERNATIONAL TRANSFERS

7.1 Any transfers of Personal Data outside the country of collection shall be carried out only on the basis of a lawful transfer mechanism under Applicable Data Protection Law. The parties agree the following mechanism(s) shall apply to transfers:

8. DATA SUBJECT RIGHTS

8.1 Processor shall assist Controller, taking into account the nature of the Processing and the information available to Processor, in fulfilling Controller's obligation to respond to Data Subject requests. Contact for data subject requests at Controller:

9. BREACH NOTIFICATION

9.1 Processor shall notify Controller without undue delay after becoming aware of a Personal Data breach involving Controller's Personal Data and, where feasible, provide a written description of the nature of the breach, categories and approximate number of Data Subjects and records affected, likely consequences, and measures taken or proposed to remedy the breach. Notification period in hours:

10. RETURN OR DELETION OF PERSONAL DATA

10.1 Upon termination or expiry of the Services, Processor shall, at Controller's choice, return all Personal Data to Controller or securely delete all Personal Data unless retention is required by Applicable Data Protection Law. Controller's preference and instructions:

11. AUDIT RIGHTS

11.1 Controller or an independent auditor mandated by Controller shall have the right to audit Processor's compliance with this Agreement, subject to reasonable notice, confidentiality obligations and the protection of Processor's trade secrets. Auditor access and frequency:

12. CONFIDENTIALITY

12.1 Each party shall keep confidential all information disclosed by the other party in connection with this Agreement that is designated as confidential or that, given the nature of the information, should reasonably be understood to be confidential. The receiving party shall not disclose such information except to those employees, agents and Sub-processors who need to know for the performance of this Agreement and who are bound by confidentiality obligations at least as protective as those contained herein.

13. LIABILITY AND INDEMNIFICATION

13.1 Each party shall be liable for and shall indemnify the other against any losses, liabilities, damages, costs and expenses arising from its breach of this Agreement or Applicable Data Protection Law. Notwithstanding the foregoing, to the extent permitted by Applicable Data Protection Law, the parties agree that Processor's aggregate liability arising out of or relating to this Agreement shall not exceed:

14. INSURANCE

14.1 Processor shall maintain appropriate insurance coverage adequate to cover liabilities arising under this Agreement. Insurance details:

15. GOVERNING LAW; SEVERABILITY; ENTIRE AGREEMENT

15.1 This Agreement shall be governed by and construed in accordance with the laws of:

15.2 If any provision of this Agreement is found to be invalid or unenforceable, that provision shall be modified to the minimum extent necessary to make it valid and enforceable, and the remaining provisions shall remain in full force and effect.

15.3 This Agreement contains the entire understanding of the parties with respect to the subject matter hereof and supersedes all prior agreements, representations and understandings, whether written or oral, relating to such subject matter.

16. NOTICES

16.1 All notices, requests, consents and other communications under this Agreement shall be in writing and delivered to the addresses below or to such other address as either party may designate by written notice to the other.

17. AMENDMENT; WAIVER; COUNTERPARTS

17.1 No amendment or modification of this Agreement shall be effective unless in writing and signed by duly authorized representatives of both parties. No failure or delay by either party in exercising any right shall operate as a waiver of that right. This Agreement may be executed in counterparts, each of which shall be deemed an original.

Controller - Print Name:

By:

Date:

Processor - Print Name:

By:

Date:

Enter text✕

What this Data Processing Agreement & Information Disclosure Document Covers

The Data Processing Agreement & Information Disclosure Document defines how personal and sensitive data will be handled between contracting parties. It identifies roles (data controller, data processor), the categories of personal data processed, permitted purposes, security measures, subprocessors, cross-border transfer rules, breach notification obligations, and the recordkeeping needed to demonstrate compliance with U.S. and international privacy frameworks.

Why a DPA and Disclosure Document Matter for Risk and Compliance

A clear DPA reduces regulatory risk, allocates liability, and documents technical and organizational safeguards. It supports compliance with ESIGN/UETA for electronic execution and helps satisfy industry-specific rules such as HIPAA when a BAA is required.

Why a DPA and Disclosure Document Matter for Risk and Compliance

Who typically completes and signs this document

Organizations and vendors use DPAs to formalize how data is processed and disclosed before operations begin.

  • Corporate legal teams and general counsel overseeing vendor agreements and regulatory exposure.
  • IT and security leaders (CISO, security operations) confirming technical safeguards and incident response obligations.
  • Vendors and third-party processors that receive personal data and must document subprocessors and security controls.

Getting the right signatories ensures the agreement is enforceable and aligns operational practices with contractual commitments.

Who signs and their responsibilities

Data Controller

Usually a senior legal or compliance officer signs for the controller. They confirm lawful bases for processing, set data subject rights handling, and accept liability allocation terms.

Data Processor

A vendor executive or authorized contract signatory signs for processors. They commit to implementing agreed security measures, restrict subprocessors, and cooperate with audits and breach notifications.

Essential security and compliance items to list

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Access Controls: Role-based access; MFA required
Audit Trail: Comprehensive signing and action logs
BAA Availability: Business Associate Agreement option
Data Location: Specify hosting region or jurisdiction
Data Minimization: Limit collection and retention periods

Core contract elements to include in a professional DPA

A well-drafted DPA contains clauses that clearly assign roles, define permitted processing, specify security and breach response, and set terms for audits, subprocessors, and international transfers.

Scope of Processing

Describe processing activities in detail: purposes, data categories, duration, and any prohibited uses. Clear scope prevents unintended data use and supports audits and compliance reviews.

Data Categories

List categories of personal data (identifiers, financial, health, contact) and any special categories. Explicit lists reduce ambiguity about what protections apply.

Security Obligations

Enumerate technical and organizational measures, encryption standards, access control policies, vulnerability management, and incident response timelines to demonstrate measurable safeguards.

Subprocessor Controls

Require processor notification before adding subprocessors, allow reasonable objection, and mandate flow-down contractual terms to ensure consistent protection.

Audit & Verification

Specify audit rights, frequency, acceptable evidence (reports or onsite), and remediation timelines for noncompliance, including access to SOC 2/ISO reports where applicable.

Data Subject Rights

Define how requests (access, deletion, portability) are handled, timeframes for processor cooperation, and responsibilities for costs and communications.

Step-by-step: completing the Data Processing Agreement

Follow this sequence to prepare, review, and execute a compliant DPA before any data transfer or processing begins.

  • 01
    Assemble details: Collect party names, processing purposes, and data categories.
  • 02
    Draft clauses: Insert standard security, subprocessors, and breach terms.
  • 03
    Legal review: Have counsel confirm liability and regulatory language.
  • 04
    Execute: Have authorized signatories sign and retain executed copy.

How to configure the online signing workflow

Set up your digital workflow to ensure role-based signing, evidence capture, and retention of the signed agreement.

Workflow Field Configuration
Signature Order Sequential | Signer order enforced
Authentication Email + SMS code | Optional KBA
Audit Evidence Enable detailed audit trail
Storage Location Specify encrypted cloud region

Technical channels and file formats for e-execution

Choose a platform that supports required integrations, secure storage, and the document formats you use.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File Formats: PDF, DOCX, HTML supported
  • Authentication: Email, SMS, SSO available

Confirm the platform preserves an immutable audit trail, supports the authentication level you need, and allows export to ISO-compatible signed PDFs for long-term evidence and legal defensibility.

Typical online execution flow for the agreement

The signing process should be straightforward for signers while capturing all required evidence and consent details.

  • Upload Document: Add the final DPA file to the platform.
  • Place Fields: Insert signature, initial, and date fields.
  • Send for Signature: Send via email or generate a secure link.
  • Collect Evidence: Platform records IP, timestamp, and actions.

Practical timelines and response expectations for DPA lifecycle

Establish clear timelines for execution, notifications, audits, and data subject request handling to avoid operational gaps.

Execution Before Processing:

Execute the DPA before any personal data transfer or processing begins.

Subprocessor Notice:

Provide at least 30 days notice before adding a new subprocessor.

Breach Notification:

Notify controller within 72 hours of becoming aware of a breach (or earlier if required).

Data Subject Requests:

Acknowledge and respond to requests within 30 days, extend per law if necessary.

Annual Review:

Conduct an annual review of security measures and contract terms.

Common mistakes to avoid when preparing a DPA

  • Leaving processing purposes vague, which can lead to disputes about permitted uses and weaken regulatory compliance.
  • Failing to identify subprocessors or permit their onboarding only with written consent and proper flow-down terms.
  • Omitting measurable security standards (encryption levels, access controls) and remediation timelines for incidents.
  • Not aligning retention schedules with HIPAA or IRS requirements, risking noncompliance and penalties.

Key legal and commercial risks of an incorrect or missing DPA

HIPAA Fines: Civil penalties and corrective action
Contract Breach: Damages and indemnity obligations
Breach Costs: Notification and remediation expenses
Regulatory Inquiry: Investigations and remediation orders
Business Disruption: Operational delays and reputational harm
Termination Risk: Loss of contracts and revenue

How a DPA compares with similar documents

A quick contrast helps decide which document you need in vendor onboarding and privacy programs.

Criteria DPA Standard Vendor Agreement
Purpose data handling general services
GDPR/GDPR-like sometimes
Notarization not required not required
Typical Duration term-based project or term-based

eSignature solution pricing for executing DPAs and disclosure records

Compare baseline pricing and common capability factors across leading eSignature platforms; signNow is listed first per page 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 No No Yes, limited Yes, limited
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 & Information Disclosure Document

Answers to common execution, compliance, and practical questions encountered when preparing and signing DPAs.


Need help? Contact support

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