---
title: "Data Retention and Deletion"
description: "Plan how long SignatureAPI keeps your data: store signed documents yourself, delete finished envelopes, and handle a person's request to erase their data."
canonical: "https://signatureapi.com/docs/api/guides/best-practices/data-retention"
source: "https://signatureapi.com/docs/api/guides/best-practices/data-retention.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T17:35:44Z"
---

# Data Retention and Deletion

Plan how long SignatureAPI keeps your data: store signed documents yourself, delete finished envelopes, and handle a person's request to erase their data.

_Last verified against API version 1.18.0._

SignatureAPI keeps every envelope, with its documents, recipients, events and signed files, until you delete it. Nothing expires on its own except temporary uploads. That puts the retention decision in your hands: keep your own copy of what you need, then delete the rest on your schedule.

## What Stays and for How Long

| Data                                           | Kept until                                                                         |
| ---------------------------------------------- | ---------------------------------------------------------------------------------- |
| Envelopes, documents, recipients and events    | You delete the envelope                                                            |
| Signed documents and audit logs (deliverables) | You delete the envelope                                                            |
| Temporary uploads (`POST /v1/uploads`)         | 24 hours after you create them                                                     |
| Stored uploads and Library files               | No expiry: they are permanent                                                      |
| Deliverable download URLs                      | By default, 1 hour after each request; request the deliverable again for a new URL |

Test envelopes follow the same rules as live ones.

## Keep Your Own Copy

Store the signed documents in your own storage when the envelope completes:

1. Wait for the `deliverable.generated` event.
2. Request the [deliverable](https://signatureapi.com/docs/api/resources/deliverables/get) and download its `url` right away, before the link expires.
3. Save the file with your record, together with the envelope `id`.

Your copy is what you keep after you delete the envelope. The audit log in the deliverable records who signed, when, and from where, so keep it with the signed document.

## Delete Finished Envelopes

Delete an envelope with [`DELETE /v1/envelopes/{envelope_id}`](https://signatureapi.com/docs/api/resources/envelopes/delete) once you have what you need:

- Only `completed`, `canceled` and `failed` envelopes can be deleted. Cancel an `in_progress` envelope first.
- The envelope becomes inaccessible through the API at once.
- Support can recover it for 14 days. After that, SignatureAPI permanently removes its documents, signed files and email copies, overwrites the personal data of the envelope and its recipients, and removes its events from webhook delivery history.

A scheduled job works well: once a day, delete envelopes that finished more than your retention period ago and whose documents you have stored.

## Erase One Person's Data

When someone asks you to erase their data, find every envelope they appear in, then delete each one. The API has no search by email address, so track the link yourself:

- Save each envelope `id` next to the person in your database when you create it, or
- Add a [topic](https://signatureapi.com/docs/api/resources/envelopes/topics) with your customer ID, such as `customer_4821`, and list their envelopes with `GET /v1/envelopes?topic=customer_4821`.

An envelope that is still `in_progress` must be canceled before you can delete it. Signed agreements may also be records you are required to keep, so decide with your legal team which envelopes to keep and which to delete.

## Send Less in the First Place

Every field you send is stored with the envelope. Use your own record IDs in `metadata` instead of personal data, and include only the documents the recipients need to sign. See [Security best practices](https://signatureapi.com/docs/api/guides/best-practices/security#personal-data).
