DocSpring Data Processing Agreement
Contents
This Data Processing Agreement (DPA) forms part of the DocSpring Terms of Service or another service agreement that incorporates it (Agreement). Its parties are DocSpring, Inc., a Delaware corporation, with the correspondence address 9450 SW Gemini Dr, PMB 95273, Beaverton, Oregon 97008-7105, United States (Provider), and the person or legal entity identified as the customer in the Agreement and associated account or order records (Customer, also referred to below as Data Exporter). It takes effect when the Agreement incorporating this DPA takes effect and applies whenever Provider processes Customer Personal Data on Customer’s behalf. Provider’s privacy contact is support@docspring.com (attention: Privacy).
Acceptance of the Agreement incorporates this DPA without a separate signature. An existing separately executed DPA continues to govern the processing it covers unless the parties amend or replace it in accordance with that agreement. It applies to personal data Provider processes on Customer’s behalf in providing those services. Customer Personal Data means personal data processed by Provider on Customer’s behalf under this DPA. Customer is the controller, or is a processor authorized by the relevant controller to appoint Provider as a subprocessor; the applicable role is determined as described in Schedule 1. Terms such as controller, processor, personal data and processing have the meanings given in Regulation (EU) 2016/679 (GDPR). Applicable Data Protection Laws means the GDPR and other data protection legislation applicable to the processing.
Processing consists of receiving customer-selected document data and templates, generating and storing documents, operating forms and electronic signatures where enabled, delivering results and providing related support, security and recovery functions under Customer’s instructions. The data subjects, data categories, duration, destinations and special-category conditions are described in Schedule 1. Processing for Provider’s independent account, billing and business-administration purposes is outside these processor instructions and is addressed in Provider’s Privacy Policy.
Provider shall ensure that its authorized personnel and any third party or affiliate it appoints to process Customer Personal Data (Subprocessor) comply with the following requirements.
1. Commissioned processing
Process personal data only for the purposes specifically authorized by Data Exporter and only under the documented instructions of Data Exporter. If Provider cannot comply with an instruction, or, if in Provider’s opinion any instruction issued by Data Exporter to Provider is in contravention of Applicable Data Protection Laws, it shall promptly notify Data Exporter. Provider is prohibited from processing personal data for other purposes, including for Provider’s own purposes. If Union or Member State law requires processing beyond Customer’s instructions, Provider shall inform Customer of that legal requirement before processing unless the law prohibits notification on important grounds of public interest.
2. Security of personal data
Implement and maintain appropriate technical and organizational measures to protect Personal Data against (i) unauthorized or unlawful processing and (ii) against accidental loss, damage, destruction, alteration, unauthorized disclosure of, or access to personal data; that, at a minimum, meet the requirements set forth in the measures referred to in Article 32(1) of the EU GDPR.
3. Provider personnel
Take reasonable steps to ensure the reliability of any employee, agent or contractor who may have access to personal data, ensuring in each case that access is strictly limited to those individuals who need to know or access the personal data, as strictly necessary for the provision of the Services, ensuring that all such individuals are subject to confidentiality undertakings or professional or statutory obligations of confidentiality.
4. Personal data breach
Implement and maintain security incident management policies and procedures and notify Data Exporter without undue delay, and in any event within seventy-two (72) hours of becoming aware, of any: (i) breach or suspected breach of security that may have resulted in the compromise of personal data; or (ii) unauthorized (or suspected unauthorized) processing of personal data; Provider shall cooperate with Data Exporter to fully address the matter and comply with all Applicable Data Protection Laws. Provider shall provide all relevant information to Data Exporter, including the following: (i) a description of the nature of the incident; (ii) the name and contact information of a point of contact where additional information may be obtained; and (iii) a description of measures taken or proposed to be taken to remedy the incident, including measures to mitigate negative effects.
5. Data subject rights
If Provider or a Subprocessor receives a request from a Data Subject whose personal data has been provided to it, including a request to directly exercise the Data Subject’s rights, Provider shall promptly inform Data Exporter of such request without responding to that request, allowing Data Exporter to handle these requests unless it has been otherwise authorized to do so by Data Exporter. Provider shall cooperate with Data Exporter as is necessary to respond to such requests.
6. Cooperation with Data Exporter
Provider shall provide reasonable assistance to Data Exporter to facilitate Data Exporter personal data compliance, including keeping and maintaining a record of all processing activities undertaken on behalf of Data Exporter, assisting Data Exporter in carrying out data protection impact assessments, and prior consultations with data privacy authorities, where required by Applicable Data Protection Laws.
7. Audit
Provider shall allow for and contribute to audits, including inspections, by Data Exporter or an auditor mandated by Data Exporter in relation to the processing of personal data by the Provider and shall cooperate with Data Exporter in any investigation of Data Exporter by a governmental or regulatory authority regarding the processing of personal data by the Provider. Data Exporter shall give Provider reasonable notice of any audit or inspection to be conducted and shall make reasonable endeavours to avoid causing any damage or disruption to premises, personnel and business in the course of such an audit or inspection. Such audit or inspection shall not be conducted (i) outside normal business hours, unless the audit or inspection needs to be conducted on an emergency basis and Data Exporter has given notice to Provider; and (ii) no more than once in any calendar year, except for any additional audits or inspections which Data Exporter reasonably considers necessary because of genuine concerns as to Provider's compliance with these terms or which Data Exporter is required to carry out by data privacy authorities and/or Applicable Data Protection Laws. Provider shall make available the information necessary to demonstrate compliance with Article 28 GDPR and this DPA. Audit arrangements shall not prevent an audit required by applicable law or an applicable SCC.
8. Cross-border transfers
The parties shall identify the entities and countries involved in each transfer in Schedule 1. A transfer requiring a Chapter V GDPR mechanism must be covered by an applicable adequacy decision or another lawful safeguard before it occurs. For transfers falling within the scope of Commission Implementing Decision (EU) 2021/914, the standard contractual clauses in its Annex (SCCs) are incorporated without modification, using Module Two where Customer is a controller and Provider is a processor, or Module Three where Customer is a processor and Provider is a subprocessor. The applicable module, options and completed annexes form part of this DPA as set out in Schedule 1. If those SCCs do not cover a particular transfer, the parties must establish another applicable lawful mechanism before that transfer; merely referencing the SCCs does not extend their legal scope. New Zealand’s adequacy decision may cover qualifying transfers to recipients in New Zealand; it does not establish adequacy for Provider’s US entity or other US recipients. Provider shall document any required transfer assessment and supplementary measures and ensure that subprocessors provide appropriate safeguards. In a conflict, applicable SCCs prevail over this DPA and the Agreement.
9. Retention, return and deletion
Provider shall process and retain Customer Personal Data only as necessary for the Services and Customer’s documented lawful instructions. Customer controls submission expiration during the Services. New accounts expire submissions 30 days after processing and combined PDFs one day after processing, and keep submissions with signature requests until Customer deletes them; Customer can change or turn off each setting, and set a different period per template. Accounts created before these settings were introduced in November 2026 have automatic expiration off until Customer turns it on, except that an account whose template defaults expired submissions keeps that period for submissions with and without signature requests. Template expiration defaults to seven days when enabled. Turning expiration on or shortening it also expires records already older than the new period, starting 24 hours after Provider emails the account’s owner. A failed submission is kept for at least 48 hours, even if its period is shorter, so that a retry still has its data, and test submissions are deleted after 30 days. If storage charges stay unpaid for 90 days after live processing pauses, Provider expires the account’s stored documents that are past their included 30 days of storage, after notifying the billing contact.
Expiration deletes the generated documents and preview, submitted data and metadata, webhook data, the submitter’s IP address, browser and location, compiled HTML and submission images. For a submission with signature requests, it also deletes the signature requests, signers’ names, email addresses, answers and signatures, their authentication and event records, related emails, the audit trail and the hash manifest. Provider retains technical details of the submission, such as its identifier, state, template, test or live status, timestamps and document hashes.
For each completed live signing, Provider writes an integrity record containing hashes of the signed document, audit trail and signing events, with account, submission and template identifiers, timestamps, the number of signers and how each one was authenticated, and the kind of record. It contains no signers’ names, email addresses, IP addresses or document contents. Provider retains integrity records for at least 10 years, with no fixed deletion date, including after expiration, account deletion and the end of the Services, so that a copy of a document can still be verified. For the first 10 years they are in storage that cannot be changed or deleted. Test and demo signings have no integrity record. The completion package (the signed document, the audit trail and, through API v2 or webhook version 4, the hash manifest) is Customer’s record, and Customer is responsible for keeping it for as long as Customer needs it.
A deleted template can be restored for 30 days; after that Provider permanently deletes it, or, if it still has submissions, keeps what those submissions need until the account is deleted, such as its name, identifier, field definitions, shared field values, and its expiry and webhook settings. Users removed from an account are permanently deleted after 30 days. Account export archives are deleted after 6 months.