Establishing secure connection…Loading editor…Preparing document…

Data Controller Agreement Template

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

DATA CONTROLLER AGREEMENT

This Data Controller Agreement (the "Agreement") is entered into as of Effective Date: between Controller Name: with principal address: ("Controller") and Other Controller Name: with principal address: ("Other Controller") (each a "Party" and together the "Parties").

RECITALS

WHEREAS, each Party independently determines the purposes and means of processing certain personal data relating to individuals and will act as a data controller in respect of such personal data;

WHEREAS, the Parties intend to set out the terms under which they will process, protect, disclose and otherwise manage personal data that is shared between them in connection with their respective activities;

WHEREAS, the Parties agree to allocate responsibilities for compliance with applicable data protection laws and to record their respective obligations in this Agreement.

NOW, THEREFORE

In consideration of the mutual covenants contained herein and other valuable consideration, the receipt and sufficiency of which are acknowledged, the Parties agree as follows:

1. DEFINITIONS

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 processed by either Party in connection with the activities contemplated by this Agreement. Categories of Personal Data exchanged under this Agreement are:

2. PURPOSE AND SCOPE

The Parties will share and process Personal Data solely for the following documented purposes:

Each Party warrants that it will only process Personal Data in a manner consistent with its role as a controller and in compliance with applicable data protection laws.

3. CONTROLLER RESPONSIBILITIES

Each Party, acting as a controller with respect to the Personal Data it collects and shares, shall:

(a) lawfully collect and process Personal Data only for the purposes set forth in Section 2; (b) maintain appropriate technical and organizational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access; and (c) ensure that any third parties to whom Personal Data is disclosed are bound by written contractual terms sufficient to protect Personal Data consistent with this Agreement.

4. DATA SUBJECT RIGHTS

Each Party shall, to the extent it is the controller with respect to a request, respond to requests from Data Subjects to exercise their rights (access, rectification, erasure, restriction, portability, objection) in accordance with applicable law. The Party receiving a request shall:

(a) notify the other Party of any request that reasonably appears to relate to the other Party's processing within calendar days; and (b) cooperate in good faith to ensure requests are handled within applicable legal timeframes.

5. SECURITY MEASURES

Each Party shall implement and maintain appropriate technical and organizational measures to ensure a level of security appropriate to the risks, including, as appropriate:

The Parties shall review such measures periodically and shall document security incidents and remedial measures.

6. BREACH NOTIFICATION

In the event of a confirmed personal data breach affecting Personal Data exchanged under this Agreement, the Party discovering the breach shall notify the other Party without undue delay and in any event within hours of discovery, providing sufficient details to enable the other Party to meet any obligations to notify supervisory authorities and Data Subjects. The notifying Party shall provide reasonable cooperation and assistance.

7. SUBPROCESSORS AND THIRD PARTIES

Each Party shall not transfer Personal Data to any third party acting as an independent controller without providing prior written notice to the other Party. Use of subprocessors, contractors or other service providers by a Party shall be subject to contractual obligations requiring protection of Personal Data at least as protective as this Agreement.

Authorized subprocessors or third parties (if any):

8. INTERNATIONAL TRANSFERS

Where Personal Data is transferred across national borders, the transferring Party shall ensure that such transfers are lawful and subject to adequate safeguards. Mechanisms to authorize transfers (if required) and the responsible Party are:

9. AUDIT AND COMPLIANCE

Each Party shall, upon reasonable notice, provide the other Party with information necessary to demonstrate compliance with this Agreement and allow for audits or inspections, subject to confidentiality protections and protection of commercially sensitive information. Audit frequency and scope:

10. LIABILITY

Except for liability arising from willful misconduct, gross negligence or breach of confidentiality or data protection obligations, each Party's aggregate liability under or in connection with this Agreement shall be limited to in the aggregate. This limitation shall not apply to liability for death or personal injury resulting from negligence or to other liabilities that cannot be excluded or limited by law.

11. CONFIDENTIALITY

Each Party shall treat Personal Data and any related proprietary information received from the other Party as confidential and shall not disclose such information to any third party except as permitted in this Agreement or required by law. Confidentiality obligations shall survive termination of this Agreement.

12. TERM AND TERMINATION

This Agreement shall commence on the Effective Date and remain in effect for years, unless earlier terminated by either Party for material breach or as otherwise agreed in writing. Upon termination, the Parties shall cease processing the other Party's Personal Data except as necessary to comply with legal obligations.

13. RETURN OR DESTRUCTION

Upon termination or expiration of this Agreement, the receiving Party shall, at the disclosing Party's election, return or permanently delete all Personal Data in its possession and certify in writing that such deletion or return has been completed, except where retention is required by applicable law. Retention exception and rationale (if any):

14. NOTICES

All notices required or permitted under this Agreement shall be in writing and sent to the addresses below:

15. AMENDMENT; WAIVER

No amendment to this Agreement shall be effective unless in writing and signed by authorized representatives of both Parties. No failure or delay by either Party in exercising any right shall operate as a waiver of that right.

16. COUNTERPARTS

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.

17. GOVERNING LAW; SEVERABILITY; ENTIRE AGREEMENT

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction selected by the Parties:

If any provision of this Agreement is held to be invalid or unenforceable, that provision shall be modified to the extent necessary to make it enforceable, and the remaining provisions shall remain in full force and effect. This Agreement constitutes the entire agreement between the Parties regarding the subject matter hereof and supersedes all prior agreements.

EXECUTION

The individuals signing below represent and warrant that they are authorized to execute this Agreement on behalf of their respective Parties.

Controller — Print Name:

By:

Date:

Other Controller — Print Name:

By:

Date:

Enter text✕

What the Data Controller Agreement Template Is

A Data Controller Agreement Template is a standardized contract used when one party (the controller) determines the purposes and means of processing personal data while another party (the processor) carries out processing on the controller’s behalf. The template sets roles, legal bases, security measures, data subject rights handling, subprocessor rules, cross-border transfer mechanisms, and termination steps. In the United States, controllers should ensure clauses align with ESIGN/UETA where electronic execution applies and with sector-specific rules such as HIPAA for health data or FERPA for education records.

Why a Clear Controller Agreement Matters

A well-drafted Data Controller Agreement clarifies responsibilities for compliance, reduces disputes about liability, and documents security expectations for regulators and customers.

Why a Clear Controller Agreement Matters

Who Typically Completes This Template

Use the template to ensure consistent clauses across supplier relationships and to speed legal review while retaining negotiated flexibility.

  • In-house legal teams and privacy officers at mid-size and enterprise companies that handle regulated data.
  • Vendors and cloud providers when they act as processors under a controller’s direction.
  • HR, IT, and procurement teams managing vendor integrations and data-sharing relationships.

Step-by-Step: Completing the Template

Follow these sequential steps to populate, review, and execute a Data Controller Agreement with minimal delay.

  • 01
    Upload Document: Load the template into your e-signature platform or document editor.
  • 02
    Fill Parties: Enter controller and processor legal names, contact details, and addresses.
  • 03
    Update Scope: Define data categories, purposes, retention, and subprocessors clearly.
  • 04
    Obtain Signatures: Execute electronically or via notarization if required; capture audit trail.

Typical Execution Workflow for the Agreement

This sequence shows the common routing from drafting to final storage when using an e-signature-enabled process.

  • Drafting: Legal drafts template with required clauses and variables.
  • Internal Review: Privacy, security, and procurement teams review and approve terms.
  • External Negotiation: Counterparty proposes changes and confirms subprocessors.
  • Execution & Archival: Parties sign electronically and store executed copy with audit trail.

How to Configure an Online Signing Workflow

Set up fields and authentication in your e-signature system to mirror the agreement lifecycle and compliance needs.

Field Configuration
Signer Order Sequential or parallel routing depending on approval needs
Authentication Email link, SMS OTP, or KBA per risk profile
Required Fields Signatures, dates, printed names, and checkboxes for consent
Audit Capture Enable IP, timestamp, and completion certificate retention

Digital Signing and Technical Requirements

Use platform features like conditional fields and audit trails to reduce error rates and produce admissible electronic records.

  • Formats Supported: PDF, DOCX, and flattened PDF/A for long-term storage
  • Integrations: CRM, cloud storage, and ERP connections for automated archiving
  • Security: TLS in transit and AES-256 at rest

Core Clauses to Include in a Professional Template

A complete Data Controller Agreement should combine operational detail with legal protections to allocate risk and ensure regulatory compliance.

Data Scope

Precise description of personal data categories, subject groups, and processing purposes to limit unintended processing.

Roles & Responsibilities

Define controller vs processor duties, incident response obligations, and cooperation in data subject requests.

Security Measures

Detail technical and organizational measures, encryption, access controls, and third-party assessments.

Subprocessors

Rules for prior written consent, notification, and flow-down contractual obligations to subprocessors.

Transfers

Cross-border transfer mechanisms or safeguards and any required contractual clauses.

Termination & Return

Data deletion or return timeline and certification obligations after contract end or breach.

Essential Information and Fields to Capture

Controller Identity: Legal name and address
Processor Identity: Legal name and address
Data Types: Categories of personal data
Processing Purpose: Specific business purpose
Retention Period: Duration or deletion rule
Security Standards: Controls and certifications

Practical Tips for Accurate Completion

Adopt consistent internal practices to reduce negotiation time and compliance risk when issuing controller agreements.

Use a Master Template
Maintain a centrally managed template that legal updates for regulatory changes and ensures uniform clauses.
Pre-Approve Subprocessors
Keep a vetted list of subprocessors to avoid repeated negotiations and speed onboarding.
Standardize Retention
Apply consistent retention rules tied to data categories and legal requirements to simplify records management.
Record Consent
Document any data subject consents and include proof methods in the agreement or associated records.

Common Errors to Avoid

  • Ambiguous scope language that broadens processing beyond intent
  • Missing subprocess or transfer disclosure to downstream vendors
  • Unclear retention periods that conflict with legal obligations
  • Failure to require audit rights or security evidence from processors

Risks and Legal Consequences of Poorly Drafted Agreements

Regulatory Fines: Violations can trigger enforcement and fines
Contract Liability: Breach exposure for unallocated responsibilities
Data Breach Costs: Remediation and notification expenses
Loss of Business: Termination by customers or partners
Tax Penalties: Incorrect reporting or data retention issues
Reputational Harm: Public trust and brand damage

eSignature Vendor Comparison for Signing and Managing the Template

The table compares starting price and basic capability signals across popular eSignature vendors; signNow appears 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 Varied Varied Varied Varied
Bulk Send Yes Varied Varied Varied Varied
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real-World Examples of Use

These brief case summaries show how different organizations apply the template in practice.

Optica Ventures

The company standardized vendor contracts across portfolios to reduce review time

  • Implemented a fixed subprocessor list
  • Resulted in consistent clauses and faster onboarding while preserving legal oversight across entities.

Fertility Centers of Illinois

The clinic added a HIPAA BAA and technical safeguards section

  • Required processor audit evidence annually
  • This ensured regulatory alignment and improved patient data handling confidence with documented controls.

Time-Sensitive Dates and Processing Expectations

Track execution and post-execution deadlines to meet retention, audit, and regulatory notification obligations.

Execution Date:

Use MM/DD/YYYY and record execution timestamp

Breach Notification:

Notify affected parties per contract and law; HIPAA requires prompt notification

Subprocessor Updates:

Notify controller within agreed days when adding subprocessors

Annual Review:

Review security controls and certifications yearly

Record Retention Start:

Retention counts from end of processing or termination

Key Milestones from Draft to Archive

A sequential milestone view helps teams meet approvals, signature, and archival tasks on schedule.

01

Template Approval

Legal finalizes master agreement and variables

02

Internal Sign-off

Privacy and security teams confirm controls

03

External Execution

Counterparty signs and completes authentication steps

04

Archival and Audit

Store executed copy with audit trail and retention metadata

Frequently Asked Questions

Answers to common questions about executing and managing a Data Controller Agreement Template in the U.S. context.


Need help? Contact support

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