OPTIMIZED CORE
Trust & security
Product pages describe intended purpose and current product work. They do not by themselves establish that a feature is deployed, independently audited or certified. Discuss the evidence and controls relevant to your intended use with the technical director.
To report a suspected website security issue, email the technical director with a brief description and affected page. Do not include passwords, access tokens or other people’s data. Contact us before conducting tests that could affect the service.
Evidence for the questions that matter.
Evaluate the relevant product and conditions. Request scoped evidence for access, provenance, recovery, human review and offboarding before agreeing a pilot.
- Who can access the information?
- Ask for the product's access boundaries and applicable isolation tests.
- Where does the information come from?
- Agree the sources and inspect a representative source-to-record example.
- What happens when something fails?
- Agree operational ownership and request relevant monitoring and recovery evidence.
- What can we review and take with us?
- Confirm review history, retention, export formats and offboarding within the agreed scope.
Contact the team
JPH van Mastrigt
Founder & Technical Director
Technical direction, architecture discussions and review of product claims and evaluation scope.
j@optimizedcore.tech