TRUST & METHODOLOGY

A review method built to show its work—and its limits.

Findings link back to the contract. If evidence is missing or unclear, Aletura keeps that uncertainty visible. Here is how analysis and document handling work, and what they cannot guarantee.

The technical ceilings below do not enable uploads. The active deployment’s admission limits apply. Public preview accepts at most 80 PDF pages and three OCR pages, in PDF, DOCX or TXT, in German or English. Demo disables uploads and live analysis.

Structured review

You do not have to know every question before uploading. Aletura combines universal checks across WHAT, MONEY & COMMITMENT, RISK and EXIT with contract-specific checks, kill questions and applicable scenarios.

  • Every defined question receives an explicit state.
  • Objective facts are extracted once and reused across findings, risks and reports.
  • The framework is application configuration, not an improvised hidden prompt.

Full accepted-document analysis

Accepted readable content is extracted locally in full. Aletura rejects a document before analysis when a current acceptance limit is exceeded; it does not intentionally truncate an accepted document to fit a model context.

  • 20 MB and 300 pages per document.
  • 1.5 million extracted characters per document.
  • Comparisons accept 2–3 files, up to 40 MB and 600 pages in total.
  • Additional segment, table, cell and runtime safety limits also apply.

Evidence

Important factual findings retain source references where possible. Evidence identifiers are checked against known document segments, and quotations remain in the source language. Source matching and support checks reduce unsupported findings, but do not independently establish interpretation correctness, legal accuracy or enforceability.

  • A finding can be traced to a passage and page or section.
  • Referenced documents not supplied are marked as not provided.
  • Evidence retrieval is benchmarked separately from model answer quality.

Privacy

Guest use requires no account; guest contracts and analysis reports are not saved. Signed-in users may explicitly save an encrypted masked structured result or, where policy permits, separately choose to retain the original contract with it. Unmasked extracted text and temporary identifier mappings are never saved. Detected personal identifiers are replaced locally before Mistral, and the complete outbound payload passes a privacy guard.

  • Saving is explicit and limited by the account or workspace policy.
  • Optional identifier restoration occurs locally after the response and restored names are not persisted.
  • An explicit save may retain bounded masked Ask Aletura turns and the consumed follow-up count; raw questions and prompts are not saved.
  • Automated masking cannot guarantee that every sensitive value will be detected.

Regional inference

The default Aletura endpoint is Mistral EU regional inference at https://api.eu.mistral.ai. The active deployment configuration must still be verified, and this statement does not establish complete end-to-end EU residency, provider Zero Data Retention or legal compliance.

Languages

EN, DE, FR, IT and RO are configured report-language and benchmark targets. Contracts are reviewed in their original language and evidence remains in the original wording.

  • All five languages are currently not yet validated for full end-to-end quality.
  • Deterministic multilingual benchmarks exist, but live fact extraction and follow-up quality are not yet certified.
  • Other detected languages receive English reports and are likewise not yet validated.

Document text is untrusted data

Uploaded text is JSON-isolated from Aletura’s trusted instructions. Prompt-injection-like language is preserved as evidence and locally flagged; model calls expose no tools and do not follow document URLs.

  • Suspicious output is rejected with one bounded retry before safe failure.
  • Referenced external material is not fetched automatically.
  • Aletura does not claim that prompt injection is solved.

Download rendering, not authentication

PDF downloads render report data submitted by your browser; JSON downloads contain browser-held report data. Neither format proves authenticity, completeness or that Aletura generated the submitted content. Downloads are not signed certificates.

What result states mean

Found

The document supports a finding and the available evidence passed validation.

Not found

The clause or fact was not found after broader document-wide absence validation.

Ambiguous

The wording supports more than one reasonable reading or does not resolve a key detail.

Contradictory

Two or more relevant provisions conflict and the document does not safely resolve them.

Insufficient information

The document, extraction or available external context is not enough to determine an answer.

Verified snapshot

Current public proof snapshot

These are deterministic inventory and corpus denominators, not live-model accuracy claims.

13

versioned review frameworks

Universal, specialist, fallback and kill-question frameworks.

700

globally unique configured questions

Methodology breadth; not all 700 have direct fixture-ID coverage.

39

configured scenarios

Practical failure and exit situations built from validated facts.

69

synthetic benchmark fixture groups

Primary and independently generated corpora remain separately attributable.

7

multilingual benchmark datasets

Five native-language sets, equivalence and red-team data.

Sources: docs/framework-inventory.json, docs/testing/synthetic-benchmark-baseline.json, src/main/resources/language-certification.json.

Important current limitations

Next step

Review your own agreement with the same structure

This public information page sends no contract data to Mistral.

Review a contract