How the data is kept.
An institution's disclosures are the sensitive part of this product. The design answer is separation: each institution's records live in their own instance, and nothing crosses between instances but anonymised distributions.
Separation
- Under phase one we operate the pipeline over a backlog you send, and return assessments. Nothing is installed at your end.
- Under phase two your institution has its own deployment with its own store. Your disclosures are never written into a shared table alongside another institution's.
- Under phase three, comparison uses anonymised distributions computed inside each instance. Raw disclosures do not move, and an institution can decline to take part while keeping everything else.
In transit and at rest
The site and the interfaces are served over HTTPS. Backing stores are encrypted at rest by the hosting provider. Database credentials and any API keys are supplied as environment variables and are never committed to the source tree or written into a page.
Access
Access to an institution's instance is limited to the people operating it, is authenticated per person, and is logged. API access uses keys that are stored only as a hash, so a stolen store does not yield a usable key. Every source URL touched by the pipeline is recorded with the time it was read and the status returned, which also makes access to the data auditable.
What we do not do
- We do not sell, share or publish raw disclosures.
- We do not train anything on one institution's disclosures for the benefit of another.
- We do not keep an individual assessment beyond 30 days.
Retention and deletion
An institution can ask for its data to be exported or deleted at any time, and at the end of an agreement the instance and its store are deleted. Backups roll off on a fixed schedule, so a deletion completes when the last backup containing it expires; the schedule is stated in the agreement.
Reporting a weakness
If you find a security problem in this site or in the service, tell us before telling anyone else, and give us a reasonable period to fix it. Use the contact form and say that it is a security report. We will confirm receipt, keep you informed, and credit you if you want the credit.
Assurance
We hold no third party security certification today, and we say so rather than implying one. An institution that needs a security review before a pilot should ask for it through the contact form, and we will complete its questionnaire honestly, including the parts where the answer is that a control does not exist yet.