Public Documentation
Lawie Docs
Trust Centre
A factual map of Lawie’s data, AI, human-control, audit, and procurement boundaries.
Lawie does not claim SOC 2, ISO 27001, EU AI Act conformity, or another certification on this page. Readiness work and design alignment are not certification.
Data governance
- Customer data remains governed by the customer agreement and DPA.
- Roles, tenant boundaries, retention, deletion, exports, and integrations must be configured for the deployment.
- The public subprocessor register lists only verified production processing relationships.
AI assurance
- Citations and evidence links support verification but do not guarantee a correct conclusion.
- Confidence and evidence-strength signals are decision support, not probability or legal certainty.
- Missing or conflicting evidence should produce a limitation, request for more evidence, or human escalation.
Human control
- Consequential decisions and privileged actions require an accountable human owner.
- Approval rules, roles, and escalation paths belong to the customer workflow.
- Feedback and correction records support quality review without transferring professional responsibility to the model.
Audit and evidence
- Audit records should identify actor, tenant, action, time, object, and outcome where the product supports that event.
- Source provenance, workflow history, exports, and evidence packs serve different purposes and should not be treated as interchangeable.
- Evidence availability and retention depend on the enabled product, plan, contract, and tenant settings.
Procurement and assurance requests
Public material is available below. Deployment architecture, data flows, control evidence, pen-test summaries, recovery evidence, RACI records, and questionnaires may contain sensitive information and are shared only through an approved sales or security review under appropriate confidentiality terms.