Identity of Controller
Name and contact details of the data controller, and any joint controllers. This identifies who answers data subject requests and is essential for lawful consent under GDPR; include postal and email contacts.
Using a Legal GDPR Consent Form documents lawful basis for processing, demonstrates informed consent to regulators, and clarifies data subject rights and retention. Proper phrasing reduces compliance risk under GDPR and supports admissible electronic consent under ESIGN and UETA frameworks.
Data controllers, privacy officers, HR staff, and vendors handling EU personal data prepare or request Legal GDPR Consent Forms.
The form is used by organizations of all sizes that collect or transfer EU personal data, including online services and multinational employers.
Name and contact details of the data controller, and any joint controllers. This identifies who answers data subject requests and is essential for lawful consent under GDPR; include postal and email contacts.
Specific, granular description of why data are processed. Ambiguous or overly broad purposes risk invalidating consent; tie each purpose to a lawful basis and limit processing accordingly.
List types collected (identifiers, contact, financial, health, usage) and the sources of those data. Mark any special categories explicitly and explain why such sensitive data are necessary for specified processing.
State retention period or criteria for deletion, and describe international transfers and recipient categories, including safeguards such as standard contractual clauses or adequacy decisions where applicable.
Inform data subjects of access, rectification, erasure, restriction, portability, objection, and complaint rights. Provide contact details for supervisory authority complaints and the internal data protection officer, including escalation steps for unresolved issues.
Capture explicit consent via signature, checkbox with clear wording, or recorded affirmative action. Retain an immutable audit trail (timestamp, IP, authentication) and note storage location to demonstrate attribution, intent, and retrievability.
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS code, or KBA |
| Consumer Disclosure | ESIGN consumer disclosure required for consumer-facing forms |
| Audit Trail | Enable timestamping, IP logging, and downloadable certificate |
| Retention Settings | Set storage location and retention rule per policy |
Ensure the signing platform supports secure authentication, audit trails, and exportable records for compliance purposes.
| 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 | Yes, varies by plan | Yes, varies by plan | Yes, varies by plan | Yes, varies by plan |
| 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 by plan | Varies by plan | Varies by plan |
Retention begins on effective date or when consent given.
Respond within one month under GDPR; extend if complex.
Document date, method, and effects on processing.
Retain audit logs per retention policy to support legal defensibility.
Provide records and evidence within timeframes requested by authority.