DPA compliance for your signing workflows
By the Sign Docs team · October 3, 2026
When you send a document for signature, you are not just moving a file — you are processing personal data: names, email addresses, signatures, and the contents of the document itself. Data privacy laws like the GDPR in Europe and the Data Privacy Act in the Philippines apply to that processing, and a signing platform sits right in the middle of it.
What the platform does
Sign Docs acts as a processor for the organizations that use it, and as a controller for the account and technical data of its own users. Practically, that means:
A public privacy policy covering collection, use, storage, sharing, retention, and international transfers.
Signer-facing notice on the signing portal, so recipients know how their data is handled before they sign.
Automated redaction of common personal identifiers before content is sent to AI features.
Access controls like secret codes and token-based signer links so only the right people reach the right document.
What the sending organization should do
You remain responsible for the documents you send. Before you start collecting signatures, make sure you have:
A lawful basis for processing the signer's data — consent or contract performance, depending on the document.
A privacy notice or policy of your own covering what you do with the signed documents.
Written agreements with your processors, including your signing platform and any subprocessors it relies on.
A retention plan: keep completed documents only as long as you need them.
Questions about a specific document
Signers should direct questions about a particular request to the organization that sent it — they control that document and its recipients. For questions about the platform itself, our contact channels are listed in the privacy policy.

