Processing in the EU
Processing is designed around European data-location requirements. Processing locations and subprocessors are documented and disclosed.
Document API for legal and compliance products
Extraction infrastructure for
confidential legal documents.
Contracts, case files, and scanned pleadings become structured data through a single API — processed in the EU, deleted after a defined retention period, and backed by contractual documentation for professional-secrecy requirements.
100 pages included · No credit card · Full API access
contract.json
{
"document_type": "contract",
"parties": ["Acme Legal", "Example GmbH"],
"effective_date": "2026-07-01",
"governing_law": "DEU",
"obligations": […]
}
EU processed
API-first
No training
Verifiable compliance
Documentation that holds up in legal and security review.
Product, legal, and information-security stakeholders receive the evidence they need before confidential documents enter a production workflow.
Defined retention periods
Uploaded documents are deleted after processing. Results remain retrievable for no longer than one hour.
Contractual documentation
Data processing agreement, technical and organizational measures, and a confidentiality undertaking for engagement as a contributing service provider under § 203 StGB.
No model training
Documents and extraction results are used for neither training nor improvement of AI models.
These documents support your assessment. They do not replace a legal review of your specific processing activity.
One API, two output modes
From scan to data your product can rely on.
Structured extraction for defined fields, or full-text Markdown for search, retrieval, and downstream analysis.
- Contracts with parties, dates, terms, and obligations
- Scanned PDFs and image-based case files
- Full text with tables and headings in Markdown
- Automatic document-type detection
Structured JSON
Stable schemas for product logic, databases, and automated workflows.
Full-text Markdown
Readable document structure for retrieval, search, and legal AI systems.
Pilot project
Evidence first, commitment second.
A three-week evaluation against your own documents, with defined acceptance criteria and the compliance review running in parallel.
01
Define the use case
Document types, output fields, and measurable acceptance criteria are defined jointly.
02
Evaluate on representative documents
Field accuracy, processing time, and integration effort are measured before production use.
03
Complete the compliance review
Your legal and information-security stakeholders receive the relevant documentation early in the process.
Start with one real document workflow.
We support the assessment of extraction quality, integration effort, and the documentation required for production use.