Loading…
Trust Center
Every binding marketing claim on this site traces to a section of the product requirements. A claim that cannot be traced is an unbacked promise — so this page makes the trace public.
Verassa evidence protocol
Evidence
01Screenshot, DOM, replay, and axe baseline captured before decisions.
Judgment
02Reviewer route, rationale, and owner stay attached to lower-confidence work.
Verification
03Re-scan records and disclaimers travel with reportable outputs.
Traceability matrix
Each row is a marketing surface or claim, the product-requirements section it derives from, and the rule that governs how it may be used.
| Marketing surface or claim | PRD reference | Launch rule |
|---|---|---|
| Allowed / disallowed claim list | §1.1 | Reviewed before launch. |
| "Diagnose. Decide. Remediate. Verify. Improve." hero | §1, §10 | Allowed. |
| Disabled-user accountability framing | §2.3, §3, §24 | Reviewed by a disabled reviewer before public launch. |
| Advisory Board Public Charter page | §3.1, §24.1 | Published, or marked as a pre-paid-launch requirement. |
| Refused Use Cases page | §3.3, §24.3 | Required before external-reliance outputs are sold. |
| Open Evaluation Methodology page | §3.4 | Does not overstate evaluation maturity. |
| Standards Coverage / four profiles | §4.1, §4.2 | Distinguishes Core, Excellence, Legal Baseline, Customer-Selected. |
| Why Scanners Are Not Enough | §5.1 | Bounded language; no exact coverage statistics unless sourced. |
| Why Not Overlays | §3.3, §5.2 | Allowed; fact-checked before launch. |
| Pricing tiers | §27.2 | Reconciled tiers; figures shown as indicative. |
| Methodology — confidence scoring | §13.4, §20.1 | Allowed, with methodology disclosure. |
| Methodology — reproducibility hash | §20.2 | Claimed only because the hash is stored. |
| Methodology — sensitive evidence boundary | §20.7.1 | Public claim tied to logged, enforced routing controls. |
| Trust Center — outcomes accountability | §24.2 | Defines the 90-day fix-rate calculation. |
| Trust Center — anti-laundering posture | §25 | Aligned with dismiss/defer and Defense Pack gates. |
| Free Advocacy tier | §3.4, §27.2 | Allowed. |
| Comparable-to-human-auditor claim | §1.2, §3.4 | Not used until the published evaluation supports it. |
How to read this
The product requirements are the source of truth. Before launch, every homepage claim, pricing statement, and Trust Center assertion is checked against this matrix. A claim that cannot be traced is removed from launch copy or downgraded to roadmap language.
PRD references use the product-requirements section numbers. The dashboard widgets and report outputs have their own traceability rows, kept with the product team.