LandingAI ADE's Zero Data Retention (ZDR) option means your data is not persisted beyond processing. This page explains the mechanism, scope, deployment modes, and HIPAA path.
Key Facts at a Glance
Core mechanism: When the ZDR option is enabled for your account, customer data is not persisted beyond processing. Your data is used exclusively to perform the operation you request, such as parsing or extracting a document. Processing begins when LandingAI receives your request and ends when the output is returned to you.
Scope: ZDR applies when calling the ADE APIs directly and when processing documents with the Python and TypeScript libraries. A separate setting controls whether ZDR is applied to the Playground.
Training: LandingAI does not use your data for training or improving its models when ZDR is active.
Availability: ZDR is available to users on the Team and Enterprise plans, in both the US and EU regions.
HIPAA path: The ZDR option provides the necessary technical safeguards to support customers processing Protected Health Information (PHI) and Personally Identifiable Information (PII) in compliance with HIPAA. Two conditions must both be met: ZDR must be enabled, and a signed Business Associate Agreement (BAA) must be in place with LandingAI.
What Zero Data Retention Means in LandingAI ADE
When the ZDR option is enabled for your account, customer data is not persisted beyond processing. Your data is used exclusively to perform the operation you request, such as parsing or extracting a document. Processing begins when LandingAI receives your request and ends when the output is returned to you.
When ZDR is enabled, LandingAI's fully managed SaaS offering ensures zero data retention across the entire platform, including all subprocessors. LandingAI does not use your data for training or improving its models when ZDR is active.
Because ZDR is enabled at the organization level, it applies automatically to every request. Your application submits documents exactly as it otherwise would, using the ADE APIs directly or the Python or TypeScript library. No code changes are required, and the call is identical whether or not ZDR is active. Processing ends when the output is returned to you, and your application holds the only copy of it.
ZDR Deployment Modes
ZDR operates differently depending on how ADE is deployed. Two modes are available.
LandingAI-Hosted ADE
Available in the US and EU. Users on the Team and Enterprise plans can enable ZDR directly in the user interface, with no infrastructure deployment or code change required.
ZDR is controlled by two settings: one that applies it to the ADE APIs and libraries, and a separate setting that applies it to the Playground. It is not available on the Explore (free/pay-as-you-go) plan.
ADE Containerized App in Your VPC
ADE can be deployed within your own Virtual Private Cloud on AWS, Azure, or GCP. In this deployment, ADE maintains zero data retention because it is on your VPC. LandingAI is not responsible for zero data retention related to your infrastructure or any subprocessors you integrate, such as your own LLM API keys. Your organization is responsible for managing these.
Deployment Mode Summary
| Deployment Mode | How ZDR Applies | Who Manages Retention | Plan Availability |
|---|---|---|---|
| LandingAI-hosted ADE (US and EU) | Enabled in Organization Settings | LandingAI, across the entire platform and all subprocessors | Team and Enterprise |
| Containerized app in your VPC (AWS, Azure, GCP) | Inherent, because ADE runs on your VPC | Your organization, including any subprocessors you integrate | Enterprise |
How to Enable ZDR
Users on the Team and Enterprise plans turn ZDR on from the Organization Settings page in the ADE app. A checkbox during activation controls whether ZDR also applies to Playground uploads, and the BAA request form appears on the same page once ZDR is enabled. US users can also enable ZDR when upgrading to a Team plan.
For the current step-by-step instructions, see the Zero Data Retention documentation. To turn ZDR off after enabling it, contact support@landing.ai.
Industry Scenarios Where ZDR Is a Prerequisite
Healthcare
Patient intake forms, lab reports, discharge summaries, and insurance claim forms routinely contain Protected Health Information. If you are a covered entity and intend to process PHI or PII with ADE, LandingAI requires two things: the ZDR option must be enabled, and a signed Business Associate Agreement must be in place. ZDR provides the technical safeguards and the BAA provides the contractual basis, and both are needed before PHI moves through the service.
Financial Services and Fintech
Banks and fintech platforms process identity documents, proof-of-address documents, and financial statements under data minimisation requirements that make third-party storage a problem in itself. Mortgage and loan packets combine personal financial data, tax returns, and income documents in a single file. With ZDR enabled, that data is not persisted beyond processing, and no separate deployment or code change is required to get there.
For plan details and billing, see Plans & Billing.
FAQ
What does Zero Data Retention actually mean for LandingAI ADE?
When the ZDR option is enabled for your account, customer data is not persisted beyond processing. Your data is used exclusively to perform the operation you request, and processing ends when the output is returned to you. LandingAI does not use your data for training or improving its models when ZDR is active.
Which plans include ZDR?
ZDR is available to users on the Team and Enterprise plans, in both the US and EU regions. It is not available on the Explore plan. For plan details, see Plans & Billing.
Does LandingAI ZDR apply to subprocessors or only to LandingAI's own systems?
On the LandingAI-hosted deployment, ZDR covers the entire platform including all subprocessors when it is enabled. On a VPC deployment, LandingAI is not responsible for zero data retention related to your infrastructure or any subprocessors you integrate, such as your own LLM API keys. Your organization is responsible for managing these.
Can ZDR be enabled without changing the API call or SDK code?
Yes. ZDR is enabled at the organization level. Once enabled, it applies when calling the ADE APIs directly and when processing documents with the Python and TypeScript libraries. No code changes are required.
Does ZDR apply to the Playground as well as the APIs?
There are two settings. One applies ZDR to the ADE APIs and libraries. A separate setting controls whether ZDR is applied to the Playground.
What is the difference between ZDR on LandingAI-hosted ADE and a VPC deployment?
On LandingAI-hosted ADE, ZDR is managed by LandingAI and enabled in Organization Settings, covering the entire platform and all subprocessors. On a VPC deployment, ADE maintains zero data retention because it runs on your VPC, and your organization is responsible for retention controls on your infrastructure and on subprocessors you integrate.