Processing Scope
Describe permitted purposes, categories of personal data, affected data subjects, and duration of processing so obligations are narrowly tailored and enforceable.
A well-drafted DPA reduces legal and operational risk by documenting roles, legal bases, and security expectations. It supports regulatory compliance (HIPAA, specific state privacy laws, ESIGN/UETA for execution), enables consistent incident handling, and clarifies liabilities and indemnities between parties.
Organizations that collect, transfer, or process personal data use DPAs: vendors, cloud providers, SaaS platforms, and enterprise legal or privacy teams commonly prepare or request them.
Controllers should ensure authorized signatories execute the DPA and keep a signed copy in procurement and privacy records for evidence of compliance.
Typically a corporate officer or delegated contract manager with binding authority. This person certifies that their organization accepts the processor obligations and can commit to indemnities or limitations of liability.
When present, the DPO reviews data transfer mechanisms, ensures the DPA aligns with privacy policies, and confirms security and breach notification clauses meet regulatory requirements such as HIPAA or state data breach statutes.
Describe permitted purposes, categories of personal data, affected data subjects, and duration of processing so obligations are narrowly tailored and enforceable.
List technical and organizational safeguards, encryption expectations, access controls, and incident detection procedures to align with industry standards.
Require prior notice or approval for subprocessors, mandate flow-down obligations, and preserve audit or inspection rights to verify compliance.
Set maximum notification windows, required content, and cooperation steps for investigation and remediation following a security incident.
Define audit frequency, scope, and format (on-site or remote); specify remediation timelines and handling of audit findings.
Require secure return or destruction of controller data at contract end, including acceptable methods and verification of secure deletion.
| Field | Configuration |
|---|---|
| Signature Block | Require full name, title, and MM/DD/YYYY date field. |
| Authentication | Use email verification or SMS code; consider stronger auth for HIPAA records. |
| Document Versioning | Lock the DPA PDF before sending to preserve the signed text. |
| Audit Trail | Capture IP, timestamp, and signer events for evidentiary support. |
Ensure the chosen eSignature platform supports the authentication, audit trail, and security features required by the DPA and any applicable regulations.
Choose a solution that yields a tamper-evident signed file and stores an auditable certificate of completion to meet ESIGN/UETA evidentiary tests.
MM/DD/YYYY — determines start of processing obligations.
Specify maximum days for notification; common windows are 72 hours or 30 days depending on sector.
Specify lead time for notice or consent before onboarding a subprocessor.
Define notice period for audits, commonly 30 days.
Set timeline for return or deletion after termination, e.g., 30–90 days.
Drafting and redlines between legal teams before signature.
Authorized signatures and recording the effective date.
Periodic security reviews and subprocessor checks.
Trigger data return or secure deletion obligations.
| 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 plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |