Jina Search Foundation API

Jina excludes model training on request content, but retention and broader support or improvement handling remain imprecise.

Plan Scope

Jina AI Search Foundation APIs after Elastic's October 2025 acquisition; current Elastic data terms supersede portions of Jina's legacy legal page.

Prompt Retention

Request data, inputs, prompts, and uploaded content are processed to provide the APIs; no current public per-request retention period was found.

Response Retention

not documented

Ordinary Logging

Operational, diagnostic, and usage metadata may be retained and used in aggregated, anonymized form to operate, secure, and improve the services.

Model Training

Jina's published terms state customer request data, inputs, prompts, and uploaded content are not used to train its models.

Product Improvement

Aggregated and anonymized metadata can be used for service improvement; the terms exclude request content from model training but do not promise that all content is excluded from every support or product-development activity.

Human Or Operator Access

Access is governed by confidentiality, service delivery, security, support, and current Elastic data-processing controls; no operator-blind statement is published.

Subprocessors And Routing

Jina AI is owned by Elastic, and current processing is governed by Elastic's DPA and privacy statement with their subprocessors.

Deletion Controls

Contract termination requires deletion or return of confidential information and data under Jina's published terms, subject to mandatory retention; current self-service per-request deletion is not documented.

Caveat

The acquisition creates a policy-transition risk, and neither legacy Jina terms nor linked Elastic terms publish a Search Foundation request-content retention duration.