For security reviewers and procurement
What is in place today, and what is not yet.
Government buyers need a technical answer alongside the ethical one. Stewardship covers what we refuse to do. This covers how the platform is built and governed.
We do not claim certifications we do not hold. Items marked on the roadmap are exactly that. A reviewer can request the current overview and we send it with dates attached.
Filter by status.
Eighteen controls. Ten in place, eight on the roadmap. Open any card for what it covers and what a reviewer receives.
Hosting
Managed cloud infrastructure in United States regions, with environment separation between development and production.
Managed cloud, United States regions. Development and production are separated at the account level.
Reviewer receives: hosting overviewEncryption in transit
TLS on every connection to the platform and between services.
TLS 1.2 or higher on every connection to the platform and between internal services.
Reviewer receives: transport configuration summaryEncryption at rest
Storage-layer encryption on all persisted data and backups.
Storage-layer encryption on all persisted data and on every backup.
Reviewer receives: storage encryption statementRole-based access control
Access granted by role and scoped to engagement. Least privilege by default.
Roles scoped to engagement. Access is granted by role, never by person, and reviewed at each wave.
Reviewer receives: access matrixMulti-factor authentication
Required on all administrative and staff accounts.
Required on every administrative and staff account, no exceptions.
Reviewer receives: authentication policyDe-identification
Direct identifiers separated at intake. Outputs release only above a suppression threshold.
Direct identifiers are separated at intake and never travel with the analytic record.
Reviewer receives: de-identification method summarySuppression and aggregation
No individual-level record leaves the platform, to any client, under any contract.
Disclosure and denominator floors run in code. There is no override.
Reviewer receives: threshold statementCommunity review gate
No findings release before the Stewardship Board review window closes.
The Community Data Stewardship Board holds binding authority over release.
Reviewer receives: charter excerptRetention and deletion
Retention set per engagement. Deletion requests executed and confirmed in writing.
Retention set per engagement in the contract. Deletion executed and confirmed in writing.
Reviewer receives: retention scheduleExport
Findings and dashboards exportable in open formats on request.
Findings and dashboards export in open formats on request.
Reviewer receives: export format listAudit logging
Access and action logging with client-visible reporting. In build.
Access and action logging with client-visible reporting. In build.
Target date: stated in the procurement packBackups and disaster recovery
Documented recovery objectives and a tested restore procedure. In build.
Documented recovery objectives and a tested restore procedure. In build.
Target date: stated in the procurement packIncident response plan
Written plan with notification timelines and a named responsible owner. In build.
Written plan with notification timelines and a named responsible owner. In build.
Target date: stated in the procurement packSubprocessor register
Published list of vendors with data access and their review dates. In build.
Published list of vendors with data access and their review dates. In build.
Target date: stated in the procurement packPenetration testing
Independent annual testing with a summary letter available to clients. Planned.
Independent annual testing with a summary letter available to clients. Planned.
Target date: stated in the procurement packSOC 2 Type II
Readiness assessment first, then audit. Planned. We will not claim a certification we do not hold.
Readiness assessment first, then audit. We will not claim a certification we do not hold.
Target date: stated in the procurement packWCAG 2.2 AA
Accessibility conformance review and remediation across the platform and this site. In progress.
Conformance review and remediation across the platform and this site. In progress.
Target date: stated in the procurement packVulnerability disclosure
A published route for researchers to report issues. Planned.
A published route for researchers to report issues. Planned.
Target date: stated in the procurement packFrom a resident's words to a governed finding.
A tool claiming to show the full picture must mark the edges of its own sight.
The same honesty applies to the platform underneath it. A roadmap item stated as shipped is a finding nobody can rely on.
Just Society Technologies, on disclosureWho owns what, and what happens at the end.
Who owns it
JST, under a six-line charter anchored in our articles, contracts and investor documents. The charter is the limit on that ownership.
Who can see it
Role-based access inside JST. Aggregate, threshold-cleared findings to each institution at the depth it holds. Never individual records.
Do you train on it
No model is trained for resale or for any client other than the place the data came from.
What you keep
Your findings, your dashboards and your trained research cohort stay with you.
Deletion and export
Export on request in open formats. Deletion requests executed and confirmed in writing.
Who can stop a use
The Stewardship Board holds binding authority over the red lines and can roll back any output that drifts.
Built to standards reviewers already know: the data sovereignty framing of the World Bank's World Development Report 2021, the OECD dimensions of statistical quality and the disaggregation requirements of SDG Target 17.18.
Send this to your reviewer.
We provide the security overview, data governance summary and accessibility statement without a briefing first.
Request the procurement pack