Trust starts with explainable risk intelligence.
Every score, alert, and recommendation in TierTrace can be traced back to the data that produced it — and overridden by the humans accountable for the decision.
Every number, defensible.
No black-box scores
Every risk score breaks down into the factors that produced it — with each weight visible.
Signal to impact
Each alert shows the originating signal, dependencies, and the operational impact it implies.
Confidence levels
Low confidence is shown as low confidence — never disguised by a precise-looking number.
Data freshness
Every panel surfaces when its data was last refreshed. Stale states are explicit, not hidden.
Human override & review
Operators can override any score, suppress any alert, or escalate any recommendation.
Attested where it counts, honest about the rest.
We publish only what has been attained or is verifiably in progress.
Attained October 2025. Scope: Security, Availability, Confidentiality.
AES-256 at rest. TLS 1.3 in transit.
Primary shards in AWS EU-West-1 (Ireland) and EU-Central-1 (Frankfurt).
Audit logs retained 7 years. Customer data purged within 30 days of contract termination.
Admin, Editor, Viewer, Read-Only Auditor.
SAML 2.0 / Okta integration. MFA mandatory for administrative accounts.
The system flags. Your team acts.
- · Risk scoring
- · Dependency linkage
- · Signal correlation
- · Supplier substitution
- · Purchase-order cancellation
- · Risk mitigation approval
TierTrace may map dependencies, connect signals to materials and SKUs, prepare risk views, and suggest review actions.
TierTrace does not automatically replace suppliers, reroute shipments, approve purchase orders, certify compliance, or guarantee discovery of every hidden dependency.
Human review is required for supplier changes, procurement actions, compliance decisions, and external notifications.
Every override carries a reason code.
Users may manually override risk scores. Every override is logged with a required reason code and timestamp.
Review telemetry · January 2025 — June 2026 · Internal system telemetry and user action logs.
Primarily conflicting supplier-reported data.
Flagged for manual verification when source records conflict.
The system flags for review and takes no autonomous procurement actions.