Establishing secure connection…Loading editor…Preparing document…

Data Processing Agreement Schedule

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

DATA PROCESSING AGREEMENT SCHEDULE

This Data Processing Agreement Schedule (this Schedule) is entered into as of Effective Date: by and between Controller Name: with principal address: and Processor Name: with principal address: .

RECITALS

WHEREAS, the Controller and the Processor are parties to a written agreement identified as Master Agreement dated (the Agreement), pursuant to which Processor will process certain Personal Data on behalf of Controller; and

WHEREAS, the parties agree that certain processing operations, security obligations, and other terms applicable to the processing of Personal Data shall be set forth in this Schedule in order to ensure compliance with applicable data protection laws and to document the parties' roles and responsibilities.

WHEREAS, the Controller wishes to ensure that the Processor implements appropriate technical and organisational measures and that the Processor shall only process Personal Data in accordance with Controller's documented instructions as set forth herein.

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

1. DEFINITIONS

1.1. In this Schedule, the following terms shall have the meanings set out below: "Personal Data" means any information relating to an identified or identifiable natural person processed by Processor on behalf of Controller under the Agreement; "Processing" has the meaning given in applicable data protection law and includes any operation or set of operations performed on Personal Data; "Data Subject" means the identified or identifiable natural person to whom the Personal Data relates; "Sub-processor" means any Processor engaged by Processor to assist in fulfilling its obligations with respect to the Agreement; "Security Incident" means a confirmed or reasonably suspected breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed.

2. PURPOSE AND SCOPE

2.1. Purpose. Processor shall process Personal Data on behalf of Controller for the purposes described below. Processor shall only process Personal Data for the documented purposes and in accordance with Controller's documented instructions.

3. PROCESSING INSTRUCTIONS AND DETAILS

3.1. Controller's Instructions. Processor shall process Personal Data only on documented instructions from Controller. Any request by Processor to process Personal Data for a purpose other than the documented instructions shall be subject to Controller's prior written instruction.

4. SPECIAL CATEGORIES OF DATA

4.1. Processing of Special Category Data. The parties acknowledge whether the processing involves special categories of personal data or criminal conviction data.

Yes No

5. SUB-PROCESSORS

5.1. Use of Sub-processors. Controller hereby authorises Processor to engage Sub-processors for the processing activities described in this Schedule subject to the following conditions.

5.2. Prior Notice and Approval. Processor shall provide Controller with written notice of any addition or replacement of Sub-processors and shall obtain Controller's prior written objection, which shall not be unreasonably withheld, within a reasonable review period.

Controller provides a standing authorization for Processor to engage Sub-processors subject to Processor's standard contract terms with equivalent data protection obligations.

6. INTERNATIONAL TRANSFERS

6.1. Transfers to Third Countries. Transfer of Personal Data outside the country(ies) where it was collected shall occur only if appropriate safeguards are in place to ensure an adequate level of protection for the rights of Data Subjects.

Standard contractual clauses or substantially equivalent contractual safeguards
Binding corporate rules
Other (specify below)

7. TECHNICAL AND ORGANISATIONAL MEASURES

7.1. Processor shall implement and maintain appropriate technical and organisational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access. Such measures shall be appropriate to the risks presented by the processing and shall include, as appropriate:

Encryption of Personal Data at rest and in transit
Role-based access controls and least privilege
Pseudonymization where appropriate
Audit logging and monitoring
Regular backups and tested restore procedures
Regular vulnerability assessments and penetration testing

8. SECURITY BREACH NOTIFICATION

8.1. Notification Obligation. Processor shall notify Controller without undue delay upon becoming aware of a Security Incident affecting the Controller's Personal Data and shall provide sufficient information to allow Controller to meet any notification obligations to supervisory authorities and Data Subjects.

9. AUDIT AND INSPECTION

9.1. Audit Rights. Controller or an independent auditor appointed by Controller shall have the right, upon reasonable notice and subject to confidentiality obligations, to conduct audits or inspections of Processor's facilities, systems and records to ensure compliance with this Schedule. Such audits shall be conducted during normal business hours and in a manner designed to minimize disruption to Processor's operations.

10. DATA SUBJECT RIGHTS

10.1. Assistance. Processor shall assist Controller, insofar as reasonably possible, by appropriate technical and organisational measures, for the fulfilment of Controller's obligation to respond to requests from Data Subjects to exercise their rights under applicable data protection law.

11. RETURN OR DELETION OF PERSONAL DATA

11.1. At the end of the provision of services related to processing, Processor shall, at Controller's choice, return all Personal Data to Controller and delete existing copies, except to the extent retention is required by applicable law. If retention is required by law, Processor shall isolate and protect the Personal Data and inform Controller of the legal requirement.

Return all Personal Data to Controller
Permanently delete all Personal Data from Processor systems

12. LIABILITY

12.1. Each party's liability arising from or related to Personal Data shall be subject to the limitations and indemnities set forth in the Agreement, provided that nothing in the Agreement shall exclude or limit liability for fraud, wilful misconduct, or liability that cannot be limited by applicable law.

13. GOVERNING LAW; ENTIRE AGREEMENT; SEVERABILITY

13.1. Governing Law. This Schedule shall be governed by and construed in accordance with the law specified in the Agreement or, if no law is specified, the law of the jurisdiction of the Controller.

13.2. Entire Agreement. This Schedule, together with the Agreement, constitutes the complete and exclusive statement of the parties' agreement with respect to the subject matter of this Schedule and supersedes all proposals, representations and prior agreements, whether oral or written.

13.3. Severability. If any provision of this Schedule is held to be invalid or unenforceable, that provision shall be enforced to the maximum extent permitted by applicable law and the remaining provisions shall remain in full force and effect.

14. NOTICES; AMENDMENTS; WAIVER; COUNTERPARTS

14.1. Notices. All notices required or permitted under this Schedule shall be given in writing to the address set out below for each party and shall be effective upon receipt.

14.2. Amendments. Any amendment to this Schedule must be made in writing and signed by authorised representatives of both parties.

14.3. Waiver. No failure or delay by either party to exercise any right under this Schedule shall constitute a waiver of that right.

14.4. Counterparts. This Schedule may be executed in counterparts and facsimile or electronic signatures shall be deemed originals for all purposes.

Controller Printed Name:

By:

Date:

Processor Printed Name:

By:

Date:

Enter text✕

What the Data Processing Agreement Schedule Is

A Data Processing Agreement Schedule (DPAS) is a supplemental document that details how a data processor will handle personal data on behalf of a data controller under a master Data Processing Agreement (DPA). It typically specifies scope of processing, categories of personal data and data subjects, processing purposes, technical and organizational measures, subprocessors, data transfer mechanisms, and retention limits. Organizations use a DPAS to document operational details required by privacy programs, to satisfy contractual obligations, and to demonstrate controls for audits or regulatory review when personal data is processed across systems or jurisdictions.

Why a Schedule Matters for Compliance and Operations

A clear DPAS provides precise, auditable instructions for handling personal data, reduces ambiguity about roles and responsibilities, and supports legal compliance by aligning operational practices with contractual and regulatory requirements such as HIPAA, ESIGN/UETA expectations for electronic records, and privacy frameworks.

Why a Schedule Matters for Compliance and Operations

Who Typically Prepares and Approves the Schedule

The DPAS is usually prepared by legal counsel or privacy/compliance teams and completed with input from IT, security, and the business owner who requires the processing.

  • Privacy/Legal teams draft and verify legal clauses and processor obligations.
  • IT/security specify technical and organizational measures and encryption controls.
  • Business owners define processing purposes, data categories, and retention needs.

Who Signs and Who Executes

Controller Signatory

Chief privacy officer or an authorized company officer signs on behalf of the data controller; signatory must have authority to bind the organization under contract and to specify controller instructions.

Processor Signatory

Authorized representative of the processor—often VP of Legal or Contracts Manager—signs to accept processing terms, subprocessors, and security commitments; processor must retain implementation records.

Essential Elements to Include in the Schedule

A professional DPAS clearly defines processing activities and technical safeguards so both parties and auditors can confirm compliance.

Processing Scope

Detailed description of processing activities, frequency, and geography where data will be processed and stored.

Data Categories

List of personal data types and data subject groups covered by the schedule (e.g., customers, employees).

Subprocessors

Approved subprocessors, purpose for each, and the process for prior notice or consent to add new subprocessors.

Security Measures

Technical and organizational measures including encryption, access control, logging, and breach response timelines.

Data Transfers

Mechanisms for cross-border transfers (e.g., SCCs, adequacy, or other lawful transfer bases).

Retention & Deletion

Retention periods, deletion/return instructions, and proof-of-deletion or certification obligations.

Required Information and Fields at a Glance

Parties: Full legal names
Effective Date: MM/DD/YYYY
Processing Purpose: Purpose summary
Data Types: Personal data categories
Subprocessors: Named vendors
Retention: Retention timeframe

Step-by-Step: Completing the Data Processing Agreement Schedule

Follow these steps in order to assemble, review, and finalize the DPAS with minimal revisions and consistent legal alignment.

  • 01
    Gather Inputs: Collect controller instructions, data inventory, and current processor subprocessors.
  • 02
    Draft Schedule: Populate template fields with precise processing purposes and retention periods.
  • 03
    Security Review: IT/security confirm technical measures (encryption, backups, access controls).
  • 04
    Approve & Sign: Legal and authorized signatories execute the schedule; retain a signed copy for records.

Configure an Online Workflow for the Schedule

When completing a DPAS online, map approvers and configure signing order, authentication, and retention settings to match contractual requirements.

Field Configuration
Signing Order Controller first, processor second
Authentication Email + optional SMS code
Document Type Attach as PDF/A for reproducibility
Retention Settings Enable archival for minimum retention period

Digital Signing and Platform Requirements

Choose a platform that supports secure e-signatures, audit trails, and configurable authentication that meet contractual and legal needs.

  • Formats Supported: PDF, Word DOCX
  • Authentication Options: Email link, SMS code, KBA
  • Integrations: Salesforce, NetSuite, Google Workspace

Where to Send and How Routing Works

Define routing rules and final destinations for signed schedules so parties and downstream systems receive copies automatically.

  • Upload: Upload final DPAS to contract repository and attach to master DPA record.
  • Signers: Add controller and processor signers with role-based order.
  • Notifications: Enable email copies to legal, privacy, and records teams.
  • Storage: Store signed PDF with audit trail in secure repository.

Timelines, Deadlines, and Processing Expectations

Key timing items include signature turnaround, subprocessors notice windows, breach notification deadlines, and retention start/end dates; ensure each has an owner and SLA.

Signature Turnaround:

Allow 7–14 business days for internal approvals

Subprocessor Notice:

Processor provides 10–30 days' notice before onboarding

Breach Notification:

Notify controller within 72 hours of discovery

Data Deletion:

Execute deletion within agreed timeframe after termination

Review Cadence:

Annual review recommended for changes in processing

Key Milestones from Draft to Archival

Track these sequential milestones so the DPAS moves smoothly from draft to signed record and archival.

01

Draft Prepared

Controller/legal compiles processing details and initial terms.

02

Internal Reviews

IT/security and business stakeholders validate technical and operational items.

03

Execution

Authorized signatories complete signatures and platform records.

04

Archival

Signed schedule is stored with audit trail and linked to the master DPA.

Common Risks and Legal Consequences of Errors

Contractual Breach: Damages and termination rights
Regulatory Fines: Privacy law penalties (varies by statute)
Data Loss Exposure: Remediation and notification costs
Invalid Consent: Failed consumer disclosures can void authorizations
Audit Findings: Corrective action plans and oversight
Reputational Harm: Loss of trust and customer harm

Real-World Examples of When a Schedule Is Used

These short case arcs show common scenarios where a DPAS clarifies responsibilities and supports compliance.

Healthcare Provider

A regional clinic onboarding a patient portal vendor documents PHI processing and breach timelines

  • Clinic requires BAA and encryption-at-rest
  • The DPAS clarified obligations, enabled secure integration, and supported audit evidence for regulators.

SaaS Vendor

A software company provides customer data processing across multiple countries

  • Customer requires data transfer mechanisms and subprocessors list
  • The DPAS supplied SCCs and subprocessors disclosures, simplifying contracting and reducing negotiation time.

Practical Tips for Accurate and Efficient Completion

Apply these recommendations to reduce revision cycles and ensure the schedule meets audit expectations.

Use a Standard Template
Start from a vetted template to ensure consistent language and reduce legal review time.
Keep Fields Specific
Avoid generalities in processing activities and retention instructions to speed approval.
Involve Stakeholders Early
Engage IT/security and procurement during drafting to catch operational issues early.
Maintain Version Control
Record amendment history and link signed schedules to the master DPA.

How the DPAS Differs from Related Documents

Compare related contract attachments so you attach the correct document type to the master DPA.

Document Type DPAS DPA BAA
Primary Purpose operational detail contractual obligations hipaa-specific privacy
Contains Subprocessors rarely
Regulatory Focus general privacy contract law hipaa
Typical Signatories controller & processor controller & processor covered entity & business associate

eSignature Vendor Pricing and Feature Snapshot

Comparing entry-level pricing and a few feature markers helps choose an execution platform for signing and storing the DPAS; signNow is listed first for parity with other vendors.

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 offer Varies by offer Varies by offer Varies by offer
Bulk Send Yes (Business Premium+) Yes Yes Yes Limited
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions and Troubleshooting

Answers to common questions about execution, validity, and practical issues when using a Data Processing Agreement Schedule.


Need help? Contact support

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