Privacy, as the gate operates today.

What this covers

This notice covers the public JATS Verify website and XML packages submitted to the validation workspace. It describes the current pilot operation and may change if the service changes.

Package processing

JATS XML, optional assets ZIP files, baselines, and journal profiles are processed synchronously to produce the requested inspection report or release bundle. The service does not intentionally keep durable copies of submitted package content after the response is completed.

Current request files are held only in the server workspace needed to perform the request and are deleted when that request completes. Do not submit content you are not authorized to process.

No registry verification

Validation makes no external DOI, PMID, ORCID, or other registry calls. Identifier checks are limited to local syntax and checksum checks where applicable. The report marks registry checks as not run.

Operational metadata

Standard hosting, security, and request logs may contain limited operational metadata, such as time, network address, request status, and browser information. This notice does not promise that infrastructure providers retain no logs.

Paid pilots

If a private paid pilot is arranged, payment handling may involve a payment processor. JATS Verify does not ask you to submit payment-card details in the validation workspace. Any processor handling is subject to that processor's own notices.

Questions

For operational questions about this draft or a submitted package, contact [email protected]. We cannot promise a particular regulatory classification, retention outcome outside the current request flow, or suitability for a specific legal regime.