---
title: "Customer Responsibilities and Compliance Mapping"
description: "See how SignatureAPI features support HIPAA, GDPR, CCPA and SOC 2 programs, where your data goes, and which controls stay with your application."
canonical: "https://signatureapi.com/docs/trust/compliance/customer-responsibilities"
source: "https://signatureapi.com/docs/trust/compliance/customer-responsibilities.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:45:20Z"
---

# 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.

_Last verified against API version 1.18.0._

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](https://signatureapi.com/docs/trust/compliance/soc2) 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**

|  | Status | SignatureAPI's role | Documents |
|---|---|---|---|
| [SOC 2](https://signatureapi.com/docs/trust/compliance/soc2) | SOC 2 Type II compliant, covering all five Trust Services Criteria | Not applicable | Report on request by email to support |
| [HIPAA](https://signatureapi.com/docs/trust/compliance/hipaa) | Supported, with your configuration: secure ceremony links with secondary authentication | Not applicable | Business Associate Agreement on the Standard plan |
| [GDPR (EU and UK)](https://signatureapi.com/docs/trust/compliance/gdpr) | Compliant | Data processor | Data Processing Addendum |
| [CCPA (as amended by the CPRA)](https://signatureapi.com/docs/trust/compliance/ccpa) | Compliant | Service provider | Data Processing Addendum |

- BAAs are not extended to all customers automatically: contact us to start the process.

## Where your data goes

**Where your data goes**

Parts:

- **Your backend** (Your systems): Sends documents and recipient details over HTTPS with your API key.
- **Webhook endpoint** (Your systems): Receives events. You verify each signature.
- **API** (SignatureAPI): Authenticates the API key on every request.
- **Document storage** (SignatureAPI): Holds the documents of an envelope and, once it completes, the signed deliverable with its audit log.
- **Envelope records** (SignatureAPI): Holds the recipients, places and events of an envelope.
- **Signing ceremony** (Your recipients): Opened from the signing email or embedded in your app.
- **Email delivery** (Your recipients): 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

1. **Your backend to the API.** Every request goes over HTTPS and carries your API key in the `X-API-Key` header.
2. **Storage.** The documents of an envelope are stored with it. When the last recipient completes, SignatureAPI generates the [deliverable](https://signatureapi.com/docs/api/resources/deliverables/object): the signed documents and, for the [standard deliverable](https://signatureapi.com/docs/api/resources/deliverables/standard), an audit log.
3. **Recipients.** Recipients sign in a ceremony. By default SignatureAPI emails them the signing link, and an [email code](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-code) can add a second step.
4. **Your endpoint.** SignatureAPI sends [webhook](https://signatureapi.com/docs/api/webhooks) events to your endpoint. You verify each signature.
5. **Deletion.** After you [delete an envelope](https://signatureapi.com/docs/api/resources/envelopes/delete) it is inaccessible through the API at once. It can be recovered by a support request for 14 days, then it is permanently removed.
6. **Retention and location.** The [Data Processing Addendum](https://signatureapi.com/docs/legal/terms/dpa) 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](https://signatureapi.com/docs/api/resources/ceremonies/authentication/email-code) and [multiple authentication methods](https://signatureapi.com/docs/api/resources/ceremonies/authentication/multiple) | HIPAA                      | Require a second factor whenever a signing link travels over email or SMS, so only the intended person reaches the document.                                                                           |
| [Custom authentication](https://signatureapi.com/docs/api/resources/ceremonies/authentication/custom)                                                                                                                               | 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](https://signatureapi.com/docs/dashboard/users)                                                                                                                                                             | HIPAA                      | Give each person the role their job needs and no more. Remove people when they leave.                                                                                                                  |
| [Delete an envelope](https://signatureapi.com/docs/api/resources/envelopes/delete)                                                                                                                                                  | GDPR, CCPA, HIPAA          | Download the deliverable first, store it, then delete the envelope. Decide your own retention period.                                                                                                  |
| [Deliverable verification](https://signatureapi.com/docs/api/resources/deliverables/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](https://signatureapi.com/docs/api/resources/deliverables/standard)                                                                                                                          | Your own records           | Keep the standard deliverable if you need the record of who signed and when. The [simple deliverable](https://signatureapi.com/docs/api/resources/deliverables/simple) leaves out the audit log pages. |
| [Webhook signing secret](https://signatureapi.com/docs/api/guides/how-to/set-up-webhooks)                                                                                                                                           | Your own security controls | Verify every request against the raw body and store the secret as you store any credential.                                                                                                            |
| [Data Processing Addendum](https://signatureapi.com/docs/legal/terms/dpa)                                                                                                                                                           | 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](https://signatureapi.com/docs/trust/compliance/soc2#get-a-copy-of-our-soc-2-type-ii-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](https://signatureapi.com/docs/trust/compliance/hipaa#dont-send-unencrypted-deliverables-via-email).
- **Retention.** SignatureAPI deletes envelopes when you ask. You choose when.
- **Agreements.** A [Business Associate Agreement](https://signatureapi.com/docs/trust/compliance/hipaa#business-associate-agreements-baas) is a separate contract. Request it from support.

## Next steps

- [HIPAA](https://signatureapi.com/docs/trust/compliance/hipaa)
- [GDPR](https://signatureapi.com/docs/trust/compliance/gdpr)
- [California CCPA](https://signatureapi.com/docs/trust/compliance/ccpa)
- [SOC 2](https://signatureapi.com/docs/trust/compliance/soc2)
