Establishing secure connection…Loading editor…Preparing document…

Legal Document for DPSA

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

DATA PROTECTION AND SHARING AGREEMENT (DPSA)

This Data Protection and Sharing Agreement (the Agreement) is entered into as of by and between Data Provider: with principal place of business at and Data Recipient: with principal place of business at (each a Party and collectively the Parties).

RECITALS

WHEREAS, Data Provider possesses certain categories of data, including personal data and other information, that are necessary for the Data Recipient to perform the services and purposes set forth in this Agreement; and

WHEREAS, the Parties seek to define their respective obligations regarding the confidentiality, protection, processing, transfer and return or destruction of such data in compliance with applicable data protection laws and contractual obligations; and

WHEREAS, the Parties intend that Data Recipient shall only process the data on behalf of and under the documented instructions of Data Provider, except as otherwise required by applicable law.

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, 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, transferred or otherwise made available by Data Provider to Data Recipient under this Agreement.

1.2 "Processing" or "process" means any operation or set of operations performed on Personal Data, whether or not by automated means, including collection, recording, organization, structuring, storage, adaptation, retrieval, use, disclosure, erasure or destruction.

2. PURPOSE

2.1 The Parties acknowledge that Data Recipient will process Personal Data solely for the purpose of:

3. SCOPE OF DATA AND DATA ELEMENTS

3.1 Data Provider shall disclose only the categories and elements of data necessary to accomplish the Purpose. The Parties agree that the categories of data covered by this Agreement include, without limitation:

4. OBLIGATIONS OF DATA PROVIDER

4.1 Data Provider represents and warrants that it has the lawful basis and authority to share the Personal Data with Data Recipient for the stated Purpose and that such transfer does not violate applicable law or contractual obligations to third parties.

4.2 Data Provider shall provide Data Recipient with documented instructions regarding the Processing of Personal Data and shall notify Data Recipient promptly of any changes to such instructions.

5. OBLIGATIONS OF DATA RECIPIENT

5.1 Data Recipient shall process Personal Data only on documented instructions from Data Provider and shall not use or disclose Personal Data for purposes incompatible with the Purpose.

5.2 Data Recipient shall implement and maintain appropriate technical and organizational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access. The Parties acknowledge that such measures shall be proportionate to the risk and state of the art.

6. SUBPROCESSORS

6.1 Data Recipient shall not engage any subprocessor to perform Processing on behalf of Data Provider without prior written authorization. If authorization is given, Data Recipient shall impose on each subprocessor obligations equivalent to those in this Agreement and shall remain liable for the subprocessor's compliance.

6.2 Data Provider authorizes the use of subprocessors as follows (check if authorized):

7. DATA SUBJECT RIGHTS

7.1 Taking into account the nature of the Processing, Data Recipient shall assist Data Provider by appropriate technical and organizational measures, insofar as this is possible, for the fulfillment of Data Provider's obligation to respond to requests for exercising data subject rights under applicable law.

8. BREACH NOTIFICATION

8.1 In the event of a confirmed security incident or breach affecting Personal Data, Data Recipient shall notify Data Provider without undue delay and, in any event, no later than hours after becoming aware of the breach, providing sufficient information to enable Data Provider to meet its obligations under applicable law.

9. AUDIT AND COMPLIANCE

9.1 Data Recipient shall make available to Data Provider all information necessary to demonstrate compliance with this Agreement and shall allow for and contribute to audits, including on-site inspections, subject to reasonable prior notice and protection of confidential information.

10. RETENTION, RETURN AND DESTRUCTION

10.1 Data Recipient shall retain Personal Data only for as long as necessary to fulfill the Purpose or as required by applicable law. Upon termination of this Agreement, Data Recipient shall, at Data Provider's election, return all Personal Data to Data Provider or securely destroy such data and certify destruction.

11. LIABILITY AND INDEMNITY

11.1 Each Party's liability arising out of or in connection with this Agreement shall be governed by the applicable law clause below. Except to the extent prohibited by applicable law, the Parties agree that the total aggregate liability of each Party arising from a claim relating to this Agreement shall not exceed unless resulting from willful misconduct or gross negligence.

11.2 Data Recipient shall indemnify and hold harmless Data Provider from and against all losses arising from Data Recipient's breach of this Agreement, including unauthorized disclosure or misuse of Personal Data, subject to the limitations in this Agreement.

12. TERM AND TERMINATION

12.1 This Agreement shall commence on the Effective Date and shall continue in effect until the earlier of completion of the Purpose or termination by either Party in accordance with this Agreement.

13. CONFIDENTIALITY

13.1 Each Party shall treat as confidential all Personal Data and any non-public information received from the other Party and shall not disclose such information except to authorized personnel, agents, subprocessors or as required by law. Confidential information shall be protected with at least the same degree of care as the receiving Party uses to protect its own confidential information, but in no event less than reasonable care.

14. NOTICES

14.1 All notices, requests, consents and other communications required or permitted under this Agreement shall be in writing and delivered to the addresses set forth below or to such other address as either Party may designate by notice in accordance with this section.

15. AMENDMENTS AND WAIVER

15.1 No amendment, modification or waiver of any provision of this Agreement shall be effective unless in writing and signed by duly authorized representatives of both Parties. The failure of either Party to enforce any right shall not constitute a waiver of future enforcement of that or any other right.

16. SEVERABILITY

16.1 If any provision of this Agreement is held to be invalid, illegal or unenforceable in any respect, the validity, legality and enforceability of the remaining provisions shall not in any way be affected or impaired.

17. ENTIRE AGREEMENT

17.1 This Agreement constitutes the entire agreement between the Parties with respect to its subject matter and supersedes all prior or contemporaneous understandings, agreements, representations and warranties, both written and oral, regarding such subject matter.

18. GOVERNING LAW

18.1 This Agreement shall be governed by and construed in accordance with the laws specified by the Parties below without regard to conflict of law principles.

19. COUNTERPARTS

19.1 This Agreement may be executed in any number of counterparts, each of which when executed and delivered shall constitute an original, but all such counterparts together shall constitute one and the same instrument.

IN WITNESS WHEREOF, the Parties have executed this Agreement through their duly authorized representatives.

Data Provider - Printed Name:

By:

Date:

Data Recipient - Printed Name:

By:

Date:

Enter text✕

What the Legal Document for DPSA Is and When it Applies

A Legal Document for DPSA (Data Processing and Security Agreement) is a written contract that sets the terms for processing, storing, and protecting personal or regulated data between a data controller and a data processor. It clarifies roles, permitted processing activities, security controls, breach notification procedures, liability allocation, and any subprocessing rules. Organizations use a DPSA when one party handles another party's sensitive data to ensure regulatory compliance, define technical and organizational measures, and create clear remediation and audit rights in the event of a data breach or regulatory inquiry.

Why a DPSA Matters for Legal and Regulatory Clarity

A well-drafted DPSA documents responsibilities for data protection, supports contractual allocation of risk, and helps demonstrate compliance with federal and state laws. ESIGN (15 U.S.C. §7001) and state UETA frameworks permit electronic execution of such agreements when intent, consent, attribution, and retention are met.

Why a DPSA Matters for Legal and Regulatory Clarity

Who Typically Prepares, Reviews, and Signs a DPSA

Multiple organizational roles are usually involved — legal counsel drafts clauses, IT/security teams define controls, and business owners approve processing scope.

  • Privacy and compliance teams — draft terms, map data flows, and confirm regulatory obligations.
  • IT and security leads — specify encryption, access controls, incident response, and logging requirements.
  • Vendors and procurement — review commercial terms, subcontractor rules, and indemnity language.

Signatory authority typically falls to named officers or authorized procurement representatives; include signatory names and titles to avoid execution disputes.

Step-by-Step: Complete a DPSA Efficiently

Follow these core stages to prepare, approve, and execute a DPSA with minimal rework.

  • 01
    Prepare Draft: Assemble template, define data categories, and insert required controls.
  • 02
    Review & Redline: Legal and security teams negotiate liability, indemnity, and audit rights.
  • 03
    Authorize Signers: Identify authorized signatories and confirm their authority to bind the entity.
  • 04
    Execute: Use permissive eSignature or in-person signing with complete signature metadata.

Digital Workflow Settings for Online Completion

Configure your eSigning workflow to match the DPSA approval chain and compliance requirements.

Field Configuration
Authentication Method Email link, SMS code, or two-factor
Signing Order Sequential or parallel signer order
Reminder Schedule Custom reminders and escalation cadence
Retention Policy Automatic archive and access controls

Technical Considerations for eSigning and eSubmission

Select a platform that supports required authentication, audit trails, and file formats for legal defensibility.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • Supported Formats: PDF, DOCX, HTML
  • Authentication: Email, SMS, KBA, SSO

Ensure the chosen solution can generate a tamper-evident Audit Trail, export ISO-compatible signed PDFs, and meet any industry-specific compliance such as HIPAA BAAs or 21 CFR Part 11 requirements.

Typical Electronic Execution Flow for a DPSA

A clear digital flow reduces signer friction and documents chain of custody for legal purposes.

  • Upload Document: Import final DPSA into the signing platform.
  • Place Fields: Add signature, date, and initial fields where required.
  • Select Signers: Assign roles and set signing order.
  • Record Audit Trail: Capture timestamps, IPs, and authentication events.

Essential Clauses and Structural Elements to Include

A professional DPSA combines operational detail with legal protections so both parties understand duties and risks.

Parties

Identify controller and processor by legal name, address, and authorized signatory to avoid ambiguity in enforcement or invoicing.

Processing Purpose

Describe specific processing activities, data categories, and permitted uses to limit scope and reduce compliance exposure.

Security Measures

Enumerate technical and organizational measures such as encryption, access controls, logging, and vulnerability management procedures.

Subprocessors

Require prior notice or approval for subprocessors and mandate flow-down of DPSA terms to subcontractors to maintain contractual protections.

Breach Notification

Set maximum notification windows, required content of notices, and cooperation obligations for incident response and regulatory reporting.

Liability & Indemnity

Allocate risk with clear limits, carve-outs for gross negligence or willful misconduct, and insurance requirements to ensure recoverability.

Security and Compliance Essentials to Record in the DPSA

Encryption: TLS 1.2/1.3 in transit
At-rest Protection: AES-256 encryption at rest
Audit Trail: Immutable signing history
Certifications: SOC 2 Type II, ISO 27001
HIPAA Status: BAA required for PHI
eSignature Law: ESIGN and UETA compliant

Common Legal Risks and Potential Penalties

Contract Unenforceable: Ambiguous signer identity
HIPAA Violation: Civil penalties and corrective plans
Data Breach Costs: Notification, remediation, and fines
Tax Withholding: Incorrect TIN triggers backup withholding
I-9 Noncompliance: Penalties per DHS rule
Intentional Misconduct: Higher statutory damages

Frequent Preparation Mistakes to Avoid

  • Failing to define data categories precisely, which leads to broad interpretation and compliance gaps during audits or investigations.
  • Omitting subprocessors or not requiring flow-down obligations, allowing third parties to process data without contractual protections.
  • Using vague security terms like 'industry standard' without measurable controls, which complicates technical verification and enforcement.
  • Neglecting to identify authorized signatories by title, which can create disputes over whether the document was validly executed.

eSignature Pricing and Feature Comparison for DPSA Execution

Compare common vendor price points and a few feature items relevant to executing DPSAs; signNow is listed first per vendor ordering rules.

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 Varies Varies Varies
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real-world Examples of DPSA Use and Outcomes

Organizations across sectors adopt DPSAs to secure data flows and streamline vendor risk management.

Optica Ventures (COO)

Optica standardized vendor DPSAs to reduce review time by centralizing clauses and templates.

  • Implementation simplified procurement workflows.
  • The streamlined approach improved contract consistency and reduced negotiation cycles while ensuring security controls matched company policy and audit requirements.

Martin Properties (Founder)

Martin Properties used electronic DPSA execution to sign vendor agreements remotely.

  • Mobile signing preserved timelines.
  • Processing and executing agreements online helped the company complete transactions without in-person meetings while retaining complete Audit Trails and compliance records for closing files.

Frequently Asked Questions About DPSA Execution and Compliance

Answers to common questions about signing, notarization, electronic validity, and recordkeeping for DPSAs.


Need help? Contact support

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