Scope of Processing
Describe processing activities in detail: purposes, data categories, duration, and any prohibited uses. Clear scope prevents unintended data use and supports audits and compliance reviews.
A clear DPA reduces regulatory risk, allocates liability, and documents technical and organizational safeguards. It supports compliance with ESIGN/UETA for electronic execution and helps satisfy industry-specific rules such as HIPAA when a BAA is required.
Organizations and vendors use DPAs to formalize how data is processed and disclosed before operations begin.
Getting the right signatories ensures the agreement is enforceable and aligns operational practices with contractual commitments.
Usually a senior legal or compliance officer signs for the controller. They confirm lawful bases for processing, set data subject rights handling, and accept liability allocation terms.
A vendor executive or authorized contract signatory signs for processors. They commit to implementing agreed security measures, restrict subprocessors, and cooperate with audits and breach notifications.
Describe processing activities in detail: purposes, data categories, duration, and any prohibited uses. Clear scope prevents unintended data use and supports audits and compliance reviews.
List categories of personal data (identifiers, financial, health, contact) and any special categories. Explicit lists reduce ambiguity about what protections apply.
Enumerate technical and organizational measures, encryption standards, access control policies, vulnerability management, and incident response timelines to demonstrate measurable safeguards.
Require processor notification before adding subprocessors, allow reasonable objection, and mandate flow-down contractual terms to ensure consistent protection.
Specify audit rights, frequency, acceptable evidence (reports or onsite), and remediation timelines for noncompliance, including access to SOC 2/ISO reports where applicable.
Define how requests (access, deletion, portability) are handled, timeframes for processor cooperation, and responsibilities for costs and communications.
| Workflow Field | Configuration |
|---|---|
| Signature Order | Sequential | Signer order enforced |
| Authentication | Email + SMS code | Optional KBA |
| Audit Evidence | Enable detailed audit trail |
| Storage Location | Specify encrypted cloud region |
Choose a platform that supports required integrations, secure storage, and the document formats you use.
Confirm the platform preserves an immutable audit trail, supports the authentication level you need, and allows export to ISO-compatible signed PDFs for long-term evidence and legal defensibility.
Execute the DPA before any personal data transfer or processing begins.
Provide at least 30 days notice before adding a new subprocessor.
Notify controller within 72 hours of becoming aware of a breach (or earlier if required).
Acknowledge and respond to requests within 30 days, extend per law if necessary.
Conduct an annual review of security measures and contract terms.
| Criteria | DPA | Standard Vendor Agreement |
|---|---|---|
| Purpose | data handling | general services |
| GDPR/GDPR-like | sometimes | |
| Notarization | not required | not required |
| Typical Duration | term-based | project or term-based |
| 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 | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |