Establishing secure connection…Loading editor…Preparing document…

Legal Data Processing Instructions

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

LEGAL DATA PROCESSING INSTRUCTIONS

This Legal Data Processing Instructions (the "Instructions") is entered into as of Effective Date: , by and between Controller Name: ("Controller") and Processor Name: ("Processor").

RECITALS

WHEREAS, Controller and Processor are parties to a primary data processing agreement or other master agreement referenced as Agreement Reference: (the "Agreement");

WHEREAS, Controller requires Processor to process Personal Data in accordance with documented instructions and applicable data protection law; and

WHEREAS, the parties desire to set forth the specific operational, technical and organizational instructions for the Processing of Personal Data under the Agreement.

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

1. DEFINITIONS

1.1 For purposes of these Instructions, capitalized terms not otherwise defined herein have the meanings set forth in the Agreement. "Personal Data" means any information relating to an identified or identifiable natural person processed by Processor on behalf of Controller. "Processing" and "Sub-processor" shall be interpreted consistent with applicable data protection law.

2. INSTRUCTIONS FOR PROCESSING

2.1 Processor shall process Personal Data only on documented instructions from Controller, including these Instructions, for the specific purposes set forth in Section 3. Any additional processing not described in these Instructions is prohibited unless Controller provides prior written instructions.

3. PURPOSE AND SCOPE

3.1 Purpose. The Personal Data shall be processed for the following purposes:

4. DURATION

4.1 The Processor shall process Personal Data for the period necessary to achieve the Purpose or until the Agreement is lawfully terminated. Unless otherwise instructed in writing by Controller, Processor will continue processing until termination.

4.2 Optional contract end date (if applicable):

5. SECURITY MEASURES

5.1 Processor shall implement and maintain appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including the measures listed below. Processor shall provide documentation of such measures upon reasonable request.

Encryption at rest

Encryption in transit (TLS or equivalent)

Role-based access controls and least privilege

Audit logging and continuous monitoring

Pseudonymization or tokenization where feasible

6. SUB-PROCESSORS

6.1 Processor shall not engage any Sub-processor without Controller's prior written consent. Controller's consent may be given in writing or by electronic confirmation to the extent permitted by the Agreement.

7. INTERNATIONAL TRANSFERS

7.1 Any international transfer of Personal Data shall be carried out only on the basis of an appropriate transfer mechanism permitted under applicable data protection law.

Standard contractual clauses or equivalent

Binding corporate rules

Adequacy decision or similar lawful basis

8. DATA SUBJECT RIGHTS

8.1 Processor shall promptly notify Controller if it receives a request from a data subject to exercise rights under applicable law and shall not respond to such request except on Controller's documented instructions or as required by law.

9. BREACH NOTIFICATION

9.1 Processor shall notify Controller without undue delay and, where feasible, within hours after becoming aware of a Personal Data breach affecting Controller's Personal Data. Notification shall include details reasonably necessary to enable Controller to meet its obligations under applicable law.

10. RETURN AND DELETION

10.1 Upon termination or expiry of the Agreement, Processor shall, at Controller's choice, return all Personal Data to Controller and delete existing copies, or securely destroy such Personal Data, unless retention is required by applicable law. If retention is required, Processor shall isolate and protect the Personal Data against further processing.

10.2 Controller's instruction on return or deletion (choose one): Return Delete/Destroy

11. AUDIT AND INSPECTION

11.1 Controller or an independent auditor mandated by Controller shall have the right to perform audits and inspections, subject to reasonable notice and confidentiality obligations, to verify Processor's compliance with these Instructions. Processor shall provide reasonable cooperation and access to relevant information.

12. LEGAL OBLIGATIONS

12.1 If Processor is required by law to process Personal Data in a manner inconsistent with Controller's instructions, Processor shall promptly inform Controller of the legal requirement unless prohibited by law from doing so, and shall cooperate with Controller to seek a protective order or other appropriate remedy.

13. LIABILITY

13.1 Each party shall be liable for breaches of this Instruction to the extent provided in the Agreement. Processor shall indemnify Controller for losses resulting from Processor's breach of its obligations under these Instructions, including unauthorized disclosure or loss of Personal Data caused by Processor's failure to implement required measures.

14. GOVERNING LAW

14.1 These Instructions shall be governed by and construed in accordance with the laws of:

15. ENTIRE AGREEMENT; SEVERABILITY; AMENDMENTS; WAIVER; COUNTERPARTS; NOTICES

15.1 Entire Agreement. These Instructions, together with the Agreement, constitute the entire understanding between the parties with respect to the subject matter herein and supersede all prior instructions and agreements with respect to such subject matter.

15.2 Severability. If any provision of these Instructions is held invalid or unenforceable, the remainder shall continue in full force and effect.

15.3 Amendments and Waiver. Any amendment or waiver of any provision of these Instructions must be in writing and signed by both parties. A failure or delay to exercise any right is not a waiver of that right.

15.4 Counterparts. These Instructions 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.

IN WITNESS WHEREOF, the parties have executed these Legal Data Processing Instructions as of the Effective Date set forth above.

Controller:

By:

Date:

Processor:

By:

Date:

Enter text✕

What Legal Data Processing Instructions Cover

Legal Data Processing Instructions are a formal, written set of directions that describe how an organization collects, uses, stores, shares, and disposes of personal or regulated data in the course of a specific matter or workflow. They define roles and responsibilities, authentication and access controls, retention and disposal dates, permitted disclosures, and any contractually required safeguards such as data minimization, encryption, or a Business Associate Agreement for health data. These instructions support compliance with federal frameworks (ESIGN, UETA, HIPAA) and help evidence consistent handling during audits, litigation, or regulatory review.

Why clear processing instructions matter

Clear instructions reduce compliance risk, improve operational consistency, and document decisions needed for audits or legal disputes. They also set expectations for signers and processors, and establish the technical and administrative safeguards required for regulated data.

Why clear processing instructions matter

Which roles commonly prepare or follow these instructions

Coordination among privacy, legal, and operations ensures instructions are enforceable and operationally realistic.

  • Data protection officer or privacy lead: drafts controls and maps processing activities for compliance and audit readiness.
  • Legal counsel or contracts team: tailors clauses to regulatory needs and contract obligations, and confirms retention law alignment.
  • Business unit owners: provide operational detail, approve practical handling steps, and confirm implementation feasibility.

Essential elements to include in professional instructions

A complete set of instructions combines legal, procedural, and technical detail so processors can act reliably and auditors can verify compliance.

Scope

Describe the document and data categories covered, processing purpose, and geographic or temporal limits so obligations are narrowly tailored and enforceable.

Roles

List responsible parties (controller, processor, approver), their contact details, and escalation paths for incidents or disputes.

Data Elements

Enumerate specific fields and sensitivity levels (PII, PHI, financial), noting classification and any special handling rules.

Security Controls

Specify encryption, authentication, access control, logging, retention, and secure disposal methods required for covered data.

Retention

State retention triggers, review intervals, legal bases for retention periods, and secure deletion or archival procedures.

Audit & Evidence

Require audit trails, change logs, and evidence artifacts (signed instructions, access logs, incident reports) to support compliance proofs.

Step-by-step: create and approve the instructions

Follow these sequential steps to draft, approve, and publish enforceable processing instructions.

  • 01
    Gather requirements: Collect purpose, data types, and legal mandates.
  • 02
    Draft instructions: Write scope, roles, controls, and retention.
  • 03
    Legal review: Confirm regulatory citations and contract alignment.
  • 04
    Publish and train: Distribute to stakeholders and document acceptance.

Configure an online workflow for execution

Set up a digital routing workflow that enforces signer order, authentication, and archival requirements.

Field Configuration
Signer order Sequential or parallel per approval needs
Authentication Email link, SMS code, or stronger KBA
Retention capture Enable automatic export to archival storage
Audit trail Record IP, timestamp, and action logs

Where instructions typically travel after approval

Instructions commonly move through legal, IT, and operations before final publication and integration with live systems.

  • Legal review: Confirm statutory citations and contract obligations.
  • Security handoff: IT implements controls and encryption standards.
  • Operations: Apply procedures to daily processing tasks.
  • Record retention: Archive copies to compliant storage locations.

Technical distribution and signing options

Maintain an audit trail and secure storage after distribution to preserve evidentiary value and meet retention rules.

  • Email links: Simple delivery; suitable for low-sensitivity records.
  • Secure portal: Preferred for regulated data and recurring access.
  • eSignature with auth: Use SMS, KBA, or SSO for stronger assurance.

Common timelines and responsiveness expectations

Set clear internal deadlines for issuance, periodic review, and responses to data subject or regulatory requests.

Issue to stakeholders:

Publish within 30 days after final legal sign-off.

Periodic review:

Review annually or when law or process changes.

Data subject requests:

Respond within 30 days for access or deletion demands.

Incident response:

Notify leadership and regulators per policy timelines.

Retention review:

Perform retention audits every 12 months.

Key legal and operational risks of faulty instructions

Incorrect tax reporting: $60–$330 per form (IRC §6721)
I-9 noncompliance: $281–$2,789 per violation (8 CFR §274a.2)
HIPAA violations: Civil fines and corrective action (45 CFR)
Data breach costs: Variable: regulatory fines and remediation
Contract liability: Breach damages and indemnity exposure
Evidence gaps: Missing audit trail weakens defense

Minimum technical safeguards to specify

Transport encryption: TLS 1.2/1.3
At-rest encryption: AES-256
Audit certification: SOC 2 Type II
Privacy standard: HIPAA (BAA required)
Regulatory support: 21 CFR Part 11
Information security: ISO 27001

Electronic signature versus digital (cryptographic) signature

Choose signature type based on legal requirements, non-repudiation needs, and regulatory rules for specific records.

Criteria Electronic Signature Digital Signature
Definition any electronic mark pki-based cryptographic signature
Legal status accepted under esign/ueta accepted; stronger non-repudiation
Typical use contracts, forms fda records, high-assurance filings
Evidence audit trail records certificate chain and hash

Typical vendor pricing and capability snapshot

Compare starting prices and key capabilities across common eSignature providers; signNow appears first for parity in comparison.

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 trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently asked questions about Legal Data Processing Instructions

Answers to common questions about legal validity, signing, retention, and practical implementation of processing instructions.


Need help? Contact support

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