§ Data-use boundary

Consumer PII is not a feature.

The WILL / WILL NOT boundary Pleadwright enforces on consumer PII — the same list the /trust six-proofs grid renders.

This surface mirrors the boundary already published on /trust for pilot and sandbox evaluation. The list below is the canonical, founder-maintained list — pending rows read as 'Review pending' on /trust until counsel sign-off lands.

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