§ Trust

Six proofs. One buying decision.

The case for Pleadwright, reduced to six observable facts — and each one links to the artifact behind it.

Every operator-grade claim on this page is one click away from the artifact that backs it. The boundary below is non-negotiable. Dates, versions, and scope stay explicit.

Compare Pleadwright to generic LLM and legacy suites →

№ Capability · § Capability stamps

Ten platform capabilities, documented.

Buyer-diligence claims on /privacy or /methodology map to one capability row below. Each row carries a public evidence envelope — date, version, authority, and strict scope.

№ 01 · Data in transit + at rest
Encryption
Documented
All consumer PII is encrypted at rest (managed Postgres) and in transit (TLS termination managed by our hosting provider).
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 02 · Account verification
Multi-factor authentication
Scoped
Account access is gated by magic-link email verification on signup and password + email verification at session. TOTP and WebAuthn are not configured in this deployment.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 03 · Per-route authorization
Role-based access control
Documented
Every mutating /api/<resource> handler gates on requireAuth() or requireAdmin(); per-row scope is enforced by where: { userId: user.id }.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 04 · Mode-keyed row separation
Tenant isolation
Scoped
No physical Tenant model. Isolation is mode-keyed (creditor-side vs consumer-defense) via per-table identifier columns; no cross-mode read paths in /api handlers or resolvers.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 05 · Time-bounded retention
Data retention
Documented
Capture rows carry expiresAt columns and are swept by scheduled cleanup jobs; matters and provenances are retained for the matter's lifetime.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 06 · Platform-managed snapshot + PITR
Backups
Scoped
Database backups are managed by the hosting provider with continuous WAL and daily snapshot retention; recovery window is bounded by that provider's plan class.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 07 · Reconstructable audit trail
Audit
Documented
Every compliance decision and admin action writes a reconstructable audit row (rule version + policy version + decision hash + actor + timestamp).
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 08 · Founder-mediated response
Incident response
Scoped
No published SLA. Incident intake runs through /work-with-nathan; the security response is founder-mediated and dialed per incident. No third-party SOC or on-call rotation is committed.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 09 · Declared vendor list
Subprocessors
Documented
Hosting provider; Stripe; Polsia email proxy; Polsia AI proxy. The full current list is maintained by the founder and is available at /privacy.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page
№ 10 · No training on customer data
Training data
Documented
Inputs are not used for model training. All AI calls route through the Polsia AI proxy as ephemeral utility calls — no enrichment, no fine-tune, no replay.
Evidence incompleteThe public evidence record is incomplete. This proof does not represent a legal conclusion.
Open supporting page

№ Product proofs · Proof

№ P1 · Proof
Codification
The rules are documented.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof
№ P2 · Proof
Dated coverage matrix
Where Pleadwright will not draft.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof
№ P3 · Proof
Methodology
Decisions are explainable.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof
№ P4 · Proof
Scoped connectors
No-migration integration.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof
№ P5 · Proof
Data-use boundary
Consumer PII is not a feature.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof
№ P6 · Proof
Labor + capacity worksheet
Every delta is computed against your baseline labor.
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Evidence incomplete
Open proof

What we WILL — and WILL NOT — do with consumer PII

We WILL

Read consumer PII from the matter file you uploaded, and only that.
Keep draft and dispatch artifacts in the sandboxed audit vault; do not write them back to a production system of record.
Log every compliance decision with rule version, policy version, and decision hash.
trust.dataUseBoundaryWill.3
trust.dataUseBoundaryWill.4
trust.dataUseBoundaryWill.5
trust.dataUseBoundaryWill.6
trust.dataUseBoundaryWill.7
trust.dataUseBoundaryWill.8
trust.dataUseBoundaryWill.9
trust.dataUseBoundaryWill.10
trust.dataUseBoundaryWill.11

We WILL NOT

Enrich, score, broker, resell, or syndicate consumer PII to any third party.
Train or fine-tune any model — yours, ours, or a third party's — on consumer PII.
Move consumer PII across firm boundaries. Every row stays in the tenant of origin.
trust.dataUseBoundaryWont.3
trust.dataUseBoundaryWont.4
trust.dataUseBoundaryWont.5
trust.dataUseBoundaryWont.6
trust.dataUseBoundaryWont.7
trust.dataUseBoundaryWont.8
trust.dataUseBoundaryWont.9
trust.dataUseBoundaryWont.10
trust.dataUseBoundaryWont.11

JavaScript disabled — full trust envelope below

Every Q0 capability stamp (authority, jurisdiction, coverage, effective date, version, and supersedes), the six legacy proofs, the data-use WILL/WILL NOT boundary, and the page footer meta line are all present in this static view for crawlers and screen readers.

§ Trust

Six proofs. One buying decision.

The case for Pleadwright, reduced to six observable facts — each linked to the artifact behind it.

Every claim on this page is one click away from a public artifact. Status and scope stay explicit; this page is not legal advice or clearance.

Compare Pleadwright to generic LLM and legacy suites →

№ Capability · § Capability evidence

Ten platform capabilities, documented.

Each capability links to a public supporting surface and separates what is shipped from what remains scoped or unavailable.

№ 01 · encryption
encryption
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 02 · mfa
mfa
Scoped
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 03 · rbac
rbac
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 04 · tenant-isolation
tenant isolation
Scoped
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 05 · retention
retention
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 06 · backups
backups
Scoped
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 07 · audit
audit
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 08 · incident-response
incident response
Scoped
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 09 · subprocessors
subprocessors
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page
№ 10 · training-data
training data
Documented
Public capability scope is available from the linked supporting surface.
Public evidence statusThe detailed attribution record is not part of the JS-off public projection. Use the linked supporting page to inspect the observable scope.
Open supporting page

№ Product proofs · Proof

№ P1
Codification
The rules are documented.
Every statute Pleadwright enforces is documented in plain English with its citation, jurisdiction scope, and underlying rule table.
Open proof
№ P2
Dated coverage matrix
Where Pleadwright will not draft.
Every (jurisdiction × statute × matter × exception) cell carries a dated status (verified · pilot · planned · unavailable) and every non-verified row carries the literal "Pleadwright will not X until Y" stop notice.
Open proof
№ P3
Methodology
Decisions are explainable.
Every compliance decision carries rule version, policy version, triggered rule id, and a 64-char hex decision hash.
Open proof
№ P4
Pilot-boundary connectors
Integration stays scoped.
Pilot and sandbox connector surfaces publish their data boundary, permissions model, failure behavior, and testing-evidence log before any production promotion.
Open proof
№ P5
Data-use boundary
Consumer PII is not a feature.
Pilot and sandbox evaluations use synthetic or redacted matter files, keep artifacts in a sandboxed audit vault, and do not write back to a production system of record.
Open proof
№ P6
Labor + capacity worksheet
Every delta is computed against your baseline labor.
Estimate staff minutes, attorney minutes, corrections, blocked risky actions, throughput, turnaround, capacity, and price per matter — against YOUR baseline labor. No invented industry benchmarks; every comparison runs against the buyer-entered baseline. Directional — for pilot economics, not for forecasts.
Open proof

What we WILL — and WILL NOT — do with consumer PII

We WILL

Read consumer PII from the matter file you uploaded, and only that.
Keep draft and dispatch artifacts in the isolated audit vault; production write-back is not evidenced.
Log every compliance decision with rule version, policy version, and decision hash.

We WILL NOT

Enrich, score, broker, resell, or syndicate consumer PII to any third party.
Train or fine-tune any model — yours, ours, or a third party's — on consumer PII.
Move consumer PII across firm boundaries. Every row stays in the tenant of origin.

Near-term updates

Keep the next rule release on your radar.

Leave a work email for release notes and near-term product updates. No broad newsletter — just the next useful change.

Encryption

Multi-factor authentication

Role-based access control

Tenant isolation

Data retention

Backups

Audit

Incident response

Subprocessors

Training data

The rules are documented.

Where Pleadwright will not draft.

Decisions are explainable.

No-migration integration.

Consumer PII is not a feature.

Every delta is computed against your baseline labor.

We WILL

We WILL NOT