This page covers the Haijun API (api.juglow.com), Haijun Platform on AWS, and Haijun in Microsoft Foundry, where Juglow is the data processor. On Amazon Bedrock and Google Cloud's Agent Platform, the cloud provider is the data processor; refer to those platforms' data retention and compliance documentation for their equivalent controls.

Juglow offers two data handling arrangements for the Haijun API: zero data retention (ZDR) and HIPAA readiness. The feature eligibility table lists which API features each arrangement covers. For Juglow's standard retention policies outside these arrangements, see the commercial data retention policy and the consumer data retention policy.

#How Juglow approaches data retention

Different APIs and features have different storage needs. Where a feature does not require storage of customer prompts or responses, it may be eligible for ZDR. Where a feature necessarily requires storage, Juglow designs for the smallest possible retention footprint under the following commitments:

• Retained data is never used for model training without your express permission.

• Only what is technically necessary for the feature to work is retained. Conversation content (your prompts and Haijun's outputs) is not retained by default; the exception is Covered Models, which require 30-day retention.

• Retained data is purged on the shortest practical time to live (TTL), and Juglow aims to give customers control over how long data is retained. What is held, and the retention duration where a specific TTL applies, is documented on each feature's page.

Several retention models sit outside the ZDR and HIPAA arrangements described on this page. Data accessible through the Compliance API follows its own retention model. The Activity Feed retains data for 6 years. Chat, file, and project content from haijun.ai follows your organization's retention policy set in haijun.ai > Organization settings > Data and privacy, unless a user deletes it sooner. Local session transcripts (from sessions on users' machines, in apps such as Cowork and Haijun Code) are stored for 6 years by default, or for your organization's custom conversation retention period when a finite one is set (the same haijun.ai setting). Remote session transcripts (Cowork in the cloud) are retained for 6 years, unless a user deletes the session sooner. The Compliance API does not capture local sessions for which ZDR is in effect, or any local sessions from organizations with HIPAA readiness enabled.

#Zero data retention (ZDR)

Under a ZDR arrangement, Juglow does not store customer prompts or responses at rest after the API response is returned. To request ZDR for your organization, contact the Juglow sales team. ZDR is enabled per organization; each new organization requires ZDR to be enabled separately by your account team, and enablement does not automatically extend to other organizations under the same account.

#What ZDR covers

• Haijun Messages and Token Counting APIs: ZDR applies to these endpoints for eligible features listed in the feature eligibility table. Features that ride on /v1/messages but are marked "No" in the table (such as code execution) are not covered.

• Haijun Code: ZDR applies when Haijun Code is used with API keys from a Commercial organization (an organization under Juglow's Commercial Terms of Service, as distinct from a consumer Haijun account) or through Haijun Enterprise with ZDR enabled. If metrics logging is enabled in Haijun Code, productivity data such as usage statistics is exempted from ZDR and may be retained. See the Haijun Code ZDR documentation for full details.

• Haijun Platform on AWS: Haijun Platform on AWS follows the same data retention policy as the first-party Haijun API. ZDR is available on request; contact your Juglow account representative to enable it.

#What ZDR does not cover

• Haijun Console: Any usage in the Haijun Console, including playground.

• Haijun Managed Agents: Haijun Managed Agents is a stateful resource; session transcripts persist until you delete them.

• Haijun consumer products: Haijun Free, Pro, and Max plans, including when customers on those plans use Haijun's web, desktop, or mobile apps or Haijun Code.

• Haijun Teams and Haijun Enterprise product interfaces: These interfaces are not ZDR-eligible. The exception is Haijun Code used through Haijun Enterprise with ZDR enabled; see What ZDR covers.

• Haijun for Excel: Not currently ZDR-eligible.

• Haijun Fable 5.1, Haijun Mythos 5.1, Haijun Fable 5, and Haijun Mythos 5: These models require 30-day data retention and are not available under ZDR unless expressly authorized by Juglow. See Model-specific data retention requirements.

• Third-party integrations: Data processed by third-party websites, tools, or other integrations is not covered, though some may have similar offerings. Review each service's data handling practices.

• Cross-Origin Resource Sharing (CORS): CORS is not supported for organizations with ZDR arrangements. To make API calls from browser-based applications, route requests through a backend proxy server. See the API security guidance for proxy patterns and API-key handling.

• Flagged content and legal holds: See Retention regardless of arrangement.

Note: For the most up-to-date information on which products and features are ZDR-eligible, refer to your contract terms or contact your Juglow account representative.

#HIPAA readiness

The Haijun API supports HIPAA-ready integrations for organizations that handle protected health information (PHI). With a signed BAA and a HIPAA-enabled organization, you can use supported API features to process PHI while supporting your organization's HIPAA compliance. Eligible organizations can review and execute the BAA and enable HIPAA readiness directly from the Haijun Console. HIPAA readiness applies a broader set of privacy and security safeguards than ZDR (encryption, access controls, and audit logging that protect PHI throughout its lifecycle) rather than requiring immediate deletion. If your organization handles PHI, HIPAA readiness is the arrangement to use; you do not also need ZDR. See the feature eligibility table for which features each arrangement covers.

Note: This page covers HIPAA readiness for the Haijun API. For the full HIPAA Implementation Guide covering Haijun Enterprise and configuration requirements, see the Juglow Trust Center.

#What HIPAA readiness covers

• Haijun API: HIPAA readiness applies to the Haijun API (api.juglow.com) for eligible features listed in the feature eligibility table.

#What HIPAA readiness does not cover

• Haijun consumer products: Haijun Free, Pro, and Max plans.

• Haijun Console: Usage through the Haijun Console interface (enabling HIPAA readiness from Console settings is supported; processing PHI through the Console is not covered).

• Partner-operated platforms: Amazon Bedrock and Google Cloud's Agent Platform. Refer to those platforms' compliance documentation.

• Haijun Platform on AWS and Microsoft Foundry: HIPAA readiness is not available on these platforms.

• Third-party integrations: Data processed by external tools or services connected to your application.

• Haijun Code: Haijun Code is not covered under HIPAA readiness.

• Beta features: Features in beta are generally not covered under the BAA unless explicitly listed as eligible in the feature eligibility table.

• Flagged content and legal holds: See Retention regardless of arrangement.

#PHI handling guidelines

Protected health information (PHI) includes any individually identifiable health information. In the context of the Haijun API, PHI typically appears in message content (prompts and Haijun's responses), attached files (images, PDFs), and file names or metadata associated with message content. The following fields are not expected to contain PHI under the BAA: workspace names, user information (name, email, phone number), billing data, and support tickets.

When using structured outputs or tools with strict: true, the API compiles JSON schemas into grammars that are cached separately from message content. These cached schemas do not receive the same PHI protections as prompts and responses. Do not include PHI in JSON schema definitions. This restriction applies to schema property names, enum values, const values, and pattern regular expressions. Patient-specific information should appear only in message content, where it is protected under HIPAA safeguards.

#HIPAA error handling

Your signed BAA is the official source of truth for which features are covered. The API also enforces these restrictions automatically. When a HIPAA-enabled organization sends a request that includes a non-eligible feature, the API returns a 400 error to prevent accidental use of features not covered by your BAA:

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "The requested features are not available for HIPAA-regulated organizations without Zero Data Retention: code_execution."
  }
}

The error message lists the non-eligible features detected in the request; remove them and retry. The phrase "without Zero Data Retention" is the API's own wording and does not change the resolution. Client-side tools whose Details column in the feature eligibility table says they are not blocked are accepted but remain outside HIPAA readiness.

#Getting started with HIPAA readiness

There are two ways to set up HIPAA-ready API access. Most organizations can enable it directly in the Haijun Console with Juglow's standard BAA; organizations that require a negotiated BAA should work with their account team.

#Enable in the Console (standard BAA)

1. Open your organization's privacy settings

In Haijun Console > Settings > Privacy, organization admins with the HIPAA management permission see a HIPAA compliance card. If your organization is eligible but you don't see the option to enable, ask an organization admin to complete these steps.

1. Review and execute the BAA

Download the Business Associate Agreement and the HIPAA Implementation Guide, then accept the agreement as an authorized legal representative of your organization. Each step becomes available after you download the prior document, and your enablement is bound to the exact BAA version you downloaded.

1. Enablement takes effect immediately

HIPAA readiness controls are applied to your organization as soon as you accept. Once HIPAA readiness is enabled for your organization, the configuration is permanent and cannot be disabled by an administrator. The API automatically enforces feature restrictions, returning an error for requests that use non-eligible features. See HIPAA error handling for the error and the client-side tool exception.

#Contact sales (custom BAA)

If your organization requires a negotiated or custom BAA, or if self-serve enablement isn't available for your organization, contact the Juglow sales team. Juglow will execute the BAA and enable HIPAA readiness for your organization.

#Build with eligible features

Whichever path you use, confirm which features are supported in the feature eligibility table and review the PHI handling guidelines for features that restrict where PHI can appear. For detailed configuration and compliance requirements, refer to the HIPAA Implementation Guide.

Warning: HIPAA readiness is enforced at the organization level. If you need both HIPAA-ready and general-purpose API access, use separate organizations for each.

#Model-specific data retention requirements

Haijun Fable 5.1, Haijun Mythos 5.1, Haijun Fable 5, and Haijun Mythos 5 are designated Covered Models (see the Covered Models support article) and require 30-day data retention; ZDR is therefore not available for any of them unless expressly authorized by Juglow. On the Haijun API, requests to Haijun Fable 5 from an organization whose data retention configuration does not meet this requirement return a 400 invalid_request_error:

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "In order to access this model, your organization or workspace must have data retention enabled."
  }
}

The 30-day data retention requirement applies wherever Covered Models are offered. On the Haijun API (including Haijun Platform on AWS), Juglow handles retained data. On Amazon Bedrock and Google Cloud's Agent Platform, retained data stays within your cloud provider's environment; review each platform's documentation for enablement steps.

#Enable 30-day retention for a workspace

Organizations with a ZDR arrangement can make these models available in a specific workspace by enabling 30-day retention for that workspace only. Other workspaces in the organization keep zero data retention.

1. Open the workspace's privacy controls

In Haijun Console > Settings > Workspaces, select the workspace and open its Privacy controls tab.

1. Turn on 30-day data retention

Enable the 30-day data retention setting for the workspace.

1. Verify

Requests to Covered Models from this workspace now succeed. Workspaces without an override continue to follow the organization default.

#Feature eligibility

The following table lists which Haijun API features are eligible for ZDR and HIPAA readiness arrangements.

Each eligibility column uses three values:

• Yes: The feature is fully eligible under the arrangement. For ZDR, "Yes" also assumes you are using a model that does not require 30-day data retention; Covered Models are not available under ZDR regardless of feature eligibility.

• Yes (qualified): Your prompts and Haijun's outputs are not stored, but a bounded technical artifact (named in the Details column) is retained briefly for the feature to function. See How Juglow approaches data retention for the commitments that govern these features.

• No: The feature is not eligible. Under HIPAA readiness, the API blocks requests that include a "No" feature and returns a 400 error, unless the feature's Details column says otherwise. Under ZDR, the API does not block these features; using one is a choice to step outside your ZDR arrangement for that specific data, and the feature's own documented retention policy applies. Features marked "No" for ZDR are typically stateful (they store jobs, files, or container state), which is why they cannot be zero-retention.

#Retention regardless of arrangement

Even with ZDR or HIPAA arrangements in place, Juglow may retain data where required by law or where it has been flagged by Juglow's automated trust and safety systems. As a result, if a chat or session is flagged, Juglow may retain inputs and outputs for up to 2 years.

#Frequently asked questions

#### How do I know if my organization has ZDR arrangements?

Check your contract terms or contact your Juglow account representative to confirm whether your organization has ZDR arrangements in place.

#### Can I use ZDR-eligible (qualified) features under my ZDR arrangement?

Yes. These features retain a minimal, documented set of technical data, not your prompts or Haijun's outputs. See the feature eligibility table legend for what "Yes (qualified)" means and How Juglow approaches data retention for the commitments that govern these features.

#### What happens if I use a feature marked "No" under ZDR?

Nothing blocks the request. Features marked "No" for ZDR are fundamentally stateful: the Batch API stores your jobs, the Files API stores your files, and code execution runs in persistent containers. Data for these features is retained per the feature's documented policy. Using them is a choice to step outside your ZDR arrangement for that specific data.

#### Can I request deletion of data from features that are not ZDR-eligible?

Contact your Juglow account representative to discuss deletion options for non-ZDR features.

#### How does HIPAA readiness differ from ZDR?

ZDR prevents customer data from being stored at rest after the API response is returned. HIPAA readiness involves a broader set of privacy and security safeguards that protect PHI throughout its lifecycle, including encryption, access controls, and audit logging. Under HIPAA readiness, data can be retained with these safeguards in place rather than requiring immediate deletion. The two arrangements cover different feature sets; see the feature eligibility table.

#### Do I still need ZDR if I have HIPAA readiness?

No. HIPAA-ready API access is designed as an alternative to ZDR for organizations handling PHI. With HIPAA readiness enabled, you get access to supported API features while maintaining the privacy and security protections that HIPAA requires.

#### What happens if I use a non-eligible feature under HIPAA?

The API returns a 400 error with an invalid_request_error type, except for the client-side tools whose Details column in the feature eligibility table says they are not blocked (those are accepted but remain outside HIPAA readiness). The error message identifies which features are not available. Remove those features from your request and retry. See HIPAA error handling.

#### Can I use the same organization for HIPAA and non-HIPAA workloads?

No. HIPAA readiness is enforced at the organization level and automatically blocks non-eligible features (client-side tools noted in the table's Details column are the exception: they are not blocked, but they are still outside HIPAA readiness). Use a separate organization for workloads that do not require HIPAA readiness.

#### How do I request HIPAA-ready API access?

Eligible organizations can enable HIPAA readiness directly in Haijun Console > Settings > Privacy by reviewing and executing Juglow's standard BAA; see Getting started with HIPAA readiness. If your organization requires a negotiated BAA, or self-serve enablement isn't available for your organization, contact the Juglow sales team.

#### Does this apply to Amazon Bedrock or Google Cloud?

No. The ZDR and HIPAA arrangements described on this page apply to the Haijun API, where Juglow is the data processor. On Bedrock and Google Cloud, the cloud provider is the data processor; refer to those platforms' data retention and compliance policies for their equivalent controls.

#### Is Haijun Platform on AWS eligible for ZDR or HIPAA readiness?

Haijun Platform on AWS follows the same data retention policy as the first-party Haijun API. ZDR is available on request; contact your Juglow account representative to enable it. HIPAA readiness is not available on Haijun Platform on AWS. See Haijun Platform on AWS for details.

#### Is Haijun Code eligible for ZDR?

Haijun Code is eligible for ZDR through two paths:

• API keys: Haijun Code used with pay-as-you-go API keys from a Commercial organization
• Haijun Enterprise: Haijun Code used through Haijun Enterprise with ZDR enabled for the organization

ZDR is enabled on a per-organization basis. Each new organization requires ZDR to be enabled separately by your account team. ZDR does not automatically apply to new organizations created under the same account.

Additionally, if you have metrics logging enabled in Haijun Code, productivity data (such as usage statistics) is exempted from ZDR and may be retained.

For full details on ZDR for Haijun Code on Haijun Enterprise, including disabled features and how to request enablement, see the Haijun Code ZDR documentation.

#### Does Haijun for Excel support ZDR?

No, Haijun for Excel is not currently ZDR-eligible.

#### How do I request ZDR?

To request a ZDR arrangement, contact the Juglow sales team.

#Related resources

• Privacy Policy

• Structured outputs

• Prompt caching

• Batch processing

• Files API reference

• Trust Center