> For the complete documentation index, see [llms.txt](https://developer.topazlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.topazlabs.com/resources/zero-data-retention-zdr-policy.md).

# Zero Data Retention (ZDR) Policy

Learn about how Topaz Labs handles ZDR for enterprise customers

**Effective date:** October 16, 2026

### Overview

Zero Data Retention (ZDR) is an optional arrangement that Topaz Labs offers Enterprise API customers on request. With ZDR enabled, Topaz Labs keeps the images and video you submit (inputs) and the enhanced media we return (outputs) only as long as it takes to process and deliver your request. Inputs exist only on the processing worker while your job runs. Outputs are deleted from Topaz Labs cloud storage after a short download window. Beyond that, we keep only the request metadata and account records described below.

One commitment applies to every customer, with or without ZDR: **Topaz Labs never trains its models on customer data.**

{% hint style="info" %}
ZDR is off by default and does not come with any plan automatically. It cannot be turned on in user settings or an administrator portal. Topaz Labs enables it for eligible Enterprise customers once they request it.
{% endhint %}

### Eligibility and How to Request ZDR

ZDR is available to Enterprise API customers that meet the volume and/or contractual requirements Topaz Labs sets. There is no separately published fee. ZDR is arranged as part of an Enterprise agreement, and your account manager will confirm eligibility and terms.

To request ZDR:

1. Contact your Topaz Labs account manager, email <enterprise@topazlabs.com>, or [schedule a meeting](https://www.topazlabs.com/enterprise) with our Enterprise team.
2. Topaz Labs reviews your eligibility and confirms the terms, including a contract addendum if one is needed.
3. Topaz Labs turns on ZDR for the user accounts you specify and confirms in writing when it is active.

**Account level.** ZDR is enabled per user account (user ID). It cannot be enabled for an entire email domain, an individual API key, or a single request. Tell your account manager which user accounts should be included. Requests from accounts that are not enabled for ZDR are not covered.

### What ZDR Covers

With ZDR enabled, your requests work as before, with the same endpoints and parameters. The difference is that your media is deleted as soon as it is no longer needed to process and deliver your request.

| Data                                         | Standard retention                                                   | With ZDR                                                                                                           |
| -------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| Input media (images, video)                  | Stored securely in Topaz Labs cloud storage and deleted after 7 days | Stored in Topaz Labs cloud storage for a short download window that Topaz Labs sets for your account, then deleted |
| Output media                                 | Stored securely and available for download for 7 days, then deleted  | Stored in Topaz Labs cloud storage for a short download window that Topaz Labs sets for your account, then deleted |
| Job history                                  | Retained                                                             | Retained                                                                                                           |
| Request metadata (see below)                 | Retained                                                             | Retained                                                                                                           |
| Service logs                                 | Retained for up to 3 years                                           | Retained for up to 3 years                                                                                         |
| Account, billing, and authentication records | Retained                                                             | Retained                                                                                                           |
| Use of customer data for model training      | Never                                                                | Never                                                                                                              |

#### Request Metadata

Topaz Labs keeps the same request metadata for ZDR customers as for all other API customers, in our own AWS infrastructure. We use it for billing, analytics/metrics, and troubleshooting, and it never includes the content of your images or video. Service logs are retained for up to 3 years. Usage and technical data, such as IP address and device information, is handled as described in our [Privacy Policy](https://www.topazlabs.com/privacy-policy).

#### GPU Processing and Partners

Your media exists on GPU processing workers only while your job runs and is not cached there afterward. ZDR jobs run on the same shared GPU infrastructure as other Topaz Labs traffic. All processing takes place in the United States. Every sub-processor that handles customer data, including our GPU providers, is bound by a data processing agreement and assessed under our third-party management program before it receives customer data. Any temporary handling of media on a GPU provider's infrastructure is also governed by that provider's own data policies. Our current sub-processors are listed in the [Trust Center](https://trust.topazlabs.com/).

### Scope

#### Models

ZDR covers every model available through the Topaz Labs API, for both image and video. No models are excluded. API responses do not indicate ZDR status. Your account manager confirms in writing which accounts have ZDR enabled.

#### Products and Surfaces

| Surface                                                   | ZDR Availability                                       |
| --------------------------------------------------------- | ------------------------------------------------------ |
| Topaz Labs API (Image API and Video API)                  | Available                                              |
| Desktop applications (cloud rendering)                    | Not currently offered                                  |
| Web and browser applications                              | Not currently offered                                  |
| Offline or air-gapped use (Topaz Labs Enterprise Studio)  | Not applicable: no data leaves your workstation        |
| Topaz Labs models accessed through a third-party platform | Not covered: see that provider's data retention policy |

#### ZDR Compared with Fully Offline Use

ZDR covers requests made through the Topaz Labs API. If you need fully offline or air-gapped processing, ZDR does not apply, because your data never leaves your workstation. Offline use is available only to customers with a Topaz Labs Enterprise Studio implementation.

#### Direct Customers Only

Topaz Labs ZDR applies only to direct customers of Topaz Labs. If your organization uses Topaz Labs models through a third party, refer to that party's ZDR policy.

### Default Data Retention

Without ZDR, Topaz Labs keeps media processed through the API and desktop app cloud rendering for up to 7 days to support debugging and customer support, then deletes it automatically. Media uploaded to our web applications is stored in your gallery for the retention period of your subscription plan, or until you delete it or your account is deleted. Enterprise customers who need a different schedule can request a shorter or longer retention period without enabling ZDR.

### Model Training

Topaz Labs never uses customer inputs or outputs to train its models, whether or not ZDR is enabled.

### Human Access to Customer Media

Except as described in Legal and safety exceptions, Topaz Labs staff do not access customer media without your explicit consent. If our support team needs an example to investigate an issue, we will ask you to send it through the secure transfer method you prefer.

### Things to Know Before Enabling ZDR

{% hint style="warning" %}
With ZDR enabled, you cannot access previous requests or earlier versions of jobs in your history. If your organization needs to keep backups for a set period, do not request ZDR.
{% endhint %}

* **Download outputs promptly.** Outputs are deleted at the end of the download window set for your account. Only Topaz Labs can change this window, so ask your account manager if you need a different one.
* **Video API: deliver outputs to your own storage.** You can have Video API outputs written directly to storage you control by providing a signed URL in your request.
* **Image API: download from Topaz Labs.** Image API outputs cannot currently be written directly to customer-owned storage. Download them through the signed URL in the response before the window closes.
* **Usage records remain available.** Your usage and billing records are still available, but they do not include request or response media.

### Account Deletion

You can ask Topaz Labs to delete your account at any time through your account manager, or by emailing <support@topazlabs.com> with the subject line "Data Privacy Request." We respond to valid requests within 30 days. When an Enterprise contract ends, we delete the customer's accounts and data within 60 days. We may keep records that we are required to retain by law, such as billing records.

### Legal and Safety Exceptions

ZDR governs what Topaz Labs stores in the normal course of providing our services. Topaz Labs may preserve or retain information related to a request, including media, where we reasonably believe it is necessary to:

* Comply with applicable law, regulation, court order, subpoena, or other legal process, including a legal hold
* Investigate or prevent fraud, abuse, security incidents, or violations of our Terms of Service
* Respond to illegal content submitted to our services
* Protect the rights, property, or safety of Topaz Labs, our customers, or the public

**Child safety.** Topaz Labs uses automated tools to detect child sexual abuse material (CSAM), including for ZDR accounts. If content is flagged, Topaz Labs may retain that content and related information and report it to the appropriate authorities, as required by law.

**Access to content.** Where required by law, Topaz Labs personnel, or government or law enforcement agencies acting under valid legal authority, may access and review content related to a request, including media. This may occur, for example, in response to a court order, subpoena, or mandatory reporting obligation.

Information kept for these reasons is retained for as long as needed for that purpose or as required by law. Legal holds are set and scoped by Topaz Labs legal counsel and reviewed at least once a year.

### Frequently Asked Questions

<details>

<summary>What is Zero Data Retention?</summary>

It is an account-level arrangement under which Topaz Labs keeps your input and output media only as long as needed to process and deliver your request. We keep only the metadata needed for billing, security, and troubleshooting.

</details>

<details>

<summary>Can I enable ZDR myself?</summary>

No. Topaz Labs enables ZDR after reviewing your request. Contact your account manager or <enterprise@topazlabs.com>.

</details>

<details>

<summary>Does ZDR change how I call the API?</summary>

No. Endpoints and parameters stay the same.

</details>

<details>

<summary>Can outputs go directly to my own storage?</summary>

On the Video API, yes: provide a signed URL for storage you control. On the Image API, not currently. Outputs are available for download from Topaz Labs during a short window.

</details>

<details>

<summary>Which models and products are covered?</summary>

Every model available through the Topaz Labs API. ZDR is available for the API only, not for our desktop or web applications.

</details>

<details>

<summary>Does Topaz Labs train on my data if I don't have ZDR?</summary>

No. Topaz Labs never trains on customer data.

</details>

<details>

<summary>Where can I find Topaz Labs' security policies and certifications?</summary>

On the [Topaz Labs Trust Center](https://trust.topazlabs.com/).

</details>

### Contact

To request ZDR or ask questions about this policy, contact your Topaz Labs account manager or email <enterprise@topazlabs.com>. For more about Topaz Labs' security and privacy practices, visit [trust.topazlabs.com](https://trust.topazlabs.com/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.topazlabs.com/resources/zero-data-retention-zdr-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
