Privacy-by-design
Private evidence, canonical inputs and sensitive operational details stay outside the public commitment surface by default.
Compliance & Trust
A compliance-oriented view of Loquitur.
Loquitur is designed around privacy-by-design, traceability, replayable verification and evidence lineage so regulated or institutionally reviewed workflows can inspect what was checked without exposing raw sensitive material. This page describes a preview-stage compliance posture, shared as informational context. Formal assurance — legal opinions, audit reports, certifications, KYC/AML processes and production guarantees — is handled separately.
Trust principles
Compliance starts with the shape of the evidence boundary.
Loquitur is designed so reviewers can understand how evidence, policy checks, lineage and commitments relate without assuming that sensitive evidence must be published.
Nothing confidential leaves your systems
The public commitment carries hashes, receipt references, policy identity and lineage context — never raw documents or confidential values. No anchoring is live and nothing is written to any chain today, so this describes the record's design rather than a deployment you can inspect.
Auditability
Structured receipts, reason codes and policy versions give reviewers a clearer trail than informal document exchange.
Traceability
Evidence lineage and supersession context make it easier to understand what changed, when and under which verification scope.
Replayable verification
Checks are shaped so authorized reviewers can reproduce scoped verification outcomes against the relevant evidence package.
Policy checks
Policy identity, versioning and reason-code catalogs make review outcomes easier to govern and compare.
Disclosure boundary
Proofs, not data.
Loquitur separates private evidence from public commitments. The registry model is designed to expose only minimal verification references and status context.
registry disclosure model
The public layer is intentionally smaller than the private evidence layer. The shape of what is omitted matters as much as the shape of what is committed.
Private by default
- Raw evidence and source documents
- Confidential canonical inputs
- Operational records and private bundle material
- Sensitive values unless deliberately disclosed by scope
Public commitment
- Receipt references
- Manifest hashes
- Policy identity and version context
- Verdict, standardized reason codes and lineage pointers
Explicitly not claimed
- No valuation correctness claim.
- No compliance, KYC or AML substitute.
- No production registry or live chain anchoring claim.
- No audit, SOC2, SLA or external assurance claim.
Regulated workflows
Designed to support institutional review without overexposure.
Compliance-oriented teams need evidence lineage, traceability and policy checks to be visible while raw evidence remains controlled.
Support for regulated review processes where evidence must remain controlled.
Institutional-grade workflows that need clear evidence lineage before broader disclosure.
Public-safe commitments for marketplaces, tokenization platforms and partner ecosystems.
Review surfaces for compliance teams, auditors, investors and institutional counterparties.
Compliance discussion
Discuss a compliance-oriented verification workflow.
A useful first conversation can map privacy boundaries, evidence lineage, policy checks and replay requirements before any integration scope is considered.