Trust & Evidence
A public diligence surface showing what DataSitr can prove now, what remains outside the current claim boundary, and where reviewers should inspect the evidence.
Latest published snapshot · 2026-04-29T14:40:52ZPublic benchmark gate
Pass
Required suites
12/12
Current scorecard state
unknown
Functional gates
Pass
Trend-history gate
unknown
Current public reference
The current proof boundary covers Saudi-hosted three-lane routing, the published detector benchmark snapshot, the encrypted vault, signed evidence export paths, and guarded deployment with rollback.
This page does not claim regulator approval, third-party certification, blanket HA, automatic failover, or full-vault verification. Those remain separate evidence questions.
If the scorecard stays narrower than broad release readiness, treat that as a governance-evidence limit unless one of the functional gates is failing.
Where review should start
- /benchmark — the current public detector snapshot and claim boundary.
- /status — runtime posture now, not a blanket quality or readiness claim.
- /userguide — operational description of how the product behaves today.
- /legal and /privacy — operator/legal posture and data-handling disclosures.
- /regulators — public regulator-facing surface.
Operational truth notes
- The current public pilot posture treats typed placeholders as the default external-safe transformation mode.
- FF1 structural surrogates exist for supported Saudi structural identifiers when FPE is explicitly enabled, but that mode remains reversible pseudonymization rather than anonymization and is not the default public pilot claim.
- Arabic entity detection uses a configurable local Arabic NER backend with benchmark-gated alternatives.