Compliance
Customer Responsibilities and Compliance Mapping
See how SignatureAPI features support HIPAA, GDPR, CCPA and SOC 2 programs, where your data goes, and which controls stay with your application.
Compliance is shared. SignatureAPI runs the signing service and its controls. Your application decides who receives a signing request, how recipients are identified, how long you keep documents and who on your team can reach them. This page maps SignatureAPI features to the programs on the compliance pages and says what stays with you.
SignatureAPI does not certify your application. It gives you features and contract terms that help you meet your own obligations.
Compliance programs at a glance
Compliance programs and how to get the documents
| Item | Status | SignatureAPI's role | Documents |
|---|---|---|---|
| SOC 2 | SOC 2 Type II compliant, covering all five Trust Services Criteria | Not applicable | Report on request by email to support |
| HIPAA | Supported, with your configuration: secure ceremony links with secondary authentication | Not applicable | Business Associate Agreement on the Standard plan |
| GDPR (EU and UK) | Compliant | Data processor | Data Processing Addendum |
| CCPA (as amended by the CPRA) | Compliant | Service provider | Data Processing Addendum |
BAAs are not extended to all customers automatically: contact us to start the process.
Where your data goes
Asynchronous: SignatureAPI calls your endpoint when something changes.
Diagram as text
Parts
- Your backend: Sends documents and recipient details over HTTPS with your API key.
- Webhook endpoint: Receives events. You verify each signature.
- API: Authenticates the API key on every request.
- Document storage: Holds the documents of an envelope and, once it completes, the signed deliverable with its audit log.
- Envelope records: Holds the recipients, places and events of an envelope.
- Signing ceremony: Opened from the signing email or embedded in your app.
- Email delivery: Sends the signing request, the email code and, unless delivery_type is none, the completed copy to recipients.
Connections
- Your backend to API: HTTPS requests
- API to Document storage: stores documents
- API to Envelope records: creates
- Envelope records to Email delivery: signing request
- Email delivery to Signing ceremony: signing link
- Envelope records to Webhook endpoint: webhooks
- Your backend to the API. Every request goes over HTTPS and carries your API key in the
X-API-Keyheader. - Storage. The documents of an envelope are stored with it. When the last recipient completes, SignatureAPI generates the deliverable: the signed documents and, for the standard deliverable, an audit log.
- Recipients. Recipients sign in a ceremony. By default SignatureAPI emails them the signing link, and an email code can add a second step.
- Your endpoint. SignatureAPI sends webhook events to your endpoint. You verify each signature.
- Deletion. After you delete an envelope it is inaccessible through the API at once. It can be recovered by a support request for 14 days, then it is permanently removed.
- Retention and location. The Data Processing Addendum keeps personal data for the length of your subscription plus 30 days, and states the transfer terms and the list of subprocessors in Schedule 2.
Features that support your program
Each row names a feature, the programs it helps with, and the part you still own.
| Feature | Supports | Your part |
|---|---|---|
| Email code authentication and multiple authentication methods | HIPAA | Require a second factor whenever a signing link travels over email or SMS, so only the intended person reaches the document. |
| Custom authentication | HIPAA | Use it only when you deliver links through your own authenticated portal, and set delivery_type to none so no copy is emailed. |
| Authenticated deliverable URLs | HIPAA | Ask support to enable them. Download deliverables with your API key, and keep that key out of client code. |
| Resource access logging | HIPAA | Ask support to enable it. Review the logs on request as part of your own audit routine. |
| Roles in the Dashboard | HIPAA | Give each person the role their job needs and no more. Remove people when they leave. |
| Delete an envelope | GDPR, CCPA, HIPAA | Download the deliverable first, store it, then delete the envelope. Decide your own retention period. |
| Deliverable verification | HIPAA | Keep the signed PDF in your system. Anyone can verify it later, even after the envelope is deleted. |
| Audit log in the standard deliverable | Your own records | Keep the standard deliverable if you need the record of who signed and when. The simple deliverable leaves out the audit log pages. |
| Webhook signing secret | Your own security controls | Verify every request against the raw body and store the secret as you store any credential. |
| Data Processing Addendum | GDPR, UK GDPR, CCPA | Review it with your privacy team. You are the controller (or business) and SignatureAPI is the processor (or service provider). |
| SOC 2 Type II report | SOC 2 | Request the report and compare its scope with the controls you rely on. |
What stays with you
- Who you send to. You decide recipients and how they are authenticated.
- API keys. Keep live keys on your server and out of client code.
- Delivery of deliverables. Do not send unencrypted deliverables by email when they contain regulated data. See HIPAA.
- Retention. SignatureAPI deletes envelopes when you ask. You choose when.
- Agreements. A Business Associate Agreement is a separate contract. Request it from support.