Regulated organizations evaluating LandingAI ADE require documented answers across five security domains: how access is controlled, what audit trail exists, how data is isolated between tenants, what deployment isolation options are available, and how the vendor's software development practices are governed.
Identity and Access Management
API Key Management
Every ADE API call is authenticated with an API key.
On the Explore plan, a single API key is provided, and it cannot be deleted or revoked. Explore is designed for testing, prototyping, and hobby use.
On Team and Enterprise plans, organizations can create multiple named API keys scoped to different services, environments, or teams, and revoke them independently. This supports least privilege at the credential layer: a key used by a pipeline processing contracts can be revoked independently of a key used for HR onboarding documents.
Revocation follows role: an Admin can revoke any API key in the organization, while a Developer can revoke only keys they created.
LandingAI's security guidance is not to hard-code API keys in source code. Passing a variable that holds the key, for example from a Secrets Manager, is the recommended pattern.
Organizations, Roles, and Member Management
Access within an organization is governed through member roles. An organization holds your credits, members, API keys, files, and settings.
ADE defines two roles, Developer and Admin. Both can process documents and create API keys. Admins additionally revoke other members' API keys, invite and remove members, change roles, manage billing, and update the organization name.
This structure enforces separation of duties: the team member who configures an extraction schema does not need the same access level as the administrator who manages billing or enables Zero Data Retention.
Single Sign-On
SSO through SAML 2.0 and OpenID Connect is available on Enterprise plans, allowing organizations to enforce existing corporate authentication policies through their identity provider, including multi-factor authentication, session controls, and provisioning and deprovisioning workflows.
An employee whose corporate access is revoked loses access to ADE through the same deprovisioning workflow, eliminating a separate identity silo.
Data Security Infrastructure
Encryption Standards
All document data transmitted to and from ADE is encrypted in transit using TLS 1.2 or higher, and data at rest is encrypted using AES-256. These standards apply uniformly across all ADE deployments and plan tiers. The Security and Compliance page covers the full technical safeguards overview.
Logical Data Segregation
ADE operates as a multi-tenant platform where customer data is logically separated from all other organizations, so no cross-tenant data access is possible. Logical data segregation is a standard condition evaluated in SOC 2 Type II audits.
Zero Data Retention as a Data Governance Control
With the Zero Data Retention option enabled, 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.
- LandingAI does not use your data for training or improving its models.
- ZDR covers the entire platform including all sub-processors, and applies to direct API calls and to the Python and TypeScript libraries.
- A separate setting controls whether ZDR applies to documents uploaded through the Playground.
From a security architecture perspective, ZDR addresses an entire class of risk: with no retention beyond processing, there is no retention period to manage and no deletion workflow to audit.
ZDR is available on the Team and Enterprise plans, in both the US and EU regions, and applies to synchronous requests and asynchronous jobs alike. For the strictest handling of sensitive documents, asynchronous jobs can take the document from a presigned URL in your own storage and write results back to a presigned URL you control.
Backup and Recovery
LandingAI performs regular automated backups and maintains tested disaster recovery procedures for customers not operating under ZDR. Data retention periods under non-ZDR configurations are governed by the terms of the customer's service agreement.
Audit Logging and Monitoring
LandingAI maintains an immutable record of critical user and system activity across the platform, actively monitored by the security team for threat detection and incident investigation.
ADE's output includes grounding that traces each extracted field back to its precise location in the source document. That supports the field-level traceability regulated industries require, alongside the customer's own API request records.
Deployment Isolation Options
ADE is available in two configurations beyond the default multi-tenant SaaS, for organizations whose security requirements cannot be satisfied by a shared cloud platform.
EU Region Deployment
ADE in the EU region runs on AWS EU (Ireland), with all document data stored and processed within the European Union. The EU region supports GDPR compliance and is eligible for ZDR on the Team and Enterprise plans. API keys are region-specific. See the EU documentation for region-specific endpoints and library configuration.
Containerized VPC Deployment
LandingAI offers ADE as a containerized application deployable inside your own Virtual Private Cloud on AWS, Azure, or GCP.
In that 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 sub-processors you integrate. VPC and on-premises deployments are available on Enterprise plans.
Contact LandingAI through the enterprise contact page to initiate this option or to confirm air-gapped deployment support for your specific requirements.
Secure Development Lifecycle
LandingAI incorporates security at every stage of the product development lifecycle, from design and code review through testing and deployment, as documented on the Security and Compliance page.
SOC 2 Type II and HIPAA audits evaluate the processes by which a system is built and how vulnerabilities are managed over time, not only the security of the running system.
Compliance Framework Alignment
LandingAI ADE's security controls map to the compliance frameworks most commonly evaluated in regulated industry procurement reviews, verifiable through the Trust Center.
| Compliance framework | Relevant requirement | LandingAI ADE control |
|---|---|---|
| SOC 2 Type II | Security, availability, confidentiality | Independent third-party audit completed; report available via Trust Center |
| HIPAA | Technical safeguards for PHI | ZDR plus a signed BAA required; TLS 1.2 or higher; AES-256; audit logging; organizational controls |
| GDPR Article 32 | Appropriate technical security measures | Encryption in transit and at rest; logical data segregation; ZDR for storage limitation; SSO; member roles |
| GDPR Article 28 | Data processor obligations | DPA available through enterprise sales; see Trust Center for documentation |
| NIST CSF and ISO 27001 | Access control; audit and accountability | API key management with revocation; member roles; SSO; immutable audit logs; secure development lifecycle |
LandingAI is working toward certification under the EU-U.S. Data Privacy Framework. Verify current status through the Trust Center before finalizing procurement assessments.
FAQ
What evidence does LandingAI provide for a vendor security assessment?
The Trust Center is the primary resource for compliance documentation, including the SOC 2 Type II audit report, certifications, and real-time system status. The Security and Compliance page provides a structured overview of certifications, technical safeguards, and data handling policies.
For additional documentation such as a Data Processing Agreement or Business Associate Agreement, contact LandingAI through the enterprise contact page.
Are audit logs accessible to customers, or only to LandingAI's internal security team?
LandingAI maintains audit logs that its security team actively monitors for threat detection. Customer-facing audit log access is not described in public documentation.
Regulated workflows requiring a comprehensive audit trail should maintain records at the application layer, capturing API request timestamps, document identifiers, and extraction outputs alongside LandingAI's platform-level monitoring. Contact LandingAI support to confirm what audit artifacts are available under enterprise agreements.
Does LandingAI's security posture cover sub-processors, or only the primary platform?
When ZDR is enabled, it covers the entire platform including all sub-processors. Under standard non-ZDR configurations, sub-processor coverage details are available through the Trust Center, which publishes the current subprocessor list.
Is ADE appropriate for workflows that must remain entirely within a customer's own infrastructure?
Yes. ADE is available as a containerized application deployable in a customer-owned VPC on AWS, Azure, or GCP, available on Enterprise plans. In that deployment, ADE maintains zero data retention because it runs on your VPC. Contact LandingAI through the enterprise contact page to confirm air-gapped deployment support and initiate an enterprise agreement.
What plan tier is required to access enterprise security controls?
| Control | Plan required |
|---|---|
| Encryption in transit and at rest | All plans |
| Multiple API keys with revocation | Team and Enterprise |
| Member roles | Team and Enterprise |
| Zero Data Retention | Team and Enterprise |
| HIPAA with a BAA | Team and Enterprise |
| Single Sign-On | Enterprise |
| VPC and on-premises deployment | Enterprise |
The Explore plan provides a single non-revocable API key and does not include ZDR. It is designed for development and prototyping, not regulated production workloads. See Plans & Billing for full plan detail.
Does LandingAI ADE have FedRAMP authorization?
No. LandingAI does not currently hold FedRAMP authorization. Current certifications are documented at the Trust Center.
For federal-adjacent organizations whose requirements are driven by data sensitivity rather than a strict FedRAMP mandate, two ADE controls address the underlying concern. Zero Data Retention means customer data is not persisted beyond processing, eliminating post-processing data exposure. The containerized VPC deployment runs ADE inside your own cloud infrastructure, so no document data transits LandingAI systems at all.
Both are available on Enterprise plans, and VPC deployment requires a separate agreement. Contact LandingAI through the enterprise contact page to evaluate whether these controls satisfy your procurement requirements.